yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Hoochie_Coochie:
Sorry you're right

I've the flicker on the oc kernel on slimkat 4.0 used it for a couple of days

But I've just moved to F2FS Mirage kernel bit of flicker still so don't know which one is used for this kernel. So I don't expect you to support that kernel

I've a slow bin chip
[Nexus 4 Original Android Development] ihancioglu:
Hi All,

I have decided to make Mirage with additional features. I think there is no activity on the Oasis anymore as developer sold his N4.

http://xdaforums.com/nexus-4/development/kernel-maya-kernel-t2694021

If you need Mirage with additional features just use it.

I will try to make it always up-to-date.

Thanks [MENTION=4203114]mrg666[/MENTION] for this kernel

.
[Nexus 4 Original Android Development] passlogin:
No it's not what you think.

I'm suggesting a way to reproduce such screen flicker.

When the C1 state flicker is under effect, it is guaranteed it will flicker, but it's not it will not.

Will try to merge, recompile, and report!
[Nexus 4 Original Android Development] Kaka88:
I want to ask something..

Is the OC version Undeevolted by default?

Since i have semaphore manager (just for gamma settings and dynamic hotplug). Theres an option to undervolt, but no undervolt parameters shows (default undervolt) and it makes me confuse..
[Nexus 4 Original Android Development] Swords.Grizzlebee:
Yes, it's undervolted by default. You probably can't see it in Semaphore manager because it is locked at -100mv and isn't able to be changed (I think).
[Nexus 4 Original Android Development] Kaka88:
Thanks man!

And does dynamic hotplug works anyway?
[Nexus 4 Original Android Development] Swords.Grizzlebee:
I don't think so, this kernel uses autosmp (created by mrg666). You could try changing some settings with it and see what happens but my guess is it wouldn't have any effect.
[Nexus 4 Original Android Development] Kaka88:
I think so, because it didnt have effect in benchmark..

I hope someone could tell me exatcly if the dynamic hotplug working or not..
[Nexus 4 Original Android Development] DrummerMuppet:
[MENTION=4203114]mrg666[/MENTION] already answered this question a couple of pages back:
[Nexus 4 Original Android Development] Fenvarien:
The new kernel release works just fine here and without any flickering problems. Standard MiRaGe version with Purity ROM 22/3/2014 build. :good: :)

disce aut discede
[Nexus 4 Original Android Development] Kaka88:
Thanks for the answer.. :)
[Nexus 4 Original Android Development] mrg666:
It seems to me all the answers are given and nobody needs more help. Thank you everyone!

I will add your kernel in the OP of MiRaGe, thanks for the development!
[Nexus 4 Original Android Development] SeanInToronto:
Thanks for this excellent kernel! I switched from Hells Doctor to your kernel because I was experiencing freezes, and your UV/OC edition is perfect. Extremely good idle battery consumption.

A small feature request, if I may? The only thing I miss from my pervious kernel is the ability to fool my USB charger into thinking it is an AC charger, allowing me to get the full 1A from my charger, as opposed to 500mA.
[Nexus 4 Original Android Development] exen1986:
Do you suggest kernel setting for Trickster Mod or default settings are enough? I need more battery life.
[Nexus 4 Original Android Development] iCole:
I hate to be the party pooper, but I'm noticing flicker (roughly 40% of the lower part of the display turns black for a milisecond or so at random times) with both the standard and OC 040214 kernels (happened on the previous 032814 versions too) .

Anything I can do to help debug this?

I'm on a stock 4.4.2 ROM (just rooted), ART enabled and if I remember correctly, my CPU is binned to "Fast".

Otherwise both regular and OC versions of your kernel seem to work great on my device, except for the flickering.
[Nexus 4 Original Android Development] jimyiak:
flash latest gpu drivers to see if that helps..

http://xdaforums.com/nexus-4/general/qualcomm-adreno-gpu-binaries-t2667759
[Nexus 4 Original Android Development] iCole:
Hah, I did actually think of the drivers right after I made the initial post. Flashed them, will report back later if I get flickering or not.
[Nexus 4 Original Android Development] Lord_Baal:
No Flickering Reported on PA 4.2 Beta 3 with the new OC version.

