yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] krialix:
L4Z compression

L4Z compression can be benefiacial?

https://github.com/labodj/Hammerhead-Linaro/commit/3c21b55b77654936cbc9ef09bbad7056bb161766

https://github.com/labodj/Hammerhead-Linaro/commit/198fb06b42a98dd328dff26f6b11a45b81abb541

https://github.com/labodj/Hammerhead-Linaro/commit/5ba5fb9a33bfe99d7febc72f4aada4ee403275f6

https://github.com/labodj/Hammerhead-Linaro/commit/e4ad085d7d5875d182b839199e94f36fcc2d682d

https://github.com/labodj/Hammerhead-Linaro/commit/b5f59c9ab8a0ef437c23ef8c31ace8a0c94087af

https://github.com/labodj/Hammerhead-Linaro/commit/be2be3448f0b68ccaa37cbf067a1fa065b474db5

https://github.com/labodj/Hammerhead-Linaro/commit/c34e292f36a4d60b1197a39665dd39efc59f98be
[Nexus 4 Original Android Development] mrg666:
I intended to add the latest compression methods but always deprioritized with the other tasks. Mainly because different compression methods only affect the initial boot process but they are not helpful with anything during the actual use. The next task in my list is updating /block. Why don't you take the lead with this and test the different compression methods to find the optimal configuration. I will follow you after updating /block.
[Nexus 4 Original Android Development] r3act:
As positive feedback I can vouch for the Febr.7 OC build being 100% stable!

With the stock kernel in Cataclysm ROM I used to have an occasional FC using maps navigation. Now the phone has been up for 154hrs flashed as is, NO setting changed whatsoever.

Going to nandroid and give the Febr.12 build a try!
[Nexus 4 Original Android Development] mrg666:
New build is available in the OP.

- many updates from upstream Linux to enhance/optimize ext4, hotplug, tmpfs, mm, shmem code

- Linux 3.4.80

Cheers!
[Nexus 4 Original Android Development] DarkenCypher:
Just curious, can this kernel be used with CM?
[Nexus 4 Original Android Development] jawz101:
Nope.

You could get it to work if you compile yourself and add commits
[Nexus 4 Original Android Development] DontPushButtons:
You could also try flashing this file made my [MENTION=1188493]Calkulin[/MENTION]

https://mega.co.nz/#!MA8HxapY!rbvXfQ46_hTRUofRQNYtjoUOMdzekpJl0rijoi3FQ80

Has worked for me. Flash this first, then flash the desired aosp kernel. Haven't had any problems yet.. But there is no support provided if anything goes bad.
[Nexus 4 Original Android Development] tvall:
Could you link me to the required commits? Been thinking of adding cm support to my fork.
[Nexus 4 Original Android Development] jawz101:
I'll have to dig around. I think I've posted them before or referred to the guy who has done it in the past on Franco's kernel

Edit. I just remembered his name. It is ziddey something or just ziddey
[Nexus 4 Original Android Development] mrg666:
I have uploaded the new builds.

- futex updates from Linux mainline

- Linux 3.4.81 and Linux 3.4.82

- disabled the user-space rmt_storage service. The kernel-side driver wasn't enabled anyway and it was spamming the logcat since I disabled /dev/mem.

Download links are in the OP. Let me know if there is anything to report.

Cheers!
[Nexus 4 Original Android Development] wallendiaz:
I have my Nexus 4 just rooted, but I never flashed any ROM, this kernel can work on my stock phone that only have root?
[Nexus 4 Original Android Development] criminalzen:
yes, fine with stock rom

"MiRaGe is an efficient and optimized kernel for the stock Nexus 4 ROM".- from the first page:.
[Nexus 4 Original Android Development] mrg666:
Yes, that is the way I use my n4.
[Nexus 4 Original Android Development] bertans:
Thank you so much (as usual) for your work! :good:

Here's the screenshot of my battery status. As you can see in the red rectangle (

night time

), battery drops even with radio and wi-fi turned off. With stock kernel the battery consumption in the same situation is almost zero... :confused:

For everything else your kernel is really rock-solid (as I already confirmed a few builds ago) and responsive. :highfive:

That's my personal experience, consider I don't think I'm running too much garbage or battery-hungry apps!

