yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] ihancioglu:
You will need to reflash supersu as PA is using modified ramdisk and Mirage is using a stock one. Result you are using Root right. Just flash latest supersu.
[Nexus 4 Original Android Development] icu64:
What happened to the any kernel format zips?
[Nexus 4 Original Android Development] apatal:
That was a community contribution from one of the users who builds it from MiRaGe's sources. Search the thread for links to his download page and see if he made updated builds for his anykernel builds.

ProTip: I think the name of the user is Chaos something something. Sorry I can't recall the exact username.
[Nexus 4 Original Android Development] Fenvarien:
Yes, it was [MENTION=4056635]ChaosChris[/MENTION] builds ;) Here is his last posting: http://xdaforums.com/showthread.php?p=54892608
[Nexus 4 Original Android Development] RolF2:
strange, but with 09.05 oc kernel i got no sound in call (i can't hear other side, only short beep in earpiece when you hang up) - reverted back to 08.23 oc and all is ok. (tried 09.05 one more time & still no sound in call)

R.
[Nexus 4 Original Android Development] mrg666:
Interesting, I can make calls just fine. And I don't see any commit after 8/25 that can cause such a problem either. I will double check but I think you should also check other things than the kernel on your device.
[Nexus 4 Original Android Development] RolF2:
ok, looks like corrupted download or something - downloaded 09.05 kernel on another pc and all is ok

sorry for false alarm :)
[Nexus 4 Original Android Development] guimendes:
[MENTION=4203114]mrg666[/MENTION] I love your kernel and I use it as my daily driver, but I noticed that Franco's has better WiFi stability. Do you have any idea why?

Thanks!
[Nexus 4 Original Android Development] mrg666:
It is the stock WiFi driver in MiRaGe and I haven't experienced or heard about a WiFi problem before.
[Nexus 4 Original Android Development] guimendes:
The problem may be in the network I use, then. I realized that forcing 2.4 GHz my WiFi became more stable.

Thanks for reply.
[Nexus 4 Original Android Development] ChaosChris:
Hi all, sorry for the big delay in my any_kernel builds... dont have my nexus 4 any more got a new oneplus one, anyway i currently building an updated version of my any_kernel builds. You can grab them in 10 minutes here :)

happy flashing:)
[Nexus 4 Original Android Development] haget83:
i was tryin to flash mirage kernel on latest temasek's rom , but every boot i got android.process stop working :confused:
[Nexus 4 Original Android Development] migueldbr:
try wiping cache+dalvik cache and see if it helps...
[Nexus 4 Original Android Development] apatal:
Isn't temasek's ROM CM based? MiRaGe is made for stock ROM.
[Nexus 4 Original Android Development] migueldbr:
its non-caf
[Nexus 4 Original Android Development] xenyz:
Are you on the standard kernel? OC kernel is undervolted and gives random FC/crash on some devices.

[MENTION=4203114]mrg666[/MENTION] now that you've added voltage control, why have two releases?
[Nexus 4 Original Android Development] mrg666:
I still use OC build instead of undervolting with a kernel app or script. But I can remove it if nobody needs it anymore. Everyone, please post if you still want OC build in the future builds.

BTW, it seems that Linux 3.4 kernel will be end-of-life soon. 3.4.103 (maybe 104) can be the final patch level. MiRaGe is well beyond the level of 3.4 in many parts of the kernel source and I will keep backporting important patches from the current level of Linux.
[Nexus 4 Original Android Development] Sir_gpm:
OC Rulz!
[Nexus 4 Original Android Development] apatal:
Delete: XDA derp.
[Nexus 4 Original Android Development] apatal:
[MENTION=4203114]mrg666[/MENTION] That's cool. Seems like it's another sign that "L" is about to drop soon. Good news is that it looks like there's still a chance for the N4 to get the latest version. Hopefully, we'll get a MiRaGe for L too in the future. :)
[Nexus 4 Original Android Development] vr5411:
OC build running happily here!!
[Nexus 4 Original Android Development] TheNerd:]:
OC ftw!.
[Nexus 4 Original Android Development] pachwald:
Please keep the OC build. So much more convenient!
[Nexus 4 Original Android Development] mrg666:
Okay, I will keep the OC build. I am building it for myself anyway.

I will, for sure, build the L kernel when/if we receive the L ROM. When Google stops updating the ROM, I will start building the ROM as well and it will probably be an optimized build of CM. Unless my N4 dies or lost somehow, I have no intention to upgrade it.

