yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] codesplice:
Good info, thanks. I never quite knew what the boostfreq parameter was for.

On a rather unrelated note, I'm looking to spruce up my Tasker profiles (and associated scripts) for controlling Faux kernel (check the link in my sig if you're curious), and I'd like to configure a way to automatically change color profiles. My goal is to have a much "warmer" profile for use at night. I'm not concerned with adjusting the Gamma values, just the RGB should be fine.

My attempt:

#!/system/bin/sh
echo "255 199 130" > /sys/devices/platform/kcal_ctrl.0/kcal

This works (in that the file gets updated), but the display colors don't change (even after cycling the display off and back on again). Is there another component of this that I'm missing?
[Nexus 4 Original Android Development] faux123:
You then need to put 1 also at kcal_cntrl
[Nexus 4 Original Android Development] rmead01:
Get back on your android break for the weekend!

And in case anyone is feeling adventurous, I have some settings that I'm finally happy with.

intellidemand + intelliplug - standard freq 384/1512

UV whatever your phone is cabable of, mine is -125

Governor I changed the following:

boostfeq - 1026000

boosttime - 1000000

syncfreq - 756000

up_threshold - 95

Up_threshold_any_cpu_load - 85

up_threshold_multi_core - 85

SOC C0,C1,C3

Thermal is intelli-thermal with freq throttle at 70 and core throttle at 60

freq throttle effects core 0,1,2,3 (while 2,3 should already be off at this point)

core throttle turns off cores 2,3

CPU is simple 4/7

IOSched FIOPS 2048

Just to clarify what I personally was trying to achieve. Snappiness like default with mpdecision. not lag, phone is smooth as butter when doing anything. If it's not, you can up the boost or lower the thresholds. I'm aiming for a mixture of battery and performance. I want to maximize battery life without noticing a hit in performance that i'm not willing to except. My test was playing beach buggy blitz. Went on a 6 min drive, 13~ distance (i'm not the best) and noticed minimal if any issues with frame rates.
[Nexus 4 Original Android Development] codesplice:
Thanks faux, I figured I was skipping something stupid simple. That works like a charm!

night_color.sh:

#!/system/bin/sh
echo "255 199 130" > /sys/devices/platform/kcal_ctrl.0/kcal
echo "1" > /sys/devices/platform/kcal_ctrl.0/kcal_ctrl

day_color.sh:

#!/system/bin/sh
echo "255 255 255" > /sys/devices/platform/kcal_ctrl.0/kcal
echo "1" > /sys/devices/platform/kcal_ctrl.0/kcal_ctrl
[Nexus 4 Original Android Development] v3rk:
Does anyone have a mirror for enhanced stock?
[Nexus 4 Original Android Development] justthefacts:
deleted
[Nexus 4 Original Android Development] sam razzy:
How to enable faux sound on his app called faux123 kernel app ?
[Nexus 4 Original Android Development] zephiK:
You don't.... Faux Sound is its own app.

https://play.google.com/store/apps/details?id=com.teamkang.fauxsound
[Nexus 4 Original Android Development] Globespy:
and well worth the few bucks! the change in headphone audio is wonderful. if you also have the pro version of PlayerPro, with it's downloaded DSP pack, it gets even better.
[Nexus 4 Original Android Development] RedBeardT:
Is this issue in reference to the headphone volume adjustment not functioning?

If not... Here is my issue.

'll admit that I haven't tried the OP kernel but I've cycled through a number of different ROM/kernel mixtures and haven't had any luck so far. The fauxsound drivers are recognized as installed. For control I've tried the official FauxSound Audio/Sound Control app, Trickster, and eXperience Pro which I had been using on 4.2, successfully. I've applied a large variance in settings, setting the left ear to 20 and the right ear to 50, rebooted, made sure that no audio is being played for 3 seconds prior to change, and have had no luck thus far. I'm speaking directly to the adjustment in volume with no comment on the quality of audio (which seems fine to me) and it doesn't work at all (rather than just not sticking after reboot).​

Just looking for confirmation that what I described above is a known issue.

(I will edit this post with reference if I see my question has been previously been answered.)
[Nexus 4 Original Android Development] notbrodie:
i believe that faux's statement was about the audio hacks. i'm on 19b4m and fauxsound has no effect for me. oddly enough, i feel like my n4 is much louder than it was with 4.2.2. could be placebo, but i won't know because there is no way i'm going back to 4.2.2
[Nexus 4 Original Android Development] Solitario88:
Ehi guys but faux sound and speaker on 4.3? Doesn't go?!?!

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] faux123:
FauxSpeaker works just fine under any Android version on my kernel. The HACK on speaker was deep ;)

