yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] Jagdish84:
Can we have a link to download section on the first post? I think a lot of us, tapatalkers, would appreciate it... Thank you in advance!
[Nexus 4 Android Development] passlogin:
Is linking to DevDB download place is enough?
[Nexus 4 Android Development] Jagdish84:
It is to me!

Cheers for the quick response.
[Nexus 4 Android Development] passlogin:
Source is up everybody, have a look!
[Nexus 4 Android Development] junxracr:
Blue colors look brown on Beanstalk rom.
[Nexus 4 Android Development] xenyz:
Nice, thanks!

Can you lower min voltage from 800 mV to something like 675 and add f2fs please?

https://github.com/faux123/mako/commit/693873aa7e6001fe07cdc6263fdeabba08f709df
[Nexus 4 Android Development] passlogin:
Well it's your rom issue, check if your rom is cm based or modify the gamma table.
[Nexus 4 Android Development] passlogin:
I thought that commit has gone into the kernel, thanks for remembering!
[Nexus 4 Android Development] Jagdish84:
I thought that was intentional, id appreciate it too :)
[Nexus 4 Android Development] beskalL:
Hello.

Is is posssible to create a separate version with only kexec-hardboot for multirom added ? (and probably bedalus bus speed hack).

I would like to use the mirage as original as possible with multirom

Thank you
[Nexus 4 Android Development] haget83:
Everything works good for me. I have a flickering problem using mirage, but look like this kernel works correctly for me. But i have the feeling Niruka looks less fluid and responsive than mirage uhmm

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Android Development] xenyz:
ondemand governor settings are different for some reason. Try setting sampling_rate to 10000.

echo "10000" > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate

Edit: also you have to set GPU governor as well:

echo "simple_ondemand" > /sys/devices/platform/kgsl-3d0.0/devfreq/kgsl-3d0.0/governor
[Nexus 4 Android Development] passlogin:
Less fluid is probably because of the bedalus's bus speed hack, it requires a touch boost which autosmp (seems) doesn't have one.

Sorry but I won't compile another one since I need to maintain with MiRaGe source as well.

I think I've done nothing to governor settings uhm...
[Nexus 4 Android Development] passlogin:
If you didn't aware, a new version is up! Check the OP for information.
[Nexus 4 Android Development] xenyz:
Woohoo, an up-to-date MiRaGe with f2fs support! Thanks!

Edit: OP, check out this brilliant method for easy f2fs changes to fstab. It looks like the author is fine with others using his script.
[Nexus 4 Android Development] xenyz:
Ondemand sysfs:

ignore_nice_load
io_is_busy
powersave_bias
sampling_down_factor
sampling_rate
sampling_rate_min
up_threshold

MiRaGe ondemand:

0
0
0
1
10000
10000
95

naruKa ondemand:

0
1
0
4
50000
10000
90
[Nexus 4 Android Development] passlogin:
After comparing commits, the only culprit that I can found is MiRaGe's ramdisk, since naruKa has only zImage.

I don't know if [MENTION=4203114]mrg666[/MENTION] has changed the ondemand defaults from the ramdisk like AK kernel.

I will do some testing later by flashing naruKa on top of MiRaGe boot.img

EDIT:

Please examine the attached file below, it is from MiRaGe ramdisk and hence why naruKa's ondemand and MiRaGe's are different.

naruKa's ondemand settings depends on each rom's ramdisk, while MiRaGe's ships with it's own.

