yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] brainbeatuk:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Ah I understand I think. Eg when ramping from 800 to 1242 could use lower voltage for a few ms in transition which would be too undervolted.

I just had a reboot at 1.67 and got red light so I'm sticking with what I was clocked to previous. Not touched 1.4 plus left to default. Fast binned. 1.24 max for me then
[Nexus 4 Original Android Development] starscream92:
Anyone else have the following problem?

I flashed the kernel, changed the voltages, TCP algorithm, I/O scheduler, and what not. Didn't touch the color or gamma settings at all.

Whenever I locked and unlocked the phone (through the power button), the colors would change. To very ugly ones (way too much on the cool side). Trickster doesn't seem to show that the values were changed though.

Rolled back to exp-b32 until this thing is resolved.
[Nexus 4 Original Android Development] j3di:
+starscream Sorry to say that behaviour is not happening here, I have tweaked settings via a script but I don't have any apps installed that can mess with any display settings.
[Nexus 4 Original Android Development] jazzboyrules:
Try uninstalling/freezing Trickster, reboot the phone and then see if the issue repeats.
[Nexus 4 Original Android Development] thracemerin:
Trickster MOD only adjusts the gamma amp values, not the full gamma control that Motley allows, so changing the gamma settings in Trickster may have unusual or unexpected results, it is much better to use the scripts from this thread to make adjustments so you adjust everything properly.
[Nexus 4 Original Android Development] greg17477:
AW: [KERNEL][Feb 11][b35] _motley kernel for the N4

Guys, be aware the latest trickster mod version (that with gamma settings) messes up motley hotplug management. Basically it became incompatible :/ you can't control how many cores should be active and the frequencies do apply to only one core.
[Nexus 4 Original Android Development] starscream92:
Really? I changed it from 4 to 2 and it seems to be working fine...

Shame, I love Trickster. Might have to uninstall it then.

Noobish question, but can anyone point me in the right direction on using init.d scripts correctly? How do you conveniently change them? How do you keep them after a ROM/kernel flash?

Again sorry for the noob question. Never really needed to use init.d scripts :)
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Motley, do you think it'd be possible to release a version with b32 colors? Pretty please :).
[Nexus 4 Original Android Development] thracemerin:
Just use a script to revert them.

Edit: flashable zip attached should put you back on the stock colors.

MotleyGoogleColors.zip = stock kernel settings

MotleyStockColors.zip = b32 stock colors
[Nexus 4 Original Android Development] greg17477:
Limiting max core maybe works, if you limit them within trickster mod. But using the script, try to set min cores to 4. It wont stick anymore. Or set it to something between 2-4 and set min frequency to 1,5Ghz, this will apply to only one core, while the other ones keep bouncing. These are just an examples, but prove trickster mod to break motleys hot_plug management. And i was so happy to see trickster with the gamma settings enabled, but then i noticed, something is wrong and started testing.
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Thank you, that works.

For somebody that was wondering why init.d scripts weren't working, make sure you have busy box installed to system/xbin. If you grab the installer from play store, it defaults to bin location, you need to change it to /xbin for scripts to work.
[Nexus 4 Original Android Development] lazer155:
What is the difference between RGB and Gamma control? I am confused about what the difference is. I had thought both just change the amounts of red, green, and blue to change the screen hue.

---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------

Will they stick after reboot?
[Nexus 4 Original Android Development] jazzboyrules:
To put it in simple terms, from what I understand, RGB defines the base color of any object. For analogy, imagine there is a red ball in the center of a room. Whether the room is lighted or not, the ball will be red (255,0,0). But what matters is what color YOU see. If the room is pitch dark, you will perceive the ball to be black in color, if thousands of lumens of spotlight is flashed onto the ball, you will perceive its color to be white. Here's where gamma comes into picture. The gamma settings have to be so that the saturation, contrast, brightness, etc of each of the color channels (R,G,B) is perceived in the most accurate fashion. For our N4 kernel, we have 9 gamma tweak points for each of the color channels.
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

They do stick, seems kind of dim. But I may be losing my mind now lol.
[Nexus 4 Original Android Development] jazzboyrules:
The zip puts the rgbgamma script in init.d. So the settings will stick.

You will though have to flash the same zip after each kernel update.
[Nexus 4 Original Android Development] thracemerin:
Those are the exact values that were in the kernel before motley changed them.
[Nexus 4 Original Android Development] popophobia:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

How can I make a script to modify the voltage? I'm trying to rely less on tricksterMOD app.

Thanks
[Nexus 4 Original Android Development] j3di:
Use System Tuner app. It can tune your voltages and save them as a script in the init d folder. Then remove the app if you don't like it. Remember to backup your init d folder every time you flash a rom update or instead put scripts in data/local/userinit d folder.
[Nexus 4 Original Android Development] thracemerin:
The file that keeps the voltages is '/sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels'

