yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] :
Hi,

It's not normal that /sys/module/msm_thermal/parameters/enabled is set to N. The stock setting is Y.

So here the thermal throttle is disabled it's already turned off, so no the CPU freq will not decrease according to the CPU temp. When your CPU temp will reach the max it can handle (+100°C if I'm not wrong) -> reboot.

NOT SAFE, unless you know you what you are doing...:rolleyes:

Check if you have not a script in init.d or an app wich could change this, re enable the thermal throttle. If I was you it will be the first thing I'll do...

At worst you can raise the CPU temp limit (max is 80°C):

For gaming (especially if it's some heavy games), raise a little the max CPU temp limit to avoid thermal throttling "permanently", but there is a moment where there will still thermal throttling if you are playing for a long time and it's normal...

But all these settings are "sensitive", if you change them do not come here because your phone reboot when you're playing or your phone is extrem overheating :D

Run with car without cooling system, makes 2 / 3 runs... and see the result...:eek:

:)
[Nexus 4 Original Android Development] csunny95:
That's really strange, every time I reboot my phone, the setting revert to N. I am using carbonrom, I don't know what is going on
[Nexus 4 Original Android Development] :
Re,

Check your init.d folder and check if there are some scripts, post them here if needed.

Which app (s) do you use to control the kernel settings?

Reflash the kernel and / or the rom, re do a full wipe and doing all from scratch :confused:

:)
[Nexus 4 Original Android Development] csunny95:
Re: [KERNEL][Feb 25][b40] _motley kernel for the N4 (smp patches back for 4.2.2)

I am using the build in "performacnce setting" in carbon rom for oc. Have already reflashed the kernel and rom, but problem still presence.

Here is a scripts inside the init.d

By the way, I change the value of "enabled" by using R.E explorer, isn't it appropriate?
[Nexus 4 Original Android Development] :
Re,

I do not know that there here I have not more ideas, I'm sorry :crying:

Yes it's good in Root Explorer "in live" but after a reboot... make an init.d script to enable the thermal throttle at boot, but it's weird your issue...

For information, and maybe I'm too late or it has already been said but the interface from franco Kernel updater (on the Play Store) for Gamma control works perfectly with _motley kernel, I've just tested ;)

It's the interface with Gray, Mids, Blacks, etc...

Less hard to adjust than Trickster or Faux, at least for me... If I remember correctly there is someone who asked about the settings between the two different interface (Faux / Franco).

And for color settings an app is the best, it needs many adjustments to find the best setting and now no need to turn the screen on / off, it's perfect!

With init.d scripts, make the script, reboot, see, adjust, reboot, see, etc... more than 20 time a day :eek:

I'm more and more lazy :p:D

:)
[Nexus 4 Original Android Development] csunny95:
So, may I know what do u use to change such value? R.E explorer?
[Nexus 4 Original Android Development] :
Re,

What do you mean, wich values?

I don't understand :(
[Nexus 4 Original Android Development] Kocai:
Re: [KERNEL][Feb 25][b40] _motley kernel for the N4 (smp patches back for 4.2.2)

You can always run the script in terminal to change the color.
[Nexus 4 Original Android Development] jarayn:
Does the kernel affect Bluetooth ?

My bluetooth fails to connect unless I cycle it off then on which seems a bit like my public wifi wont connect unless I reboot phone.

Kernel or rom most likely?
[Nexus 4 Original Android Development] csunny95:
I mean the /sys/module/msm_thermal/parameters/enabled

how do you change the value, using R.E explorer?
[Nexus 4 Original Android Development] :
Re,

Ok, follow the path /sys/module/msm_thermal/parameters/enabled then longpress on "enabled" file, a window will appear scroll down and choose "open in text editor" then change the value and save.

Or here an init.d scrip to enabled it at boot + CPU temp limit (just edit the value on what you want, I make it to 70°C). Set the correct permissions (755 or like the other script you have in your init.d folder) and reboot.

http://www.multiupload.nl/74I1HA7UZ0

:)
[Nexus 4 Original Android Development] csunny95:
thanks anyway, but it just not working, the files still shows "N" after reboot, even I put a script in the init.d.

Is ok, just leave it, thats trouble
[Nexus 4 Original Android Development] _motley:
This is stock behavior, /sys/module/msm_thermal/parameters/enabled is "Y" by default. If you choose to turn off thermal management (set to "N"), then it won't allow you to turn it back on from what I recall.

I highly recommend that you keep /sys/module/msm_thermal/parameters/enabled = "Y" and then adjust the throttle temp higher as is shown in post #2. This will keep things safe.
[Nexus 4 Original Android Development] _motley:
Build 42 posted

