yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] ChaosChris:
cool already used this toolchain :P had this for my other kernel-projects :D thanks

Anykernel-zip-MiRaGe: Download MiRaGe_Any

( [MENTION=4203114]mrg666[/MENTION] if you want you can add this link to OP, i will update the zip´s as soon as possible when you update your source :) )

edit: did some changes to naming the zip (looks better now). Also you can find now the Overclocked Version of MiRaGe on my ftp as ready-to-flash zip. both version are updated, uploaded, tested and working, have fun :)

If you want to know whats changed in the buildstuff, look at the txt on my ftp.
[Nexus 4 Original Android Development] vampire36:
[MENTION=4056635]ChaosChris[/MENTION] : There is a chaos kernel there ? Which kernel is that :p
[Nexus 4 Original Android Development] ChaosChris:
if you mean this kernel: http://dl-chaos.tk/kernel/mako/ChaOS-Kernel/ (https://github.com/ChaOSChriS/ChaOS-mako) , this is a personal kernel. Its not released here on xda. This is a current project from me, and some of my friend are testing for me, but i dont want to clutter up this thread so if you want more Infos about the "ChaOS-Kernel" pm me :)
[Nexus 4 Original Android Development] defconoi:
fyi guys, I talked to [MENTION=5658634]apb_axel[/MENTION] and he added autosmp to Synapse/UKM :)
[Nexus 4 Original Android Development] apatal:
Like [MENTION=4203114]mrg666[/MENTION] said, this really isn't a tweaker's kernel, and it's what I love about it, being able to just flash and forget about it and it will work just as well, but I guess it's nice to have that option for people who do like to play with it a bit. :)
[Nexus 4 Original Android Development] aviz1911:
Yes this is one of the several awesome reason's why we love franco, mirage and semaphore kernels. Just undervolt if you want. If gamma control is available, change the color profile and you are good to go :D

These trickster, synapse etc etc are for people who like to experiment with those tunables. But i think [MENTION=4203114]mrg666[/MENTION] knows the best right ;)
[Nexus 4 Original Android Development] karthi89:
Is there any modified version of this kernel with fast charge included?? If its not, can anyone build with fast charge included??
[Nexus 4 Original Android Development] Federico_96:
Take a look at NaRuKa kernel, which is modded version of MiRaGe, but I'm not sure if fast charge is included
[Nexus 4 Original Android Development] mrg666:
New build is up!

- Linux 3.4.102

- many minor fixes (thanks to [MENTION=5842140]moddingg33k[/MENTION] for reporting two of them)

Downloads are available in the OP and the details in my repo.

Cheers!
[Nexus 4 Original Android Development] ChaosChris:
New Anykernel-MiRaGe builds are uploaded (based on lastest MiRaGe) :o grab them here
[Nexus 4 Original Android Development] icu64:
Hey guys a little help. I have a "fastest" bin CPU and normally I can undervolt by 125 or 150 if I really want to pish it but for some reason the oc any kernel version will give me random reboots. I understand some of you may see this and think its because of the small over clock that this kernel comes with no matter what you do but its not. On any other kernel I can oc to 1.8 GHz without an issue... Please help, for now I'm using the standard version without oc/UV and I really miss UV.... Can anyone help me out?
[Nexus 4 Original Android Development] jmtjr278:
Any plans to just add gamma control? Everything else is perfect.

I understand the need/want to keep everything simple and stockish so if the answer is no that's OK too.
[Nexus 4 Original Android Development] xenyz:
There is semaphore's gamma interface. Use Trickster MOD or Semaphore Kernel Manager to adjust.
[Nexus 4 Original Android Development] icu64:
Any help guys?
[Nexus 4 Original Android Development] apatal:
I suggest staying with the regular version then. If you're using UV to deal with heating issues, it's not that important here as Mirage's hotplug runs much cooler than most other custom hotplugging solution out there, including stock mpdecision. :)
[Nexus 4 Original Android Development] xenyz:
Same boat as you. I can't undervolt by -100 mV with a fast bin and therefore have to run the standard kernel. As OP says, don't be disappointed and just run what's stable. Undervolting is overrated. :)
[Nexus 4 Original Android Development] icu64:
Not trying to be rude bro but that didn't answer my question. If you read it again I was asking why I have issues with it on just this kernel but I do the same thing on every other kernel without an issue
[Nexus 4 Original Android Development] xenyz:
[MENTION=4203114]mrg666[/MENTION] will you consider adding faux's voltage interface?
[Nexus 4 Original Android Development] icu64:
Yea or look at what you have, something's off or maybe different. Its the only kernel that gives me issues at an 100 undervolt.... The only thing that keeps it for being perfect.... OK no it is perfect I would just really rather use oc
[Nexus 4 Original Android Development] apatal:
[MENTION=4203114]mrg666[/MENTION] cannot answer something that would depend on a lot of factors. I suggest posting your complete setup here, including ROM, any mods or app that might affect system performance. Like the OP said he developed and tested this for the stock ROM, which he uses. He cannot vouch for its performance on other ROMs.

