yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] jawz101:
If I'm touching my screen with 10 fingers and a movie is playing I could get my battery to drain fast on any kernel by doing that.

The battery graph is only useful if you want to see how much your phone drains in idle.
[Nexus 4 Original Android Development] xenyz:
I was demonstrating a projected SOT of 7.5 h by showing 3 h 45 m on at half battery.

Are you trying to not so subtly say I was just leaving the screen on at the home screen and running it down without use?

What may surprise you is that I was watching some videos in a flash video player in Firefox beta, browsing reddit using Flow, forums on Tapatalk, and some web sites on Chrome.
[Nexus 4 Original Android Development] mrg666:
WOW! 3h45m SOT doing all those and 50% battery use is amazing. I was at the car service today and I had to wait two hours there. I used the phone all of that time, web surfing, gaming, etc and I used only 30-35% battery. I really like the latest kernel. Thank you for the feedback.
[Nexus 4 Original Android Development] xenyz:
Same here. I do believe its the combo of your hotplug and the newer ondemand governor. They play well with each other. :)

Have you considered back porting the latest ondemand? The messages on the kernel list have reports of even better performance and energy use. Linus seems to agree. :)
[Nexus 4 Original Android Development] mrg666:
I had backported the current ondemand from 3.8. Let me check the latest but I think it will require fixing a lot of other dependencies. I will check.

Current interactive is still my favorite though
[Nexus 4 Original Android Development] mrg666:
I was able to backport @stratosk's ondemand commit from mainline Linux 3.12. Instead of pushing the level of our code to 3.12, I have skipped some of the earlier patches and adapted the specific ondemand commit because it was going to be too much work and add some unnecessary code in the kernel. My initial testing showed the same behavior described in the commit message. The statistical distribution of cpu frequency don't accumulate at the lowest and highest frequencies anymore. Instead, mid frequencies are used more than the old ondemand and interactive giving a more uniform frequency distribution. I think the adaptation is working fine. The following is the standard kernel for your testing with the default governor set as ondemand. Please post your feedback.

http://www.mediafire.com/download/z1fju4aqkj987ht/MiRaGe_mako_test_kernel_KOT_032714.zip

I will be testing as well. If the feedback is positive, we can keep this ondemand. I will post the OC kernel after testing.

Reminder: Don't expect a quick reply from me and please be nice to each other in the thread.
[Nexus 4 Original Android Development] ramig:
On Kernel 03/25 the Battery use is amazing!

Thanks
[Nexus 4 Original Android Development] Sir_gpm:
I am using 325 version, leave the phone all nigth to see how does it deep sleep, seems that is ok, but 3.3/h looks too high for me. Or not?

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Original Android Development] mrg666:
If 3.3% per hour is while the phone is sleeping, it is too much. I am getting <0.5% per hour. There is something wrong with your confiiguration. Check the background processes, sync settings of the extra apps such as tapatalk, facebook, etc.

______________

Everyone,

The new ondemand governor in the test kernel is remarkable both in performance and battery use. There are no stability problems either. I will upload the stable kernels tonight with ondemand as the default governor. Please post until then if you have any comments.
[Nexus 4 Original Android Development] mimsiroll:
Running rastakat rom and former ak kernel user here..recommended by zenyz..battery life is the same as AK, but im not using the o.c version because it gives flickering effect and constant reboots..the latest experimental kernel works great. Anyway, is it okay if you add a color presets for faux app.. :p if it's okay..

Edited: added my pic for the sot, doing very great runs for 3.45 hrs with browsing and heavy game
[Nexus 4 Original Android Development] mrg666:
New builds are up. I only added the new ondemand governor and set it as default. Thanks to [MENTION=3118524]xenyz[/MENTION] for the suggestion and to [MENTION=3750240]stratosk[/MENTION] for his contribution to Linux.

Enjoy!
[Nexus 4 Original Android Development] stratosk:
Thank you!
[Nexus 4 Original Android Development] mrg666:
The ondemand patch is genius. It really decreases the number of unnecessary jumps in the cpu frequency. I thought at first that the performance was going to suffer but couldn't see any performance penalty either. The hotplug driver I use doesn't do load calculations itself but uses the cpu frequency to decide hotplug event as a slave to the governor. So, the new ondemand governor decreases the number of hotplug events too. Thanks for stopping by.
[Nexus 4 Original Android Development] xenyz:
Before...