The kernel is in a very good shape and I am not going to build a new version this week. But I am working on it. Let's see if there is something worth posting next week.
[Nexus 4 Original Android Development] Federico_96:
It's a great news to read that you will stick with the nexus 4, and seeing how good your work is in kernel development, I can't wait to try your custom rom in the future
[Nexus 4 Original Android Development] xenyz:
Looks like it got a new maintainer and a new lease on life: https://www.kernel.org/category/releases.html
[Nexus 4 Original Android Development] mrg666:
Thanks for this. You are always helpful. So they decided to extend the life of 3.4 with a new maintainer. That is good news, actually.

Edit:

Everyone, I hit a very bad bug in gcc 4.9 today. After disabling loadable module support (without any code change), the kernel became totally unstable rebooting by itself every several minutes with a completely clean kernel log. Rebuilding the kernel with gcc 4.8 fixed the problem. I suspect there is a misoptimization in the arm code (possibly thumb or cache). I will leave this problem to be sorted out by the Linaro/GNU devs. Until then, we are going back to gcc 4.8 with the next build.
[Nexus 4 Original Android Development] TheNerd:]:
Thank you so much for not moving on!
[Nexus 4 Original Android Development] MtG92:
[MENTION=4203114]mrg666[/MENTION] I'm curious as to what settings you use on Viper4Android. Is that something you'd be willing to share?
[Nexus 4 Original Android Development] mrg666:
I only enable v4a for the headset. Phone speaker is too weak for v4a. This might also save some battery. The other settings depend on your personal preference.
[Nexus 4 Original Android Development] iskandar1023:
Thanks for sticking with this aging phone, [emoji2]

Sent from my deepest part of my heart
[Nexus 4 Original Android Development] mrg666:
New MiRaGe build is available!

- Removed loadable modules support

- Removed modules dependence from BPF_JIT code

- several small code clean ups

- switched back to gcc 4.8

There are no modules included with the MiRaGe kernel but loadable module support was needed just for the BPF_JIT code which is, curiously, not a module by itself. I have modified the BPF_JIT code to replace the two calls that required modules support with direct calls to vmalloc. The original mako kernel also comes without loadable module support.

While testing removal of loadable module support, I have seen a gcc 4.9 bug that caused spontaneous kernel reboots. The kernel crashes were not even leaving any error message in the kernel log. Switching to gcc 4.8 resolved the problem. Actually, I have a feeling that gcc 4.8 produces a better kernel binary. Just check and let me know please.

Cheers!

BTW: Upgrading to this build is highly recommended.
[Nexus 4 Original Android Development] ForMartha:
[MENTION=4203114]mrg666[/MENTION] - thanks, downloaded and seems to works fine + faster.
[Nexus 4 Original Android Development] deepss1:
Working fine with Paranoid latest beta 2.
[Nexus 4 Original Android Development] defconoi:
[MENTION=4203114]mrg666[/MENTION] I just got PowerSuspend ported over to the N4, just gotta get Doubletap to wake working, would you mind helping me with it? Spent 3 days on this and my mind is fried, didnt think I'd get this far, but it compiles and works:

https://github.com/ion-storm/Unleashed-Kernel-Series/commits/aosp-power2

Other than what I did so far, just lge_touch_core & kgsl.c need to be edited to allow them both to powersuspend
[Nexus 4 Original Android Development] mrg666:
Let me check what is powersuspend first. I will post if I can do something.
[Nexus 4 Original Android Development] Sir_gpm:
Also let your users what it is and what is it for. [emoji6]
[Nexus 4 Original Android Development] mrg666:
defconoi gave the following link.

http://xdaforums.com/showpost.php?p=55696449&postcount=1803

There are many components in the kernel that will be affected. I will need to test before posting it here. It will take some time.
[Nexus 4 Original Android Development] malson:
Read this : lkml.iu.edu/hypermail/linux/kernel/1407.3/00650.html
[Nexus 4 Original Android Development] mrg666:
WOW! This is what he said: "Your compiler is total ****".

Linus is doing his usual thing again :) Somebody had to say it. I am glad it is Linus.
[Nexus 4 Original Android Development] ChaosChris:
synced my sources, downgraded toolchain, did some code cleanup/optimization to my build-script and builded a new anykernel version :)

(KTU_20140929_153231 | KTUO_20140929_155153)

grab them here

detailed changelog in my github :)
[Nexus 4 Original Android Development] icu64:
You should make your own thread to make finding your builds easier
[Nexus 4 Original Android Development] xenyz:
MiRaGe users, I know you're already used to the fastest, most responsive kernel around, but I thought everyone should know about [MENTION=4544860]osm0sis[/MENTION]' optimized hybrid dalvik and bionic patches available in this post.