look for lines that starts with #
[Nexus 4 Android Development] xenyz:
Here's what I got on my last charge. 100% wireless and a dim screen, but a lot of browsing and redditing. I did tweak the kernel as well. I'll post my config in a bit.
[Nexus 4 Android Development] passlogin:
In any time on my mako history, I never got battery life like that, even with my own kernel.
[Nexus 4 Android Development] Jagdish84:
With a pretty bad signal for a good amount of the time... I think all these high screen on times are achieved by by using the phone straight not letting it be idle too much...
[Nexus 4 Android Development] sidnoit22:
MONSTER BATTERY :eek:
[Nexus 4 Android Development] passlogin:
I had 5.3% drain on mobile network with phone untouched.
[Nexus 4 Android Development] pancham7:
Pls post your kernel tweaks
[Nexus 4 Android Development] passlogin:
A new version is up! Do read the OP carefully this time before you flash
[Nexus 4 Android Development] mimsiroll:
F2fs support right? Just clarifying the term in first page which is f2fs merge?
[Nexus 4 Android Development] passlogin:
Yes it is.
[Nexus 4 Android Development] mimsiroll:
Whats the read/write code?? For zenyz script to run on boot? I forgot :) im using es file and hacing hard time copy pasting those codes and re- editinf
[Nexus 4 Android Development] xenyz:
755 or rwxr-xr-x with owner/group root.

OP, new MiRaGe release today!
[Nexus 4 Android Development] passlogin:
I will merge that when I feel better
[Nexus 4 Android Development] senthilrameshjv:
Looks like color profile is not from mirage. How do I set iPhone color profile with trickster
[Nexus 4 Android Development] passlogin:
Someone put a script for that on page 4
[Nexus 4 Android Development] passlogin:
R7 is going up merged with that changes, check the op
[Nexus 4 Android Development] mimsiroll:
My phone's getting severe lag and uber slowness on boot .reverted back to ext4
[Nexus 4 Android Development] xenyz:
Did you happen to be using that 00kernel init script I posted? After testing for a while, I found the ignore_nice_load, while handy for battery life, was not the best for performance. I'm trying a few more things to balance it out at the moment.
[Nexus 4 Android Development] mimsiroll:
I'm not using any script xenyz, i had encounter a problem after reverting back to ext4 got a password after boot so my data got corrupted, i got no choice but to reformat my phone back to original stock and then re customized then tried r7 but severe lagging at the loading screen of purity latest version. Then after getting at the homescreen..it went black but i can still use the hardware buttons to flash new kernel, using the oc mirage kernel.. Perhaps the f2fs made it conflicting?
[Nexus 4 Android Development] passlogin:
F2FS stuff is beta stuff i don't dare to use it now.
[Nexus 4 Android Development] mimsiroll:
Yeah, me too..not gonna use till nexus 4 has lost its support.
[Nexus 4 Android Development] dxxvi:
I'm waiting patiently for this kernel to have s2w.
[Nexus 4 Android Development] mimsiroll:
I saw the problem..after boot my phone was running yo the lowest frequency at min and max 380-162mhz

Haven't tried the r4 but it worked flawlessly on f2fs but still going to try at ext4

.
[Nexus 4 Android Development] passlogin:
On last few days, I'm getting unproductive, since I'm not longer using gitg and now will be using git-gui and will take some time to learn it.
[Nexus 4 Android Development] passlogin:
As it turns out, while it doesn't sports a good ui. It's simply the overpowered Git Gui I've ever encountered!

S2W has made it's way to the source code, but it's not pushed yet.
[Nexus 4 Android Development] xenyz:
Time to sync with MiRaGe again? He made a few changes to autoSMP and GPU I believe.

Best of the best kernel here. :)
[Nexus 4 Android Development] passlogin:
R9 is being uploaded with many new changes.

See OP.

Edit: it's R8
[Nexus 4 Android Development] Jagdish84:
Couldn't find the changelog :-\
[Nexus 4 Android Development] xenyz:
There's a problem with the hotplug driver in R8: It looks like it's missing :)
[Nexus 4 Android Development] passlogin:
Is that the logcat spam problem?

Edit: Okay, I'm so clumsy to enable the config.

Will be fixed in the next release
[Nexus 4 Android Development] xenyz:
Why switch to bricked mpdecision? Wasn't autosmp supposed to have improved on it?
[Nexus 4 Android Development] passlogin:
bricked ramps to 918khz which is over the minimal moob suggested for his bus speed hack.

Edit: it's also more configurable and shipped with msm_thermal since there is no thermald
[Nexus 4 Android Development] Jagdish84:
Sorry for the double post... Stupid tapatalks fault! Did you merge mrg666 latest top commits?
[Nexus 4 Android Development] passlogin:
R9 is out, do aware this is the last release for sometime because school exam is coming up.

