yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] rachitshah:
New user here

Sorry to ask

I just rooted my phone and m on stock 5.0.1

Just want to ask should i flash standard 1 or overclock 1

Which 1 is more better?
[Nexus 4 Original Android Development] jolas:
From post #1:

"...Each CPU has different overclock/undervolt ability. Don't get disappointed if the OC build doesn't work for you..."

So, if 100 users say that normal version is better and another 150 users say that the OC version is better, what your decision would be?

It's better for you to test and decide which version fits better your hardware... :)
[Nexus 4 Original Android Development] HdSht:
Download both..flash OC first...see how it's behaving: if you face bootloops, crashes, fcs of apps, then back into recovery and flash normal :). Knowing your cpu binning might help you in deciding. (please do correct me if my english is wrong :D)
[Nexus 4 Original Android Development] icu64:
Made a thread for color scripts for this kernel. Hopefully it'll make sharing the scripts easy because they'll be in the same place

http://xdaforums.com/showthread.php?t=3073546
[Nexus 4 Original Android Development] newb1e:
I have finally decide to unlock and root my nexus just to flash this kernel, only after reading so much praise of it on XDA and reddit ..

It would be great if anyone would answer my few questions ..

1) What Roms it support? ..

2) Will it support CM 12 or 12.1? ..

3) What is the average S.O.T that is increased from the Stock Kernel after flashing it? ..

4) Difference between normal and anykernel zip? ..
[Nexus 4 Original Android Development] HdSht:
By reading page 1 you could easily answer almost all your questions but since I'm here:

1)All and only AOSP roms (no CM based);

2)Read 1;

3)Not exact numbers...people do report 1 to 2 (maybe) sot more than stock;

4)Normal is for stock (factory image), anykernel for every AOSP rom (yes, no CM again).

And since you didn't read first page yes, it has uv, oc, d2w and gamma.

And last, good choice :good:.
[Nexus 4 Original Android Development] rachitshah:
Tested the oc kernal runs smooth and battery has improved a lot.. But 1 problem m having while charging

It shows charing through USB most of times and it charges slowly

Why i am facing this? Any solution
[Nexus 4 Original Android Development] ihancioglu:
IMHO This could be charger/USB cable related not kernel.
[Nexus 4 Original Android Development] HdSht:
Charging from usb was always slow for me...it's not kernel related (at least I can't imagine how could that interfere).
[Nexus 4 Original Android Development] newb1e:
Thanks a million, Yeah your right, i didn't read it full and what ever i read, half of it i didn't understood, My mistake ..

Actually i have come from droid razr m, that has no kernels and other glittering stuff ..

One last question, how to know that which rom is AOSP based? ..
[Nexus 4 Original Android Development] guimendes:
You'll discover which ROM is AOSP in ROM Thread. Almost all devs post the type of their ROMs on the title or the first topic. In general terms, if the ROM is not CM based, then it's AOSP, but this may not be true in all cases.
[Nexus 4 Original Android Development] jer_ying_fd:
What io scheduler do you guys use?
[Nexus 4 Original Android Development] xenyz:
Defaults; I don't think it matters much on phones and flash memory.

To anyone reading this thread, I have a new theory about the 'Sleep of Death'. I'm wondering if any Mirage users experience this or not. I made one change to Mirage kernel (increasing the cpufreq sampling rate) and had a SoD soon after. Do those of you on Mirage's default settings ever have a SoD?
[Nexus 4 Original Android Development] jolas:
Not me.
[Nexus 4 Original Android Development] mrg666:
I got tired of waiting for 5.1 source and uploaded new builds. You can download with the links in the OP.

- backported NEON optimized SHA-256 code from 3.10 AOSP common kernel

- backported an ARM update from mainline kernel

I think the NEON optimized crypto code is important enough for a new build.