I still haven't finished my investigation on FauxSound issues (since WCD9310 chipset or any chipset from Qualcomm is super mysterious without any documentations at all).
[Nexus 4 Original Android Development] Solitario88:
The last question dear the best settings are the same of 4.2.2 version?

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] rmead01:
I would highly recommend trying my settings posted a little earlier. They are based off faux recommendations for battery life and then I fine tuned them a bit more. Never been as happy with a kernel as I am now
[Nexus 4 Original Android Development] indiandragon:
I don't think mpdecision let's you come back to the minimum freq you set while on idle, music etc. It rather stays in >= 1GHz after you touch. That's the reason faux is advicing to turn the mpdecision off . As I said before, intellidemand serves well in realtime as even if you get stutter during intial throttle it gradually becomes smoother and later comes back to the min freq set during idle.
[Nexus 4 Original Android Development] DirgeExtinction:
Thanks for this, I'm trying it out. :)
[Nexus 4 Original Android Development] mammenj:
There should not be any stutters or lags for such high end spec'ed phones 'period'.
[Nexus 4 Original Android Development] faux123:
yeap.. My N4 is silky smooth.. I don't know why some users are experiencing stutters and lags :p
[Nexus 4 Original Android Development] DirkBelig:
Isn't your phone "magic" in that it can handle settings that green-screen and otherwise bomb out on mere mortal units?
[Nexus 4 Original Android Development] faux123:
I am running 18m_r3 same as everyone else :( Therefore there are no differences... :cool:
[Nexus 4 Original Android Development] stab244:
It does. I watched it go back down in fauxclock while letting it idle a bit after touching it.
[Nexus 4 Original Android Development] DirkBelig:
That's not what I'm saying. IIRC in the past, you've had trouble swatting bugs that others have reported because YOUR SPECIFIC HANDSET wasn't having a problem with it. Just as there are different bins for the CPU, your specific phone may be more robust than others.

All I know is that I've used your kernels since December or January (v6 IIRC) and they've just gotten better and better, providing great battery life and smooth performance UNTIL NOW. Ever since 4.3 and r18_x, it's been stutter city and all sorts of weirdness. I used to be able to set and forget the recommended settings for battery, but now it's a constant struggle to try different settings in the hopes of getting that old performance back.

Dismissing the complaints of users because YOU aren't having a problem is insulting and unhelpful. I'm wishing I'd spent more time with the stock 4.3 kernel in order to have more of a baseline, but I can't stand the washed-out colors without your kernels and I've never had a problem with them before now.
[Nexus 4 Original Android Development] faux123:
No one is dismissing user issues. But as I stated countless times and I will state one more time here again posts of issues without logs is meaningless and not helpful to me or other users who can help.
[Nexus 4 Original Android Development] DirkBelig:
Where do I pull the logs for stuttering performance, but nothing crashes? I'm about to dig out my Flip camera to shoot a video of it hitching and hanging. Bother.

I'm trying rmead01's settings and while they seemed good at first, it's back to its bad old tricks. Sigh...
[Nexus 4 Original Android Development] mammenj:
[MENTION=3332811]faux123[/MENTION], you are not on a JSS ROM? Maybe that's why you are not seeing any issues!
[Nexus 4 Original Android Development] sam razzy:
I have his app and I don't know how to enable in the settings.. Can you please tell me the way to enable it ?
[Nexus 4 Original Android Development] evcz:
I'm running 019b04m on cm10.2

Setting boostfreq to 918000 helped, currently using intellidemand with intelliplug

I can confirm that mp decision does the same (touch boost) and it set the frequency back to lower values when not needed anymore (when you stop touching the screen)

I do not think there's a difference between phones, but just a difference based on how we were used to use the phone.

I notice mainly the difference when typing with SwiftKey, I've friends on aosp keyboard that keep saying me that cannot feel any difference, maybe SwiftKey is really more demanding ;)
[Nexus 4 Original Android Development] Solitario88:
dear have don't understand!! the mdprecision will be on off or on?? the governor is intellimand? on thermal settings i m on Intelli-Thermal (kernel) and my frequency thrittle limite are 60 C and core off line limite to 60 C, is correct?? then wich core i need to active in "frequency throttling participation??

thank u
[Nexus 4 Original Android Development] ak:
You have to find where is your problem ... In this moment also jss stock rom have problems with lockup or deadlock. Find your culprit. :D

AK land valley! ;)
[Nexus 4 Original Android Development] DirkBelig:
But how? Telling someone to "find your culprit" presumes they know where to look. If I knew what to look for, I would've looked there and reported findings. Also, I'm on JWR66V, not JSS - while my N7v2 got JSS shoved upon its 2nd boot, I manually updated my Nexus 4 to 4.3 by taking apart the factory image and shoving them via ADB since the OTA failed because of the faux kernel and the "reset kernel" doesn't actually revert anything back to stock. No further updates are available when I manually checked earlier this evening.
[Nexus 4 Original Android Development] Tinfoil Hat Tom:
Have had settings pretty similar to [MENTION=4832686]rmead01[/MENTION] on a jwr66v 18m kernel and I too seem to be getting a nice combination of battery and performance.