As usual, read the changelog.
[Nexus 4 Android Development] nedooo:
Thanks for GPU OC, I'm switching to this if no issues are detected :)

Thanks again :)
[Nexus 4 Android Development] xenyz:
Ran R9 all day today, works well. I don't know about that 27 MHz step though, I think Nexus 4 is too busy at idle for it. OTOH, it seems to be OK with 135 MHz so maybe that's a good new low step for me.

Thanks for the update.
[Nexus 4 Android Development] passlogin:
R10 is out, bringing in my favorite features during the Faux days.

Intellidemand and Intelliactive! For more details check the op.

and xenyz, the voltage table was messed up and my phone refuses to boot. It should be fixed now.

And do note I'm getting closer to school exam so don't expect a new release anytime soon.
[Nexus 4 Android Development] passlogin:
After the dead links R10 is uploaded

Intellidemand and Intelliactive is disabled due to making phone unbootable.
[Nexus 4 Android Development] nedooo:
In changelog you say: "Faux123's GPU Overclock to 487.5 MHz"

But max GPU frq. is 450MHz?

I know Faux uses 450, but can you make 487.5 MHz?

Thanks.
[Nexus 4 Android Development] xenyz:
R10 working great as usual.

Since you were itching to swap out the hotplug driver, have you considered the one from myfluxi? I ran ak kernel for a few days last week and he uses it. Using System Monitor I noticed the cores were offline longer while idle, whereas on current autosmp core 1 comes online and offline every couple seconds regardless of load.

Just a small suggestion, and no rush for it, everything is fine as is. Thanks again.
[Nexus 4 Android Development] passlogin:
I will look into it, exactly by % wins over autosmp?

After examining his commits, he made the 450 MHz overwriting the 487.5MHz, with some hack I can make both of them exist. Just wait after I got some days of school holidays.
[Nexus 4 Android Development] nedooo:
Thanks a lot :)
[Nexus 4 Android Development] passlogin:
I pushed into my GitHub, but still not compiled yet.
[Nexus 4 Android Development] xenyz:
Not sure, but beladus uses it in his kernel and you know how he likes benchmarks. I suppose the only thing that matters is better performance or better battery life. In his thread I remember him stating it was better to have 2 cores online at all times. I'll try to dig it up, but check out how he configured the hotplug in moob kernel.
[Nexus 4 Android Development] passlogin:
All frequencies exposed! Still in testing though, I need a way to set 400MHz as default.
[Nexus 4 Android Development] hartleyshc:
How are you setting 487.5 and 450, since they use the same PLL?
[Nexus 4 Android Development] passlogin:
AFAIK different frequencies can share the same pll.
[Nexus 4 Android Development] hartleyshc:
They can, but the math has to be right when setting the frequency by multiplying the pll.
[Nexus 4 Android Development] passlogin:
Okay, thanks for the heads up.

Are you experienced in building kernels?
[Nexus 4 Android Development] Swords.Grizzlebee:
So, to use your init.d scripts all I should have to do is paste them into a text file, put them in the init.d folder, delete the .txt extension, and set the correct permissions right? I can't seem to get them working for some reason.
[Nexus 4 Android Development] xenyz:
MiRaGe / naruKa doesn't come with init.d support in the ramdisk, you have to use something like term-init, although it looks like things are heading towards using Synapse and N4UKM instead of scripts for kernel config these days.
[Nexus 4 Android Development] Swords.Grizzlebee:
I actually did enable term.init already, I'm not sure where I'm going wrong. I'll try some more to get it working. I've used Synapse a bit with AK's kernel but I'm not too familiar with it yet, I'll give that a more in depth look. Thanks for replying!
[Nexus 4 Android Development] xenyz:
I've forgotten to mention that N4UKM requires init.d support to hook itself in during startup. You're going to need to get it working to use either.