Will keep Updated.
[Nexus 4 Original Android Development] Bladyle:
Same here exsept i'm not on ART
[Nexus 4 Original Android Development] chewu.pg:
This is awsome kernel !!! Very pleased and i am using it only 2hrs :) Keep up amazing work... Benchmark scores are crazyy 1930 multicore on geekbench and 24000 antutu... Just cant belive, real miracle ;)
[Nexus 4 Original Android Development] chewu.pg:
Just one thing, i know you dont prefer sound engines but could you just cherry pick hedphone volume boost from franco which is btw really good...viper4and is rly not that much of an improvment and i love strong sound ;)
[Nexus 4 Original Android Development] DontPushButtons:
I recommend going to the modded mirage kernel in the android development forum (I believe there's a link in the OP) and request it in that kernel thread. As you stated, [MENTION=4203114]mrg666[/MENTION] has made it pretty clear how he feels about adding sound mods.
[Nexus 4 Original Android Development] chewu.pg:
I know,i know:) Kernel lacks only that mod cause all other features are kinda not needed :) I dont like to requests, will respect mrg666 decision ;) just wanted to point that out
[Nexus 4 Original Android Development] DontPushButtons:
Personally, I'd love to see faux sound, so I know where you're coming from. You could also set up a build environment and learn to compile his kernel and cherry pick what you want. I know both [MENTION=4203114]mrg666[/MENTION] and [MENTION=4128576]bedalus[/MENTION] are both incredibly helpful with getting people started if that's something you'd be interested in.
[Nexus 4 Original Android Development] chewu.pg:
Actually i know java and somewhat c++ but actually know nothing about kernels :D
[Nexus 4 Original Android Development] DontPushButtons:
Only one way to learn!
[Nexus 4 Original Android Development] chewu.pg:
Heat up a chair :)
[Nexus 4 Original Android Development] passlogin:
Here's one mrg666. This is more tweakers kernel.

I've made my kernel based on mirage's but I'm not ready yet to make my own thread due to school life.

May I upload mine in your thread mrg666?

Features:

AOSP based. Anykernel based

-synced with Mirage's source at the time of complication.

-reenabled disabled governor and iosched (for 'as close to stock' reason)

-PA Halfbreed

-kexec

-fauxsound

-fauxgamma

-bedalus's bus speed hack
[Nexus 4 Original Android Development] mrg666:
As I stated in the second post, please don't upload the kernel here because the simultaneous feedback for two different kernels in the same thread will be too confusing for everyone. Just start a simple thread with your source, changelog, and binary. You can work on the OP later.
[Nexus 4 Original Android Development] nibla101:
THIS is all I need :victory:
[Nexus 4 Original Android Development] mrg666:
Sound boost has been already done several weeks ago. If you can't notice the difference why are you asking for it?
[Nexus 4 Original Android Development] jawz101:
I just started using viper4android and it's actually really awesome if you use the input response profiles people have made. Anything profiles with "tube" in the name changed my sound completely
[Nexus 4 Original Android Development] chewu.pg:
Oh wait i just saw sound control in trickster cool!!! Sry for the fuss
[Nexus 4 Original Android Development] passlogin:
http://xdaforums.com/nexus-4/development/mirage-aosp-4-4-2-naruka-kernel-t2706668
[Nexus 4 Original Android Development] xenyz:
Didn't this make it into MiRaGe already?
[Nexus 4 Original Android Development] droid_legacy:
Hey guys. MIght it be suggestive to add a kernel version (stock clockspeeds) but undervolted. If I got OP right, just the OC version is underclocked due to heat problems.

I know it's up to which chip is buid into phones but I think -100mV should be working for everyone and might save some battery and reduces heat.

Just my two cents.

Really appreciate your work!

:highfive:
[Nexus 4 Original Android Development] RolF2:
no, OC kernel is not underclocked - it's undervolted by -100mV and slightly overclocked (1.566 GHz) by default :
[Nexus 4 Original Android Development] droid_legacy:
I should learn to read properly. Thanks anyway!

Scumbag me! :D
[Nexus 4 Original Android Development] mrg666:
Yes, with a twist :)
[Nexus 4 Original Android Development] SeanInToronto:
6h 20m SOT on the OC/UV kernel with Wi-Fi and the radio on 2G, using the default max clock of 1.566 GHz. Hells Doctor gave me closer to 7h SOT, but it had freezing and random reboots issues, of which Mirage has none. Pleased so far!

I guess it's important to mention that I have Google Now and location reporting disabled, and my wakelocks are minimized using Greenify.

My device is awake during idle 3 - 5% percent of the time. Idle battery drain using this kernel is <0.5% per hour.