For stock ROM, I highly recommend the Bionic-LG3 and Dalvik-Hybrid_1+Z3. Both in benchmarks and regular use, they sure do speed up operations.

Remember to clear the dalvik cache after flashing these, to ensure apps get rebuilt with the new optimized libs.

And the dev is so awesome that there's even a revert zip that you can flash to get back to stock for an OTA update.

I searched the thread but hardly any mention of this simple upgrade that gives real positive results.
[Nexus 4 Original Android Development] mrg666:
I have been using ART since so many months without any problems. Are you still using Dalvik VM, xenyz?
[Nexus 4 Original Android Development] xenyz:
Yes, I can't go without Xposed modules. :)

I'm worried about the Android L release. No more Dalvik, so no more Xposed framework, and no more Adobe Flash!
[Nexus 4 Original Android Development] mrg666:
OK, I use neither of them but I am pretty sure there will be a solution for running Xposed with Android L.

I have seen a screenshot of Android L on Nexus 6 the other day with 3.10 kernel. I am wondering if Android L will still come with 3.4 kernel for mako. 3.10 kernel would be great but 3.4 kernel is still be okay with me as long as mako receives the official Android L. Any news that I missed on this?
[Nexus 4 Original Android Development] guimendes:
Ages ago Google released sources of 3.10 for some SoCs, but AFIK nothing to mako.
[Nexus 4 Original Android Development] mrg666:
New MiRaGe builds are up in the OP!

- Linux 3.4.104

- arch: arm: lib: optimize memcpy for cortex-A15

- several other small changes

Enjoy!
[Nexus 4 Original Android Development] Connor Baker:
All of the Android Wear devices run on 3.10 kernels, and to my understanding, they use a variant (or maybe the same) s400 chip that is inside our Nexus 4. However, I have no clue if it would be possible to back/forward port to that kernel. It would likely require a complete rebase.

- Connor Baker
[Nexus 4 Original Android Development] albundy2010:
They are not the same SoCs as what's in the nexus 4. Those are off the shelf ARM a7 cores. Nexus cores are krait. That aside, getting everything working with the rest of the board...
[Nexus 4 Original Android Development] ForMartha:
[MENTION=4203114]mrg666[/MENTION] - It seems that I'm suffering from horrible reception and disconnection from the mobile network provider. this havnet occurred even once while using an older version than the newer one. got any clue why? (BTW a lot of people that I'm talking with them via my N4 say that they can't hear me..)
[Nexus 4 Original Android Development] mrg666:
I don't think that is related to the kernel. You can test with reverting back to previous or stock kernel but it will most probably be resolved by itself when the network provider fixes the network problem.
[Nexus 4 Original Android Development] migueldbr:
[MENTION=4203114]mrg666[/MENTION] are you still testing the powersuspend by defconoi?
[Nexus 4 Original Android Development] mrg666:
I didn't have time to test it yet. I will do at the first chance.
[Nexus 4 Original Android Development] defconoi:
If you do make sure you test my latest changes, getting a flatline in battery with it and no battery drain, It was a **** ton of work to port it over. My commits are kinda sorta a mess with allot of manual edits, maybe [MENTION=4203114]mrg666[/MENTION] can port it cleaner since he has more developing skill than I do.
[Nexus 4 Original Android Development] mrg666:
I haven't done yet, I will check your latest commits too. Thanks for letting me know.

Is flat line practically possible? Even when the phone is off, it may not be noticeable in a few hours but the battery still loses charge, right?
[Nexus 4 Original Android Development] albundy2010:
Flatline is what you get because androids battery reporting sucks.

It's impossible for it not to draw power during standby but that won't stop the stats from making a flat line.

Here's one.
[Nexus 4 Original Android Development] ChaosChris:
Anykernel_build is ready to flash! grab them (like always) here :)

Edit:

something strange is happend to my server :/ cant access my mirage folder but its subfolder are accessable, also the parentfolder is accessable hmmmmm, anyway here you can download both versions :) :

Standard Mirage_Any

Overclocked Mirage_Any

Edit 2: Fixed!:) stupid RewriteRule in htacces ;)
[Nexus 4 Original Android Development] apatal:
Really getting good battery life running the latest build with rastakat.

BTW, has anyone tried using MiRaGe with PA? Any issues?
[Nexus 4 Original Android Development] leolawliet:
Hey mrg666! As usual your work is flawless
[Nexus 4 Original Android Development] mrg666:
Hey, nice to see you here! So you have an N4 now?
[Nexus 4 Original Android Development] HiM@L:
this is not bad at all... although most of the time is on wifi....with Purity.
[Nexus 4 Original Android Development] leolawliet:
Yep I got a good deal for it so here I am :)

