yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] _motley:
Hi, glad you are enjoying the kernel. I played with even lower voltages early on and didn't see any benefit. I have the regulator in the kernel lowered to 600mV and this is the only limitation that I know about. It will probably stay there since I don't see much reason to go back and test that stuff again. I can typically run my 304 @650mV and don't see any issues.

I ran some tests with enabling pointer location and I don't see any limitations on where I can touch. Perhaps I am not running the tests just as you are, but after several screen on/off cycles throughout this morning, I seem to be able to create a blue trace lines anywhere I want on the screen, even the corners and out to the far edges.

Now, I see Stryder says his works, but I know the PA ROM is able to be customized ten different ways 'til Tuesday;) Are you guys sure you are both running with the same exact build and configuration?

There are some patches for the input drivers in the kernel that bponury and I talked about early on when he was trying to add support for my kernel. I looked in his git and faux has these patches applied. I never applied them as it wasn't necessary at the time and I decided to stay like stock. I have been thinking about going back to research the patches since I have seen other devs apply them as well. Not sure if it is related or not, but we could give the patches a try.
[Nexus 4 Original Android Development] jazzboyrules:
Yes, we both are running the Feb 9 build (v3.0) of PA. Stryder is running the faux kernel. For now I have switched to faux to try it out. I will run it for 24hrs and see if the issues replicate.

Probably those patches make a difference. I am now on faux for about 2 hours and the whole screen becoming unresponsive and slivers of screen going dead on top and bottom have not reoccurred. It is too early to say if the kernel switch fixed it. I will report tomorrow with the results of the switch. Then we can be sure that those patches did something that prevented those screen issues.
[Nexus 4 Original Android Development] whittikins:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

What are you using for 1026?

Any cool features or changes planned for a future build?

If one wanted to mimic mpdecision, would simply increasing bootpulse duration to a few seconds do the trick? Thanks :)
[Nexus 4 Original Android Development] _motley:
I use 962.5mV for 1026MHz (nominal chip). Sure, you can mimic mpdecision with interactive gov and a boostpulse_duration of 2,000,000 (2 million microseconds = 2 seconds). Make sure you reboot if you changed the gov back and forth recently....that seems to stop the PowerHAL requests after they fail for awhile.

New build is ready, hope to have it posted tonight!
[Nexus 4 Original Android Development] ctfrommn:
Wow, changing to 2,000,000 makes a huge difference. Any reason we keep it at 10% of that by default? New builds make me :D

Hmmm, odd.....changing that seems to negatively affect cpu scores. I would think it would have the opposite effect.
[Nexus 4 Original Android Development] Remoteconcern:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

It probably keeps it on 1000mHz for longer, preventing it from ramping up? The reason we don't keep it like that is because keeping the minimum frequency as 1Ghz for 2s whenever you touch the screen is extremely battery unfriendly!
[Nexus 4 Original Android Development] jazzboyrules:
Ah! I ran out of today's thanks! Should I be looking forward to the Touch Control fix? :)
[Nexus 4 Original Android Development] ctfrommn:
Thats probably valid to a point. I care more about smooth then battery as I never come close to using it in a day. Stock kernel goes a bit too far though. Onlining cores is so aggressive on stock.
[Nexus 4 Original Android Development] _motley:
Build 35 released

Hi everyone, I have just released build 35. See OP for all the details.

Unfortunately not this release. I was too close to trying to get this build out the door and didn't want to try to add anything new into the mix. However, I can merge the input device commits we talked about and send you an AnyKernel zip so we can test. Sound good? Let's make sure b35 is sound and still replicating the problem on PA first.
[Nexus 4 Original Android Development] thracemerin:
The new gamma settings based on something moles put together or just something you put together?

I like them btw :good:
[Nexus 4 Original Android Development] Raphael17:
How Exactly Should I Flash?

Hey, I am on the Franco kernel and am looking to try something else I have read good things about your kernel. What steps should I do in flashing should I just download the newest AOSP download (I'm on Paranoid Android) and then flash? Or do I need to flash a previous build and then flash the newest one. If so, which one should I flash? Thank you SO much for everything you do
[Nexus 4 Original Android Development] thracemerin:
Probably need to reflash PA or the reset kernel to get rid of the Franco stuff, then flash the b35 zip from the OP, that's it.
[Nexus 4 Original Android Development] Kocai:
Just want to make sure, do we need to flash b31 first before flashing b35?
[Nexus 4 Original Android Development] thracemerin:
Nope, its a full package.
[Nexus 4 Original Android Development] azrash:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

The colour looks good! Even on a very low brightness setting and when I crank it up. Thanks again for the update. Didn't notice that there were grey background on the G+ app before this.

Sent from my Nexus 4
[Nexus 4 Original Android Development] jazzboyrules:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Hi motley,

I tried faux for about 12 hours and the Pie issues didn't happen. Now I'm back home on b35. I am loving the colors!

Now I am just waiting for those touch screen issues to happen once again haha.

Since installing, my phone has gone to deep sleep twice and those issues haven't come up yet.

So far so good. Loving this kernel :)