Did you remember to install busybox?
[Nexus 4 Android Development] Swords.Grizzlebee:
I did, and also the script I used to enable term-init adds a test log to the data folder to confirm its working, and it appears to be working. I'm stumped.
[Nexus 4 Android Development] xenyz:
It's gotta be an owner or permission problem. Check owner/group is root and permissions set to 755? Does your script have the shebang on line 1?
[Nexus 4 Android Development] Swords.Grizzlebee:
Sorry, I'm sure I missed something basic. I'm kind of new to scripts in general. These are the permissions and text in the script. Is that the equivalent of 755?
[Nexus 4 Android Development] xenyz:
Yeah you got it, looks good. So it's in /etc/init.d/00kernel as root:root?

u0_a105@mako:/etc/init.d $ ls -l
-rwxr-xr-x root root 6580 2014-05-18 02:03 00kernel
[Nexus 4 Android Development] Swords.Grizzlebee:
I'm pretty sure, does this look right?
[Nexus 4 Android Development] xenyz:
Yeah you got it. Are you certain it's not running? Could the settings be getting reset by another app, like Trickster?
[Nexus 4 Android Development] passlogin:
Check if your rom has init.d support.

If there is init.d support, it will be used since naruKa leaves the ramdisk intact.

And is your init.d folder is set to 755 as well?
[Nexus 4 Android Development] Swords.Grizzlebee:
I guess it could be, I am using trickster but I don't have set on boot enabled. Maybe it's still messing things up, I'll check it out. Thanks for the help, very nice of you.
[Nexus 4 Android Development] passlogin:
R12 is out, I'm spending a week for these. (and got preety stressed hehehe)
[Nexus 4 Android Development] passlogin:
R13 is out.

Check the op, i've fixed the link.
[Nexus 4 Android Development] jimyiak:
r13 is based to latest mirage from 23/5?i don't at the download link the latest kernel..
[Nexus 4 Android Development] Jagdish84:
Ya, R13s not uploaded to your drive folder...
[Nexus 4 Android Development] passlogin:
It should be now.
[Nexus 4 Android Development] xenyz:
bfq didn't quite make it into R13.
[Nexus 4 Android Development] passlogin:
R14 is up, I've double checked it so nothing is missing

[MENTION=3118524]xenyz[/MENTION], what app do you use for monitoring?
[Nexus 4 Android Development] xenyz:
$ cat /sys/block/mmcblk0/queue/scheduler
noop deadline [row] cfq sio fiops

I'll try R14.
[Nexus 4 Android Development] passlogin:
I know, I've double-checked it from Trickster
[MENTION=3118524]xenyz[/MENTION], what app do you use for monitoring?
[Nexus 4 Android Development] xenyz:
Working in R14 now, thanks.

I use system monitor, perfmon and trickster usually.
[Nexus 4 Android Development] mimsiroll:
Dude, how many phone's you have? Lol
[Nexus 4 Android Development] xenyz:
Just one, I switch from ak to Mirage for longer battery life some days.
[Nexus 4 Android Development] passlogin:
For GPU freq
[Nexus 4 Android Development] xenyz:
Trepn Profiler
[Nexus 4 Android Development] AzizWahid:
Thanks dev for this kernel. Looks like I'll be testing this kernel for a while as it has my two favourite feature which is support for multi rom and S2W.

Only sometimes (most of the time maybe) sweep 2 wake doesn't work for me. Sweep 2 sleep doesn't have problem though. It would be great if you can look at this :D

BTW, I'm on latest mahdi rom. Thanks again for this kernel :good:
[Nexus 4 Android Development] passlogin:
Unfortunately since the S2W is a Bricked's implemetation, nor I change them in anyway, I can't provide any major support

I'm going to implement Faux123's s2w tuneables if that provides any help

Edit:S2W here is so smooth, rom related issues maybe?

C-Rom 6.6

Edit: Maybe this is the right time to upload R15, as usual check the OP
[Nexus 4 Android Development] passlogin:
R16 is out, check the op.
[Nexus 4 Android Development] passlogin:
Will do!

Guys, I need your feedback

Those feedback may go into the appropriate tabs on the DevDB section above. Thanks!
[Nexus 4 Android Development] jimyiak:
Big update in mirage :D:D
[Nexus 4 Android Development] jimyiak:
It is already f2fs compatible!! ?

