yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] MatAuc12:
Again, read the thread.

PS. This is very well related to kernel nonetheless. One major advantage of custom kernels is UV and these smarties read somewhere that a CPU that is so unstable that it reboots qualify as valid grounds for arguments.
[Nexus 4 Original Android Development] raptir:
Thanks, good to know. I wonder if changing that could show some battery improvements? I'll leave that to people who know more about this than I do.
[Nexus 4 Original Android Development] rlaw:
IIRC, this min-max behavior was introduced with Jellybean when it was first debuted back in June (or was it July?) as part of Project Butter. Google wanted increased responsiveness and a smoother, faster experience using Android.

Same reason governors that only run at min and max exist, running at max frequency results in speed and smoothness (also possible battery savings since the device can complete whatever task is needs to quick then return to min or deep sleep faster).
[Nexus 4 Original Android Development] JmPTaz09:
Yes; race to idle.
[Nexus 4 Original Android Development] Redmed427:
Will I be able to flash this kernel over the stock rom? (rooted and unlocked bootloader of cours)
[Nexus 4 Original Android Development] rlaw:
Yes.
[Nexus 4 Original Android Development] ltylty123:
Set max and min cpu to the specific speed. Try running through apps and camera to see if its stable.
[Nexus 4 Original Android Development] Step1Mark:
Is there an easy way to completely remove these tweaks? When I look at designs on my phone I want to see it how my client will see it on their phone.

EDIT

Nevermind. I think I fixed it with Trickster MOD.
[Nexus 4 Original Android Development] more2come:
So,how do I make alterations to the touch boost frequency and boost duration without using any tools that mess with the kernel's hotplugging routines?!
[Nexus 4 Original Android Development] lazer155:
How do I edit an int.d script to put the vibration strength back to 70? I prefer 70 over the new b35's setting of 80. I was using trickster mod but would prefer to do it myself with a script.
[Nexus 4 Original Android Development] jazzboyrules:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Check out the second post in this thread. That has scripts for a bunch of init.d customizations.
[Nexus 4 Original Android Development] lazer155:
Could you post a b35 settings zip too? I want to switch back and forth between b32's gamma settings and b35's settings.
[Nexus 4 Original Android Development] Step1Mark:
Well I thought I fixed it but I just held it up next to another Nexus 4 and it is still the wrong colors. Anyone know how to completely remove these adjustments?
[Nexus 4 Original Android Development] thracemerin:
I posted some scripts yesterday to change back to the stock colors.

See here: http://xdaforums.com/showthread.php?p=37904248#post37904248
[Nexus 4 Original Android Development] jazzboyrules:
Try removing Trickster mod and using the script for LG/Google gamma settings in the second post.

Doesn't Trickster have presets for Google/LG (I don't use Trickster)? - Nope, they don't.
[Nexus 4 Original Android Development] thracemerin:
This should do it.
[Nexus 4 Original Android Development] thracemerin:
Trickster can only change RGB and Gamma Amp 1/Gamma Amp 2, so switching back to the LG/Google preset will put the amp values back to default, but not the other settings.
[Nexus 4 Original Android Development] jazzboyrules:
I wish they at least had LG/Google presets that would set all 27 values. That way people won't be confused about the colors.
[Nexus 4 Original Android Development] thracemerin:
Yeah, I thought that's where they were going with their setup, and initially I thought they just hid all the other values, but playing with the gamma in Trickster is not the same as using a script, I switched to Google preset on it and it looks nothing like the version from Post 2.
[Nexus 4 Original Android Development] more2come:
Nobody here who can help me with my question? Is boostpulse control somehow broken in the latest release?
[Nexus 4 Original Android Development] thracemerin:
No changes were made to bootpulse by motley, how are you attempting to control it?
[Nexus 4 Original Android Development] lazer155:
echo "70" > /sys/class/timed_output/vibrator/amp

To make it persist after reboot do I just put it in any one of my int.d scripts? (I have a couple different ones that are for restoring and deleting various apps after rom updates.)
[Nexus 4 Original Android Development] more2come:
First attempt was with the help of Trickster Mod, but I was told that the newest release of Trickster would break motley's hotplugging routines. Second attempt was by altering the values within the files in /sys/devices/system/cpu/cpufreq/interactive