Enjoy!
[Nexus 4 Original Android Development] jer_ying_fd:
You made my day, mrg666! :)
[Nexus 4 Original Android Development] :
There is a chance that the kernel will support ever CyanogenMod ?
[Nexus 4 Original Android Development] icu64:
Ever looked into fixing the logcat touchboot spam?
[Nexus 4 Original Android Development] mrg666:
After the discussion here and my response also there, I don't think any other fix is necessary. I recommend deleting the two files in the second post.
[Nexus 4 Original Android Development] icu64:
OK thanks, and I'm really having a hard time figuring out how to make a script for color profiles and where to put them and stuff. I would like to make a thread with scripts for different color profiles for this kernel. This is really the only thing that's keeping me away for the time being because honestly... The only other people that seem to do things that make sense other thank you are Franco (the Dev of saber mod as well), semaphore kernel is pretty nice, and Nash is pretty well made but he changes things a lot. I like the entire set it and forget it idea so it makes me want to use your work.... Just really want to have a good color profile
[Nexus 4 Original Android Development] mrg666:
Did you see this post? Just comment out or delete the other profiles that you don't want if you have more than one color profile in the script.
[Nexus 4 Original Android Development] icu64:
yes I did and I think he was talking to me lol. I tried it and it didn't work but I didn't want to bother him. I assumed I needed to paste that in a normal text file and then remove the extention... the I place it in the init.d folder (forgot where that was) and on next boot itll work?
[Nexus 4 Original Android Development] HiM@L:
i have that as .txt file.. and use rom toolbox to run it as a script....works fine for me.

btw....awesome update. thanks.
[Nexus 4 Original Android Development] icu64:
From what I'm gathering.... The ROM doesn't have init.d support.... Why?
[Nexus 4 Original Android Development] xenyz:
Here it is: the normal kernel installer (boot image) includes init.d support, but the anykernel installer requires the ROM's kernel to have init.d support already, as it doesn't add it.

If you read the last page, I recommend flashing stock, then Semaphore for his touch boost fix, then Mirage anykernel. This will get you init.d support.

To use init.d, you need Busybox installed for the run-parts command. You need a /system/etc/init.d dir with permissions 755 (rwxr-xr-x), and you need a script in this folder, by convention starting with a number, like 01example (so you can run scripts in order).

In this file, you need it to begin with the following:

#!/system/bin/sh

# script goes here

Finally, this file, /system/etc/init.d/01example needs permissions 755 as well to run at boot.

Hope this helps you get it going.
[Nexus 4 Original Android Development] icu64:
I love you lol
[Nexus 4 Original Android Development] icu64:
I wonder if he knows the source code dropped for the kernel.....
[Nexus 4 Original Android Development] jer_ying_fd:
Nvm this
[Nexus 4 Original Android Development] nycelitemaster:
Updated to 5.1, now waiting for mirage update [emoji14]

Sent from my Nexus 4
[Nexus 4 Original Android Development] mrg666:
MiRaGe LMY (Android 5.1) builds are available in the OP.

Changes:

- Lollipop mr1 source sync

- LMY build ramdisk updates from Google

Many changes in the mr1 source release were already in MiRaGe. I just added the missing patches. Looks like everything is working fine to me. Please post if you find any problems.

Cheers!
[Nexus 4 Original Android Development] nycelitemaster:
I installed Normal kernel updated on 4/14, and UV by -100mv myself. Stable as usual :) Cheers

Sent from my Nexus 4
[Nexus 4 Original Android Development] mhejek:
Latest kernel both normal and oc make phone service fc.i tried couple times with clear dalvic
[Nexus 4 Original Android Development] guimendes:
Which ROM are you using? Is the ROM Android 5.1?
[Nexus 4 Original Android Development] jtwebfusion:
The latest LMY standard kennel has been working well on stock 5.1. Thanks!
[Nexus 4 Original Android Development] mrg666:
I haven't seen any problems yet with the stock ROM. Are you using stock ROM? Which kernel package are you using? Please post the kernel messages and give more information if you want me to look at.
[Nexus 4 Original Android Development] mhejek:
Yes.im using stock 5.1.at the time using ur build at 0410.and normal.
[Nexus 4 Original Android Development] zEr0Punk:
Hello all, this is my first kernel I have ever flashed. I've heard a lot of good things about this kernel so I flashed it, the only thing bothering me is that Viper4Android is not working.

Last night I flashed 5.1 stock and installed all my mods, including viper and it was working atm. But when I flashed mirage it dosen't work anymore, I'm using PowerAmp as my music player.

Any help?
[Nexus 4 Original Android Development] mrg666:
I have never been able to use V4A after Android 5. I just gave up with it. We have discussed building a permissive kernel earlier in this thread so that V4A would work. But we have decided against that not to sacrifice security.

It is surprising to hear that the stock 5.1 kernel (not permissive either) is working fine with V4A. I will check this out myself. It would be great if other users can also chime in.
[Nexus 4 Original Android Development] HdSht:
Today's Chroma rom release added sepolicy permissions in order to run Viper4Android.

Give it a try if interested.