sent by neXus 4 using xda premium
[Nexus 4 Android Development] halfbytecode:
Not booting on full F2FS for me.
[Nexus 4 Android Development] passlogin:
Previosly I used barome's commit for f2fs then I switched to MiRaGe's commits.

Hell I'm out of town for days before I saw this. Sorry for the late reply

I will sync to mirage commits once I got enough sleep.
[Nexus 4 Android Development] passlogin:
Please try R16

If that boots I will use barome's implementation then
[Nexus 4 Android Development] gorilla p:
I checked out this kernel again and I really like the way it is going. It has some great features and a good list of governors available, and it is compatible with UKM/Synapse which is a huge plus as well.

If you dont mind, I like to make a couple recommendations/requests

I'd like to see the 81mhz freq available. 81mhz is stable as long as it isn't underclocked too much. 750mv should be sufficient for everyone. I have a fast binned CPU and 700mv is stable for me on 81mhz.

The voltage on the GPU cores seems to be stuck on 1200mv, while many other kernels have these between 900-1100.

Could you also see about adding the conservative GPU governor?

Sent via Mental Telepathy
[Nexus 4 Android Development] gorilla p:
Same here. I have fast binned. I use the following and it's stable.

81mhz@700mv

162mhz@725mv

384mhz@750mv

Sent via Mental Telepathy
[Nexus 4 Android Development] passlogin:
Sorry for long disapperance times as busy life takes over

R18 is there. There's not much changes other that there is now CM builds

If you are interested view my github commits, and my Gdrive folder since I'm kinda lazy to update the op.
[Nexus 4 Android Development] passlogin:
I dont know what makes it's stuck at 1200

as for now, it's removed for safety reasons.

for <162 mhz cpu freqs, it's just about how many time I have to implement that, it isn't too hard.
[Nexus 4 Android Development] 0.0:
I don't see R18 in your GDrive...does anyone have a copy?
[Nexus 4 Android Development] xenyz:
R18 was split into A18 for AOSP and C18 for CM I'm guessing.
[Nexus 4 Android Development] robbieast:
Not working with synapse.

I get "no UCI support detected" error.
[Nexus 4 Android Development] Almayce:
Unnistall synapse, Flash kernel, flash ukm install synapse again. Or clearing data also works, too.
[Nexus 4 Android Development] THEBANDIT420:
Awesome kernel, came from ak and this almost has as many 'features' but with better battery and performance!
[Nexus 4 Android Development] passlogin:
Do post what features you want

Since I'm kinda lazy if no one demanded new feature :P
[Nexus 4 Android Development] apatal:
Is the latest one synced to the latest Mirage sources? And does it have dt2w from Semaphore? :)

EDIT: BTW, new Mirage build has just been released. See post here.
[Nexus 4 Android Development] xenyz:
How about a test, swap out bricked msm_mpdecision and msm_thermal with faux intelliplug and intellithermal?
[Nexus 4 Android Development] passlogin:
I was thinking the same, intelliplug doesn't starts at boot so we can compile both

I just changed my linux distros and don't have the mood to do some kernel works ehe

BTW on gpu voltage control I found them working as intended.
[Nexus 4 Android Development] jmtjr278:
[MENTION=4852799]passlogin[/MENTION] I see mrg666 has tweaked his own hotplug driver autosmp. Any chance we could get a build with it and updated sources? Thanks for all your hard work!
[Nexus 4 Android Development] passlogin:
I have no plans on doing that, neither with myfluxis

If autosmp is cant be turned off, I will consider that.

EDIT: I mean if autosmp can be turned off.
[Nexus 4 Android Development] xenyz:
I'm seeing these messages in the kernel log. Must be pretty benign, but maybe the hsic host patches should be reviewed?