Funnily enough Beach Buggy Blitz was my go to app too for testing performance and thermals.

One thing I've kept different is that I normally keep eco mode enabled, and it doesn't seem to affect normal UI performance (or in lightweight apps and games for that matter) in any visible way whatsoever. On the other hand, battery savings due to it are quite apparent. My phone is UVed to -125 too (might have gone further, but I thought 125 was enough), and while UVing doesn't seem to have made much of a difference battery-wise, thermals are noticeably better, particularly battery temps.

So, all in all pretty satisfied with the kernel. The only thing that's irking me now is fauxsound not working, hopefully that'll be fixed when faux gets time because the stock aux volume on the N4 is pathetic.
[Nexus 4 Original Android Development] cocchiararo:
i am using a JSS rom and i have no issues :P

Then again, i had no green screen crashes on the original 19b4 either.
[Nexus 4 Original Android Development] danslecarton:
Does FauxClock have to run in background?
[Nexus 4 Original Android Development] evcz:
At boot for sure, once booted shouldn't be needed anymore
[Nexus 4 Original Android Development] zephiK:
Dont try and greenify or kill task of apps man. Just leave it running, theres a reason why its running in the background or else you're going to be wondering why your phones acting weird.
[Nexus 4 Original Android Development] danslecarton:
Nah, I just want to swipe it away from the recent apps list and wanted to know if the settings stay applied when I do so ;)
[Nexus 4 Original Android Development] evcz:
Yes, they do
[Nexus 4 Original Android Development] psycho693:
This may be a really stupid question but where can I down load 018? I can't find the link or in his mirror
[Nexus 4 Original Android Development] szucsgf:
http://faux.androidro.ms/mako/jb43/

------------------

Someone didn't search? Read this before you react:

http://xdaforums.com/showthread.php?p=44478830
[Nexus 4 Original Android Development] psycho693:
Thank you! And just to be sure is the kernel based on jss?
[Nexus 4 Original Android Development] Craxx:
When you take the 19 version YES

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Original Android Development] szucsgf:
No, 18 is jwr, 19 is jss. For 19:

http://faux.androidro.ms/mako/beta/

You might want to bookmark the parent directory of that link.

------------------

Someone didn't search? Read this before you react:

http://xdaforums.com/showthread.php?p=44478830
[Nexus 4 Original Android Development] psycho693:
Thank you for the help I really appreciate it. I am now running 19 thanks to you and my confused self lol
[Nexus 4 Original Android Development] Khaiyan:
Not sure if this is the correct place to post but...

I'm running version 18 on my stock 4.3, however, the custom gamma settings I have enabled through Faux Clock do not stick after reboot. Is this is a recognised issue? Is there a solution to this?
[Nexus 4 Original Android Development] gianton:
Have you installed busybox?
[Nexus 4 Original Android Development] wharmecht:
I had to have BusyBox installed and then after a reboot all I had to do was cycle the screen off and on once the app was loaded.
[Nexus 4 Original Android Development] Khaiyan:
Interesting. I didn't think BusyBox was needed since Faux Clock did change my gamma settings (it just didn't stick after reboot).... I'll give it an install now and report back.
[Nexus 4 Original Android Development] Guto ViP:
[MENTION=4832686]rmead01[/MENTION], is that?
[Nexus 4 Original Android Development] occtec:
I flashed the 4.3 mainline kernel over PA 3.95 following instructions to the dot from OP I then installed touch control and set it up for s2w and s2l after exiting the app my phone reboot when I attempted to swipe to lock and I was welcomed with a kernel crash screen. Have I done something wrong :confused::confused:
[Nexus 4 Original Android Development] Stryder5:
Which kernel did you install? v19? What was the message that you got when it crashed? Did you get a last kmsg log? You really need to provide details.
[Nexus 4 Original Android Development] occtec:
Yes it was v19 and no sorry didn't get log. Noob question how to get this log when the crash is reported before JB loads up?
[Nexus 4 Original Android Development] defffizz:
is it just me or sweep to wake doesnt work after screen was off for longer than couple of seconds? sweep to lock works good, sweep to wake only if i try it immediately after locking device. after some time, it works only after 5,6 times, sometimes not even than. im using faux clock from playstore.
[Nexus 4 Original Android Development] gariak:
Just so people are aware, the latest 10.2 feature merged, hardware tunables, seems to interfere with the color settings from this kernel. It looks like they're conflicting in some way. I get a weird blue cast to the screen. I reverted the change that enabled them on mako and it fixed the problem. Just an FYI.