UPDATE:

The colors look good but they don't faithfully reproduce the bright grays and whites. Banding in whites can be seen in pictures that have high exposure. This is a result of clipping happening on the white side.

But I am thankful to your generic gamma interface. I am back on mole's original halfbreed settings.
[Nexus 4 Original Android Development] efan3719:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

_motley the colors look great. I was using a tweaked Halfbreed from moles but this looks just as good or better. :D
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Personally I'm not that keen on the colours, to me the whites and grays look a bit out of whack, it would be great if there was a version without hard coded colours, maybe you could ship a init script with your preferred colours, so those who don't want them can revert with ease?

Really appreciate your work, r32 has been rock solid for me :)
[Nexus 4 Original Android Development] ctfrommn:
They arent hard coded.....Im still using the same script I was. Although I will give these a fair try, they seem they may be too light for me though by looking at the values.
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Hardcoded/set as default, w/e
[Nexus 4 Original Android Development] thracemerin:
You can always use the scripts from post 2 to go back to his original defaults.
[Nexus 4 Original Android Development] ctfrommn:
Exactly my point.
[Nexus 4 Original Android Development] KaliKot:
Whats the difference between the CM10.1 build and the Stock/AOSP build?

Is it only CM users which should use it or does it cover CM-based roms as well?
[Nexus 4 Original Android Development] thracemerin:
You'll never find a color/gamma combo that everyone is going to like.
[Nexus 4 Original Android Development] ctfrommn:
Very true.....this is why I'm a bit leery to see devs building them in. I would be for easy ways to implement.
[Nexus 4 Original Android Development] thracemerin:
Well, motley does expose the whole gamma interface so you can set it however you like. Imho the colors that the dev likes should be the default, but I'm biased because I like them.
[Nexus 4 Original Android Development] jazzboyrules:
The devs have the right to set the default values that appease them. They are simply sharing their work with everyone and on top of that are also adding features based on public opinion. The users do help the devs weed out some bugs but the whole ecosystem is not a justified symbiosis. So if someone is using the dev's work, they should be grateful that they have a way to override the defaults. I don't understand why people complain when they can set the colors/rgb the way they want.
[Nexus 4 Original Android Development] rlaw:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

There's a difference between constructive input and complaints.

---------- Post added at 05:17 AM ---------- Previous post was at 05:13 AM ----------

I believe CM uses a different ramdisk. My assumption would be that both CM and CM derived ROMs should use that version of the kernel build.
[Nexus 4 Original Android Development] thracemerin:
Right, but again you're never going to find a combination everyone is happy with, there are those who didn't like stock preset, there are those who don't like the current preset, if he changes it to something else there are going to be people who are unhappy with that, in this case a default setting that motley is happy with and the ability for users to make any changes they'd like is the best option and we already have that.
[Nexus 4 Original Android Development] rlaw:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

I'm not sure if I agree. Every screen is different so calibration as it appears in one display won't match what another sees. I certainly understand your point but I'm not made up on whether or not this is one of those things that should be left as close to stock to possible for users to tinker with.

Motley does have the ultimate say but I s'pose he'll take public feedback into account to inform his decision.
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

I wasn't demanding or expecting anything ;) just giving my opinion, colours are not my cup of tea.

I'm slapping together a script anyhow :)

(Slightly OT, what rgb values match the LG preset? 255 250 245? Bit of booze making me a bit fuzzy :))
[Nexus 4 Original Android Development] thracemerin:
I don't think anyone is demanding anything, maybe debating the merits of the current defaults vs the stock defaults, the only thing I'm saying is the point is more or less moot since we have the ability to make whatever changes we like.

It seems that this is one of those things that people feel somewhat strongly about either way, and we could probably go on for pages and pages about it without any consensus coming out of the discussion.
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Pretty much, I chucked a script together to change them to what I like, so consider my comment (complaint I suppose :p) null and void ;)
[Nexus 4 Original Android Development] ctfrommn:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

People have been extremely irritable since gamma tweaks came out... I'm thinking I'll just shut my mouth and be happy there are options.

Sent from my blazing bionic Nexus 4
[Nexus 4 Original Android Development] warfexion:
No matter what I do I cannot make any kernel better than this! :) The smoothness is identical to mpdecision even though I have it off and this kernel is just absolutely fantastic on usage, I can't seem to find ANY other kernel that maintains the perfect UI responsiveness and decent battery! Thank you for this kernel this is the way the Nexus 4 should be experienced :)
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Oh man, b35 is a major no go for me. Starting from colors, too dark, over saturated look the the display. Doesn't look natural at all.