<4>[ 6168.178146] ------------[ cut here ]------------
<4>[ 6168.178268] WARNING: at kernel/power/qos.c:294 msm_hsic_resume_thread+0x370/0x380()
<3>[ 6168.178329] pm_qos_update_request() called for unknown object
<4>[ 6168.178421] Modules linked in:
<4>[ 6168.178543] [<c001598c>] (unwind_backtrace+0x0/0xf4) from [<c00838e8>] (warn_slowpath_common+0x54/0x64)
<4>[ 6168.178665] [<c00838e8>] (warn_slowpath_common+0x54/0x64) from [<c0083928>] (warn_slowpath_fmt+0x30/0x40)
<4>[ 6168.178757] [<c0083928>] (warn_slowpath_fmt+0x30/0x40) from [<c0420070>] (msm_hsic_resume_thread+0x370/0x380)
<4>[ 6168.178879] [<c0420070>] (msm_hsic_resume_thread+0x370/0x380) from [<c00a1774>] (kthread+0xb4/0xb8)
<4>[ 6168.179001] [<c00a1774>] (kthread+0xb4/0xb8) from [<c000f9e8>] (kernel_thread_exit+0x0/0x8)
<4>[ 6168.179062] ---[ end trace fd0b87565ccd5ceb ]---

Well, I'm hoping you get your Linux box going again soon, this kernel is looking for an update :)
[Nexus 4 Android Development] xenyz:
[MENTION=4852799]passlogin[/MENTION] look at these last 3 commits, I think they fix the stuck CPU boost issue with msm_mpdecision.
[Nexus 4 Android Development] passlogin:
My linux box is running now so now that matters is finding time to squash and fix.

[MENTION=3118524]xenyz[/MENTION], could you backup and try from which version this warning has shown up?

From R15 upwards.
[Nexus 4 Android Development] xenyz:
I started at R14 and found no warnings. On R15 they appear, so it has to be one of those commits on May 28. I wish I knew more about the kernel internals to narrow it down further. I will keep trying, who knows maybe I'll find something. :)
[Nexus 4 Android Development] passlogin:
Great then.

Mean while I have finish compiling so, wait a day or two to upload
[Nexus 4 Android Development] xenyz:
Are you compiling with one commit at a time to find out which one is the issue?

I'm not even sure if the warnings are a problem or not. The patches could be really useful, and just throwing a stupid warning. I thought they should be looked at but not necessarily thrown out, as they do look like they're useful for energy savings.

Edit: BTW if I could make a request, can you revert the reverted changes here and here and put them back? I know [MENTION=4203114]mrg666[/MENTION] didn't like them and took them out, but I believe it gives a boost to performance and it just runs things smoother. It was one reason why I stuck on R18, it was the latest kernel with those changes.
[Nexus 4 Android Development] passlogin:
mispost
[Nexus 4 Android Development] passlogin:
Eh, this is quite nonsense

See this, with this commit ondemand will target higher frequencies on lower loads (<50% ish) and without this commit ondemand target one lower freq step compared with this commit.

As for the other one, this commit. I believe it doesn't pose so many side effects.

EDIT: How fool am I, reverting it immediately.
[Nexus 4 Android Development] y3mita:
Gonna flash this once home
[Nexus 4 Android Development] y3mita:
Running last release not bad at all. I thought it had autosmp from mirage kernel.
[Nexus 4 Android Development] jmtjr278:
Not yet merged.
[Nexus 4 Android Development] passlogin:
It's removed and replaced by bricked mpd and faux's intelli_plug
[Nexus 4 Android Development] y3mita:
No plans on making one version with autosmp?
[Nexus 4 Android Development] passlogin:
No ATM, until [MENTION=4203114]mrg666[/MENTION] gives autosmp an on/off tunable
[Nexus 4 Android Development] mrg666:
I really don't care if you include autosmp or not. I am only replying here since you let me know about your comment. Didn't you see /sys/proc/module/autosmp/parameters/enable ?
[Nexus 4 Android Development] defconoi:
lol, I think the on/off tunable was included forever
[Nexus 4 Android Development] passlogin:
Thanks for the heads up, [MENTION=4203114]mrg666[/MENTION]

[MENTION=4203114]mrg666[/MENTION] how do you know what sysfs is avaliable from looking a program source code? and how to modify them?

For example, autosmp defaults to start enabled, how to disable it?