Also, when you're asking for help, try and be considerate on how you phrase your posts. The developer and people who frequents this thread have no obligation to solve problems you may have on your modded device. If you find the kernel does not suit you, you are encourage to use other ones that do. That is the beauty of Android and the reason I stick around in xda. I hope you do not take this the wrong way. I just don't want you to get into a fight in some other thread because someone misunderstands your posts. I know it can be frustrating to encounter problems in our devices, but sometimes, kindness is more effective. Just a thought. :)
[Nexus 4 Original Android Development] icu64:
Bro just chill don't preach, I already stated that I didn't mean it in a nasty way . I don't see how asking a question is rude and I definitely don't understand why you'd speaking for someone that has they're own mind. The guy I was speaking to before didn't take it a way and its not like I said "FIX THIS **** NOW OR ILL EAT YOUR SOUL!!!".... So yea, just chill and stop it right here so the thread doesn't get messed up for no reason.... And again, I'm only asking what's different about this kernel where I'd only have an issue with this one.... Sucks because I would like to use it because it really makes Franco (in my opinion) look kinda bad
[Nexus 4 Original Android Development] apatal:
Yeah fair enough. :)

And yes, you're right: people are starting to take notice of the kernel since Mirage's hotplug solution gives consistently good experience. Can you maybe help out a bit more so [MENTION=4203114]mrg666[/MENTION] can trace what's causing the reboots? If you are still running the OC version and it happens again, please extract the last_kmsg and share it to [MENTION=4203114]mrg666[/MENTION] so he can see what's causing the kernel to panic.

Tbh, I've recently run into reboots using it as well, but only when sharing photos using fb messenger, so I thought it may have something to do with the camera. I'll help out and run the oc version as well and get the last-kmsg of I run into trouble. Sound good? :)
[Nexus 4 Original Android Development] icu64:
OK I think you understand I wasn't being a **** now lol and sure but there's just one thing... What's your setup? I'm on the latest pa with no other tweaks but this kernel running and I am using the normal any kernel version of it now... I'll try the oc version again and see what happens bro but really would like to know your setup as well
[Nexus 4 Original Android Development] xenyz:
Same here, but I just ran with standard kernel and have had zero issues. It is the perfect kernel for those who want performance and battery without any config, IMHO.
[Nexus 4 Original Android Development] apatal:
I'm running stock rastakat (latest one for mako), PA gapps and now running the OC kernel as well. I'll see if I can replicate the random reboot when I'm using the camera on my fb messenger (chat head). Can you replicate the reboots on your setup? :)
[Nexus 4 Original Android Development] icu64:
Exactly why I would like to help make the kernel better where I can

---------- Post added at 07:48 AM ---------- Previous post was at 07:45 AM ----------

This the problem, it would just randomly happen after a given amount of time but I just flashed it and now it won't reboot o.o
[Nexus 4 Original Android Development] apatal:
Lol same here. I can't seem to make it reboot now. Haha.

Well, just keep your file explorer and pastebin app if any, handy just in case you get the reboot so you can extract the last_kmsg and share it here and with [MENTION=4203114]mrg666[/MENTION]. I'll do the same. :)
[Nexus 4 Original Android Development] icu64:
Will do bro
[Nexus 4 Original Android Development] apatal:
Oh I forgot, I've switched to ART last night, so not sure if that helped with the reboots,, but so far none yet. :)
[Nexus 4 Original Android Development] icu64:
Well I'm on dalvik and so no reboot, after downloaded the file again and flashed it everything seems to be OK
[Nexus 4 Original Android Development] mrg666:
If the kernel is stable with the standard kernel and oc is rebooting, then your CPU is not stable. The other kernels cannot be stable either at the same voltage levels. My voltage profile are completely reconfigured and your ov settings in other kernels do not correspond to the same voltage profile in MiRaGe. All this said, please post last_kmsg after one of your reboots I will check.