Cheers :).
[Nexus 4 Original Android Development] mrg666:
AFAIK, if the kernel is not built permissive, the OS cannot change it.
[Nexus 4 Original Android Development] zEr0Punk:
Decided to flash the Chroma ROM, used SELinux Mode Changer and changed it to Permissive nad V4A works :D

btw: How big of a security flaw are we thinking about?'

EDIT: Didn't saw today's update, downloading as I speak, now with this update V4A can be run in Enforcing mode.
[Nexus 4 Original Android Development] xenyz:
I believe they are making ramdisk changes, so the anykernel format must be used with Chroma. I'm going to try this ROM this weekend, I'll post more info then.
[Nexus 4 Original Android Development] icu64:
How is that true when there are apps that can change it with root permission?
[Nexus 4 Original Android Development] mrg666:
That is only possible if the kernel is permissive. MiRaGe is not ... just like stock kernel. We tried and discussed this before in this thread. You can also try one those apps to check by yourself. Please let us know if you try.
[Nexus 4 Original Android Development] redj12:
Hi guys. I am on Euphiria 5.1 and tried this kernel but can't boot. After Euphoria boot splash, there are apps optimization. In the end of process the phone reboot and start app optimization again. Do it 5 times until I decided to back on my previous kernel. Any explanations ? Thank
[Nexus 4 Original Android Development] jtwebfusion:
Correct me if I'm wrong, but euphoria is a CM build and this is an AOSP kernel. You need a CM kernel.
[Nexus 4 Original Android Development] urim225:
I think you are wrong, mirage works with euphoria. Euphoria isn't a cm build but with a cm theme engine that's all

---------- Post added at 04:11 PM ---------- Previous post was at 04:10 PM ----------

Make sure you flash the any kernel build of this kernel
[Nexus 4 Original Android Development] mrg666:
Thank you for helping each other since I am only able to test the kernel with the stock ROM.

and

I have updated the MiRaGe kernel with the following changes.

- Sync with Linux 3.4.107

- Removed Android logger

- Removed Android alarm device

Download links are available in the OP as always.

Enjoy!
[Nexus 4 Original Android Development] HdSht:
Running latest version without any problems, thanks a lot.

Also, Chroma with viper4android works flawlessly (in normal mode not compatibility).
[Nexus 4 Original Android Development] icu64:
1) I really hope you weren't getting mad because I was honestly asking a question 2) I'll see if I can find the app again but I know I've done it before. I think kernel auditor has the option as well
[Nexus 4 Original Android Development] mrg666:
Not at all. Please let us know if you figure out how to run this v4a without a permissive kernel with the stock ROM. Because MiRaGe will not be permissive. I don't change the kernel for an app.
[Nexus 4 Original Android Development] icu64:
Ok cool. So I did find the so and found out it only worked because I was on kitkat and I think the kernel is permissive
[Nexus 4 Original Android Development] nycelitemaster:
I have been using the kernel since 5.0, because faux kernel started to lag after a while. I must say I am using mor!all with -100mv UV, this is the far stable kernel I have seen with no performance loss. Thanks Mirage!
[Nexus 4 Original Android Development] HdSht:
[MENTION=4203114]mrg666[/MENTION] Since you implemented stratosk's dt2w feature I was wondering if you could add the last thing that was introduced in Semaphore: I mean the possibility to temporarily disable dt2w by pressing the power button. That would be a great save of battery during long idle periods. If the answer is no then, Mirage is still the best kernel for me so no problem at all :).
[Nexus 4 Original Android Development] mrg666:
Sure no problem. I think this was asked long time ago. But I forgot among other priorities. I will include the patch in the next build.
[Nexus 4 Original Android Development] nycelitemaster:
[MENTION=4203114]mrg666[/MENTION], can you provide the link to previous version? I'm am having issues with deep sleep. I want to blame an app not kernel for this, so I'm going to be running tests. Thanks

Sent from my Nexus 4
[Nexus 4 Original Android Development] xenyz:
I'm running the latest kernel on Cataclysm (holy crap, great ROM!) and there's no kernel wakelocks out of the ordinary. It's always an app :)
[Nexus 4 Original Android Development] mrg666:
That cannot be related to the kernel. I try to avoid posting older builds unless there is a serious problem with the latest build since that can cause confusion on the feedback. Please check your apps and ROM to resolve the sleep problem.
[Nexus 4 Original Android Development] ilyadan:
I am using this kernel since 4.4.4, and want to thank you for your work. On latest version with LP 5.1 the battery life is great, and the phone is rock solid. No problems spotted by me. Great job you have done!
[Nexus 4 Original Android Development] nycelitemaster:
No issue,all issue resolved after clearing cache.