Build 42 has been posted. By request, I have merged the speaker amp control by faux and touchscreen accuracy filter control by franco (Thx!). I have not had a chance to test these features yet, but I will update post #2 with tuning details once I/we do. These features shouldn't affect any defaults, so don't worry if you don't want to use them.

Let me know how it goes!
[Nexus 4 Original Android Development] csunny95:
But how can I turn it back on now? When I adjust it to "Y" now? it just turns back to N after reboot. As a remember, I didn't touch that file before, the first time I see it ,it is already "N"

Even, I have reflashed the rom and kernel, it still stuck on "N", Help! OMG
[Nexus 4 Original Android Development] :
THANKS!!! ;););), thanks for taking in consideration these requests ;)

Just for reminder about touchscreen accuracy filter (until instructions in the second post):

And for the sound control: the app from Faux123 to control the sound: https://play.google.com/store/apps/...sMSwxLDYsImNvbS50ZWFta2FuZy5mYXV4c3BlYWtlciJd

I don't know if it's possible by init.d script :confused:, in any case easier with an app...

Downloading, feedback later ;)

And thanks to Franciscofranco and Faux123 ;)

:)

EDIT:

Re,

It's not a big deal since at the beginning you wanted disabled the thermal throttle :D

Have you tested the init.d script I've posted?
[Nexus 4 Original Android Development] csunny95:
Tried, not working:crying:, at the beginning I wanted to disabled it because my phone downclock automatically, but once I check the value, It has already set to "N". Strange
[Nexus 4 Original Android Development] :
Is TC working with b42?

The current version of TC dosn't work with b40, insmod can't loud the modul.
[Nexus 4 Original Android Development] :
Re,

Weird, the only thing that I see: full wipe then reflash rom / kernel... because if the init.d script doesn't work... I have not more ideas, sorry.
[Nexus 4 Original Android Development] chrone:
Re: [KERNEL][Mar 2][b42] _motley kernel for the N4 (new feature testing)

B42 is silky smooth so far. :thumbup:

Sent from my Nexus 4
[Nexus 4 Original Android Development] csunny95:
Re: [KERNEL][Mar 2][b42] _motley kernel for the N4 (new feature testing)

Thanks for your helping. My devices is strange.

Automatically Dowbclocked, even set as "N"

Just 36 degree, not even reach 70degree
[Nexus 4 Original Android Development] swaggerwocky:
@motley, did you disable the conntrack SIP module in b42?
[Nexus 4 Original Android Development] chrone:
whoa thanks for the update. it's nice of you listening user requests. silky smooth so far with default settings. :)

i've been following faux and franco kernel change log, and found this gpu vsync (faux) and gpu patches (franco).

quoted from faux123:

quoted from franco:

i would like to know how to force gpu vsync in hoping to avoid the window/transition/animator scale animations micro stuttering i'm experiencing days ago. i wonder if _motley kernel force gpu vsync all the time? or is there already in jelly bean project butter (gpu vsync and triple buffering)?

have you tried set the min and max cpu freq profile the same above the temp threshold frequency just to see it keeps downclocking?

and is mpdecision turned off already?

i'm on stock rom and don't have problem with the temp limit cpu freq. perhaps changing rom or so will fix problem. :)
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Mar 2][b42] _motley kernel for the N4 (new feature testing)

Same issues as with Franco r93, touch driver issue I'm guessing. When you hit power button, device acts as if you're swiping from top of the ts, when you're not. Grrr lol
[Nexus 4 Original Android Development] thracemerin:
Yeah, I noticed this too, I think its related to Franco's touch driver changes.

Appears to be still active at the moment. I might be able to build you one without if you'd like.
[Nexus 4 Original Android Development] faux123:
Re: [KERNEL][Mar 2][b42] _motley kernel for the N4 (new feature testing)

Everything is adjustable via init.d scripts.

Check:

/sys/bus/i2c/devices/0-0058/
[Nexus 4 Original Android Development] swaggerwocky:
That would be amazing if you could, if you find yourself with some free time. :good:
[Nexus 4 Original Android Development] Cygnust:
Sorry for the noob question but under b42 release it's stated that we have to be on b37 first.

Is not it possible to flash directly above the CM10.1 nightlies ?

Many thanks
[Nexus 4 Original Android Development] knapz:
Re: [KERNEL][Mar 2][b42] _motley kernel for the N4 (new feature testing)

Nope. Flash 37 then 42 back to back while in recovery.
[Nexus 4 Original Android Development] _motley:
I didn't see a response back to my questions about what you are trying to fix, so I am not sure what to test.