My chip is also binned nominal, but able to handle the undervolt just fine.
[Nexus 4 Original Android Development] haget83:
Any tip to solve screen flickering?

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] DontPushButtons:
Try to provide a little bit more information for debugging. What version of the kernel, what rom, and what are you doing when it happens?
[Nexus 4 Original Android Development] haget83:
Screen flickering happens since about 23 March build. I had same problem using semaphore months ago. I dont know how replicate, it happends on whatsapp, Chrome, SwiftKey, apex launcher home, Tapatalk .Im always on slimkat

There is something in common with semaphore and mirage that cause This problem to me

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] mrg666:
Can you please try the following test build and let me know if it fixes flickering?

http://www.mediafire.com/download/v2kan8qycf1j4sl/MiRaGe_mako_test_kernel_KOT_040514.zip
[Nexus 4 Original Android Development] haget83:
Got flikering in bottom part as soon as I open play store to update apps, after clean install and restore from titanium backup.

Did u made some change in GPU?I cant see GPU setting in fauxclock now.
[Nexus 4 Original Android Development] mrg666:
Yes I reverted one commit in the kgsl driver. You don't need to do clean install and restore. Just flash the kernel and reboot. Plus, at least while testing, please uninstall the kernel tuning apps. I will post another test kernel tonight with another commit reverted.
[Nexus 4 Original Android Development] haget83:
i got this problem on about 20 March, after introduce semaphore gamma interface if i well remeber . Could This cause My problem uhm.. I have to try each previous version and check when The problem start.. Where i can find previous versions? Did u have 031314 version and Next?

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] mrg666:
Here is the next test kernel. Please post if it helps. Just flash and reboot without wiping anything and also uninstall all kernel tuner apps at least for now.

http://www.mediafire.com/download/ax0qsr8juvf6yp0/MiRaGe_mako_test_kernel_KOT_040614.zip
[Nexus 4 Original Android Development] haget83:
what did u do?

im' testing but seems

for now

all works perfect!!
[Nexus 4 Original Android Development] mrg666:
Please keep testing without changing anything. If you can confirm that the flickering is still fixed after more testing, I will post the kernel in the OP tomorrow. I hope others can test too.
[Nexus 4 Original Android Development] SeanInToronto:
I don't think I've experienced any flickering with the current stable release.. can someone describe to me what this flickering looks like?

The only thing that I have noticed is that when I open the Facebook Messenger app sometimes, my screen flashes red for a brief moment before loading the app. I would say it flashes red for less than half a second, is this the flickering people are talking about? I only experience this with the Messenger app, although I do not use my phone for gaming at all.
[Nexus 4 Original Android Development] mrg666:
Very few users are having the problem and you would know if you had it. Let's not get into app-specific little glitches.
[Nexus 4 Original Android Development] haget83:
[MENTION=4203114]mrg666[/MENTION] always the same problem, screen starts flickering after a bit =(

let me try another rom, tomorrow i try this on google stock
[Nexus 4 Original Android Development] Bladyle:
it's not ROM related. I'm using stock and excluding this problem this kernel is very good
[Nexus 4 Original Android Development] clockworkstop:
I tested the latest test release and there is no flickering. Will report any issues, but I don't see them coming up.
[Nexus 4 Original Android Development] mrg666:
I will try to put another test kernel when I find time in the following days. This flickering thing is so strange and I am shooting in totally dark. Let's see
[Nexus 4 Original Android Development] mrg666:
Here is the next test build. Please test for flicker and let me know.

http://www.mediafire.com/download/s3hhaj937zesg9w/MiRaGe_mako_test_kernel_KOT_040714.zip
[Nexus 4 Original Android Development] passlogin:
mrg666, can you add my kernel to your OP?

Since GitHub already up.
[Nexus 4 Original Android Development] snak3ater:
I see you have your own thread...

it's totally up to [MENTION=4203114]mrg666[/MENTION] but i think it's better to keep 2 threads separate & not to mix them...It would just confuse all other users..

Just s suggestion :)
[Nexus 4 Original Android Development] haget83:
looks like i have no flicker problem using naruKa kernel, which derived from Mirage,

I stay on naruKa for now :good:
[Nexus 4 Original Android Development] passlogin:
Its done.

