yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] C4SCA:
[MENTION=4203114]mrg666[/MENTION] are u planning to addind simple gpu governor or a personal tweaked gpu gov? I think it may help on battery, gaming and heat ;)

sent from my NEXUS 4 tasting a revamped cooking recipe of Jellybeans (4.3).
[Nexus 4 Original Android Development] mrg666:
I am not sure about the gpu governor. I haven't seen the benefits you mentioned when I tested. But I will check it out again after the kitkat kernel source is released. I don't want to diverge further before that.
[Nexus 4 Original Android Development] xenyz:
f2fs is actually already being used by Motorola on the X and G devices, I've read.
[Nexus 4 Original Android Development] jawz101:
...and probably on at least some thing made by Samsung. It could be the filesystem on a Smart Tv, toaster or something. I mean, they did invent it.
[Nexus 4 Original Android Development] 26.2man:
I just flashed my phone back to factory setting's for a while. Is anyone using this kernel on stock. Did you change any of the out of the box settings and if yes what and why. And finally how is your battery life and sot. I will appreciate any feedback.
[Nexus 4 Original Android Development] clockworkstop:
thanks for that made my day
[Nexus 4 Original Android Development] mrg666:
New build is available in the OP.

- flicker should be fixed now (please confirm if you were having the problem)

- Linux 3.4.86 and 3.4.87

I was able to reproduce the flicker problem using ES File Explorer and reverting one of the earlier kgsl patches fixed it. Hopefully it is also fixed for the ones who were reporting the problem.

Enjoy!
[Nexus 4 Original Android Development] wong.izzat:
Great job there. So far so good!
[Nexus 4 Original Android Development] Fenvarien:
+1

The new version is working very nice and without any flickering here.

disce aut discede
[Nexus 4 Original Android Development] nexxx85:
Switched from ak right before. Kernel runs smooth without any issues. Will keep an eye on battery.

Thanks!
[Nexus 4 Original Android Development] senthilrameshjv:
Velocity + ART + mirage + 1.3 GHz max + All data + data off on screen off + location and Wi-Fi always scanning off.

Been struggling to get 3 hrs sot. Mirage and velocity changed it.

Lotta Whatsapp, FB,tapatalk, voice calls, texting today.
[Nexus 4 Original Android Development] Bladyle:
Still having flickering with last update...
[Nexus 4 Original Android Development] mrg666:
oh no! not again.

Please record a video with another device to show how it happens. That way I can see this super elusive bug.
[Nexus 4 Original Android Development] TheNerd:]:
Please it's not your fault; not all devices are created equally.
[Nexus 4 Original Android Development] wong.izzat:
Yes. I'm on PA beta 4 no problem at all.
[Nexus 4 Original Android Development] 26.2man:
I just have to say that after being repeatedly disappointed with several custom Roms I went back to stock, rooted the phone and installed this kernel. It's been great. 4 to 5 hours sot and the phone is as smooth as could be. I can't see changing to anything else for quite a while.
[Nexus 4 Original Android Development] Bladyle:
I was able to record one flick. I think they happened randomly. You can see in the video I upload at 5-6 sec. Usualy I have more than one flicks but this time is only one

http://youtu.be/vesom1GJUik
[Nexus 4 Original Android Development] r3act:
With the lastest testkernel the flicker has moved to the top portion of the screen. So you must be onto something since the behaviour changed!
[Nexus 4 Original Android Development] mrg666:
Thanks, now I know what you mean. It seems like a very minor glitch but If I can find some time out of work, I will work on fixing it.
[Nexus 4 Original Android Development] mrg666:
New builds are available in the OP.

Changes:

- kgsl fixes

- autosmp optimization

I can't see flickering but these changes were done to help with the problem. Please let me know if you still have it.

Cheers!
[Nexus 4 Original Android Development] apatal:
Sorry never mind.
[Nexus 4 Original Android Development] nexxx85:
Battery is amazing. 3.5 days with a sot of 3hours! Thanks
[Nexus 4 Original Android Development] dioadi:
Wow. 3.5 days ??? In one run of full charge?
[Nexus 4 Original Android Development] iCole:
Tried both normal and OC builds since you uploaded them yesterday, both still flicker. Anything more I can do to help debug?
[Nexus 4 Original Android Development] aproape:
For me Last version with no flicker was MiRaGe_mako_oc_kernel_KOT_031614
[Nexus 4 Original Android Development] Fenvarien:
Not a single flicker here, both versions are working great with Purity ROM and the latest Adreno drivers.

Here's the link for those drivers, maybe they can help with this issue:

http://xdaforums.com/showthread.php?t=2667759
[Nexus 4 Original Android Development] nexxx85:
Yes... I only use data/wifi on demand and dont play games. On other kernels i only get 2.5 days with ~2h sot.

Btw. no flickering here. All runs smooth
[Nexus 4 Original Android Development] krialix:
Do you use Greenify?
[Nexus 4 Original Android Development] Bladyle:
Same here.
[Nexus 4 Original Android Development] nexxx85:
Nop. Purity Rom with MiRaGe (all stock settings, no batterylife apps)

As said before, i dont play games or browse alot. Most of the time i read with greader, a bit sms/whatsapp. Data/WIFI only on demand. Brightness controlled via LUX
[Nexus 4 Original Android Development] mrg666:
Okay, since I am not able to fix this stupid flicker problem and I am not even able to reproduce it, I will revert the latest kgls commits and be done with it. Give me a couple of days since I am away from home. I will do this by Saturday the latest.
[Nexus 4 Original Android Development] Lord_Baal:
Did the Same Thing. Updated the Kernel and the drivers.

On 2 days running, not a single flicker detected here.
[Nexus 4 Original Android Development] fluffier:
Hi, these are my results with latest build. First cycle, just 3G. Very impressed, thanks mirage.
[Nexus 4 Original Android Development] haget83:
Not for me. Drivers updated but fliker still here

But is Very sporadic, is not to much annoyng
[Nexus 4 Original Android Development] racin910:
Same here. Updated drivers. Still flickers. Doesn't happen too often tho and I'm not to bothered with it. Lemme know if you need any data tho
[Nexus 4 Original Android Development] 26.2man:
For what its wort. Been on it for last 48 hours. Not the first flicker. It's a nice product. Thanks!
[Nexus 4 Original Android Development] mrg666:
I have posted the new builds in the OP.

- Reverted the kgsl changes that was most likely causing the flicker

- Linux 3.4.88

Flicker must be fixed now. If not .... please don't tell :silly:

Cheers!
[Nexus 4 Original Android Development] haget83:
probably it too soon to say this but i dont notice any flicker after 1/2 day of usage.

The problem seems solved(?)
[Nexus 4 Original Android Development] mrg666:
I think you should stop looking for it after this point :laugh:

I have received by PM another report of no flicker. On the other hand, one PM reported 'extremely rare" occurrence of flicker. I think, after the latest reverts, it is even more difficult to see now.
[Nexus 4 Original Android Development] jawz101:
If I say I've never noticed a flicker ever does that mean anything at this point? :p
[Nexus 4 Original Android Development] H-Body:
Wow great kernel, so smooth and fast! Finally i found a new home :fingers-crossed:

One question, i compile the kernel myself to get other screen colours and i wonder if its enough to put the zimage into the oc template provided by you to get the oc verrsion? Or do i have to put mako_oc_config instead of mako_config as .config in the root direction of the kernel source, too?
[Nexus 4 Original Android Development] mrg666:
If you want the oc version just copy mako_oc_config as .config in the root directory of the kernel source and build. zImage will be for the oc version and you can just put it in the zip template. Before flashing the any-kernel package with you build, flash my zip file once to include MiRaGe specific changes in the ramdisk. Thanks!
[Nexus 4 Original Android Development] H-Body:
Thanks for your reply, so far all is working flawless :good:
[Nexus 4 Original Android Development] ohitspat:
Best kernel I've used on my nexus 4
[Nexus 4 Original Android Development] jawz101:
[MENTION=4203114]mrg666[/MENTION]

Have you looked at these TCP Fast Open and TCP Small Queues commits?

http://kernelnewbies.org/Linux_3.6#head-ac78950a7b57d92d5835642926f0e147c680b99c
[Nexus 4 Original Android Development] mrg666:
There seems to be dependencies prior to those commits. Let me see what I can do.

Edit: I have resolved the dependencies of TCP Small Queues and testing now. TCP Fast Open is a much bigger commit and I will work on it after testing the first one.
[Nexus 4 Original Android Development] jawz101:
Wow. I'd started looking into bufferbloat a week or so ago... You may find this thread interesting as a maintainer of bufferbloat.net - Dave Täht started chiming in on my questions. I'd seen some youtube videos of presentations he'd done which piqued my interest.

http://xdaforums.com/showthread.php?t=2163790

His last comments in that thread implied more configuration is needed... which was beyond me.
[Nexus 4 Original Android Development] mrg666:
TCP Small Queues (Bufferbloat fight) seems to be working fine. I will post the kernel on tomorrow or Friday since I am away from home today. Thanks for the link, I will check the comments in detail in the weekend.
[Nexus 4 Original Android Development] mrg666:
New build is available in the OP