To data, I can barely get reliable data now, it literally times out left and right, I can't even get xda to load. Tried rebooting, reflashing, same thing.
[Nexus 4 Original Android Development] thracemerin:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

The colors are changeable with a script, the script to return to the original Google colors is in post 2, just name it 91rgbgamma and stick it in your /system/etc/init.d folder with the appropriate permissions and you're good to go.

There were no data related changes from b32 to b35, so the data issues you are experiencing are unrelated to the kernel update.
[Nexus 4 Original Android Development] Kocai:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

It's weird that after running the script using System Tuner, it didn't show the value of RGB and all the gamma but the colors did change and I checked the value with Solid Explorer.
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Yea, I know. Data started working fine all of the sudden, odd.

Colors, I'll have to read on how to tomorrow, moles colors have way more eye strain to me :/. I'm picky when it comes to colors and I used to love superamoled. However, since yellow tint has been gone, I loved nexus display more than any other. Now though, I don't see what people like about moles colors. I tried them few times now, am not a fan at all. To each their own I guess.
[Nexus 4 Original Android Development] Try4Ce:
I LOVE the new b35 kernel release. It feels so slick and fluid, and I really like the color calibration.

Attached are 2 screenshots of AnTuTu, Quadrant and Epic Citadel, if of interest.

Running the PUB Krait AOKP build from Steve.
[Nexus 4 Original Android Development] j3di:
I like the latest update Motley, screen looks fantastic and the user experience is unbeatable; well, until your next release!
[Nexus 4 Original Android Development] keda:
I'm also not a fan of new default color calibration. Too saturated. I think the default should be the default. :(
[Nexus 4 Original Android Development] pawo99:
I like new colours in b35 :good:
[Nexus 4 Original Android Development] dark_ente:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

B35 here, temperature is incredible

No data drop so far, consider I'm mostly on 2g

Sent from my Nexus 4
[Nexus 4 Original Android Development] sideeffects:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

If the default gamma values are changed in kernel are they identified/read properly in apps like trickster?
[Nexus 4 Original Android Development] Remoteconcern:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Yeah.
[Nexus 4 Original Android Development] Minux31:
Love colors in b35, thanks _motley :)
[Nexus 4 Original Android Development] :
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Hi

Is there GPU overclock with the experimental builds?

I read the changelogs but I don't see an info (I was thinking yes for GPU overclock but don't remember exactly). Because Trickster mod see 400 Mhz as current frequency and I can't choose 487 or 480 Mhz, so I presume no GPU overclock

Thanks :)
[Nexus 4 Original Android Development] batman368:
b35 is really nice, i use the LG gamma preset in trickster mod, gives better whites than google preset, imho

speed of kernel is awesome, as usual :)
[Nexus 4 Original Android Development] _motley:
Thanks for all the feedback everyone. I always gain valuable information and enjoy reading what everyone has to say if I don't directly comment.

Unfortunately, we won't ever have a color default that everyone likes. First I used the stock default, then I tweaked RGB a bit, then went to the LG Presets without RGB tweaks. Along the way, there was always someone that didn't like the change, but I always tend to go with the majority. So, we'll see how it goes after everyone responds. But, like most have said, the good news is that we can all have the colors we want.

For those evaluating the colors, please make sure you don't have any other apps starting automatically (or scripts) manipulating the gamma or RGB on startup. For example, if you use faux or trickster, it will overlay their options on startup. While the apps have have access to all 27 slots in the gamma interface, the are not taking advantage of all of them. If the app or script reads in the values and then sets half of them back, the colors will look funny. For now, if you want to create you own colors and/or use the apps, then it is best to create an init.d script that is created by values kicked out using your app of choice.

The main problem we have currently is that apps are only honoring some of the 27 values possible gamma slots, and scripts and apps don't play well together. Right now, if you load and then apply my colors values, they will partially overlay my colors and they will look bad as a combination. Please keep this in mind when evaluating my new color scheme. Since you can't manipulate all the values in the apps currently available, there is no way to get back to my original scheme. Some of us devs are discussing a kernel interface that will hopefully give everyone what they need from apps and scripts so they can live and play together. Currently, the scripting interface can update all 27 gamma slots + 3 RGB values. This is more powerful than what the apps will allow. The goal would be to get them in sync with a common interface. All 27 must be controllable and honored in some fashion or another. A few slots are unknown and we currrently leave them as zeros, but we still need to allow for them as they might be considered useful at some point.

They are only kinda shown properly as I have explained above.