boost seems to be disabled by default, so I enabled it by changing its' value from 0 to 1. But this ramps the first core up to the chosen boost frequency all the time, not really what I wanted.

My goal is to set the CPU boost duration to around 3-4 seconds. I want the CPU to keep the defined frequency for a few secs after taking my finger off the display. But somehow I wasn't able to achieve that, any suggestions?
[Nexus 4 Original Android Development] thracemerin:
Second post:
[Nexus 4 Original Android Development] more2come:
Seems I misunderstood some parts of the manual. Thanks for helping me out, much appreciated!
[Nexus 4 Original Android Development] thracemerin:
I think the boost value you tried originally locks the frequency to that step, I remember reading something to that effect a few pages back.
[Nexus 4 Original Android Development] jazzboyrules:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

You can put that in any script you want. I have a script called 80basicsetup that has the vibrator strength tweak.

I have one question for everyone though: what is the importance of having a number in front of an init.d script? Is it just because the scripts get executed in alphanumeric order?
[Nexus 4 Original Android Development] thracemerin:
Yeah, they get run in alphanumeric order, so putting a number in front just guarantees you get them in the order you want in case something needs to be set before something else.
[Nexus 4 Original Android Development] more2come:
Finally, it works the way I want it to work! Thank you again! :)
[Nexus 4 Original Android Development] mastrgamr:
Coming from faux kernel?

I'm currently running the Xylon ROM, which has faux built in. How would I go about flashing this?

The instructions for build 35 are kind of confusing for me. Do I flash the stock kernel first, then flash _motley build 31, then build 35?
[Nexus 4 Original Android Development] thracemerin:
No, just flash b35.
[Nexus 4 Original Android Development] _motley:
Thanks everyone for the feedback on b35. I am still considering whether or not to go back to the gamma defaults in the prior version, or to tweak the values based on feedback. Going back to the old default might make the most sense since we can set whatever we want. I can then just offer a few baseline scripts if I come up with anything interesting. I see some of you have suggested some values to try, so I will be doing that as well.
[Nexus 4 Original Android Development] jassycliq:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Aroma with different presets set by init.d?
[Nexus 4 Original Android Development] ceejay83:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Have you tried the half breed color settings? It's a mix between contrasty and brightness, and it looks great
[Nexus 4 Original Android Development] nicatronTg:
I reset back to stock for 4.2.2's official update package, but I can't install it. I'm fully stock except for the kernel, so shouldn't it work fine?

Getting:

assert failed: apply_patch_check("EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot")
[Nexus 4 Original Android Development] efan3719:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

I think your colors look great and stock looks like garbage but if people want it back to stock I'm fine with tweaking the colors myself. And if you offer a few scripts that's even better.
[Nexus 4 Original Android Development] keda:
I prefer b32 color with custom zip !
[Nexus 4 Original Android Development] ogrillion:
So I flashed b35 and so far i really like it but only issue I have is this: Maybe its not kernel related but I don't have this issue on other kernels (or on older versons of motley's kernel) and I haven't flashed a new rom or anything..

But I get a lot of wakelocks on WiFi, battery stats list it under partial wakelock, and first one is DHCP and the other one is AndroidConnectivity Service..

What's odd is I only get these two wakelocks when I am on my home network, at work on their wifi I don't have them.. Any idea? I haven't changed any router settings either..

Thanks
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

You need stock kernel for it to work.
[Nexus 4 Original Android Development] ptesmoke:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

again hot plug works fine with trickster.
[Nexus 4 Original Android Development] nextelbuddy:
was running B32 on 4.2.1, just flashed 4.2.2 and really want the motley kernel back. is it safe to flash the 35 kernel on 4.2.2 yet or shall i wait, be patient and give Dev some time?
[Nexus 4 Original Android Development] thracemerin:
There are no 4.2.2 sources as yet, so there's the possibility it may be incompatible, you can try it, worst thing that would happen is you bootloop.
[Nexus 4 Original Android Development] jazzboyrules:
I am on PA's Feb 14 (4.2.2) and b35. Everything's perfect :)
[Nexus 4 Original Android Development] JaysonthePirate:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