...and after:
[Nexus 4 Original Android Development] TheNerd:]:
So that means more time spent on the middle frequencies and less time on the min and Max frequencies?
[Nexus 4 Original Android Development] davidsteele1975:
Maybe a little off topic but have you changed how you host the file? I can't seem to download it, it pulls in a ~88 KB file. :(
[Nexus 4 Original Android Development] xenyz:
Yes, it looks like, with similar usage it saves time at the high end and loses time at the low end, but with more mid steps. I think the savings at the high frequency are greater than the loss of the low frequency, in terms of energy use.

I can't find one thing wrong with this kernel. I think you've won the game mrg666. :)
[Nexus 4 Original Android Development] stratosk:
Thanks again!

Actually the patch achieves a little bit more performance, a little bit more power saving with less code. :)

There are several benchmark results in LKML that show the above, during the discussion of the patch submission.
[Nexus 4 Original Android Development] The Zel:
Could you make this kernel available even for non-stock roms? From how people talk about this kernel, it seems great!

N⁴
[Nexus 4 Original Android Development] fabian.m:
It will work on most AOSP (not CAF) based ROMs, the problem being many of these do have bugs so it is a lot harder to support the users, which mirage does a wonderful job at currently ;)

Sent from my AOSP on Mako
[Nexus 4 Original Android Development] criminalzen:
roms

I have been using it with no problems for the last few months with art on velocity and cfx, with psx, pslx also. Short runs with pa and slim. Has only improved over time.
[Nexus 4 Original Android Development] jawz101:
I have to agree that it has improved over time. Early on I was getting reboots but the last several versions have been stable for me
[Nexus 4 Original Android Development] apatal:
Hi guys, can someone help me please. Mediafire is giving me trouble downloading the latest non-OC version. Can someone upload it somewhere and share the link please.

Edit: never mind. Looks like the issue is with my connection. I'll try again later. Thanks.
[Nexus 4 Original Android Development] mimsiroll:
Here.
[Nexus 4 Original Android Development] Kaka88:
Ive just flashed the newest version. But i have questions..

What is igonore nice load in ondemand gobernor options? Should i enable it?

And which scheduler best in your opinion?

So far so good. I love this kernel and its giving me very good battery life!
[Nexus 4 Original Android Development] mimsiroll:
According to OP and zenyz, all settings are already being tune up ao there's no need for re -tweak.
[Nexus 4 Original Android Development] apatal:
Latest one is definitely the smoothest version I've tried. I'll report some more later. Thanks.
[Nexus 4 Original Android Development] Kaka88:
Thanks..

Ive changed the settings.. :(

Could you or somebody tell me the default scheduler and ondemand governor settings?
[Nexus 4 Original Android Development] mimsiroll:
Read the first page. Default is ondemand due to the latest build because it syncs perfectly according to OP

I/o is row.
[Nexus 4 Original Android Development] apatal:
Remove any kernel control app or at least disable it's set-on-boot option then reboot. You should be back to default settings then. :)
[Nexus 4 Original Android Development] Kaka88:
Im using set CPU, so i have to unistall it first? Allright then. Thanks..

Thanks. But i mean the governor settings like: up treshold, ignore nice loads, sampling rate.etc..
[Nexus 4 Original Android Development] Federico_96:
Good morning to everyone, I would like to install this kernel, I have only a question, can I use Francisco franco app , FKU, to control gamma settings and apply color profiles with this kernel ?
[Nexus 4 Original Android Development] hughfollett:
I think that semaphore manager is better, as this kernel uses stratosk's gamma interface..

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] Kaka88:
So this kernel also supported gamma control..

I give it a shot..
[Nexus 4 Original Android Development] apatal:
I prefer Trickster. Much more generic, and has gamma presets as well for lazy tweakers like me..
[Nexus 4 Original Android Development] mrg666:
I have just edited the first and seconds posts to reflect that latest change in the default governor from interactive to ondemand. I had forgotten that and sorry for any confusion so far. Just a small reminder that this is not a tweaker's kernel. You can, of course, do the tweaks you want since that is your phone and kernel. But please try removing your tweaks before posting any problems.
[Nexus 4 Original Android Development] apatal:
Definitely am liking the state in which the kernel is in right now. First time I've used it without feeling any jitter or UI stutter. I think you definitely deserve a break if you need it. This last one is a work of art. Really balanced. :)
[Nexus 4 Original Android Development] H-Body:
Does this kernel has support for init.d-scripts?