Here is b43. It is b42 without SIP. I am running it now too to see if I notice any diffs.

View attachment motley_anykernel_422_nexus_4_build_43.zip

b42 and prior:

CONFIG_NF_CONNTRACK_SIP=y
CONFIG_NF_NAT_SIP=y

b43:

# CONFIG_NF_CONNTRACK_SIP is not set
# CONFIG_NF_NAT_SIP is not set

Let me know how it works.

Thx
[Nexus 4 Original Android Development] _motley:
Thanks faux, much appreciated.
[Nexus 4 Original Android Development] _motley:
This setting is enabled by default, so if something is changing it to N it has to be a script since the change won't survive a reboot. Check to make sure you don't have an init.d script (/system/etc/init.d/) or for CM based ROMs (/data/local/userinit.d/). If you wiped and re-installed your ROM etc., it wouldn't clear out scripts from for the latter userini.d for CM.

vsync is on by default in stock and in my kernel (i.e. nothing changed). vsync on keeps the frame rate the same as the refresh rate for the display. However, you can turn V-sync off in order to try to achieve higher fps. Sometimes this can cause "tearing" in games if the refresh rate is then exceeded. Vsync keeps the next frame rendered by the GPU on pause until the panel has finished displaying the last one so you don't end up with half of one frame and half of another that is described as "tearing".

Not seeing this, but must be related to the franco merge for the touch driver. How do I duplicate it? Or, are you talking about something in relation to the touch control app not working?

As far as Touch Control, it is odd, I am still on v1.5c of TC and it still works fine on b40, b42, and b43. But, I haven't upgraded yet to 1.5d. I hope this doesn't break it...
[Nexus 4 Original Android Development] nextelbuddy:
I'm sorry if I missed it, but is there a way to import gamma colors fro ma script into an app like Trickster?

i updated my kernel and lost my gamma settings and it sucks going back and manually typing them in line by line and was hoping there was a script for the PA Half breed settings that I could just point to form trickster and say run?
[Nexus 4 Original Android Development] chrone:
Re: [KERNEL][Mar 2][b42] _motley kernel for the N4 (new feature testing)

much appreciated. :)

Here you go:

http://xdaforums.com/showthread.php?p=38677054

Extract, run it from terminal, fire up trickter mod, and you'll see the halfbreed gamma settings. Somehow you need to adjust the rgb manually as posted inside the script. Or just put the script in /system/etc/init.d. ;)

Another way is by looking under the public spreadsheet > grey gradient sheet on:

http://xdaforums.com/showthread.php?p=35249530

Sent from my Nexus 4
[Nexus 4 Original Android Development] IAmAN00bie:
Franco made some changes to the Accuracy Filter Control in his latest r95, so I flashed it and checked out the changes he made.

Here they are: just copy them into your init.d script!

#Touchscreen Accuracy Filter Control

echo 5 > /sys/devices/virtual/input/lge_touch/ignore_pressure_gap

echo 8 > /sys/devices/virtual/input/lge_touch/touch_max_count

echo 50 > /sys/devices/virtual/input/lge_touch/delta_max

echo 8 > /sys/devices/virtual/input/lge_touch/direction_count

echo 4 > /sys/devices/virtual/input/lge_touch/time_to_max_pressure
[Nexus 4 Original Android Development] csunny95:
Sorry to say that, even I have delete all the script in the init.d folder, the "enabled' and "throttle_temp" still revert back to "N" and "70" after a reboot:crying::crying:
[Nexus 4 Original Android Development] thracemerin:
Do you have any kernel control apps installed? (Trickster, System Tuner, Franco Kernel Updater, Fauxclock, Rom Toolbox, etc)
[Nexus 4 Original Android Development] csunny95:
Re: [KERNEL][Mar 2][b42] _motley kernel for the N4 (new feature testing)

I am using the rootbox rom built in performance setting for setting the CPU frequency
[Nexus 4 Original Android Development] swaggerwocky:
You may have missed my reply earlier in the thread, but this should fix the issue of missing incoming SIP calls while on 3G. I'll give this a go and let you know how it goes, thanks!
[Nexus 4 Original Android Development] :
Hi,

The control sound works perfect, there is really a real big difference in volume! Better than all the "Beats audio thing with extra mega giga bass of death" who bloats your phone with a ton of additionnal files :eek::p:D

I use the app by Faux123 (Speaker Loudness & Amp Control on the Play Store) and the settings are great (except that the settings doesn't set on boot, I don't know where it comes from :confused:)