I used the reset zip on the original post and am running stock rom, yet I still get the same error when trying to install 4.2.2. Anyone have the same problem?
[Nexus 4 Original Android Development] thracemerin:
My guess is the stock kernel from the first post is compiled from AOSP not the Google stock factory image kernel, you should be able to get the boot.img from the JOP40D factory image and flash it via fastboot, should fix you right up.
[Nexus 4 Original Android Development] JaysonthePirate:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

I downloaded the factory image but I don't couldn't figure out how to extract the .tar format with root explorer. Is there a ready to flash reset kernel that works? I could just wait for the update to get pushed. :(
[Nexus 4 Original Android Development] thracemerin:
Try flashing this with fastboot:
[Nexus 4 Original Android Development] DynamicRam:
I'm running b35 with PA 4.2.2 with no problems
[Nexus 4 Original Android Development] azrash:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

if he flashed the full stock 4.2.2 update, it might be different than running PA 4.2.2 as the update will most likely include new bootloader and baseband / radio.

Flowed from my Nexus 4
[Nexus 4 Original Android Development] lcheng1:
Would there be a way to apply these settings?
[Nexus 4 Original Android Development] azrash:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

look a few pages back for the script made by jazzboyrules, you can input the values from the linked post into the script and run it with this kernel. If you are happy with the colour, copy the script to initd folder and set the appropriate permissions

Flowed from my Nexus 4
[Nexus 4 Original Android Development] lcheng1:
Either I'm doing something wrong, or the script isn't working. I've attached my version; would you be able to check what I'm doing wrong? Thanks!
[Nexus 4 Original Android Development] ceejay83:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Colors are nice on b35! Are they PA's half breed settings?
[Nexus 4 Original Android Development] j3di:
Motley, according to your post Dynamic is default from B35 upwards. When i flash B35 i have Dyn_fsync_active = 1 / fsync_enabled = 0

No problem to add a script to turn it on if i have this wrong.
[Nexus 4 Original Android Development] thunderger:
@_motley:

Using B35 withouth trickster results in a high contrast and supersaturated 'gamut'. Contrast is nice but colors looks like candy. I know a lot of people love such supersaturated colors but this shouldn't be the goal of 'kernel-configuration'. Neutral grays and a neutral white at 120-140 lm brightness should be the goal. At this point a icc should be written and used but android doesn't support icc profiles. But we shouldn't try to set up a fake icc profile by manipulating display defaults. :D

@GPU settings:

My goal isn't to overclock GPU part of SoC but to set lower idle clocks and to tune govenor (if possible). Eventually lower GPU voltages.
[Nexus 4 Original Android Development] greg17477:
Great answer.. ;)

And again for you, NO it does not, not anymore (not the new version, which includes the gamma settings, the old one works fine). And yes it has been proven by providing values from various tests and not just "by saying so".

In fact i just tested it again in case trickster mod has been updated and it is still broken. Even the dev himself said, he made changes to the hot_plug stuff...
[Nexus 4 Original Android Development] Dave11:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Running stock 4.2.2 and b35 seems to be working fine here. For anyone else wanting to try.
[Nexus 4 Original Android Development] amigo_s:
I would like to calibrate the display according to this post:

http://xdaforums.com/showpost.php?p=37917796&postcount=12471

The settings are:

R 175

G 175

B 175

Whites 20

Mids 100

Blacks 255

Contrast 0

Brightness 0

Saturation 200

Grays 0

But he uses Franco's kernel and I like yours better ;). Now, with motley's kernel, how can I adjust the gamma and colour values correctly according to the above presets? I found this post that tells me something about what each digit means. Now, if I'm correct this should work:

#!/system/bin/sh
# Set data color pro presets from shared Google spreadsheet (thanks user acer73!)
# Use LG presents as your starting values and then adjust columns 6 & 7 from the spreadsheet
echo "625 20 100 255 0 0 200 0 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_red
echo "625 20 100 255 0 0 200 0 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_green
echo "625 20 100 255 0 0 200 0 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_blue

#Set the complimentary RGB values for this calibration
echo "175 175 175" > /sys/devices/platform/kcal_ctrl.0/kcal
echo 1 > /sys/devices/platform/kcal_ctrl.0/kcal_ctrl

Who can help me out? Thanks!
[Nexus 4 Original Android Development] sophan:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Hi,