Looks like the perfect kernel for my needs, but i need to tweak the screen a bit. So i thought about the best way. An app, which runs in the background or an init.d-script? :)
[Nexus 4 Original Android Development] mrg666:
Thank you, apatal! Let's keep this version for a while. I was planning to update net/ipv4 and block but they will need to wait.

No change needed in the kernel for init.d support since it is done outside the kernel, in the ramdisk and ROM. I have not added init.d support since I avoid changing anything outside the boot partition. But you can add init.d support yourself. Please see the links in post 571.
[Nexus 4 Original Android Development] Kaka88:
Yes, exactly same with me..

Im just using semaphore manager just for gamma control..

This kernel juat exacly what i looking for..

Fast, simple, no need tweak, stable..

Thanks for this great kernel [MENTION=4203114]mrg666[/MENTION] :)
[Nexus 4 Original Android Development] davidsteele1975:
This. I think I was late to the party and I've had three kernel updates in a few days, but things are working beautifully now. Thanks for your hard work [MENTION=4203114]mrg666[/MENTION] :)
[Nexus 4 Original Android Development] The Zel:
With mahdi ROM, after flashing the kernel, theme manager continues FCing ? I should have expected since mahdi rom isn't stock rom

N⁴
[Nexus 4 Original Android Development] H-Body:
Didn't know that about init.d support before, thx for the lesson! :high five:

Will take a look at your post or just install any of the kernel control apps.

And thank you for this great kernel, i love this "flash and forget" mindset :)
[Nexus 4 Original Android Development] mimsiroll:
After a day of using the latest kernel..I'm very satisfied with the result having a 2hr 59mins at 60+% very decent.

Now I'm reporting the latest o.c kernel which my CPU bin is labeled 4 or fastest which OP said it's suitable for OC.

tested on AK kernel at freq 1728~210. Running smooth with UV of 75 .

Latest mirage kernel OC and undervolted to -100 if I'm correct. It doesn't fit really well on my phone, crashing at max frequency 1728 Stated on stability test app.

===

It looks like StabilityTest crashed unexpectedly or your device rebooted.

The following information were gathered right before the event occured:

cores: 4

frequency: 1674 mhz

load: 7.48

temperature: 39.0°C

# passed test runs (core 1): 2

# passed test runs (core 2): 2

# passed test runs (core 3): 2

# passed test runs (core 4): 3

# passed test runs (ram): 58

runtime: 00:03:20

system log:

emtpy

I'm really no good at tweaking and zenyz endorsed me this kernel which really suits me..I'm no fan of deep tweaks etc,

It just happened that i had an idea of what zenyz thought me on undervolting..maybe the safest that my phone could reach is -75. I'm not going to contradict your firdt post regsrding posting some tweaks, i just want to really used the O.C version..but if my phone is a big liar regarding the cpu bin then lol itsw my phones fault after all for not achieving the -100 uv
[Nexus 4 Original Android Development] hughfollett:
If you want to UV just for battery life, don't worry it won't make a noticeable difference :)

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] mimsiroll:
How? Since there's no init.d? Dunno how to make a script.
[Nexus 4 Original Android Development] criminalzen:
fc

I use cfx (codefirex) routinely which includes tmobile theme chooser and have had no fc with mirage. Suggest a problem with phone, apps, rom or its implementation of the theme chooser.. no disrespect meant to madhi-rom. I have had fc with a specific theme however... :)
[Nexus 4 Original Android Development] mrg666:
I didn't say any specific CPU is suitable for OC in the OP. You are misinterpreting due to lack of knowledge on your part. The voltage profile for each bin is defined separately, and your CPU is getting lower voltage than the others since it is highest bin. But apparently it is not able handle even lower voltage profile defined in the OC kernel. That is it.

I will not discuss any tweaking related posts, including init.d, etc since

MiRaGe is not for tweakers

.

Everyone: Please, for the sanity of this thread, can somebody, with the knowledge of building kernels, fork my repo and build a "feature-rich" kernel just like tvall did some time ago?
[Nexus 4 Original Android Development] mimsiroll:
I understand your point. Okay thanks, my bad for being unknowledgeable still a total newbie in this, but really, i apprraciate the kernel.. i really dont have any idea about tweaking. Thanks for enlightening me though. Just wanted to try the OC version. :)
[Nexus 4 Original Android Development] :
I'm happy to field questions in your thread if you're taking a break for a bit. Let me know.
[Nexus 4 Original Android Development] mrg666:
That is very kind of you and I can't imagine anybody more capable to answer questions. If you have the bandwidth, you are always welcome
[Nexus 4 Original Android Development] fluffier:
Hi,