Sent from my Nexus 4
[Nexus 4 Original Android Development] evcz:
Backup application settings is not working on cm10.2, is that a known issue or am I doing something wrong?
[Nexus 4 Original Android Development] faux123:
make sure you have busybox install properly.
[Nexus 4 Original Android Development] sujith1994:
1.9 GHz is frikin awesum but what about the temp and stability man is it good?

Love your kernel BTW!
[Nexus 4 Original Android Development] evcz:
busybox seems fine (the app itself works ok)

btw posting some battery stats that I consider amazing (coming from a i9300... so I'm easily suprised)

cm10.2 euroskank

kernel faux 019b04m

6hours on 3g

all the other time on wifi

sync always on

-125mv UV

intelliplug + intellidemand (boostfreq 810000, boosttime 2sec)
[Nexus 4 Original Android Development] californicated:
There are already some people reporting about the issue in this thread. Some other kernels with s2w have the same unresponsiveness, some not.

You could try the touch control beta, although the battery drain is higher than with s2w enabled.

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Original Android Development] notbrodie:
touchcontrol isn't working for me either. i don't think the dev has properly updated the app for 4.3
[Nexus 4 Original Android Development] 2010ngojo:
Can anyone reupload the stock kernel for 4.2.2. It's not availible for me. I need it because everytime set the CPU clock speed the phone freezes and reboots. Using the tbu version by the way.

Also crashed when I start Touch Control and load the modules. Crashes when loading around the "modley" module or whatever.
[Nexus 4 Original Android Development] szucsgf:
Anarkia keeps a stock reset kernel in the OP of his kernel thread:

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

[KERNEL] [AK] [FAUX☆017b2] [3.4.55+] ★ HYBRID MEETS AK ★ v.069 ★
[Nexus 4 Original Android Development] 2010ngojo:
Thanks, I just updated the Touch Control to the lastest version, and the modules seem to load fine.

The kernal seems very unstable to me when especially when changing clock speed.

Also I'm having problems getting the CPU settings to set on boot. Keeps reverting to some weird settings which bogs down my system like crazy.
[Nexus 4 Original Android Development] mgorman:
I just flashed the PA JSS and JWR blended rom and flashed 19b04m and I get screen tearing again
[Nexus 4 Original Android Development] californicated:
you need v018
[Nexus 4 Original Android Development] zephiK:
019 is for JSS15J.

018 is for JWR66V.

use 018.
[Nexus 4 Original Android Development] Solitario88:
News about faux sound friend??

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] malukiz:
I like this kernel ! Very smooth, no lags with games and a good battery.

However plz do something for your apps, a lot of options but not very user friendly :p
[Nexus 4 Original Android Development] n82k:
If you want to use 19b04 just disable hardware overlays in Dev settings and boom... buttery again.

But just like the old days, has to be done on each reboot.
[Nexus 4 Original Android Development] myturbo1:
Any shed any light on this kernel , with pa 3.96 (jwr) battery life. Max/min CPU & GPU clock. Antutu bench ?

★Nexus⁴★LTE★
[Nexus 4 Original Android Development] 2010ngojo:
Anyone got v16 tbu or v15 tbu running stable? Crashes everytime for me and I didnt even overclock it. I got v16 tbm running fine though, even fully overclocking the CPU and GPU.

On a side note, does anyone know how to disable the 60fps limit?
[Nexus 4 Original Android Development] Sucalakafufu:
not all chips can handle the tbu builds. and the kernel boots up defaulted to max so it would be overclocked even if only for the boot process
[Nexus 4 Original Android Development] andrewk2x:
Nice kernel and very good battery..Thanks!!
[Nexus 4 Original Android Development] Enzopreme:
I'm not seeing a download link for anything other than "stock cpu frequencies" where is the download link for the OC kernels?
[Nexus 4 Original Android Development] szucsgf:
No oc kernels for now. Oc was causing issues on 4.3 kernels.