Nice to see you as well, I look forward to seeing what this phone is truly capable of

Sent from my Nexus 4 running LiquidSmooth v3.2
[Nexus 4 Original Android Development] mrg666:
I haven't updated MiRaGe this week as well. Because I will wait until Google releases the 5.0 kernel source for the next MiRaGe build. I want to apply the 5.0 updates on the current stable code.
[Nexus 4 Original Android Development] criminalzen:
sounds good to me... :)
[Nexus 4 Original Android Development] apatal:
An Oasis of Lollipop = MiRaGe ;)
[Nexus 4 Original Android Development] mrg666:
:)

There was an Oasis kernel based on MiRaGe but with additional features. Its development stopped sometime ago and you guys eventually made me add some of those features (voltage control, dt2w, screen gamma control).
[Nexus 4 Original Android Development] MtG92:
And we are very grateful for those "treats"! ;)
[Nexus 4 Original Android Development] tvall:
you gave in to their demands? that was unexpected. does that mean no one continued where i left off, or no one moved to the new fork?
[Nexus 4 Original Android Development] apatal:
It was a gradual process involving a lot of testing and weighing of advantages and disadvantages. [MENTION=4203114]mrg666[/MENTION] did not add features haphazardly and did not add features for the sake of adding them or luring more users. I like how deliberate the growth of MiRaGe is. Restraint is a virtue not a lot of "developers" have. :)
[Nexus 4 Original Android Development] mrg666:
Glad you stopped by, tvall. There are several other forks but, AFAIK, no parallel development is going on now like Oasis. That is probably because a few most requested features are included now after testing to make sure that there were no adverse effects.
[Nexus 4 Original Android Development] xenyz:
I sometimes use naruKa if I'm looking for a little smoother performance. The dev kept those ondemand patches mrg666 reverted and I still think it gives a better ride.

[MENTION=4203114]mrg666[/MENTION] any thoughts on adding a sysfs control to use the regular or higher freqs with the ondemand governor?

edit: stumbled across the announcement for BFQ-v7r6 with an interesting update:
[Nexus 4 Original Android Development] mrg666:
I had reverted the ondemand patches after testing. I didn't notice much/any improvement in the performance with those patches. You might feel that the kernel is more responsive (if not placebo) since my testing showed that the cpu was kept at higher frequencies which increased the heat and battery use. You can get the same result if you use performance governor which always keeps the cpu at max freq. The ondemand governor is very well balanced right now. You know my standing about the tweaking options in kernel. Instead of adding tweaking options to ondemand, I can enable the performance governor when you need the best performance.

I will test the new BFQ before the next build.
[Nexus 4 Original Android Development] mrg666:
This patch causes spontaneous reboots. I will try the next when available.
[Nexus 4 Original Android Development] leather.face:
Hi mrg666 :) ... Thanks for your work here but I wanted to ask you, give you me your permission to integrate this kernel in my tweaked Purity rom??? Have many thanks for all and have a nice day!!

Regards

leather.face
[Nexus 4 Original Android Development] mrg666:
Thanks for asking. Not a problem with me. You can integrate the kernel of course.
[Nexus 4 Original Android Development] ap1618:
Running Mirage on purity. Perhaps the best kernel I have tried to date.

Sleeps well, quite efficient.

thank you for great work.
[Nexus 4 Original Android Development] Sir_gpm:
Will love to run in L preview.
[Nexus 4 Original Android Development] schetz:
This kernel runs perfectly with purity rom.. Tried few others, each for at least two days, and at least on purity this one is flawless. Smooth and battery friendly, nice job
[Nexus 4 Original Android Development] mrg666:
Thanks for the reports with Purity ROM. I am waiting for the L ROM and kernel source released. I will build the L kernel as soon as these are released. I don't have the extra time to flash and test multiple ROMs and I can only support the stock ROM that I use.
[Nexus 4 Original Android Development] vampire36:
Actually if you wish to try out you can use the latest android l release 15...

Rock solid and working flawlessly :)
[Nexus 4 Original Android Development] TheNerd:]:
That's not an official build from Google
[Nexus 4 Original Android Development] mrg666:
I had some time today to work on MiRaGe and I was able to resolve the spontaneous reboot problem problem with the latest BFQ patch. All I had to do was using gcc-4.8.4 based 14.08 Linaro toolchain (thanks to [MENTION=4825437]Christopher83[/MENTION]). With this resolved, I have uploaded the new build with the following changes.