304000: 725000
486000: 875000
594000: 900000
702000: 925000
810000: 937500
918000: 950000
1026000: 962500
1134000: 975000
1242000: 987500
1296000: 1025000
1350000: 1035000
1404000: 1037500
1458000: 1040000
1512000: 1050000
1566000: 1067500
1620000: 1075000
1674000: 1100000

first column is frequency, second is voltage.

so to change the voltage on the lowest step you would want to

echo "304000 725000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels

with your settings of course, keep in mind that the first number has to be a valid frequency step.
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

If you put your scripts in /data/local/userinit.d (make the userinit.d folder if needed) then the scripts should live though a rom or kernel update, I know they will last a cm10.1 nightly update :)

Edit: hah, that's what I get for not fully reading the other people's posts before posting ;)
[Nexus 4 Original Android Development] rlaw:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

I'm still testing out the new color defaults. Does anyone else experience what look like severe artifacts when looking at media that's already very bright? Particularly with natural sunlight and bloom?
[Nexus 4 Original Android Development] logo20heli:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

I'm using b35 with CM10.1 nightly 10.1-20130210. The new colors are looking very nice. Thanks! The only issue I see is that some of the near-whites get crushed to white. In other words, near whites are not individually discernable. But the colors pop and are way better than Google stock. Thanks!
[Nexus 4 Original Android Development] ptesmoke:
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

if your testing as you say, your not testing properly. throwing a script into the works does not prove trickster is at fault. show me a way to prove trickster breaks hot plug and I'll submit a bug report.

motley b35 seems great. try out these color settings see if you like...

lg presets

r 248

b 248

g 248

gamma0

24

24

24

gamma1

0

0

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

Yes. So I switched back to halfbreed.
[Nexus 4 Original Android Development] AcmE85:
I also noticed odd artifacts on bright areas. Other than that, colors were really good.

Right now I am using b32 colors.
[Nexus 4 Original Android Development] popophobia:
I made a small script to change the values each boot and put it in init.d folder. However, the voltage table does not stick. If I run the script again, it would work. Any ideas?

#!/system/bin/sh
#FSYNC option
echo "1" > /sys/kernel/dyn_fsync/Dyn_fsync_active;
echo "1" > /sys/class/misc/fsynccontrol/fsync_enabled;
#USB fast charge
echo "0" > /sys/kernel/fast_charge/force_fast_charge;
#Vibration
echo "100" > /sys/class/timed_output/vibrator/amp;
#TCP control
echo "westwood" > /proc/sys/net/ipv4/tcp_congestion_control;
#Voltage
echo "304000 600000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "486000 600000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "594000 600000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "702000 600000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "810000 600000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "918000 650000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1026000 750000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1134000 925000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1242000 937500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1296000 962500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1350000 968000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1404000 975000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1458000 982500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1512000 987500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1566000 1012500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1620000 1030000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1674000 1037500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
#Interactive
echo "interactive" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor;
echo "1512000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
echo "304000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq;
echo "918000" > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq;
[Nexus 4 Original Android Development] thracemerin:
Is the other stuff applying correctly during boot?
[Nexus 4 Original Android Development] popophobia:
I think so. I also have a color script there. That one works fine too. It's really odd...
[Nexus 4 Original Android Development] thracemerin:
I wonder if it's because you're changing the scaling table after applying the voltages.

Edit: mine most definitely stuck with just the voltage settings copied out of your script, so something else in your script is messing with it.

Here's the script:

#!/system/bin/sh

#Voltage
echo "304000 600000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "486000 600000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "594000 600000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "702000 600000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "810000 600000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "918000 650000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1026000 750000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1134000 925000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1242000 937500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1296000 962500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1350000 968000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1404000 975000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1458000 982500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1512000 987500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1566000 1012500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1620000 1030000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1674000 1037500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;

I named it '90voltage' and put in in /system/etc/init.d and set rwxr-xr-x as the permissions
[Nexus 4 Original Android Development] popophobia:
You're right, I split it into two scripts and it sticks. It wouldn't stick when I move that portion of the script down. I would never understand how these scripts are executed.
[Nexus 4 Original Android Development] thunderger:
B35 runs well but screen is 'blueish', espexially whites. Perhaps it is related to trickster mod update that enables gamma settings in this app. Before I used init.d script to set colors as some posted here. But after update to B35 and update of trickster colors look wrong.

Perhaps trickster mod affects gamma settings that were done by kernel but there is no option to disable gamma (alone) in trickster mod.

Second I played with FIOPS vs. SIO vs. ROW and it seems that ROW has the highest read speed around 30 MB/s - FIOPS around 24 MB/s - but the lowest write speed - around 12 MB/s against 14 MB/s (FIOPS). SIO has lowest read and write speed.