- TCP small queues (thanks to jawz101 for pointing out this important patch)

- several other tcp and library fixes

Enjoy!
[Nexus 4 Original Android Development] fajarlazuarding:
Sorry if i posted in a wrong thread, but i lost root after flashing mirage on PA 4.3 beta2, can someone help me to recover it? Because i really want to taste this kernel :) Thanks in advance.
[Nexus 4 Original Android Development] mrg666:
Please see the second post, recommendations, last bullet :)
[Nexus 4 Original Android Development] fajarlazuarding:
Ah, i missed that, thanks mate :) charging state now, will try for a couple days.
[Nexus 4 Original Android Development] Federico_96:
Is the non overclock version of this kernel undervolted by default? What's gonna happen if my phone can't handle such undervolt? Sorry for the question but I never undervolted before
[Nexus 4 Original Android Development] mrg666:
The standard version is not undervolted. You can safely use it.
[Nexus 4 Original Android Development] xenyz:
I know mrg666 recommends SuperSU but clockworkmod's open source superuser works as well. You may have to flash it again after installing MiRaGe, as the installer checks for init.d support and installs there first if found. If not, it installs to /etc/install-recovery.sh which works on MiRaGe.
[Nexus 4 Original Android Development] xenyz:
[MENTION=4203114]mrg666[/MENTION] it looks like GPU clock is stuck on 320 MHz after removing devfreq. I've been monitoring with watch `cat /sys/devices/platform/kgsl-3d0.0/kgsl/kgsl-3d0/gpuclk`
[Nexus 4 Original Android Development] Crisisx1:
Been using rastakat ROM for about a year w stock kernel it came with.. Everything was fine but wanted to give this kernel a spin..

It's awesome..the only annoyance I found was in the stock browser favorites screen it flickers like crazy. Any fix? Oc version.

EDIT: it stopped flickering after I posted this lol weird.
[Nexus 4 Original Android Development] mrg666:
I don't it is stuck since there is no reduction in the gpu benchmarks or battery life. It should be reported incorrect there. I will check it out.

I think you mean Chrome since I don't have any other browser on my stock kitkat ROM. Give some time for the system to settle down after first boot. All kinds of weirdness happen before that.
[Nexus 4 Original Android Development] fajarlazuarding:
Thanks for response mate, but for now i have used SuperSU as [MENTION=4203114]mrg666[/MENTION] recommend me.

Well, if i want to use superuser, what did you mean by flash it again? Since PA included it on their rom and i don't know which installer should i use :) sorry if my english seems pretty bad lol
[Nexus 4 Original Android Development] xenyz:
Look for the manual installation link on the Play Store.
[Nexus 4 Original Android Development] Kaka88:
After trying several kernel, im decided to going back to Mirage..

But i cant acces the link in the first page..

Can anyone help me?
[Nexus 4 Original Android Development] Kaka88:
Problem solved..

Now im on MiRaGe OC version :)
[Nexus 4 Original Android Development] TheNerd:]:
It's not stuck, that is the default behavior

of many kernels. The app (or I guess terminal) you are using is reporting the frequency incorrectly. When the GPU goes idle many apps report 320 MHz for some odd reason. This is normal across all kernels even stock, well most not all.
[Nexus 4 Original Android Development] TheKnux:
Is there a CM/CAF version available?
[Nexus 4 Original Android Development] Shubhamqweasd:
this is the only kernel with better gaming performance than franco's kernel :D good job . [MENTION=4203114]mrg666[/MENTION] ...
[Nexus 4 Original Android Development] Kaka88:
Im very agree with you..

And very stable like semaphore..
[Nexus 4 Original Android Development] jimyiak:
Is it easy to make it f2fs compatible?? :D

sent by neXus 4 kitkat-ed ?
[Nexus 4 Original Android Development] senthilrameshjv:
Someone said or somewhere I read mirage based naruka is compatible with f2fs
[Nexus 4 Original Android Development] fajarlazuarding:
Been trying this kernel for 3days, i must say this kernel is so impressed me. thanks [MENTION=4203114]mrg666[/MENTION] for your hardwork, keep going :)