- BFQ updated to v7r6 which should improve the IO scheduler performance especially during boot process

- included the performance governor and removed conservative governor

- updated the gcc 4.8 linaro toolchain to 14.08

This should hold up until Lollipop kernel source arrives.

Boooo :)
[Nexus 4 Original Android Development] Matteo Mazzu:
When I try to flash it in recovery it says "unable to open zip file".. I have last TWRP.. Any idea why?
[Nexus 4 Original Android Development] Hoochie_Coochie:
Bad download most likely, try it again and check the size of the file. Or try a different browser to download it.
[Nexus 4 Original Android Development] Matteo Mazzu:
Is there a way for changing the screen colors? Like on PA at examples..
[Nexus 4 Original Android Development] jimyiak:
Try semaphore manager..with this values 0 39 119 0 6 0 2 0 2

sent by nexy 4
[Nexus 4 Original Android Development] mrg666:
I am on it! But I will need a couple of days.
[Nexus 4 Original Android Development] apatal:
My mako is ready. :)
[Nexus 4 Original Android Development] mrg666:
Here are the Lollipop kernels after syncing with Google's Lollipop source release and replacing the ramdisk from Lollipop stock boot image.

http://www.mediafire.com/download/78aywa1bz3udc53/MiRaGe_mako_kernel_LRX_111614.zip

http://www.mediafire.com/download/5rb0gu1rd317e78/MiRaGe_mako_oc_kernel_LRX_111614.zip

MiRaGe runs great with stock LRX build but you will need to root again after flashing the kernel. Let me know how it goes while I work on the re-root problem.

Edit: The re-root requirement seems to be fixed. I have updated the download links. Please try and let me know
[Nexus 4 Original Android Development] Shubhamqweasd:
thnks :D ,

i guess you need to change SELinux to permissive to make root stick and work :D
[Nexus 4 Original Android Development] mrg666:
The re-root requirement seems to be fixed. I have updated the download links above.

Everyone, please try and let me know.
[Nexus 4 Original Android Development] nibla101:
Confirmed working here
[Nexus 4 Original Android Development] yantz:
Working now :good: added 2k+ antutu score

yantz
[Nexus 4 Original Android Development] mrg666:
Thanks for the confirmation!

I have updated the OP with the new MiRaGe LRX builds. This build comes only with Google's updates on top of MiRaGe. Many of the updates included in Google's new kernel release were already in MiRaGe. The followings are the main changes.

- Many updates to MSM:KGSL (Adreno) drivers

- Prima WiFi driver updated to 3.2.3.22

- Small number of other patches

Please see the repo for details.

Enjoy!
[Nexus 4 Original Android Development] MtG92:
[MENTION=4203114]mrg666[/MENTION] would it be possible for you to keep the last KK kernel in the OP for those who are still on KK? Thanks :)
[Nexus 4 Original Android Development] ihancioglu:
Hi mrg666,

Would you please advise how did you root your lollipop?

CF Auto Root or just flash UPDATE-SuperSU zip file?

Thanks,
[Nexus 4 Original Android Development] mrg666:
I just restored the downloads for the last KTU builds of MiRaGe.

I used the latest CF-Auto-root which installs SuperSU 2.20. You can download from CF's website. UpdateSuperSU didn't work with the stock boot image. But I didn't try with MiRaGe boot image.
[Nexus 4 Original Android Development] vampire36:
SuperSuflashable 2.19 beta works too with latest mirage :)
[Nexus 4 Original Android Development] ihancioglu:
I was using stock kernel last two days with Lollipop, already hated my N4.(Terrible battery life, Always Overheated, Poor performance) I think I could not use my N4 If there is no custom kernel for it.
[Nexus 4 Original Android Development] mrg666:
I received a question by PM and I wanted everyone know my answer before similar questions appear more frequently.

Lollipop is very new yet and it came with important changes in security that made even rooting difficult. I am expecting that the problems, such as you describe, will sort out in short time. I don't want to disable selinux by default if the problem can resolved by V4A and other applications. I will wait until the app developers act on these since changing the kernel and putting everyone's devices in insecure mode should be our last resort. If you can't wait for a while, I would recommend going back to Kitkat. I will post the question and answer in the thread so that others can read.
[Nexus 4 Original Android Development] ihancioglu:
Do you noticed that Lollipop animations are not smooth enough sometimes? Is this needs more cpu power to display that animations? Maybe a few ondemand/autosmp finetune is needed after Lollipop.
[Nexus 4 Original Android Development] nibla101:
Yeah I noticed this too, slight stuttery at the end of some animations.