BTW, undervolt at a single value is not an accurate description since CPU voltage is not a single value but a set of values at each possible frequency. CPU can crash at any of those frequencies not necessarily at the highest frequency. The base voltage profile settings in MiRaGe is different. So the same voltage change will give different voltage level. I had posted those voltage profiles earlier in this thread, just search.
[Nexus 4 Original Android Development] mrg666:
I will add the voltage interface and the oc frequencies in the standard kernel. It will be the standard kernel at the default settings, but oc and uv will be possible. I think the kernel builds will be easier for me this way.
[Nexus 4 Original Android Development] icu64:
Thanks bro, actually its been pretty stable after I downloaded your kernel again and flashed it so I think I just have a bad download ._.
[Nexus 4 Original Android Development] defconoi:
after testing autosmp in my kernel, it seems that it scales to cpufreq_up allot when idle, was watching the cpu scale on kernel tweaker and all 4 cores get stuck at cpufreq_down and cpufreq_up, is there any way we can get it to offline cores and save battery when idle while being less agressive at scaling up when not needed?
[Nexus 4 Original Android Development] mrg666:
I don't think you can get a good idea by watching the kernel tweaker since the tweaker polls the cpu data at a much smaller rate than the cpu governor polling the load. You can't increase the polling rate of tweaker at the same level since tweaker loads the system itself in that case. But if you want to adjust the aggressiveness, you can increase the cpufreq_up parameter in sysfs. With autosmp, additional cpu cores are plugged in only when cpufreq governor detects high load. Either your cpufreq governor is not efficient or there is a background process loading your device.
[Nexus 4 Original Android Development] Tommy-Geenexus:
[MENTION=4203114]mrg666[/MENTION]

Just saw you are using gzip compression.

Is there any specific reason for that?
[Nexus 4 Original Android Development] mrg666:
I didn't bother changing it. Gzip is the default with the highest compression ratio and the slowest decompression. But the difference in decompression time is just a couple of seconds at most during the boot time and the compression method doesn't matter at all once the kernel is decompressed during boot. So I prefer the better compression and smaller image size. Please let me know if I am missing something here.
[Nexus 4 Original Android Development] Tommy-Geenexus:
Thanks.

I'll try it and see how gzip works on the yuga.

Edit: it works fine(better than XZ), i'll use this.
[Nexus 4 Original Android Development] mrg666:
Kernel Friday!

- Linux 3.4.103

- hwrng and crypto updates/fixes from Linux 3.16

- user-space cpu voltage control enabled in the OC kernel.

Changes are in the repo as always. Take a look if you want.

Enjoy!
[Nexus 4 Original Android Development] xenyz:
Woohoo, new kernel!

From what I gather in the repo, the OC kernel boots up with your custom OC freqs and VDD curve still, right? Any chance of stock frequencies and voltages by default? My device can only handle -75 mV, so I won't be able to get to the point of using the voltage control.
[Nexus 4 Original Android Development] mrg666:
Correct. OC Kernel will boot up with my default undervolt. I didn't want to give the overclock option without lowering the voltage to a somewhat safer level since N4 overclock is not viable without undervolting to avoid too much heat. Regarding your CPU which cannot handle even a slight undervolt, I am sorry to say, overclocking is not worth trying.
[Nexus 4 Original Android Development] TheNerd:]:
Semaphore undervolt? And what app do you recommend to control the voltage?
[Nexus 4 Original Android Development] mrg666:
I didn't understand this?

All of the available apps should work.
[Nexus 4 Original Android Development] TheNerd:]:
Semaphore has a different kind of undervolting. It divides the set of frequencies into two parts, high and low. You can't individually set voltages for the frequencies. The halves have to undervolted as a whole. For example, I designate every frequency above 1.35 GHz as a high frequency and every frequency below a "low" frequency. I can only choose to undervolt the halves as a whole. I can't undervolt 1.5, 1.4, 1.35 frequencies individually; I can only choose to undervolt the whole half? I'll see if I can find a picture...