U can use the pahalfbreed script posted here by jazzboyrules :

http://xdaforums.com/showthread.php?p=37673702#post37673702

And edit the values.
[Nexus 4 Original Android Development] jazzboyrules:
From what I have read, Franco has identified that the whites and greys variables are swapped with respect to moles' variable nomenclature. We don't know if that's the case for sure but one thing's for sure that if you are reading Franco's variables, swap the numbers between whites and grays when using my script (which follows moles' convention). Use my halfbreed script linked above and copy the variable values from that post from Franco's thread and swap the whites and greys. I haven't yet tried yet as I am too happy with the halfbreed colors :D

But you give a try to that and let me know if it worked.
[Nexus 4 Original Android Development] nikzDHD:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Been an avid user of Harshs kernel which is good itself, but been running this kernel for the last few days and it's excellent as well. Got home now off the plug since 8.45am and got 76% left still, screen on time of 45 mins, 10 min phone call, about 50 sms sent and received, Google Now sync on, 3g all day, works a treat seems a keeper only thing I've done in under volt a little. Liking the colours as well.
[Nexus 4 Original Android Development] tlongren:
b35 kernel and codefireX SR12.1 (4.2.2) have been good for me so far. I think you'll run into issues though if you flash the new radio or bootloader, if those are applicable to your ROM.
[Nexus 4 Original Android Development] thracemerin:
CodefireX is a frankenstein anyway since there is no device tree or kernel sources for 4.2.2, that's why the new radio and bootloader don't work.
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Bootloader is fine btw, just the radio that doesn't work ;)
[Nexus 4 Original Android Development] thracemerin:
I knew that, idk why I said both, I'm tempted to see if the new radio + sensor fix + 4.2.2 kernel fixes the issue with wifi, since the wifi modules are in the kernel.
[Nexus 4 Original Android Development] :
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Hi,

Kernel sources are out...

:)
[Nexus 4 Original Android Development] thracemerin:
Woot!

https://android.googlesource.com/kernel/msm/+/android-msm-mako-3.4-jb-mr1.1
[Nexus 4 Original Android Development] :
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

I've just edited my post, it's from Francisco's kernel thread....

EDIT: I was to post the link, thanks ;)
[Nexus 4 Original Android Development] iPwn_:
What I'm using both the new radio and bootloader on CFX and my Wi-Fi works fine. (With the motley b35 kernel).
[Nexus 4 Original Android Development] thracemerin:
Yeah, the issue is using a 4.2.1 kernel with the .48 baseband and sensor fix, seems to break WiFi. If you use a 4.2.2 kernel it seems fine.
[Nexus 4 Original Android Development] iPwn_:
Oh I edited the post after you posted. I'm actually using this b35 kernel, which I'm assuming is still for 4.2.1.

Unrelated: The calibrated colors posted earlier are absolutely brilliant. No over-saturation, perfect grays, perfect gamma values in Display Tester. The stock b35 colors are sort of weird. Action overflow box shadows are look like they're pasted on to white backgrounds. @jazzboy I did switch the two values you asked for.
[Nexus 4 Original Android Development] Elchemist:
If you are referring to the calibration done from the Franco thread, I guess the screens vary quite a bit.

The main issue is, I see banding using the gradient test found here

http://www.lagom.nl/lcd-test/gradient.php

I didn't see it with halfbreed or with motleys default.

It is also noticeably darker, but the OP did mention in his post that it would be darker...

While I really like the colors of halfbreed, and motleys defaults, I found that sms were unreadable outdoors unless using brightness >75% (I am not faultless in this, because I am using a theme which has grey backgrounds) Not a complaint, just thought it was worth mentioning because I find it counterproductive to UV and tweak to extend battery life only to use more than what is saved on increasing screen brightness.