And since Faux posted the path for use an init.d script, it's an awesome feature in your kernel :)

@ _motley, I noticed this in the kernel thread of Faux, can you take a look?:

Is this this commit?:

https://github.com/faux123/mako/commit/efce8f98ce5198b324f6f83677c1d471edc35c13

I'm not too familiar with github, maybe I'm wrong here...

Thanks ;)

Thanks, will test.

Have you tested? Any difference?
[Nexus 4 Original Android Development] :
AW: [KERNEL][Mar 2][b42] _motley kernel for the N4 (new feature testing)

I'm on 1.5d and over adb insmod get an exec format error.
[Nexus 4 Original Android Development] pa.pn2:
if i flash b42 and dont use scripts to get the new features, its useless for me isnt it?
[Nexus 4 Original Android Development] :
Hi,

Hum, yes if you don't use it it's useless for you :D

You can still flash b42 and see after for testing the sound / touchscreen feature ;)

You can play with /sys/bus/i2c/devices/0-0058/ for the sound, with some values the sound from speaker is louder, much louder... it's the "fixed_gain" value which is needed to be modified. I used the app from Faux it's easier. There is realy a gain in quality / louder sound it's awesome!

You should try it

:)
[Nexus 4 Original Android Development] pa.pn2:
ok.do you know if the aokp pub supports init.d support?

so if i flash b42 i dont have to do extra things to test this "new"touchscreen features?what does it do?
[Nexus 4 Original Android Development] :
Re,

Yes AOKP PUB support init.d, in any case _motley kernel support init.d so if your rom doesn't support init.d by flashing the kernel you'll have init.d support...

For the new touchscreen settings you need an init.d script:

I'am currently testing this one... I don't really know if I feel a difference, maybe we need to tweak some values. In any case it's still in test...

:)

EDIT:

From Franciscofranco's thread:
[Nexus 4 Original Android Development] chrone:
Re: [KERNEL][Mar 2][b42] _motley kernel for the N4 (new feature testing)

I thought we need to create init.d folder in /system/etc and put the script inside init.d since the kernel already supports this. I use stock rom and the script works well. Make sure you already install busybox by stericson in /system/xbin first. :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] _motley:
Awesome, let us know how it goes. I have noticed anything different thus far, but I don't use VOIP and video conferencing apps on my phone at the moment.

Glad to hear it is working well. That commit is already in b42 and I don't see any others that are newer. I have been really busy this weekend with family stuff. Hope to have time tonight to play around with some of this stuff.

Weird. I don't see any problems on my end. Last night I updated to 1.5d and it still works fine. Just for grins, I killed the TC app, cleared it's data and rebooted just to be sure. I was able to run the app and it detected the kernel module properly as "motley" and it is still working fine. Is anyone else using TC that can report back?
[Nexus 4 Original Android Development] :
Re,

No worries _motley ;), again thank you to you to have included these features ;)

I made an init.d scripts for the touchscreen settings. It sill need some testing. I used the values posted by IAmAN00bie and added the "lge_touch/max_pressure" with stock value since Francisco posted this line in his thread. Like he sait it needs proper tweaking and testing before to see if there is really something to do to the touchscreen.

For the sound Faux123 posted the path to tweak the sound. I wanted to make a script with the values ​​that I set with its app but there is some values which do not appear.

So I don't really know wich values put in the script for each path..., maybe asking to Faux123 or if he read the thread...

Here the paths if you want to test:

The init.d scrip for the touchscreen settings is in attachment (remove the .txt before).

:)
[Nexus 4 Original Android Development] Luigi_2:
Can I flash b42 directly after installing pa 3.1 without the b37? :D
[Nexus 4 Original Android Development] :
Hi,

No, b37 first then reboot (for to be sure) and you're good to flash b40.

:)
[Nexus 4 Original Android Development] jarjar124:
Re: [KERNEL][Mar 2][b42] _motley kernel for the N4 (new feature testing)

What does the speaker patch do? Increases volume and quality of just the speakers? Or earphones as well?
[Nexus 4 Original Android Development] :
Hi,

It's only for the speaker, yes it increases volume / quality. I'm not too melomane for fully appreciate the quality but in any case the volume is increased, what an improvement! (all the system volume sound, I mean music app and notifications / ringtones too).

Details:

Speaker Loudness & Amp Control

:)
[Nexus 4 Original Android Development] direwolf1:
Re: [KERNEL][Mar 2][b42] _motley kernel for the N4 (new feature testing)

I believe it is the speaker only, based on the description of the app in Google play

Sent from my Nexus 4
[Nexus 4 Original Android Development] faux123:
Here's a screen shot of my "Classical Profile" ;)