Sent from my Nexus 4
[Nexus 4 Original Android Development] cirapfc:
Which app to use to calibrate colors, enable dt2w etc? I have read in this thread not to use trickster...
[Nexus 4 Original Android Development] xenyz:
Trickster MOD is just fine, but you need the paid app to change gamma values. A good free easy option is Semaphore kernel manager. A more advanced option is Synapse with UKM. Even more advanced is init.d scripting. There are so many options, but for gamma and dt2w, just use Semaphore Manager.
[Nexus 4 Original Android Development] mrg666:
There is an app as well for dt2w here.
[Nexus 4 Original Android Development] icu64:
Did you put this in the op? How'd I miss this? ._.
[Nexus 4 Original Android Development] mrg666:
It was discussed here once. Don't forget thanking the dev in the app's thread.
[Nexus 4 Original Android Development] Ivan609:
Hi, first of all thanks dev for this great kernel. Been using it since first lollipop update for N4 and it works flawlessly.

Did anyone managed to install any working sound enhancement. on Mirage kernel + stock 5.1 rooted?

I tried V4A and Dolby DT port from Huawei, with both no success.
[Nexus 4 Original Android Development] HdSht:
V4A requires permissive kernel (stock and mirage are enforcing). With that said as far as I know only Chroma rom has the sepolicy changes to allow you run V4A with enforcing kernel (I'm running that combination and it's simply awesome) :good:.
[Nexus 4 Original Android Development] xenyz:
The dev posted an anykernel updater that has the sepolicy changes. Disclaimer: I don't know much about this and what it will do to your non-Chroma ROM, but since it only touches the boot partition, it seems safe enough to try it. You can easily re-flash Mirage if it goes sideways.
[Nexus 4 Original Android Development] HdSht:
Or you could just flash Chroma, semaphore for the mpdfake file and mirage over it and discover a new meaning of beauty :highfive:.
[Nexus 4 Original Android Development] xenyz:
I couldn't get cf.lumen working on Chroma, and it's now a neccesity for me. I ended up on Cataclysm, which is fantastic. Stock + layers + bonus features. :)

It would be nice to have the sepolicy included in Mirage as well, if it gets third party apps working in selinux enforcing mode.
[Nexus 4 Original Android Development] mrg666:
New MiRaGe build is available in the OP with not too many changes.

- temporarily disable DT2W with power button (thanks to stratosk)

- V4A works with stock ROM now (use boot image packages) after replacing selinux binary with the one from Chroma ramdisk.

Kernel is still not permissive so there shouldn't be much risk of security. Please let me know if I am missing anything here. But hey! V4A is working now if MusicFX is frozen. I used Link2SD to freeze it.

Cheers!
[Nexus 4 Original Android Development] mk3y:
the bootimages in the op are for 5.1 only, right? i'm looking for a bootimage for 5.0.1.
[Nexus 4 Original Android Development] mrg666:
Correct. I am only working with 5.1 now.
[Nexus 4 Original Android Development] xenyz:
Is anyone else seeing these selinux messages in the kernel log? I'm wondering if it is my custom ROM or not.

<36>[95338.807831] type=1400 audit(1430171141.761:24340): avc: denied { search } for pid=3748 comm="QcRilReceiver" name="qmux_radio" dev="tmpfs" ino=3133 scontext=u:r:radio:s0 tcontext=u:object_r:qmuxd_socket:s0 tclass=dir permissive=0
[Nexus 4 Original Android Development] mrg666:
There are no radio or ril related messages in the stock rom
[Nexus 4 Original Android Development] HdSht:
I have read something like that regarding cataclysm. It's because some features were added to n5 but not ported properly to n4.

---------- Post added at 08:26 AM ---------- Previous post was at 08:13 AM ----------

@mrg666 if you remember some releases back a user asked to make the kernel be more conservative. Well I took some time to see how it behaves under different circumstances and in general I felt some lose of responsivness and occasionally stutters when listening to music with screen off. Since you don't use input touch boost I'm not sure that change is helpful (you should notice micro stutters/slow downs when pulling down menus or some animations). I'm not complaining but since nobody did report anything I gave my opinion. Other than that is everything perfect :good:.
[Nexus 4 Original Android Development] mrg666:
what were your changes to make more "conservative" ?
[Nexus 4 Original Android Development] HdSht:
Uhm, so yea, digging back into the thread looking for that, I was referring to the building of 26 march regarding the request of zenyx to apply one of stratosk's patch (regarding the down_treshold). But if you didn't notice any issuse maybe it's just me.
[Nexus 4 Original Android Development] xenyz:
You are correct sir, definitely not a problem with Mirage.