More interesting is the fact that the best read and write values were obtained with a 'read ahead buffer' value of 2048.

I suggest someone else to test ROW with RAB 2048 and perhaps to set these values as default.

Then I saw that I can set lowest GPU clock value to 200 but I haven't enough control over GPU govenor resulting in lower FPS in Epic Citadel and other games using a lower minimum GPU clock. My hope was to save battery but no lower "game perfomance".

Also I saw some N4 benchmark results showing 1.7 and 1.8 GHZ CPU clock. Is it possible to enable such settings by an experimental flag? ;)

EDIT:

I saw that trickster sets "Google" as default color preset. After changing it to LG, colors are less blueish. But still it seems that trickster affects kernel default gamma & color settings. Hopefully someone calibrate our display to iPhone5 / iPad4 "values" because these devices cover sRGB and are beautiful not over-saturated as Samsung GS2, GS3, N2, etc. (amoled wide gamut :D :D )
[Nexus 4 Original Android Development] thracemerin:
Trickster only modifies the gamma amp values (column 6 & 7 in motley's gamma interface) not all 9 values so what you get by modifying gamma in trickster is going to be much different and somewhat limited compared to what you can do with an init.d script, also if it's putting in it's own gamma amp values after the kernel has set its values (either by default or by script) then you aren't getting the values that motley (or the scripts author) intended, you are getting something entirely different.
[Nexus 4 Original Android Development] direwolf1:
Battery life on b35 is great

Don't know if it was the changes here, the updates to the Xylon ROM, or both, but I upgraded from Xylon 19 to 19.1 and motley from b32 to b35 simultaneously (clean flash). I finally broke the the 6 hour screen on time (all Wi-Fi) for the first time ever (I broke 5 hours a few times before, but barely), and that also included over 1 hour of voice calls (some on bluetooth). Wow. motley, you are fantastic.

Edit: the kernel's default color settings look great on my screen. I'm using Trickster, so I hope that doesn't screw them up on the reboot, but they look quite good.
[Nexus 4 Original Android Development] Franklin Bernard:
4.2.2 +motley

Hi,

I just found that CodeFireX have released the ROM with [AOSP-4.2.2 JDQ39].

Lets see how it goes with B35

Thanks,

EDIT : will B35 be compatible with 4.2.2 ? Am i good to flash B35 over latest CodeFireX 4.2.2 ROM ?
[Nexus 4 Original Android Development] batman368:
the world belongs to the brave :) flash and find out...
[Nexus 4 Original Android Development] thunderger:
@thracemerin:

Yeah, that's the problem I figured out. It's a dilemma for me. I want to have cpu/gpu/io control with trickster but not it's color/gamma control because I want to set by init.d script with which I can control more settings. As you said, trickster overrides some of these values and that my cause a different "gamut" :( Hopefully trickster mod will get an update that allows to separately enable/disable every kind of setting.
[Nexus 4 Original Android Development] more2come:
I'd really like to use the touch boost on a daily basis, but if I switch it on in Trickster Mod and apply the settings, the first CPU core (Core 0) always stays at 1 GHz, the chosen boost frequency. I lowered the boostpulse duration, but nothing changes. Can someone help me out here?
[Nexus 4 Original Android Development] Franklin Bernard:
working :)
[Nexus 4 Original Android Development] greg17477:
As stated before, trickster mod (the version with gamma settings included) is not compatible anymore. It breaks motleys hot_plug management.

But what do you mean by " but if I switch it on in Trickster Mod" ? You do not switch touch boost in there, it's already on by default. The setting "boost" in trickster mod shouldn't be touched either.
[Nexus 4 Original Android Development] more2come:
Thanks for pointing that out, I just followed instructions in the OP, there it says Trickster Mod would be good for testing. How can I make changes to the default values then? Thx in advance
[Nexus 4 Original Android Development] :
Re: [KERNEL][Feb 11][b35] _motley kernel for the N4

Hi,

Thanks for the reply ;)

Maybe you can implement the ability to overclock the GPU via init.d script (or with the interface of Trickster app, Sysctl interface). You provide your kernel with the stock GPU freq and if some users want to test GPU overlock they can, like you do for Fsync control, thermal control, etc..., no?

It would be great to have the choice like some other settings :)

Thanks in advance ;)

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

Hi all. Apologies for a UV related question.

I have the following voltage settings. It's apparently stable. The strange thing is that gap between 1.13Ghz and 1.24Ghz. As soon as I set 1.24Ghz to 850mv, it crashes almost immediately. Why is the gap here so big? How can I confirm the voltage settings for 1.13Ghz down to 304Mhz have indeed been implemented properly? Thanks!
[Nexus 4 Original Android Development] darkamikaze:
Lol you guys are so quick to shut me down. I really wish I could find the thread but I can't. I recall it was debunking information regarding oc/uv and that below 800mV it doesn't give enough power making your device work more that and it actually doesn't help battery life below this threshold. Something along those lines. I can't prove it so w/e forget I said anything.