My Speaker Amp control app allows for Many different profiles and easy to use interface for very reasonable price ;)

It ONLY CONTROLS SPEAKER! NOT HEADPHONE/HEADSET... JUST SPEAKER :cowboy:
[Nexus 4 Original Android Development] :
Thanks Faux! ;) , yes it's why I bought it, perfect to tweak the sound. These patches are really awesome, well done ;)

Also thanks to _motley for including these patches ;)

:)
[Nexus 4 Original Android Development] IAmAN00bie:
For the lazy:

Faux's classical profile into an init.d script:

#Sound Tweaks

echo 0 > /sys/bus/i2c/devices/0-0058/out_lim

echo 12 > /sys/bus/i2c/devices/0-0058/AGC_Max_Gain

echo 2 > /sys/bus/i2c/devices/0-0058/ATK_time

echo 6 > /sys/bus/i2c/devices/0-0058/fixed_gain

echo 1 > /sys/bus/i2c/devices/0-0058/Hold_time

echo 1 > /sys/bus/i2c/devices/0-0058/Noise_Gate_Threshold

echo 29 > /sys/bus/i2c/devices/0-0058/Output_limit_level

echo 8 > /sys/bus/i2c/devices/0-0058/REL_time
[Nexus 4 Original Android Development] :
AW: [KERNEL][Mar 2][b42] _motley kernel for the N4 (new feature testing)

I found the problem, I don't know how or why but my su made some problems. I tested tc with some compatible kernel but it doesn't work, replace su solved the problem.
[Nexus 4 Original Android Development] :
Hi,

@ _motley, is your kernel mounts partitions with discard option?

I just see this post from chrone (thanks): http://xdaforums.com/showthread.php?t=1971852 (tested with Nexus 4 also) and want to test some things.

:)
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Mar 2][b42] _motley kernel for the N4 (new feature testing)

Onw of the things ive always loved about this kernel was how stable it was and how little iasues weve had.

I had to drop down to r40 due to touch drivers having weird bugs, like swiping from top upon unlock, or sensitivity issues. Is it going to stay in future releases?
[Nexus 4 Original Android Development] :
Hi,

No issues here with touchscreen or sensivity :confused:
[Nexus 4 Original Android Development] :
Re,

I'm currently testing the Interactive governor (like I said a few pages back) with some different settings, here's a screenshot for those I use:

You know that my goal is not an extreme battery life... :D These settings looks pretty good and the general UI seems smoother than Ondemand governor with my previous settings.

Since the Interactive governor has some settings that I have not found in the "big" threads here on XDA (like HERE) like timer_slack and target_loads, I found this:

Source: https://android.googlesource.com/kernel/common/+/android-3.4^/Documentation/cpu-freq/governors.txt

It's a little hard for me to undersatnd all this stuff but I try :D

As for my tests decreasing timer_slack tend the CPU to spend more time at the hispeed_freq...

As for the LagFix app, I've tried. I noticed nothing in general use except in Androbench :D. More than 100 TPS in the SQLite part and about 2 / 3 Mbps for Random Write (see my post above for explanation).

:)
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Mar 2][b42] _motley kernel for the N4 (new feature testing)

Having boost on will mean it's always at the high speed req, that's not the same thing as boost pulse.

Sent via Nexus 4
[Nexus 4 Original Android Development] :
Hi,

Sorry, I don't understand what you mean about boost set to on and boostpulse_duration :confused:
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Mar 2][b42] _motley kernel for the N4 (new feature testing)

The button in tricksters mod, that says boost, with it on, it means that your phone will always be at highspeed freq.

Turn that to off its not needed, the powerhal will send the correct events on touch, boost pulse duration will control how long each pulse on touch lasts.

Sent via Nexus 4
[Nexus 4 Original Android Development] _motley:
Build 44 posted

Build 44 posted to hopefully fix the touch issues some reported in the last beta. I have also kept in the SIP netfilter change from b43 to see how it goes for everyone. We'll have to get an update from the gentleman that was testing this to see if it fixed his issue. I see no issues at all with this change, so it makes sense to leave it in and let everyone beat it up to see what they think.

Let me know how b44 goes! If this is fixed, beta status can be taken off:fingers-crossed:
[Nexus 4 Original Android Development] franciscofranco:
Hey motley whats CONFIG_NF_CONNTRACK_SIP/CONFIG_NF_NAT_SIP for? Didn't find much info on those options.
[Nexus 4 Original Android Development] thracemerin:
Related to this: https://code.google.com/p/android/issues/detail?id=32736#c8