Cheers ;)
[Nexus 4 Original Android Development] mrg666:
Thanks for the report.I have been looking into improving the idle battery life but I haven't found any problems yet. I will also compare with the stock kernel. Can you use better battery stats and report the deep sleep and wake lock information?
[Nexus 4 Original Android Development] bertans:
Do you have a free alternative to Better battery stats?
[Nexus 4 Original Android Development] mrg666:
There is an xda edition.
[Nexus 4 Original Android Development] bertans:
Ok, thank you! Now I have to install your kernel again and wait for night-time... I'll keep you posted! ;)
[Nexus 4 Original Android Development] clockworkstop:
Hello again. I'd like to confirm [MENTION=2149302]bertans[/MENTION] observations on idle drain, there are other kernels out there, like for example AK, trinity or even stock, that have a lot better idle drain than mirage, to the point of loosing 0 percent in one night.

Otherwise I'd just like to give an updated opinion on performance and battery life. Very speedy and smooth and battery life is above average at worst. Thanks.

Sent speedily from my scurrying Nexus 4
[Nexus 4 Original Android Development] mrg666:
Thanks for the feedback but 0% drain after 7-8 hours can only be wrong reading since this is not physically possible. I will work on improving the idle battery drain but 0% is not my goal.
[Nexus 4 Original Android Development] clockworkstop:
Well yes of course, I wasn't clear, sorry. I meant showing zero percent.

That's the way android handles battery stats.. pretty badly.

Sent speedily from my scurrying Nexus 4
[Nexus 4 Original Android Development] mrg666:
So, based on your comments, I understand that the overall battery life is good but MiRaGe doesn't read 0% drain over the night. Also from your comments, Android's battery stats are not reliable too. This eliminates the 0% argument and leaves us with good battery life :) Thanks!
[Nexus 4 Original Android Development] clockworkstop:
Oh you... :P Android's battery stats are reliable, they always show the same result, just not the right one. So if I make my observations on idle drain using the android battery stats, the results will still be comparable.

Sent speedily from my scurrying Nexus 4
[Nexus 4 Original Android Development] Yadro:
Even with the kernels you mentioned i always got a loss of 9-12% in 7-8 hours with or without airplane mode.

If your phone doesn't even have gapps,its just rooted you may lose 0.25 to 0.5% per hour.

This is just my observation as an one year nexus 4 owner.
[Nexus 4 Original Android Development] clockworkstop:
You must be right

Sent speedily from my scurrying Nexus 4
[Nexus 4 Original Android Development] Yadro:
I was talking on my personal experience.i have even greenified most apps and i have that much battery loss.

Congrats to you sir.may the odds be always be in your favor.
[Nexus 4 Original Android Development] mrg666:
This is physically impossible and clearly a reading error. I can't take this serious and set as a goal.

________________

Everyone, battery use of MiRaGe is completely satisfactory for me. Please use whichever kernel makes you happy. I will of course keep working on improving the efficiency of this kernel since that is my original goal. Battery life discussion is over for me.

Cheers!
[Nexus 4 Original Android Development] mrg666:
I am testing a new kernel build with QSEECOM disabled. I wanted to check if there is any real world use of this kernel feature. I have also disabled user-space services qseecomd and kesytore since they depend on the kernel QSEECOM client. There seems to be no problems after these changes but I wanted to ask before posting the kernel here if anybody knows any other dependence that might cause problems that I haven't seen yet. Any feedback appreciated.

Update: I added back QSEECOM. Android wasn't really happy without it while uninstalling apps.
[Nexus 4 Original Android Development] leather.face:
Hi mrg666 :) ... Thanks for your good kernel here and I search in the past a modified stock kernel ... And I found now your kernel thread ... :D I`ll now tested the kernel but I think this is a good modified kernel for our device ... Keep it up mrg666 ... But I have a question ... Is your kernel compatible with the Trickster Mod app from the play store or what app would be recommended? Thanks for your answer and help to me! I wish a nice evening!

Regards leather.face
[Nexus 4 Original Android Development] snak3ater:
Yes.. Go for trickster mod

Sent from someone else's Nexus 4
[Nexus 4 Original Android Development] mrg666:
I haven't added the sysfs interface parameters that trickster app needs to change the kernel settings. As I have noted in the OP, MiRaGe is not a tweaker's kernel. It is more like a flash-and forget type of kernel that I tried to optimize as much as I can. I don't like adding many parameters to the sysfs interface since each parameter added to the sysfs is an additional monitoring task and overhead for the kernel.

And, you are welcome.
[Nexus 4 Original Android Development] leather.face:
Hi mrg666 :) ... I have now tested your kernel in the different variants ... I have yesterday flashed your kernel in the variant, overclocked ... And today your normal KOT kernel and I must say my device runs smoother and stable with the normal kernel as such the overclocked version ... I do not know to what it is but I am really happy with your work :good: :fingers-crossed: ... I think your kernel is better as the franco or the faux kernel for me (I have this kernel tested in the past) ... Because of battery life ... Your battery life is really better! But I have also two questions:

1/ Can I manage your kernel with any app ... Trickster mod or a other paid app from the play store?

2/ Have your kernel init.d support?

mrg666 ;) ... Thanks for your answer and hard work here ... I`m happy and I have a lot of fun! :laugh: I wish a nice evening!