I want to list my kernel own his op.
[Nexus 4 Original Android Development] aproape:
I can confirm that the flickering is still fixed.
[Nexus 4 Original Android Development] clockworkstop:
[MENTION=4203114]mrg666[/MENTION] what do you think about this f2fs stuff that everybody's using nowadays
[Nexus 4 Original Android Development] apatal:
I really doubt that "everybody" is using it. I don't. I can't really connect the term "flash friendly" with something that needs a lot of compliance from a lot of devs to work. I'm flashing stuffs on my phone just fine without errors before all this F2FS hullabaloo. It can't get any "flash friendly" than that.

EDIT: OK so I've finally had a chance to read some more on this and it looks like it may have it's advantages. Whether it will gain traction though is something we still to need to see.
[Nexus 4 Original Android Development] mrg666:
I have looked into that. But there were several problems and I decided not to include it. First, data and system partitions need to be reformatted with f2fs. This breaks the compatibility with stock ROM completely and official updates cannot be directly applied anymore. The f2fs file system also requires special recovery which is another complication. Second, f2fs is still considered beta software and comes from Samsung. I know how bloated their kernel sources and Android implementations are. I simply don't trust that Samsung can develop anything optimized and efficient. I don't think it is worth considering the risks and complications. I will stay away from f2fs at least until Google stops supporting N4. When I start building Android for N4, I will reconsider f2fs.
[Nexus 4 Original Android Development] xenyz:
For those who don't know, there is one dev who is compiling MiRaGe with f2fs support here. It's a few releases behind, but I hope he tries to keep it in sync for those who use this kernel and also use f2fs.
[Nexus 4 Original Android Development] diogo.sena:
lol, It's flash as in flash memory, not as in flashing stuff

Enviado de meu Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] apatal:
haha. i know. i was trying to pun it out, if you know what i mean. :)

i just mean, i don't think using a new filesystem type would really affect the way our phones perform, and that i had doubt on whether it was worth it. again, i said those things before i read about it some more. as [MENTION=4203114]mrg666[/MENTION] said, it seems to have it's advantages, but the barrier to adapting it outweighs the advantages...for now.
[Nexus 4 Original Android Development] howard bamber:
Problem maybe having it on interactive. On other kernels in the past that setting went up and down all the time, draining power

Sent by mobile telephone.
[Nexus 4 Original Android Development] mrg666:
I did some mild overclocking (1.728 GHz) and undervolting of the CPU. Please let me know how it goes if you test the kernels below. My phone (which is a fast bin) is completely stable after my initial testing but I will not include this in the stable kernels until they are extensively tested.

http://www.mediafire.com/download/x43o7bej2us46mn/MiRaGe_mako_test_kernel_JWR_102113.zip

http://www.mediafire.com/download/m8yk1ncczeh9rir/MiRaGe_mako_test_kernel_JSS_102113.zip

Don't use these kernels as your daily when you need a stable phone.
[Nexus 4 Original Android Development] nibla101:
You mind building a test with sound patches? I'm going on a trip for a few days and I need a stable setup and I always listen to music when I travel :)
[Nexus 4 Original Android Development] mrg666:
Check this out and let me know. I hope JWR is okay.

http://www.mediafire.com/download/xdixt32eua4dp3v/MiRaGe_mako_testsound_kernel_JWR_102113.zip

Sound max volume is permanently boosted. Use the volume control to make it lower if it is too loud. I don't see any benefit of using sysfs parameter to control.
[Nexus 4 Original Android Development] nibla101:
Thanks for your time, I can hear a small difference between the both. I think it has something to do with digital gain, when i'm on faux sound i always max the poweramp which controls the digital gain( I think), otherwise the sound just becomes distorted when maxed out and the limiter on my music player (Poweramp) lowers it.
[Nexus 4 Original Android Development] mrg666:
Okay, I have removed the download for now. Actually, even the default sound is plenty for me. I will leave it as it is. Thanks for checking.
[Nexus 4 Original Android Development] nedooo:
For OC it is ok and makes sense, but there are few different LCD types, I have one and my wife have other type, and friend of mine have somewhat different type. The difference is more then noticeable. Luckily even stock kernel (4.3) can change color temperature ( try trickster), so it could be sufficent, still extended gama (color) tweaking is final touch that can make different types of LCD look almost same. Thanks for your work and reply.
[Nexus 4 Original Android Development] zwodziarz:
I've tried this JWR-test kernel and my phone stuck in a bootloop at Google-kernel screen. Wiped cache before
[Nexus 4 Original Android Development] mrg666:
Thanks for testing. It seems your CPU didn't like oc. Just revert back to the stable build in the OP.