These are my results with version KOT 032214.
[Nexus 4 Original Android Development] TheNerd:]:
Sports tracker is killing your battery
[Nexus 4 Original Android Development] fabian.m:
Was using WiFi all day. Not much left to say except: thank you mirage! :)

Sent from my AOSP on Mako
[Nexus 4 Original Android Development] Kaka88:
Hey [MENTION=4203114]mrg666[/MENTION], i think you should change your topic name to "MiRaGe for Nexus 4 Stock/AOSP". So more people will be using this kernel. Because everyone think this is for stock ROM only..

Its just my opinion anyway.. :)
[Nexus 4 Original Android Development] apatal:
I think any Android user worth his custom recovery should know by now that stock is just aosp with some proprietary additions.

If [MENTION=4203114]mrg666[/MENTION] wants to entice more users though, I suppose it wouldn't hurt to add that bit in the OP. His call. :)
[Nexus 4 Original Android Development] jimyiak:
I use semaphore manager to set color..do i have ti disable hotplug to run kernel's hotplug or it doesn't matter?

Edit...i mean dynamic hotplug in semaphore manager settings should be enable or not?

neXus⁴ running kitkat 4.4.2
[Nexus 4 Original Android Development] mrg666:
The hotplug driver in MiRaGe is autosmp and there is no other hotplug driver. Semaphore app cannot enable dynamic hotplug or disable autosmp. I think the hotplug settings are just ineffective with MiRaGe. If the app is not crashing that is good coding of the app developer. You can check with system monitor if the cores are turning off, they should be turning off and on normally.

Thanks for the suggestion. But I agree with apatal, the title is enough description. I am not really trying to increase the number of users. People should stick with that they want.
[Nexus 4 Original Android Development] Kaka88:
I think you're right [MENTION=4203114]mrg666[/MENTION].. :)

But im glad founding this kernel as [MENTION=3118524]xenyz[/MENTION] told me..
[Nexus 4 Original Android Development] davidsteele1975:
I'm ashamed to write that until now I'd never thought of it like this! ;)
[Nexus 4 Original Android Development] apatal:
Nah man, it's cool. I just learned it a few months ago. That's what I like about Android modding, the whole thing is a learning process. :)
[Nexus 4 Original Android Development] davidsteele1975:
True. That and the jargon!
[Nexus 4 Original Android Development] fluffier:
Hi, that particular day, I only used sports tracker for the last 20% of the battery life, so I doubt it killed it (as it is greenefied like most of my apps). However, I am sure the results would be better if I hadnt used. I will flash the newer kernel version and post my results without using it.
[Nexus 4 Original Android Development] RolF2:
strange, but with latest 03.28 release i first time noticed that "flickering lover part of screen" problem ... Never seen this before & i was using mirage long time before ...
[Nexus 4 Original Android Development] aproape:
Same here...
[Nexus 4 Original Android Development] xenyz:
Try running this script as root.
[Nexus 4 Original Android Development] RolF2:
C1 is disabled on all cores by default in 03.28 build, maybe new governor is not playing nicely for me... will try revert to 03.25 build ...
[Nexus 4 Original Android Development] xenyz:
Try interactive?

echo "interactive" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
[Nexus 4 Original Android Development] RolF2:
one more question about C3 - i can find /sys/module/pm_8x60/modes/cpu0/power_collapse/idle_enabled set to 1 for cpu0, but no "idle_enabled" entry at all for other 3 cores , only suspend_enabled set to 1

this is normal ?
[Nexus 4 Original Android Development] :
Yep, that's normal!
[Nexus 4 Original Android Development] mrg666:
I thought screen flickering was resolved two builds back after we disabled C1 and C2 states. I can only try to fix it again if you describe how to reproduce the problem since I don't see it. Please specify the ROM you are using and the last build that didn't cause flickering. Please also make sure that you are using the latest standard kernel. If you are using OC kernel, test with standard kernel again. I hope that all of the kernel tweaks are reverted and kernel tuner app is deleted before reporting this problem?
[Nexus 4 Original Android Development] RolF2:
I'm always using OC version of your kernel without any tweaks on stock rom ( only color profile changed ) . With 03.28 kernel I first time noticed that flickering problem when started "cut the rope 2" game (only few first steps of the game, then flickering was gone), then same problem occurred simple when browsing playstore . I reverted to 03.25 OC build and can't reproduce the problem. So I think my phone don't like new cpu governor introduced in last build... That's all I can think for now ...