Regards leather.face :cool:
[Nexus 4 Original Android Development] mrg666:
1. You don't need to control MiRaGe, just flash and forget it. I didn't include extensive control capabilities and tweaking hacks.

2. I am afraid, the answer is "no" again :) I didn't add any additional init support than the default init support in the stock kernel.

Thanks for the feedback. If you haven't changed your mind after my answers yet :cyclops:, I am glad you are enjoying the kernel.

__________

BTW, everyone, I have reverted some of my latest changes that I was planning to include in the next build due to some regressions I have seen after my testing. So, I don't have any significant changes anymore to have a new build yet. One questions is the following. Do we really need SELINUX? I don't see any problems without it and would it be a problem for you if I remove it?
[Nexus 4 Original Android Development] leather.face:
Hi mrg666 :) ... Thanks for your quick answer and I will continue to use your kernel :fingers-crossed: ... Do not worry I will not change my mind ;) ... I search in the past a good modified stock kernel and I found this now ... Your kernel is very good for me and I would be very happy if you update this ... The battery life is very good on my device ... Keep it up and good luck for your development!

Best wishes

leather.face :cool:
[Nexus 4 Original Android Development] Fenvarien:
Awesome kernel, with very good performance and battery life! Thanks for sharing this :) :good:

disce aut discede
[Nexus 4 Original Android Development] clockworkstop:
I don't think Selinux is really needed. I wouldn't mind a build without it.
[Nexus 4 Original Android Development] criminalzen:
+1
[Nexus 4 Original Android Development] mrg666:
Thanks for the selinux replies. I also don't find it really useful but also disabling something related to security is not an easy decision. Although there is QSEECOM for security, I want to investigate a little more about the potential risks of disabling selinux. All this debate is because the kernel seems to me more responsive without selinux. I will post a test kernel without selinux tomorrow so that you can also give your feedback in case my observation is just placebo.

I have fixed the problem with the QSEECOM and QCE commits. As it turns out, the freeze problem I was observing was completely due to an app which was updated recently. I have disabled it and the problem disappeared. I went back to the repo to delete the commits that reverted the QSEECOM and QCE updates. I think I should apologize from all devs who are following my repo for this but I really don't like too many commits reverting each other. You can just do "git reset --hard HEAD~1" followed by "git push --force" to eliminate my deleted commits. I will try not to do such hacks in the repo again.

I will test one more day and post the new stable and test builds tomorrow.
[Nexus 4 Original Android Development] mrg666:
I have never tried using with jellybean (assuming 4.3 is jellybean). Why don't you use kitkat?
[Nexus 4 Original Android Development] socialdistortion:
Trying it. Like the simplicity of run it and forget it. So far so good with the OC kernel.

Just minor stutters in launcher drawer (Apex) and scrolling (it must be due to lack of touch boost).
[Nexus 4 Original Android Development] XenderX666:
Because the build of KK on PAC it's not stable( so it's on development) always i change my rom and i think 4.3 on PAC it's very stable and a like this ^^.

And i try to found a kernel , i create a thread on Question , help etc.. ^^
[Nexus 4 Original Android Development] mrg666:
The micro stutters should be due to Apex launcher not kernel. Because I don't see any stutters with the stock launcher, Google Now Launcher, and Holo Launcher HD. Sure, touch boost might help but I would just delete the stuttering app instead.
[Nexus 4 Original Android Development] mrg666:
The new build is available in the OP.

- updated QSEECOM: cleaned up old/unused code, added power efficiency patches

- updated QCE from CAF kk_3.5_rb2.9

- several other patches (see the repo)

The test kernels without selinux are below. I would appreciate your feedback if you can compare the performance with the kernels in the OP.

no OC: http://www.mediafire.com/download/ynlx56b4uchaz2v/MiRaGe_mako_test_kernel_KOT_030514.zip

OC: http://www.mediafire.com/download/r2hfd2nm2u99kf6/MiRaGe_mako_oc_test_kernel_KOT_030514.zip

Cheers!
[Nexus 4 Original Android Development] pirigu:
Hello mrg666 you think should be the best kernel in the OP or in this test? Thank you