Uhm, anyway, can i change gamma setting with semaphore manager on this kernel? Franco's nexus display control didn't work thought.
[Nexus 4 Original Android Development] mrg666:
Yes, gamma settings are based on stratosk's implementation. And his controller apps was confirmed to be working. I haven't tried since I don't use gamma settings.
[Nexus 4 Original Android Development] fajarlazuarding:
Confirmed! Now this is perfect, thanks mate :)
[Nexus 4 Original Android Development] Rafase282:
It would be nice of you to implement multirom support. But intil then I guess I'll stay with one room.
[Nexus 4 Original Android Development] guimendes:
You can include multirom support by yourself. I did it for me. It's pretty easy.
[Nexus 4 Original Android Development] mrg666:
New builds are available in the OP

- cpufreq optimizations

- nohz optimization

- net cleanup

- Linux 3.4.89

Enjoy!
[Nexus 4 Original Android Development] Galaxyfire:
Have this kernel init.d ?

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] mrg666:
I just added links in the second post about adding init.d and multiROM support by yourself. There is no change needed in the kernel source to add these.
[Nexus 4 Original Android Development] beskalL:
Can you please explain the step to add the multirom support?
[Nexus 4 Original Android Development] aviz1911:
getting these errors while compiling your kernel from source, And i'm using sabermod 4.9 toolchain

any ideas ??
[Nexus 4 Original Android Development] mrg666:
Should be related to the 4.9 toolchain if you are using the correct configuration.
[Nexus 4 Original Android Development] aviz1911:
This is the first time i'm compiling with sabermod 4.9 bro. I don't know much about these toolchains. Can you suggest me any changes i should make ??

Thanks
[Nexus 4 Original Android Development] mrg666:
Newer toolchains usually cause incompatibilities and also instability. I haven't tested the 4.9 series yet. You can either check the other devs to see what parts of the kernel were fixed for 4.9 or wait for me to fix the source. I am not sure if I will have time for this soon. You can use the linaro 4.8 for now.
[Nexus 4 Original Android Development] aviz1911:
Thanks bro. I'll try that xD
[Nexus 4 Original Android Development] xenyz:
[MENTION=4203114]mrg666[/MENTION] any advice on adjusting the autosmp tunables to slow the jump to additional cores online? I was comparing autosmp to myfluxi's hotplug driver and noticed the latter keeps to one core unless there is significant load, and usually only has one core online while 'idle'.
[Nexus 4 Original Android Development] mrg666:
You can try changing cpufreq_up. It is set at 1000 right now which I found to be optimal regarding performance and battery life. But if you increase it, 1200 for example, autosmp will delay hotplugging additional cores.
[Nexus 4 Original Android Development] jawz101:
@mrg666 I have a few commits I've been pulling from Franco's kernel if you want to take a look. Really only stuff that pulled in cleanly

https://github.com/jawz101/android_kernel_mako

my phone seems to be doing well so far with them.
[Nexus 4 Original Android Development] Galaxyfire:
With this kernel my Phone is very hot at Shadow Fighter 2 (60°C) at other kernels (HellsCore , AK) it is 40°C

Can you help me ?

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] mrg666:
I would recommend staying with the kernel running cooler.
[Nexus 4 Original Android Development] Galaxyfire:
But I like your kernel, very smooth, it is clean, no useless features, etc. . I dont want to use another, is there no solution ?

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] mrg666:
I don't optimize the kernel for specific apps/games since it is simply not practical within my free time. And I have never seen excessive heat with the games/benchmarks I use for testing. I am confident that MiRaGe has much lower heat than the stock kernel which is the only kernel I benchmark against. Your case could be false reading, background process running wild, or a super special case for that game, I am guessing. But, sorry, I don't have any solution for that.
[Nexus 4 Original Android Development] Galaxyfire:
Okay, maybe i can solve the problem with the app "per app modes" . It is possible to change the values of the hotplug, like "up threshold" ??

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] xenyz:
I still think there is a problem with the GPU ondemand gov. I can set max clock to 128 or 200 MHz and apps like Trickster report it. I can even set to max and whilst pulling down notifications I can see the GPU jump to 128 MHz but whenever it is idle it goes back to 320 MHz. I think the terminal and the apps are reporting the clock value correctly, contrary to what others have posted. It could have something to do with the gaming performance issues as well.