P.S. one more thing - with 03.28 kernel there was one more strange behavior - after waking up my phone with power button i got unresponsive digitizer, but after pressing power button few more times got it working again ...
[Nexus 4 Original Android Development] mrg666:
That's puzzling because this is the build that received the most positive feedback so far and I don't see the problems you're describing. CPU governor is the only change after 3/25 and it wouldn't cause a problem like screen flickering. Can you try switching to interactive governor (you can easily use nofrills for that, see the link in the OP)? If that doesn't make any difference, can you try standard kernel? Based on these tests, I will see what I can do.
[Nexus 4 Original Android Development] xenyz:
If I may suggest: after a few months reading the Matr1x kernel thread (which has a -100 mV undervolt as well), a significant amount of devices have an issue with a -100 mV undervolt. The kernel dev has since decided to go with -75, so perhaps a -75 mV undervolt would be a bit safer on the MiRaGe O.C. kernel? (at least I could then run it on my device :)

That being said, in the past 4-5 days since release, I haven't had any screen problems on the normal kernel, and I even re-enabled the C1, C2 states.
[Nexus 4 Original Android Development] mrg666:
Thanks for the suggestion. For the cpus that can't handle -100mV, I am building the standard kernel. You are right that -100mv could be too much for some processors. But the cpus that can't handle the undervolt at the same time, overclock will be dangerously warm since APQ8064 heats up very quickly in Nexus4. OC kernel becomes pointless at that point since it will be constantly throttling. Let me think a little about this.
[Nexus 4 Original Android Development] RolF2:
[MENTION=4203114]mrg666[/MENTION]

OK, I'm back to 03.28 OC kernel with ondemand governor and can't reproduce the screen flickering problem with all my efforts... I'll try to play with phone little longer time and write back if something changed ...
[Nexus 4 Original Android Development] krialix:
[MENTION=4203114]mrg666[/MENTION] I had screen flickering too. So i decided to compile your OC kernel with Linaro GCC 4.8.3-2014.03 Toolchain. Now screen flickering disappeared.
[Nexus 4 Original Android Development] passlogin:
Just to want shine some light.

My hypothesis still says C1 is the culprit. However it's depending on how each kernel handles C1

I'm now running my own build of Mirage.

In CM M4, I'm using my own kernel, Hells doctor, and Ak-Xgenesis. All under all cstate enabled, and -100mv.

Only ak didn't flicker.

Getting annoyed with flicker, I flashed carbon nightly, the 20140325 if i'm not mistaken. Using faux kernel with same settings and voila! no flicker.

With curiousity I compiled my own kernel and flashed again, the result is flicker comes again, but when I turned off C1 and restarted, the flicker is gone.

P.S to test for flicker, download PPSSPP from play, open it, find a free demo over the internet, and play it. I've found this method has successfully reproduced any lower screen flickers. (I'm used to play project diva, the first one until I fed with flickers)
[Nexus 4 Original Android Development] mrg666:
Guys, I asked you to try the standard kernel and let me know if the flickering problem persists. But nobody tried. I asked which ROM you are using. Nobody specified. If you want my help, you need to help me first. Otherwise, I am fine and having zero problems here
[Nexus 4 Original Android Development] jawz101:
I haven't experienced flicker and if I did, while playing some game, I wouldn't care. Overall if my phone is running cooler my battery is lasting longer. To me that's a good trade-off. Unless my camera shows artifacts or some radio or sensor stops working I'm fine.
[Nexus 4 Original Android Development] mrg666:
I wouldn't even try to fix a problem with the PSP emulator app. If all other apps are working fine, they should fix their hardware emulator since hardware emulators are notorious with such problems.
[Nexus 4 Original Android Development] mrg666:
The suggestion by [MENTION=5178640]krialix[/MENTION] makes sense since I had recently applied some patches in kgsl driver to fix gcc compiling problems. I have updated the builds in the OP. I have been testing Linaro 14.03 since several days without any problems anyway.

Changes:

- Built with Linaro 14.03

- Linux 3.4.85

This is my best shot without the help I asked.

Cheers!