yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] zaclimon:
Yeah I'm sure. Every kernel that doesn't use mpdecision has this problem and it never had any issue. Now if it's not working right with cm is because you may have mpdecision and power.mako.so not renamed/deleted. Try to rename/delete and report if all is good.
[Nexus 4 Android Development] keyra74:
yup i can confirm that
[Nexus 4 Android Development] tvisforme:
Are there instructions for this in the thread? I've tried to find them but there are 70+ pages now and search is (as always) less than helpful.
[Nexus 4 Android Development] zaclimon:
The solution for this could be found 2 pages ago from this. Surely enough, I'll try to find a way to fix this by V4.
[Nexus 4 Android Development] ObihoernchenDE:
Here we go: http://xdaforums.com/nexus-4/develo...ernel-r211-t2858561/post60215231#post60215231
[Nexus 4 Android Development] xenyz:
There actually is a cost. logd uses much more CPU than normal when processing those messages every time the screen is touched.

Two solutions:

- remove/rename power.mako.so from /system/lib/hw. This will break Battery Saver mode on Lollipop, however.

- flash stock boot.img, flash Semaphore anykernel, then flash Quanta. [MENTION=3750240]stratosk[/MENTION] has implemented a 'fake' touch boost driver to handle touch boost events

When I was testing with another kernel, I found logd using up to 3x more CPU (30m in a day vs 10m). I don't think it's the cause of your slowdown/lag though.
[Nexus 4 Android Development] zaclimon:
Sorry guys if I feel like not really responding anymore these times, working on QT 2.0 and V4.

For people who are using microphone gain using faux sound, have you tried to set it up also via FKU? (if ever you do have it) If both ways aren't working, something in the implementation might be broken off... I'll try to see what is possible.

EDIT: If quick fixing isn't possible, a release will most likely be available later today
[Nexus 4 Android Development] ViRb3:
Color profile restore glitch

So I re-flashed Cataclysm ROM 5.1 for Nexus 4 (to get stock kernel) and directly afterwards flashed Quanta-V3. Everything is smooth like butter, fast like the wind etc. etc., but when I reboot the phone and FKUpdater restores the color profiles, I get a very distorted color effect. Basically all colors are extremely washed out and everything is terribly bluish. It all fixes when I re-apply my color profile.

I've been using franco r217 right before and it worked without any flaws.

Thanks!
[Nexus 4 Android Development] zaclimon:
Have you tried to re-apply the values using FKU? Also It could be a root related issue.
[Nexus 4 Android Development] ViRb3:
Tried twice. I am properly rooted with SuperSU if your question was about that.
[Nexus 4 Android Development] zaclimon:
Ahh haven't seen that it was working when you restore using FKU again. Hmm the issue is definitely not from the kernel. What happens if you uninstall FKU and try to apply them again on boot?
[Nexus 4 Android Development] jacoghi:
Zaclimon, any clues whether the kernel could be responsible for watchdog reboots? Yesterday I had three on euphoria, but I'm not sure whether this is roms or kernels fault. Thanks for all your shared work.
[Nexus 4 Android Development] adaytoremember:
That is a know issue (with the app I guess), Happens to everyone, the same with my galaxy nexus (with every kernel) and in my nexus 4. Re-applying the profile every time the phone is rebooted seems like the only way for now.
[Nexus 4 Android Development] ViRb3:
Dumb me took screenshots of the bug but APPARENTLY they appeared all the same.

Anyway, I tried reinstalling FKU and the result is still the same. Whenever colors get applied on boot they are applied as a VERY, VERY incorrect profile. I can swear it all worked perfectly on stock franco.

Have you tried if it works good for you with Quanta kernel?
[Nexus 4 Android Development] zaclimon:
I'm using Quanta + Chroma, 0 problems whatsoever on my side. All looks good.

Also everything from that side is taken directly from franco so I find it weird how it isn't applying the correct values. :confused:

Interestingly, Euphoria seems to be the only ROM that has major issues with Quanta. Kernel panics up to watchdog issues. I don't think it will serve much help but have you tried to lower your UV? Sometimes UV can make watchdog go crazy and reboot your device.
[Nexus 4 Android Development] ViRb3:
Re-flashed kernel, re-installed FKU, cleared all kinds of leftover data and cache, no change whatsoever: I continue getting the awkward color distortion. Even more confused at this point :/
[Nexus 4 Android Development] Italico:
It's here! JIT for a clean flash!

Thank you so much :)
[Nexus 4 Android Development] zaclimon:
Quanta V4 and QT 2.0

Hi guys, I wanted to finish that thing quick so I can concentrate on other things instead.

Quanta V4:

- Compiled with UberTC 5.1.1

- Fixes for good the CM PowerHal issue (it actually do it's stuff while installing the kernel instead of executing the script after the device has booted)

- Added DT2W Power Suspend Key from Stratosk.

I know that some of the quirks aren't fixed yet. Though I will look at them later when I'll some time to relax XD

As for Quanta Tweaks V2.0 here's the changelog from the Play Store:

2.0:

- Sound Tweaking support (Based off Faux123's implementation)

- Remade the interface backend (there are now animations between sections)

- Mako: Added DT2W Power Key Suspend from Stratosk

- Flo: Added S2S support

- Misc fixes and optimisations

The values for the Sound tweaks are in the help message when long pressing the card related to the tweak. Going beyond these values will simply reset the card to 0.

QT2.0 should be available in the next hours, though I'll leave available on this post because 1.4 crashes when using V4.

Enjoy!! :)

EDIT: Looks like [MENTION=5598884]Italico[/MENTION] was a tad faster than me. ;)
[Nexus 4 Android Development] yaymalaga:
Hey, thanks for the amazing kernel, just flashing right now!

Btw, some questions:

- Do you use undervolting or something extra in your kernel configuration?

- What are the benefits of using Quanta tweaks instead of for example Kernel Auditor?

- Why don't you use UBER 6.0?

Thanks for your time;)
[Nexus 4 Android Development] zaclimon:
1. I didn't understand what you meant by something extra? I mean it's based upon franco.Kernel so it has all it's features + more (The feature list is in the OP)

2. None actually. (I believe) Quanta Tweaks was made to be a complement of FKU while not having to download another kernel manager like Kernel Adiutor. It regroups all the features that aren't already available in FKU and you can set them up if you want.

3. Because I don't feel like going through an experimental GCC if using GCC 5.0 on Linux 3.4 is "sort of" experimental as well.
[Nexus 4 Android Development] yaymalaga:
The first question was about which configurations do you have in your phone that they are not by default in the kernel, so I meant if you use undervolting and also which governess do you prefer to use on your phone.
[Nexus 4 Android Development] zaclimon:
Ahh. In that case, I'm mostly using everything stock except that I UC the CPU clock down to 1242 MHZ and the GPU clock down to 320 MHZ, I UV down to -125 mV. Also the load threshold on the hotplug is set up at 85. As for the governor, both interactive and conservative are good. Though I always go with the default setting which in this case is conservative.

There have been some reports that people have been able to get 4+ hours of SOT. I also got myself 4+ hours of SOT so it is definitely possible with those settings or even lower ones. ;)
[Nexus 4 Android Development] yaymalaga:
Wow, I will try settings like this, I think my battery is dying and now my SOT is about 3.5h
[Nexus 4 Android Development] ObihoernchenDE:
Powerhal and mpdecision with cm is fixed now (Y)
[Nexus 4 Android Development] zaclimon:
To make sure that it is fixed, I made a temporary jump into CM which is why I'm certain that this issue is squashed for good. XD
[Nexus 4 Android Development] MusadiqManas:
Thanks for your time and efforts!