Currently I am using the rev2 bright settings with the whites toned down a bit (LG's default) Will have to check more outdoors, but there is only very slight banding using the test mentioned above.
[Nexus 4 Original Android Development] iPwn_:
I'm talking about these http://xdaforums.com/showpost.php?p=37985634&postcount=1832

I don't know they look much brighter than motley b35 stock colors to me. And I'm getting no banding on the link you posted. I can no longer tell the difference between my Nexus 4 and iPhone 5 with these settings.

However I am using 255-255-255 for rgb instead of his defaults, so that might explain the brightness. I'm not getting the artifacts he mentioned.

Maybe our panels are different.
[Nexus 4 Original Android Development] thracemerin:
@_motley:

I'm testing whether or not Google merged the stuff to fix the hsic problems, it looks like maybe they merged some of what we merged, but not all of it, I built from pure AOSP in my thread and I'm going to run it through a few days of testing then reintroduce the stuff Google didn't add and see where it goes.

Interestingly enough, for some reason the mr1.1 branch doesn't include the 2 charger patches from the mr1_r1.2 release, I'm not sure why the heck that is, I guess we'll have to look at that as well. Oops, they were committed on different days and I just didn't see them.

Anyway, I'll let you know how my testing goes in a day or two and you can decide whether or not to keep that stuff merged when you merge the new AOSP sources.
[Nexus 4 Original Android Development] Elchemist:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Yeah those are the same settings I was referring to as well. Will test it with 255 rgb, not sure by how much but it should make the display brighter. Now trying the 2nd setting by Kel Ghu from the color spreadsheet. Pretty decent and bright. No banding.
[Nexus 4 Original Android Development] AcmE85:
Sounds great, could you please post your script for this?
[Nexus 4 Original Android Development] bboran:
Does this kernel updated to 4.2.2?
[Nexus 4 Original Android Development] mko000:
Not yet. Hopefully soon :).
[Nexus 4 Original Android Development] bamsbamx:
Motley, i share this link here, maybe its useful for you

They released factory images

https://developers.google.com/android/nexus/images
[Nexus 4 Original Android Development] more2come:
Finally I found the kernel that absolutely matches my needs! Low battery consumption, UV capabilities, higher tolerance in thermal controls (CPU-speed never throttled once with Motley kernel!!), customizable CPU-governor (tweaked the interactive gov to match my preferences), highly customizable color and gamma settings.

Great stuff, couldn't be happier! Now my Nexus works just exactly the way I want it to work!
[Nexus 4 Original Android Development] more2come:
Just one tiny little question left!

I wrote this small init.d-script, that should set boostpulse_duration to my desired value on startup:

Permissions were set correctly, but it goes back to default values on each boot. Any soggestions?
[Nexus 4 Original Android Development] _motley:
Hi everyone. Sorry, been busy the last few days. Appreciate you helping each other like you do so well when I am away. I plan on merging the 4.2.2 stuff as soon as I can. I should be starting on it tonight.
[Nexus 4 Original Android Development] mko000:
Thanks motley! While you're at it, could you please take a look at that as well:

http://xdaforums.com/showpost.php?p=37976286&postcount=1828

Does that mean that fsync is disabled by default now?
[Nexus 4 Original Android Development] yurilebbie:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

If you look in the second post he says that we should enable it via an init.d script.
[Nexus 4 Original Android Development] thracemerin:
fsync was always disabled by default to my knowledge, Motley added the dynamic fsync system written by faux123 in b35. If you want to enable fsync, you can do so with the scripts in Post 2.
[Nexus 4 Original Android Development] rlaw:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Starting with b35, fsync is enabled by default along with faux's dynamic fsync implementation.

Edit: I guess I should say as part of the dynamic fsync implementation.
[Nexus 4 Original Android Development] thracemerin:
Yeah, that's what I meant, poor wording on my part.

b32 and earlier it was off.

b35 it's using faux123s dynamic fsync
[Nexus 4 Original Android Development] j3di:
My experience with b35 is fsync defaults to 0 (disabled) :(
[Nexus 4 Original Android Development] lazer155:
If I use the new PACman rom that was just released, do I use the CM 10.1 version of motley since I think PACman is CM based? It is a mixture of AOSP and CM, that's why I am not exactly sure which to use.
[Nexus 4 Original Android Development] :
Hi,

I don't realy care about battery life but here is my last cycle:

ROM: AOKP PUB unofficial_Feb-05-13

No undervolt / On demand governor /304Mhz-1.51Ghz/ sio scheduler / All in 3G (no sync's) / 45% brightness.

Usage: XDA app, internet and a little sms / call, mainly browsing...

All is fast, smooth (realy)...

After testing a few kernel this one is in the top ;)

:)