---------- Post added at 10:03 PM ---------- Previous post was at 09:58 PM ----------
[Nexus 4 Original Android Development] Fenvarien:
With MiRaGe I can undervolt every frequency step individually now, that's great! Currently I'm using Trickster to set the voltages.
[Nexus 4 Original Android Development] Almayce:
I must say this kernel is great, had two cycles so far on the newest and getting 4 hours of sot on 16-20 hours of uptime. Mostly WiFi, tapatalk, messenger, browsing and even gaming for almost an hour(bards tale if anyone is interested, very very good game considering it's on the phone, playing with moga pro though. I wouldn't enjoy it as much with on screen controls). I was kinda bummed that uv didn't make it to the regular kernel, as I'm slow binned I can't boot the oc one, BUT I think there is no need for it seeing the results(temp never got higher than 50C)

So to conclude, sorry for long post, with great simplicity comes great satisfaction(who's gonna "c Wat I did ther"? :D). Keep up the good work, man!
[Nexus 4 Original Android Development] ForMartha:
[MENTION=4203114]mrg666[/MENTION]

I have a noob question, hopefully I won't get busted because of that,

Well, It seems that every new build is using a newer Linux kernel, why you'r using a newer version? the kernel fixes added via the newer kernel or by modding it ?

thanks once again for evolving it :)
[Nexus 4 Original Android Development] Fenvarien:
Additionally to the work, coding and modifications by mrg666, he syncs the code with the releases of the Linux longterm kernel 3.4.x. The changelog for those patches is here:

https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.4.103
[Nexus 4 Original Android Development] mrg666:
Fenvarien replied before me. I don't use version numbers, the build date can be considered as the version number for MiRaGe. The kernel version only determine the 3.4 patch level. I squash the official 3.4 patches into a single commit since the official changelogs are available and it is easier for me to apply a single commit. However, the official 3.4 patches frequently don't apply directly to MiRaGe since MiRaGe has so many components backported from the later kernel versions (3.8, 3.12, 3.16 ...). Many times I have backported some of the commits in the official kernel weeks/months before the official patches. Many of my backports will never be included in the official 3.4 source which is expected and understandable. You can see the summary of changes in the OP or check the repo for details.
[Nexus 4 Original Android Development] criminalzen:
thank you very much for this explanation... there is a sort of arms race going on in some xda nexus kernels .. this helps me understand what see in gits ..
[Nexus 4 Original Android Development] mrg666:
Being an ordinary and quiet xda member, I am completely unaware of the arms race :angel:
[Nexus 4 Original Android Development] snak3ater:
You are quiet but not Ordinary..lol :eek:
[Nexus 4 Original Android Development] ChaosChris:
New Anykernel-MiRaGe builds are uploaded (20140818) grab them here :)
[Nexus 4 Original Android Development] ForMartha:
well,

after using it for more than a week I can say that there is a major GPS issue (lock time takes ages & the GPS is locking/unlocking all the time).

[MENTION=4203114]mrg666[/MENTION] - Can I upload something in order to assist to fix it?

thanks :)
[Nexus 4 Original Android Development] smoka206:
I don't think this kernel is doing it. I have been using it with no issues whatsoever, GPS locks right away. Maybe you need to start over and return to stock and try again. It has helped me with issues in the past.
[Nexus 4 Original Android Development] ForMartha:
on an the version before 15/8 it worked fine :/
[Nexus 4 Original Android Development] xenyz:
It could be a clock (timing) issue. If your network time is off or incorrect, you're gonna have problems. [MENTION=4149362]ForMartha[/MENTION] if you're rooted, look up an app called FasterGPS (time) and GPS Toolbox (AGPS data) to help speed things up.
[Nexus 4 Original Android Development] mrg666:
That is not a kernel problem. Please check xenyz's suggestions before my post.
[Nexus 4 Original Android Development] mrg666:
New MiRaGe builds are available in the OP.

- Android logger disabled (thanks to ak). I like the ability of disabling this busy log. You can enable with

echo 1 > /sys/module/logger/parameters/log_mode

and disable again with

echo 2 > /sys/module/logger/parameters/log_mode

- many other itsy-bitsy fixes/updates/cleanups, please see the repo

Everything seems to be still in order to me. Please post if you find something :)

Enjoy!

______________

Just a quick note:Today's last commit for autosmp is not included in today's build since I am still testing it. I will include it in the next build if testing result is okay.
[Nexus 4 Original Android Development] ForMartha:
downloaded and installed yesterday, the GPS was fixed. (but, as you said before it dosnet concerns the kernel).