---------- Post added at 07:08 PM ---------- Previous post was at 06:54 PM ----------

Hello mrg666 you think should be the best kernel in the OP or in this test? Thank you
[Nexus 4 Original Android Development] mrg666:
I posted the test kernel to find out the answer. It would be great if you can let us know your feedback. The only difference is the missing selinux option in the test kernel. So theoretically the test kernel could be faster due to reduced overhead. But if there is no noticeable difference it is best to keep selinux.
[Nexus 4 Original Android Development] pirigu:
ok thank you very much! Now I try and test what I say! At the moment no one in OP OC is nothing short of fantastic! Thank you for your excellent work:good::D
[Nexus 4 Original Android Development] leather.face:
delete
[Nexus 4 Original Android Development] snak3ater:
Bashing & Praising going on at the same time..Sigh!!

No one is forcing us to use their kernels.If you like it,that's great..But if you did not like it,please move on..

Judging from your comment,i can see that you have respect for Mirage but those feelings were expressed it in such a weird way :eek:
[Nexus 4 Original Android Development] mrg666:
any testers?
[Nexus 4 Original Android Development] clockworkstop:
Whelp, I just tested the one without se and it seems a bit quicker to me, but that might just be placebo. I'm curious what others observed.
[Nexus 4 Original Android Development] mrg666:
I have the same feeling but I was also suspecting if it was just placebo. It looks to me that there is no clear advantage of eliminating selinux. Thank you for the feedback.
[Nexus 4 Original Android Development] socialdistortion:
Tested both the OC kernels. Benchmarks were almost identical (20.5k antutu) and even general smoothness was similar (all this based on quick ten min checks.

Sticking to the stable OP overclock kernel. Working well.

And I just disabled all the animations and the stutters are gone.

Good work and thanks!
[Nexus 4 Original Android Development] socialdistortion:
The device does not go into deep sleep with the latest kernel. And the phone's been plugged in ac charging for 3 hours and had only charged 50%. Is anybody else facing this problem.
[Nexus 4 Original Android Development] jimyiak:
Check if on the battery menu shows usb instead of ac...maybe you cable or something..

neXus⁴ running kitkat 4.4.2
[Nexus 4 Original Android Development] kkruglov:
i'm sorry, i know that this kernel is made for stock rom, but i used it with paranoid, for all the time, and it was ok until the latest test version (03.05).

latest version is very fast, but sometimes, randomly device becomes unresponsive, i can't lock screen, or do anything. it can last 30 seconds or 1-2 minutes or forever and i have to reboot device via button.
[Nexus 4 Original Android Development] albundy2010:
Chances are it's the roms fault.

And if you're using the pie feature in that rom it's definitely the roms fault. There is a bug in it that causes exactly that.
[Nexus 4 Original Android Development] socialdistortion:
Can confirm freezes in PA. Reverted back to the last update and running stable.

PA with pie was running smoothly with the last update. Used it for two days without a hitch.

However, lots of freezes with latest kernel.
[Nexus 4 Original Android Development] mrg666:
I will fix the freezes ASAP. I hope you can help me with testing.
[Nexus 4 Original Android Development] socialdistortion:
I'll paste the logcat when I have a freeze. Currently running the latest kernel to get a logcat.
[Nexus 4 Original Android Development] mrg666:
A new build is in the OP

- reverted QSEECOM changes to fix freezes

- added power_efficient workqueue (thanks to [MENTION=4003363]xboxfanj[/MENTION])

- added msm memutils for faster memory operations (thanks to [MENTION=4003363]xboxfanj[/MENTION])

Please let me know if freezes are fixed, seems to be fixed to me.

Cheers!
[Nexus 4 Original Android Development] clockworkstop:
Fixed, cheers.
[Nexus 4 Original Android Development] socialdistortion:
Testing. Looks fine so far.

Logcat has this a lot: 03-06 19:59:54.049 W/linker (3416): app_process has text relocations. This is wasting memory and is a security risk. Please fix.

Is this a kernel or specific issue?
[Nexus 4 Original Android Development] mrg666:
I don't see such messages in the logcat of stock ROM. It must be related to the ROM you are using
[Nexus 4 Original Android Development] socialdistortion:
Yep got it. The kernel is running smooth otherwise. Thanks for the quick update.
[Nexus 4 Original Android Development] apatal:
Thanks!
[Nexus 4 Original Android Development] mrg666:
So the fix is confirmed.

Everyone, please update your kernels if you are using 030514 build. Today's build so much smoother even if you didn't have the freeze problem.

Sorry about the botched build yesterday :o
[Nexus 4 Original Android Development] socialdistortion:
Just got a massive screen freeze on the latest kernel. Was browsing through the Twitter app. Had to hard reboot the phone.

Logcat: http://pastebin.com/M9ddEmqg
[Nexus 4 Original Android Development] mrg666:
:crying:

Okay, I have reverted the QCE patch as well. Can you test the following kernel?

non-oc: http://www.mediafire.com/download/60v1p6xd3e28np2/MiRaGe_mako_test_kernel_KOT_030614.zip

oc: http://www.mediafire.com/download/2omg6v26qi6uieg/MiRaGe_mako_oc_test_kernel_KOT_030614.zip
[Nexus 4 Original Android Development] Fenvarien:
Just tested it here and the new test builds work perfectly fine and quite smooth. Thanks for your hard work! :good: :)