Since Nexus 4 heats up fast, higher vdd is not desirable. So I didn't increase the max voltage while increasing the max frequency to 1728MHz. This is counter-intuitive for overclocking since higher voltage is generally required for higher frequency. However, I have used the VDD profile of 1.7 GHz batch of APQ8064 CPUs. So only the 8064's which would have qualified for the 1.7 GHZ batch will be able to handle the overclock settings in the test kernel. My phone is handling the 1.7 GHz nicely.

Anyway, Nexus 4 doesn't need OC and I will keep building the OC kernel separately.
[Nexus 4 Original Android Development] sellers86:
Yes!!! Good to see you here man!
[Nexus 4 Original Android Development] norwoodesteel:
you may be on to something here.battery appears to be significantly improved [only 2 days running it]

and the watchespn app was perfect for the first time in 10 months [usually freezes 2-3 times per use]

the phone doesn't lose root but the franco updater app announces no root when you turn IT on.

still runnining your rom on my optimus v, use the kindle app in bed at night.

thanks
[Nexus 4 Original Android Development] zwodziarz:
Have a question: got this NotificationToggle app. Is that possible that it drains more battery? This thing's really usefull for me and I deleted any bloatware like google search,voice etc, got few apps like Chrome,NoFrillsCpu,RootBrowser not much there. Got Nexus4 from about a month now and I asume the battery performance was better at the beggining.
[Nexus 4 Original Android Development] howard bamber:
Which govoner /scheduler do you recommend?

Sent by mobile telephone.
[Nexus 4 Original Android Development] mrg666:
I don't use Notification Toggle app but, just looking at its functionality, it shouldn't have an impact on battery life if it doesn't do any background sync or wake locks.

Interactive and row work optimally regarding performance and battery life in my tests. I have ported the latest revisions from AOSP common-3.4 and CAF msm-3.4 kernels, respectively, and set as default in the kernel already.
[Nexus 4 Original Android Development] mrg666:
I have added the optional kernels with CPU overclocking enabled in the OP. Since CPU gets hot quickly in Nexus 4, I have also undervolted the CPU in the overclocking kernel. So, only exceptional CPUs that could have been qualified for the highest bins will work with this kernel. The maximum CPU freq is 1.89 GHz and the default CPU freq is 1.566 GHz. If you don't manually select a higher frequency than the default 1.566 GHz, the CPU will only be slightly overclocked and undervolted. So, even if you don't overclock, you might want to try the OC kernel for battery savings. If the phone doesn't boot, it means that your CPU is not able to handle the overclock/undervolt settings. In that case, just reboot into recovery and flash the stock kernel. No-frills CPU Control is recommended to set the max overclock frequency.

Each CPU has different overclock ability. Don't get disappointed if it doesn't work for you.

My APQ8064 CPU, for example, cannot handle 1.89 GHz but works completely reliable at 1.782 GHz without any heat or stability problems.
[Nexus 4 Original Android Development] sellers86:
Apparently my phone can't handle the OC and UV settings, but at the stock speeds I've noticed a slight battery improvement. Run smooth. Good job mrg, you never cease to amaze!
[Nexus 4 Original Android Development] mrg666:
Thanks, Sellers. I have done a slight optimization of overclocked vdd profiles. It is not always the highest frequency that cause instability. Sometimes, especially if the vdd levels are not distributed evenly, intermediate frequencies are also the source of instability. When I checked the vdd curves as a function of frequency, I have seen that the vdd curves were not smooth as shown in the figure below.

The dark blue curve above is the improved vdd profile and the light blue curve is the older one. You can easily see that the vdd curve dips just around 1.5 GHz when compared with the improved curve. The above figure corresponds to the fast bin and I have done the similar improvement for all bins (slow, nom, fast, and faster)

I have updated the oc kernels with these changes and this can help with stabilizing the oc for some of the CPUs. You can try again with the updated kernels if it failed before. There is still no guarantee but I just gave a little more chance for OC to succeed. Download links are in the OP.

Best of luck :)
[Nexus 4 Original Android Development] zwodziarz:
OC kernel doesn't work for me. Seems I got a ****ty phone cause any other custom kernel doesn't work as well only Yours without OC. Flashed it cause U said something about battery life improvements everything worked fine I got it at max 1,45ghz/interactive/row then I run Antutu - at CPU testing (21%) it reboots twice and changed my language set, wallpaper, wifi settings. Got another random reboot at Chrome and flashed the NO-OC one