one other thing (that you already know about) - is there any way to make a better sample rate for the light sensor in order to reduce battery drain? - one last thing, it seems that the phone is hot (like always), any idea how to keep it cooler?

heat issue (that causes slow downs) and battery life extender should be in consideration if you got the time and patience for it (if is there anything that i can assist with, please let me know)

thanks once again mate, you make a fantastic job.
[Nexus 4 Original Android Development] mrg666:
MiRaGe has improved heating considerably compared to stock kernel. But the N4 CPU heats up quickly to begin with. Please check the repo and search this thread to see what has been done to reduce heat. You can post if you have any new ideas. I am not sure what you mean about the light sensor.
[Nexus 4 Original Android Development] Fenvarien:
[MENTION=4149362]ForMartha[/MENTION]

Heating has improved here very much with MiRaGe although I oc'ed to 1728 MHz. Overclocking comes to a certain price of course, but this can be countered by undervolting. All depends on the piece of hardware you actually have and how experienced you are with oc & uv.
[Nexus 4 Original Android Development] ForMartha:
thanks for the replay,

please take in consideration that i'm not using the OC version. meaning that the heat still exsits on the regular one. I will try to do the things that are mentioned on the OP in order to reduce the heat.

thanks once again.
[Nexus 4 Original Android Development] pachwald:
Hi!

I installed the kernel from the 23d and after a reboot, Google Now Launcher's home screen went black and reshowed constantly. I downgraded to the previous version and everything is fine again.

I will investigate further when I am back home.

Cheers!

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] aviz1911:
Flashing a kernel update and launcher goes black ?? I don't think that's a kernel related issue. Try to wipe cache/dalvik before and after flashing the latest mirage and see if the problem is solved :good:
[Nexus 4 Original Android Development] defconoi:
This happens to me too after dexopting on a new flash, reboot once and its fixed.
[Nexus 4 Original Android Development] migueldbr:
i have a Faster binning (4) cpu and the oc kernel does not go past the boot screen...shouldnt my cpu be able to boot it?=/
[Nexus 4 Original Android Development] DontPushButtons:
Does the standard kernel boot fine for you?
[Nexus 4 Original Android Development] derking1:
So this kernel is only good for stock eh? How's the battery life? Good for xposed?
[Nexus 4 Original Android Development] migueldbr:
it does...
[Nexus 4 Original Android Development] mrg666:
This is unrelated to the kernel. If you are wiping cache or dalvik-cache, it could happen because of that. It is not needed for a kernel flash.

No. This has been discussed several times already. In short, faster bins are already running at their lower voltage settings. Your cpu cannot handle more undervolt than it is already using. Use the standard kernel .... see below.

==================

Everyone, I will add the overclock frequencies to the standard kernel so that people can start at default and try overclocking from the standard settings. And, I will call the OC kernel UV kernel in the next build. Is this okay with everyone? BTW, to be consistent, the standard kernel will be running at 1566 instead of 1512 by default. I think this shouldn't be a problem for all cpus.
[Nexus 4 Original Android Development] migueldbr:
oh i see...so my cpu already comes undervolted from the manufacturer?I thought that the original voltage was the same to all nexus 4 but being a faster bin made it able to lower the voltages without problems=p.thanks for the explanation!
[Nexus 4 Original Android Development] Fenvarien:
That's a very good decision IMHO! More choice and options for everyone and less questions. ;)
[Nexus 4 Original Android Development] mrg666:
The new builds are up in the OP.

- Atutosmp now consistently scales the hotplug thresholds with changes in the maximum cpu frequency (over/underclock).

- Enabled the overclock frequencies and voltage control in the standard kernel. Now the only difference between the two builds is ~100mV undervolt in the OC build.

Please let me know if you find any problems.

Cheers!
[Nexus 4 Original Android Development] mrg666:
I am planning to remove interactive governor and f2fs. These features are not needed and used, I think, by anyone. Please post here if am missing something.
[Nexus 4 Original Android Development] defconoi:
Id keep interactive and f2fs, for whatever reason this f2fs didn't even work in my kernel, had to redo f2fs completely and got it working, check my commits. Also F2FS is pretty fast, I was hesitant on even having it on in my kernel but now multirom supports it and it was easy.
[Nexus 4 Original Android Development] apatal:
Sounds good to me.