I appreciate the input. Actually, I don't care for the moles colors either, while they liven things up a bit, they are too dark for my liking. The color scheme I am using is my own. It is a bit brighter than moles and it is a work in progress. I am sure things can be done to make it better. It kinda feels that we have had two extremes, stock from Google that was yellow and too washed out, then LG that is still kinda washed out and now we are trying to find something a little better without overcompensating. If anyone has any numbers for a color scheme that has these goals, let me know. During my testing (see my script I used a few pages back), I compared LG with mine and mine with moles. I tried to hone in on something that was middle of the road.

Thanks warfexion, I wish all the feedback could be like yours:)
[Nexus 4 Original Android Development] _motley:
No GPU overclock at this time. I played with it, but have not seen any evidence that it helps much at all. Plus it uses more battery and generates more heat.
[Nexus 4 Original Android Development] rlaw:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Odd. Before this build, fauxclock/trickster would not show the option to clock past 400MHz. Now they both do. Perhaps this is where confusion stems from?

Could also be the result of updates to those apps and not this build, though this is coincidentally the first build I've encountered with the behavior.
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

It's showing as the app updated with support for changing it, nothing todo with the kernel.
[Nexus 4 Original Android Development] dj_ghosie:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Now I see proper colors, thank you!
[Nexus 4 Original Android Development] Remoteconcern:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Motley, your feedback and support on this thread are absolutely top notch. I love it.

The kernel is the fastest for me, and I'm looking the new colours although I tweaked them slightly with trickster. I'm somewhat confused as to the meaning of tricksters settings and why they're so different to trinity or francos, which is slightly confusing. I imagine you developers will all settle on a unified interface at some point though.
[Nexus 4 Original Android Development] AcmE85:
I am on b35 right now and like the color improvements,

but unfortunately there is some color distortion on pictures

which can not be seen on screenshots.

Bright areas getting even "brighter" which is weird,

because in gallery the picures are displayed correctly while

swiped. When the transition from one to another picture is done,

the distortion becomes visible.

I am on latest CM10.1 right now and flashed the appropriate Kernelversion.

I even flashed the nightly and Kernel again to eliminate

possible interference from b32 Kernel.

My old digicam is charging right now, so I will post some pictures later.

Is there a way to use b35 with b32 color scheme?

I tried

#!/system/bin/sh
# Set LG presets (motley stock) - i.e. popular partial revert of Google's tweaks just before release
echo "383 114 21 118 0 0 0 80 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_red
echo "383 114 21 118 0 0 0 80 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_green
echo "383 114 21 118 0 0 0 80 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_blue

as init.d script, but no change.

edit:

Tried to capture some pictures, but my crappy cam is no help in pointing out what I want to show :/

edit2:

Nevermind, back on b32 for now. I can observe the same behavior now, though there is almost no distortion on bright areas.

So I just think it is this way for everyone with b35.

Thanks again for your Kernel, I will wait for future improvements! :)
[Nexus 4 Original Android Development] azrash:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

^

Have you checked whether the script have been given the right permission? I tried copy pasting the script into a text editor but it didn't work as well. What i did was to use jazzyboy script file, change the values to my desired values and copy it to initd and set the proper permissions and it works.

@ motley I think you have find the right balance with this colour preset, i have tried moles revisions but I find them a bit too dark for my liking.

To others, disable other third parties colour control apps, freeze them or something and reboot your device with b35. Try to use it for a day or two. I am definitely liking it more than when I first tried it. It looks better as compared to my old HTC Desire Z screen (the HTC have a better colour reproduction as compared to N4 with LG 's preset.)

Sent from my Nexus 4
[Nexus 4 Original Android Development] AcmE85:
Shame on me! I forgot to give the permissions to execute :eek:

Now it works. Thank you.
[Nexus 4 Original Android Development] DynamicRam:
use this flashable zip

http://xdaforums.com/showpost.php?p=37854974&postcount=365

you can adjust the values the way you want it
[Nexus 4 Original Android Development] brainbeatuk:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

@motley or anyone.

I have been messing with undervolting and have found something.

I can set my CPU to 1242 at performance and can low volt to 800 it stays on and seems stable when at set speed but as soon as I switch to interactive get a reboot.

This happens if you min max aswell . will look sweet then when your happy with every level bam instability.

I love 1024 at four core as it doesn't overheat trying to lower 1.13 and 1.24. My 1024 is at 650mv.

Seems smooth but only been using twenty mins
[Nexus 4 Original Android Development] jazzboyrules:
Hi _motley,

Either something got fixed inadvertently or my phone's having a placebo effect :P The Touch Control issues are gone and I am able to use Pie perfectly fine. One difference is that now I am on Feb 11 version of PA and earlier I was on Feb 8 version of PA.

I am happy with the motley+PA+touch control combo now. I'll keep my eye open for those old issues.
[Nexus 4 Original Android Development] DynamicRam:
this will happen if you undervolt all the frequencies with the same value so that it is stable at 1242 but when you switch to interactive it goes to a lower frequency which is unstable at that same undervolting value