I played around with down_threshold and ended up setting it to 8. It skips the 432 MHz step but seems to make little difference otherwise.
[Nexus 4 Original Android Development] mrg666:
I mostly focus on the code level optimizations and prefer leaving the base kernel settings alone as I have seen everybody has different preferences. I am sure you can improve or adapt to your preferences further with fine tuning the kernel parameters. Please share what you have found. I am sure it will be appreciated. With init.d support, it is very easy to pick and set those kernel parameters.
[Nexus 4 Original Android Development] nycelitemaster:
Any Chroma user here that uses Mirage? Can help? I am getting force close with regular then I install anykernel my play store crashes. Franco works fine.

Sent from my Nexus 4
[Nexus 4 Original Android Development] xenyz:
Flash Chroma stock boot.img with Flashify or reinstall the ROM, then flash Mirage anykernel format. Use the standard (not overclock) kernel to rule out undervolting issues.
[Nexus 4 Original Android Development] nycelitemaster:
What I did was flashed Chroma, then I flashed Franco, realized app needs to be purchased.. Then flashed Mirage (my fav) boot.img . it then boots up but crashes by giving me systemui. Then I flashed Mirage Anykernel stock voltage, it works but playstore crashes.

Sent from my Nexus 4
[Nexus 4 Original Android Development] xenyz:
Yeah I got that, just follow the steps I gave.
[Nexus 4 Original Android Development] nycelitemaster:
Xenyz can you confirm if your camera works?

Sent from my Nexus 4
[Nexus 4 Original Android Development] xenyz:
Yes, it works, but I'm no longer using Chroma ROM because of an issue with cf.Lumen. When I did try Chroma, it worked fine otherwise with Mirage kernel.
[Nexus 4 Original Android Development] nycelitemaster:
What ROM do you use?

Sent from my Nexus 4
[Nexus 4 Original Android Development] xenyz:
I'm on Cataclysm right now, it's the one 5.1 ROM with layers that I got cf.Lumen and Xposed alpha working on. I can recommend it if you want a 'stock' ROM with bonus features. It works really well with Mirage. I'm trying to help the guys out with porting it from N5, so you may see a new Cataclysm release with Mirage as default kernel. :)
[Nexus 4 Original Android Development] ihancioglu:
Hi xenyz, please don't share your personal builds of Cataclysm because dev don't allow this and he considered close the thread when somebody shared personal builds. But keep share your tips If you find something useful. Thanks.
[Nexus 4 Original Android Development] HiM@L:
PM sent.
[Nexus 4 Original Android Development] mrg666:
[MENTION=3118524]xenyz[/MENTION], no news since you got the PM. I hope your are okay :)
[Nexus 4 Original Android Development] xenyz:
Yeah I got in trouble with the ROM guys, but I still think Google should make Mirage the stock kernel on mako. :)
[Nexus 4 Original Android Development] mrg666:
I am sure I would still build my kernel and call it something else :p Good to see you back.
[Nexus 4 Original Android Development] txuki2005:
hello [MENTION=4203114]mrg666[/MENTION], I feel write in the forum, because there is if you read my private. For a lot of days testing, looking at your code and turning without finding the solution. I would activate all the frequencies of the CPU as you have in your code without adding more higher frequencies. I know you're the only person who can help me but if you do not want or do not care what I understand. If you ever molested or is inappropriate really sorry not happen again because I understand because I've looked over your code or change things is impossible to activate me. Also, thank you for your work and share your knowledge. Sorry to bother you this way. Greetings from the Basque country. Sincerely, [MENTION=5311064]txuki2005[/MENTION].
[Nexus 4 Original Android Development] mrg666:
I have the working code in the repo. Just use it as it is in the first step. You can add your changes one step at a time after that. You will find the problem easily if you go back to working code and make your changes one step at a time. Be careful about the vdd levels, HFPLL divider and multiplier (first is decimal, second is hexadecimal). Pay special attention to the line with PLL_8; use it exactly as it is; I wasn't able to modify or add more PLL_8 lines.

After all these, you should be able to make it work.