Maybe compare to ak kernel to note the difference? I notice his implementation also clocks down and idles at 27 MHz.
[Nexus 4 Original Android Development] guimendes:
First you have to be able to build this kernel from sources. Instructions are into 2nd post. Then, take a look into github acount from some kernel based on this which implements MultiROM. There you'll find a patch that does almos everything. Third, read carefully how to add MultiROM support from MultiROM thread. It'll help you to propper configure your build. There are some extra flags to insert into .config file. To install, use any kernel. It's explained into 2nd post, too.
[Nexus 4 Original Android Development] C4SCA:
[MENTION=222363]mirage[/MENTION] what am i doing wrong? (total noob here...)
[Nexus 4 Original Android Development] mrg666:
make isn't able to find the compiler. It seems to me either CROSS_COMPILE definition is wrong or the toolchain is not there.
[Nexus 4 Original Android Development] C4SCA:
besides extracting the toolchain to a folder in home directory, do i need to do anything else to get the toolchain ready?
[Nexus 4 Original Android Development] TheNerd:]:
The idle frequency is displayed as 320mhz! Don't worry don't even think about the kernel just use your phone! Everything is fine with the kernel.

P.S. did not mean to be rude
[Nexus 4 Original Android Development] xenyz:
How can you tell when it's idle and when it's actually at 320 MHz? I'm not that concerned but with others posting about gaming performance it sure seems something is up.

Edit: I stand corrected, looks like it's idle at 128MHz. (450 is max because I'm currently on modded MiRaGe, naruKa kernel)
[Nexus 4 Original Android Development] guimendes:
Try to access all folders until you find the binary file. It may have generated some extra path on extraction of the toolchain.
[Nexus 4 Original Android Development] C4SCA:
Nop, the path is correct im almost sure, check the screenshots.

Thank you for the help and [MENTION=3880032]mirage.[/MENTION]
[Nexus 4 Original Android Development] guimendes:
Well, I always use copy and paste for all folder names and file names to be sure. Try to open up this bin folder into terminal and use a pwd command to get all the path. Also, I suggest you to use an ls command into the folder to copy the file name. It'll confirm there is no typo.
[Nexus 4 Original Android Development] C4SCA:
so i done what u said... and still doesnt work :/

check the screenshot
[Nexus 4 Original Android Development] jawz101:
try

cd ~/android_kernel_mako

cp ./arch/arm/configs/mako_oc_config ./.config

make ARCH=arm CROSS_COMPILE=~/gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux/bin/arm-linux-gnueabihf- zImage modules -j2

if that doesn't work do a "make clean" and copy & paste it and do it again

Personally, under my home directory create a folder named repos. that's where I clone any repos I'm messing with

extract the toolchain to my home directory and rename the folder to "toolchain" so I don't have to think about typos in that long name

in a text file I just keep these commands to copy/paste into terminal all at once.

cd ~/repos/android_kernel_mako

cp ./arch/arm/configs/mako_oc_config ./.config

make ARCH=arm CROSS_COMPILE=~/toolchain/bin/arm-linux-gnueabihf- zImage modules -j2

if something screwy happens use "make clean". It's in my text file as well so I can copy/paste if needed.

Whatever you do just put all of your commands in a text file and paste the commands here if you run into trouble. That way you can at least be repeatable when it does finally work.
[Nexus 4 Original Android Development] C4SCA:
Im missing something for sure...

i've done the clone git.

Downloaded "linaro-toolchain-binaries 4.8", extracted it under home and renamed the folder extracted to "toolchain".

- Open terminal, cd to kernel source folder.

- cp ./arch/arm/configs/mako_oc_config ./.config

- make ARCH=arm CROSS_COMPILE=~/toolchain/bin/arm-linux-gnueabihf- zImage modules -j4

. then this happens (check screenshots)

Dunno if its relevant but im using a virtual machine to run ubuntu
[Nexus 4 Original Android Development] jawz101:
Don't worry- you're close!

can you check if files ar, as, c++, g++, gcc, ... are in this folder /home/zacuc/toolchain/arm-linux-gnueabihf/bin/ ?

if they aren't there you downloaded the uncompiled toolchain rather than the binary

next try typing the command

echo $PATH

if you see something about your linaro toolchain path with this command there's some steps you did at some point to set an environmental variable to specify where the linaro toolchain is you need to get rid of that because it's not needed

I've seen that error before. you may want to google:

gcc-version.sh android kernel

and see what others have said. Sometimes I just find a bunch of different sites talking about an error msg like this and try solutions until it works

if all else fails delete the kernel folder and clone it again, redownload the toolchain and start over

if you followed any instructions that had you do a bunch of making symbolic links (ln -s commands) delete those symbolic links you made too and try the next solution.

it really comes down to the steps that work for you. I know with me being on Arch Linux I have to deal with some python junk as well so I'd follow someone's steps that work on Ubuntu.
[Nexus 4 Original Android Development] mrg666:
This sounds highly possible. Looking at the latest snapshots, the cross compiler is still not available in the specified path. You need to check the path and verify.