disce aut discede
[Nexus 4 Original Android Development] mrg666:
Guys, I have withdrawn all new builds and rolled back to 022314 build. If you are having freeze problems, please revert to this build. I will fix and make sure it is fixed before posting again.
[Nexus 4 Original Android Development] clockworkstop:
Again with the new test build, no freezes.

I'm back to using 02-23 though now.
[Nexus 4 Original Android Development] mrg666:
I am almost sure that I have fixed the problem now. I have already pm'ed the new test builds to the members who had reported the freezes. I hope they can help with testing. I have been testing since several hours already and, after testing more tonight, I will post tomorrow. Testing is difficult since the freeze problem appears very inconsistently. But the kernel is as smooth as before now, I haven't seen a single hiccup yet.

The culprit is the following commit

https://github.com/mrg666/android_kernel_mako/commit/7c1f2d286076292c58407bf65e1e518ea82cf941

I am happy that the qseecom or qce commits can be restored since I had spent considerable time on the qseecom commits.
[Nexus 4 Original Android Development] apatal:
Great! Thanks for sharing your work! I've been always on the lookout for optimized stock-ish kernels that I can just flash and forget, and your project perfectly fits the bill. Keep up the good work! :)
[Nexus 4 Original Android Development] mrg666:
Thanks. Glad to be useful.
[Nexus 4 Original Android Development] mrg666:
I have uploaded the new kernel with the fix for freeze problem.

Just to remind, this build comes with the following changes after 022314 build

- QSEECOM updates to improve power efficiency

- latest QCE updates

- power_efficient workqueue for system processes

- msm memutils to improve memory operation performance

- other small updates

Bashliev, mrfffff, and socialdistortion helped with testing and confirmation of the fix. Thank you, all.

This has been the most difficult build so far. The freeze and stuttering were not consistently happening and some of the users didn't even see the problem. The inconsistency was most probably due to using previously unused TPIDRPRW register with the ARM 7587/1 patch. Let's leave that register unused.

Cheers!
[Nexus 4 Original Android Development] pirigu:
hello guys a question ... When I update the kernel I have to wipe? Thank you
[Nexus 4 Original Android Development] mrg666:
No wiping necessary. Just flash over and reboot.
[Nexus 4 Original Android Development] pirigu:
thanks a lot but especially thank you for your work
[Nexus 4 Original Android Development] Fenvarien:
The new version is working remarkably well, thank you [MENTION=4203114]mrg666[/MENTION]

disce aut discede
[Nexus 4 Original Android Development] haget83:
Everytime i flash Mirage i lost root privilage; flashing cwm-supersu doesnt' work, got "permission error"

I have to manually root device whit the toolkit everytime i update my roms , it's boring :crying:
[Nexus 4 Original Android Development] mrg666:
This was discussed earlier in the thread and also there is a note in the second post. You need to switch to another ROM that is compatible with the stock boot image or flash Chainfire's supersu. Another option is extracting the zImage from the boot.img in my zip file and putting it in the anykernel updater I had posted earlier in this thread.

Can you either specify your ROM, or better, post the original boot image of your ROM. I can take a look at the init scripts and conditionally add the command(s) to the boot image of MiRaGe. That will fix the problem.
[Nexus 4 Original Android Development] haget83:
edit//

sorry problem solved.

I need to download the correct chainfire_su zip

(i was flashing supersu0.93 instead of 1.93, what a fool :eek: )
[Nexus 4 Original Android Development] socialdistortion:
Possible bug report: cannot access usb storage through windows. Flashing another kernel works.

Running AOSPA 4.1 beta.
[Nexus 4 Original Android Development] mrg666:
All USB functions (storage, ADB, charging) are working fine with stock ROM.