------------------

Someone didn't search? Read this before you react:

http://xdaforums.com/showthread.php?p=44478830
[Nexus 4 Original Android Development] Zanr Zij:
ES = best for me! Smooth and amazing battery life. More than 200% standby time, 130% screen on time.
[Nexus 4 Original Android Development] trumanwu:
I am considering to update my nexus 4 to Android 4.3

But I read on the internet that there were some issues with Android 4.3 on Nexus 4.

I also saw there is a update of Android 4.3 (JWR66V vs 66N).

Does that mean the issues have already been fixed?

Is it good to update now?

Thanks.
[Nexus 4 Original Android Development] szucsgf:
Depends on how you update I suppose. If you do an OTA then you'll receive JWR66V and you'll be fine. JWR66N was just the leak. Most ROMs are based on AOSP which happens to be a newer build, JSS15J to be specific. Some new problems were introduced in JSS. If you want bug-free you might want to do OTA or a JWR ROM (there are a few).
[Nexus 4 Original Android Development] trumanwu:
Yes, I would like to do OTA.

So it seems there are no big issues on Nexus 4.

Thanks!
[Nexus 4 Original Android Development] faux123:
Yeah... ALL Nexus users should update to 4.3 since it's a Nexus and you should run the latest greatest official builds.

Also just a reminder... ALL 4.2.x support has been discontinued from me.
[Nexus 4 Original Android Development] fcb-1899:
Re: [Kernel] (ver 018) Mako JB 4.3 (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Jul-25]

EDIT: MY BAD GUYS SEEMS TO BE CAUSED BY TOUCH CONTROL...

ey guys I flashed the jws kernel on the latest build of PA but I'm having some problems, after about a minute the phone freezes and reboots to a green screen. I've flashed a lot of kernels in the past so Im not exactly a noob but I guess I'm doing something terribly wrong...

-Download the jwr from the op

-Flash from recovery and reboot

BTW I'm coming from Franco so maybe that's causing the issue?
[Nexus 4 Original Android Development] defffizz:
Does sweep to wake works with faux jwr kernel? Cause I flashed enhanced stock for jwr and can't seem to find this option in faux clock? I could use it with 19 beta

Edit: it works with 18 jwr, not with enhanced stock

N4, PA+Faux
[Nexus 4 Original Android Development] ev!denz:
The same here. I was the whole time on that kernel but now with 4.3 on PA I have problems. The display flickers if there is a touchinput.
[Nexus 4 Original Android Development] fcb-1899:
What versión of the ROM are you using?if 3.95 or older you have to use jss and from 3.96 you have to use jwr
[Nexus 4 Original Android Development] californicated:
Yes and no. You can enable it, but you will need several tries to unlock your phone as soon as it's in deepsleep.
[Nexus 4 Original Android Development] faux123:
yes.. sweep2wake has issues after deep sleep. The best way is to double tap it briefly to bring it into shallower sleep, then you can sweep to wake it...

This issue exist with the original code and showp1984, the original author for sweep2wake, would be the best person to ask about this issue.
[Nexus 4 Original Android Development] jarjar124:
I'm sure auto correct kicked in. Auto correct can be an ass at times
[Nexus 4 Original Android Development] MatAuc12:
Load doesn't work that way, you don't fill a core to 100% and than give the remaining to the other core. Additionally applications need to be optimized for more cores (distribute work load)
[Nexus 4 Original Android Development] STIawdFTW:
Which results in cooler temps and faster response :). Why have one person move a couch when you can have 4 do it quicker and use less energy.
[Nexus 4 Original Android Development] ctfrommn:
I understand all that conceptually, I am just unclear as to how exactly eco boost works.
[Nexus 4 Original Android Development] MatAuc12:
Not sure if you agree or disagree, but either way, if you would have a load distributed equally to 4 cores working at 25%, it would be more power taxing than 1 core 100%.
[Nexus 4 Original Android Development] STIawdFTW:
My analogy didn't really make sense now that I read it over. By using less energy I was supposed to be saying something like not getting as sweaty maybe......lol yep
[Nexus 4 Original Android Development] undercover:
It doesn't work like that AFAIK. Let's say core uses minimum of 5 energy units maximum of 10 (0 to 10 where 0 is offline and minimum frequency is at 5). One core at 75% load is using 7.5 units. 2 cores at 25% load will be using 5(because 5 is minimum) x2=10 units of energy. That is very simified version of how I understand it.