Can you please enlighten me with some more explanation as to how do we UV? I suppose it might be "CPU Global Voltage" under CPU VOLT but I'm not sure so I didn't apply yet.

I have applied all your suggested settings at latest V4 through Synapse, except UV.

Regards!

PS: I guess I've got it. It's decreasing volts for each CPU freq upto -125mV each e.g.

384 MHz < - - > 850mV should be altered as 384 MHz < - - > 725 mV and so on.

Plz correct me if I got the wrong idea.
[Nexus 4 Android Development] yaymalaga:
Yes, it's that. If you use kernel auditor, you can select under CPU voltage the option global offset, and then if you put -120, it will automatically reduce 120mv every cpu freq
[Nexus 4 Android Development] AndyYan:
For unknown reasons QT doesn't turn on my DT2W, and yes I installed and booted CM first, then installed Quanta. CM12.1 nightly + Quanta V4 + QT 2.0.

What's more, it seems that the parameters for DT2W have shifted location, so I can't even use the old init.d way to enable it...

Sent from Google Nexus 4 @ CM12.1

[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
[Nexus 4 Android Development] zaclimon:
Starting from V2, I've been using stratosk dt2w instead of mckael. It's parameter path is different and the activation point is only on the center of the screen now.

Does QT said that it has been activated?
[Nexus 4 Android Development] NooBs7yL3:
It's possible to active dt2w through Franco app?
[Nexus 4 Android Development] zaclimon:
Nope. Only through Quanta Tweaks, Semaphore Manager and Kernel Adiutor. (I believe)
[Nexus 4 Android Development] AndyYan:
...I see. Tried tapping on the center, and it does work.

But, to put it straight, I can't guarantee I would tap right on the center of the screen when I use DT2W, and I don't think anyone can. I don't get why stratosk's implementation is done this way. Or is there at least another parameter where I can change this?

Sent from Google Nexus 4 @ CM12.1

[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
[Nexus 4 Android Development] zaclimon:
Everyone seems to like stratosk's implementation so far because it's the one that doesn't bug out.

Sadly there are no parameter related to the area to change. Only the center of the screen is available.
[Nexus 4 Android Development] AndyYan:
Hmm, not sure what kind of "bugging out" are we talking about here (haven't experienced anything aside from occasionally having to tap more than 2 times), but if that's the case then I'll take it. Can't take having no custom kernel for my N4.

Sent from Google Nexus 4 @ CM12.1

[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
[Nexus 4 Android Development] zaclimon:
Sometimes, it wasn't possible to wake the device at all even though DT2W was activated. In a sense it "doesn't" serve it's main purpose which is to double tap in order to wake the device. Even though I liked mckael's implementation because it was more flexible, the main purpose of the feature wasn't even fulfilled. Thats's why I had to replace it.

EDIT: LOOOL at my 3700th post. XD
[Nexus 4 Android Development] yochananmarqos:
You do realize you don't have to tap perfectly centered, right? The hot zone is about 1 1/2 inches in diameter, plenty of room for error. Once I discovered that, I hit it every time.
[Nexus 4 Android Development] AndyYan:
Problem is, when using the old implementation, I never have to *intend* to tap any specific zone to wake it up. A common occasion: the phone's on the table, I reach for it and tap arbitrarily without thinking, and there it lights up. All done in under a second.

I guess the center zone will take some getting used to yet will finally grow on me - but thinking of what it takes to make the change, I chose to turn off DT2W altogether and enjoy the sheer battery life brought by Quanta.

Sent from Google Nexus 4 @ CM12.1

[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
[Nexus 4 Android Development] atulclassic:
random reboots

[MENTION=4217103]zaclimon[/MENTION]

V4 is giving me random reboots..last_kmsg has shown error as watchdog..kmsg attached

Running CM12.1 with V4..no xposed..no extra mod.

Pls help
[Nexus 4 Android Development] mdaamir1989:
Not sure about CM , but on Euphoria random reboots have been reported. I have faced the reboots myself :)

I'm not sure if it was the ROM or the kernel , but i tried a different kernel and there are no random reboots anymore . Sadly i don't think it can be fixed.
[Nexus 4 Android Development] NooBs7yL3:
I'm on cm12.1 nightly and no random reboots here
[Nexus 4 Android Development] iRefleX202:
Which kernel do you use now?
[Nexus 4 Android Development] mdaamir1989:
Semaphore :) If you feel it lacks more features you can try Jolie Kernel which is basically Semaphore + many other features ...
[Nexus 4 Android Development] zaclimon:
Mother's day update

Happy mothers day everyone. I hope you all had spent a great time with your moms. :) As you know about my semi-holiday schedule, here's an update for ya!

V5 (10/05/15)

- Reverted the mako_hotplug commits from Shamu (as an attempt to fix watchdog issues)

- Added filesystem related optimizations from Faux.

- Added some LMK optimizations from Motorola

- Added ROW optimized values back.

As some may have noticed, I have updated QT yesterday to 2.1. It is pretty much only a bugfix release and the changelog is on the Play Store.

AOSP and CM are on BasketBuild.

Enjoy! :D
[Nexus 4 Android Development] keyra74:
looks like cm changed something again.

i get the "after few hours of use" lags :(
[Nexus 4 Android Development] zaclimon:
I don't know if they changed something but could it be possible that mpdecision and power.mako.so are not renamed?
[Nexus 4 Android Development] keyra74:
power.mako.so was present

i renamed to power.mako.so.bak
[Nexus 4 Android Development] gioxoid:
Franco kernel updater app

What should i do with the FK App when it says me to download the update?
[Nexus 4 Android Development] yochananmarqos:
Nothing. FKU detects a compatible kernel, however since you're using Quanta it thinks you need to update to the latest official franco.Kernel.
[Nexus 4 Android Development] atulclassic:
watchdog

[MENTION=4217103]zaclimon[/MENTION]

Quata V5 after running great for one and a half day, a random reboot reappeared

last_kmsg shows reason as watchdog.. last_kmsg attached for your reference.

Though i am not a developer, but it seems msm_hsic_host is the culprit... i had it disabled after installing quanta but re-enabled after this particular reboot and no random reboots after that till now

device : N4 with CM12.1
[Nexus 4 Android Development] yochananmarqos:
Logic would dictate...
[Nexus 4 Android Development] atulclassic:
I am not able to understand how your post was related to my problem or any solution was there.

May be i am a noob at understanding things..

Was it really necessary to comment something unnecessary?
[Nexus 4 Android Development] zaclimon:
Alright guys don't start a war here... I was checking a dmesg I had too following a watchdog issue related to the wakelock. In that case, it would be better to disable the possibility offered by Franco to toggle it unless people really disable the wakelock...
[Nexus 4 Android Development] svnhvn:
Disabling wakelock creating more haywire than benefit.
[Nexus 4 Android Development] yaymalaga:
[MENTION=4217103]zaclimon[/MENTION] Are you using f2fs on your nexus? Do you recommend me to use it, or it doesn't make a difference in 5.1.1 roms?
[Nexus 4 Android Development] zaclimon:
I'm currently using it on both my Nexus devices. I don't know if there are differences on 5.1 but I could feel differences on 5.0 which is why I kept f2fs up to now.
[Nexus 4 Android Development] yaymalaga:
Okey, I just was thinking about giving it a try. I would use your kernel as you have updated patches for f2fs and Chroma. In Choma's forum they told me to use f2fs just with /cache and /data, is it right?
[Nexus 4 Android Development] zaclimon:
Yep. Only /cache and /data need to be wiped prior to converting to f2fs.
[Nexus 4 Android Development] fr3quency:
[MENTION=4217103]zaclimon[/MENTION], first of all I'll give you a... wait for it... bottle of Pokari. :P

I wanted to ask if you will ever add the FIOPS governor as an option. I reverted back to F2FS yesterday and, although ROW's fine, I was wondering if we'll ever get this awesome scheduler as an option. :D
[Nexus 4 Android Development] yaymalaga:
And did you notice any difference? (I mean using f2fs again)
[Nexus 4 Android Development] zaclimon:
You should buy a truck of anpan to accomodate your pokari. XD

Also as I have said earlier, I don't plan on adding any more things like more CPU governors, I/O schedulers, etc. I only want this kernel to be "good and fast" whilist not needing too much stuff.
[Nexus 4 Android Development] fr3quency:
It seems smoother to my eyes. If I keep using Quanta, why not use F2FS as well, since it was made for flash based devices such as our phones? It's like asking why you should use NTFS instead of FAT32. Although it's not that dramatic. [emoji14]

Sent from my Nexus 4
[Nexus 4 Android Development] Persechini:
And that is why I like this kernel so much. I was a franco kernel user before, but I've become attached to having usb-otg support on my nexus 4, and quanta is the only place where you get both, and with timely updates
[Nexus 4 Android Development] sidnoit22:
Best kernel yet and believe me I have tested a lot of kernels. Conservative is very optimized doesnt feel lag at all. :) 5 hr of SOT!!
[Nexus 4 Android Development] yaymalaga:
And do you know why we are also using /cache? Motorola devices only have /data with f2fs.

Other thing I want to ask you is why 384mhz is the lowest one. I know some people have problems with 192mhz, but I wonder why don't you include it and just make default 384mhz
[Nexus 4 Android Development] zaclimon:
Honestly, there are no reason to format cache as f2fs but I still do it for consistency I guess.

As for the frequency, it has been reported the 192 doesn't really improve the battery life and that 384 was enough to get the "same" results.
[Nexus 4 Android Development] yaymalaga:
So we should imagine that it's better formating /cache, right? Or could it have any negative result?

About fewquencies it's fine then.
[Nexus 4 Android Development] zaclimon:
There are no real impact of using ext4 or f2fs for /cache. Though, I did have bootloops sometimes when /cache wasn't in f2fs but it was because I dirty flashed and /cache was restored to ext4 so my fstab couldn't mount it as it was detected as f2fs.
[Nexus 4 Android Development] yaymalaga:
Then I should see the rom's installation script, and if it formats /cache it will better to use ex4 instead of f2fs right?
[Nexus 4 Android Development] zaclimon:
In this case, yes. There's no big writing in /cache so you probably won't see any big differences in performance.
[Nexus 4 Android Development] yaymalaga:
Okey,now I can stop brothering you:p thanks for the help
[Nexus 4 Android Development] dragos281993:
I dreamt last night that a "Quanta-v6" with the new 5.1.1 changes merged, came out. Just kiddin'
[Nexus 4 Android Development] zaclimon:
There are no changes for 5.1.1 as far as mako kernel is concerned. the 5.1.1_r3 tag was mostly aimed at Shamu.

Though I can tell it already, V6 won't have big changes at all. I find that the current list of features is good enough and that I should focus further on QT. (I should begin to work on 3.0 soon lool :p)
[Nexus 4 Android Development] dragos281993:
OK. Thanks for the explanation.
[Nexus 4 Android Development] sercankd:
When i use this kernel , fullscreen apps like games cause my phone freeze. is there anyone knows why? i have to hard reset my phone everytime it gets frozen
[Nexus 4 Android Development] zaclimon:
The usual stuff:

- What is your Rom?

- If it's CM or CM based, is your power.mako.so and power.msm8960.so are renamed?
[Nexus 4 Android Development] SilverDragon24:
the internal sd just disssapears on this kernel. can any one explain that?
[Nexus 4 Android Development] xshallowgrave:
This should help.

http://xdaforums.com/google-nexus-5/general/sdcard-problems-upgrading-android-t2938749
[Nexus 4 Android Development] Midomad:
Nice kernel and nice app tweaks.
[Nexus 4 Android Development] SilverDragon24:
didn't help. and usb otg doesn't work either.
[Nexus 4 Android Development] Midomad:
It should be better with v3 version to implement all options in order to not use FKU and only Quanta Tweaks.
[Nexus 4 Android Development] zaclimon:
I'm not quite ready to do a full blown kernel tuner yet. Doing something like this is a large scale project and I'm kind of lazy at the moment. Though, because I'm on vacation, I may consider doing it.

So far here's what I've planned for QT:

- Widgets

- F2FS/Ext4 Converter

- Possible in-app updater? (Would need to have a direct server)

Anyways let's see what's up in the near future. ;)
[Nexus 4 Android Development] thebrainkafka:
Nice and simpe. Thx
[Nexus 4 Android Development] Midomad:
Take you're time Bro...

You're kernel is very good and with full kernel tuner support it would be perfect.

Happy Vacation!
[Nexus 4 Android Development] shawnbrennan55:
Flash your ROMs stock kernel or dirty flash your ROM, then flash Quanta. In the meantime you should be able to see your internal SDcard as /data/media/0.
[Nexus 4 Android Development] xshallowgrave:
My apologizes then, I don't know what the problem could be.
[Nexus 4 Android Development] SilverDragon24:
the internal sd wasn't working because i flashed it ove hells core. fixed that by flashing over stock cm. but usb drives stil don;t work just keyboard and mice work. i tried stickmount without any promising results.

---------- Post added at 05:06 PM ---------- Previous post was at 05:04 PM ----------

I'm aware of that but even though i can see it my phone can't use it.
[Nexus 4 Android Development] Zenety:
I've got a broken screen so i'm trying to control my phone with a mouse. I hooked up a mouse and flashed this kernel together with the Chroma rom. But it doesn't seem to detect the mouse. Did you only flash the kernel?
[Nexus 4 Android Development] zaclimon:
Nothing big...

Hi guys, I think this is the last update to Quanta in a while. I find it pretty much stable and good now. As I said earlier, I will most likely focus on QT from now on until there are some interesting stuff about Android M. Without any other due here it is.

V6:

- Synced with the latest commits from AOSP (Looks like there were 5.1.1 commits after all)

- Compiled with an updated UberTC toolchain

- Reverted a cpufreq commit that was causing watchdog to reboot randomly the device

AOSP and CM up in BasketBuild as always.

Enjoy!! :)
[Nexus 4 Android Development] zaclimon:
Update report, now available on basketbuild.

r213 (11/09/14)

Upstream patches from Franco (hotplug fixes, interactive governor improvements)

Compiled with Up-to-date 4.9.2 GCC.

Enjoy! :)
[Nexus 4 Android Development] vampire36:
dt2w not working...on latest release ?
[Nexus 4 Android Development] zaclimon:
Hmm on what rom are you currently?

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] vampire36:
Purity rom...was working fine on r212...but after updated stopped working :)
[Nexus 4 Android Development] zaclimon:
That's strange because it dies work for me hmm. Does root works for you perhaps?

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] marcof93:
On Mahdi is working.
[Nexus 4 Android Development] vampire36:
Working fine...sorry for the false alarm :)
[Nexus 4 Android Development] jkyoho:
Works fine on my PA 4.6beta1 dirty flash from r212
[Nexus 4 Android Development] sidnoit22:
Working pretty well with Android L Port. :) Thank you developer looking forward to updates also battery seems better than Stock kernel and few more. ;)
[Nexus 4 Android Development] emanuele1986:
Works perfect with cm11 m10
[Nexus 4 Android Development] hamid3173:
Why this kernel doesn't have more governors?

Only 2 gov !!

Sent from my Nexus 4, Using LiquidSmooth 3.2, Xposed, Hells core b47