Sent from my Nexus 4
[Nexus 4 Original Android Development] MatAuc12:
It just doesn't work like that. If the chip doesn't get enough power it will simply not work. More voltage is not = performance. Higher clock = performance. Higher clock = higher voltage.

AT THE SAME CLOCK, lower voltage will always use less power. Voltage is not related (by itself) to how much work or in how much time a CPU will perform a task.

What IS true though is that lower clock is not ALWAYS = lower power drain, because it depends on the values of (time) x (power/time) if it has a load. That is usually either a rare occurrence or a threshold (that we get to know and make sure to not under clock further).
[Nexus 4 Original Android Development] whittikins:
For what it's worth, I read what you're talking about and saw tests demonstrating this. Maybe I can find it sometime. The explanation was that the chip wasn't functioning stably at a voltage that was a little bit too low so it wouldn't crash but would stall or stutter and take longer to perform tasks, thus draining more battery. You're not crazy, and the others are assuming you don't understand the basics of clock speed and voltage, which you obviously do.
[Nexus 4 Original Android Development] whitedragonz83:
I had this thread bookmarked that might be what you are talking about, however, I have not read the entire thread, nore claim this to be 100% true. First post talked about extreme UV'ing and higher usage.

http://xdaforums.com/showthread.php?t=1478406
[Nexus 4 Original Android Development] whittikins:
Yeah, here's an excerpt:

So the people giving darkamikaze a hard time need to realize they're not as smart as they think. :p
[Nexus 4 Original Android Development] darkamikaze:
THANK YOU everyone for proving I'm not crazy but I believe we've high jacked motley's thread enough! Lets continue with the kernel dev!
[Nexus 4 Original Android Development] MatAuc12:
You mean 1 CPU that's UNSTABLE at 750mv renders poor performance (obviously...). Means chips under 800mv are less power efficient? That is a pretty clever conclusion to compare an unstable voltage of a totally different chip with... You know... A stable (ie usable) and... You know different chip (chips use different voltages....)

It is beyond retarded to conclude from that that the nexus 4 uses more power under 800mv....

---------- Post added at 02:27 PM ---------- Previous post was at 02:24 PM ----------

He obviously does? You mean obviously does not. He compared a nexus S voltage with a nexus 4 chip. You can hardly compare different chips, let alone different chip models...
[Nexus 4 Original Android Development] whittikins:
Yes, that was tested using a different chip, etc. I never said the Nexus 4 will be the same. I'm responding to you saying things like:

and...

Both of which are incorrect. Anyway, the proof is there so we can all get back to the point of the thread, which is Motley's kernel.
[Nexus 4 Original Android Development] richteralan:
That post indicated that battery drain only happens with EXTREME UV and Reboots caused by it.

People please read and understand the fine prints and apply to the context of UV discussion here.

Nobody is doing EXTREME UV that causes reboots.

---------- Post added at 03:36 PM ---------- Previous post was at 03:33 PM ----------

The second sentence is correct by looking at this formula from that thread:

CPU Power Draw = C x F x V^2 (where C=capacitance, F=frequency, and V^2=Volts squared)

With same F(frequency), a lower Voltage will always yield lower power Draw.
[Nexus 4 Original Android Development] MatAuc12:
Both of those statements are correct. Educate yourself. Read the thread instead of just the numbers.

Also, HE implied Nexus 4 by posting in this thread.

Also, it is sad to go slightly off topic. But threads are a recollection of information, it would be unethical to not debunk such false information.
[Nexus 4 Original Android Development] kennyp987:
Best kernel I have tried for the n4 hands down....very very fast and good battery life excellent work
[Nexus 4 Original Android Development] whittikins:
Yes, but my point is that there are real world test results that show it's not always the case. If the CPU is running for a longer period of time due to making errors, it's going to draw more power (even if it's running at a lower voltage).

---------- Post added at 02:03 PM ---------- Previous post was at 02:00 PM ----------

No, they aren't. There are real world test results that show it's not always the case. If the CPU is running for a longer period of time due to making errors, it's going to draw more power (even if it's running at a lower voltage). Running the same period of time, yes, lower voltage draws less power. The issue is that a CPU making errors will be running for a longer period of time to perform the same task, which is what results in using more power. You aren't considering the errors and time it adds to complete a task.
[Nexus 4 Original Android Development] Razer(x):
You should had the patch for better touch
[Nexus 4 Original Android Development] Beretta93:
This stuff is off topic. Please stop. It's impossible to sort kernel related information because of you.