yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] _motley:
Thanks for stopping by to share. Looks like great work:good: We'll merge it in and give it a try.
[Nexus 4 Original Android Development] anoymonos:
Re: [KERNEL][Mar 9][b48] _motley kernel for the N4 (fix touch issues again!)
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Mar 9][b48] _motley kernel for the N4 (fix touch issues again!)

B48 is great so far! Responsive as always and no issues with touchscreen at all! Thanks motley!!!
[Nexus 4 Original Android Development] ceejay83:
Re: [KERNEL][Mar 9][b48] _motley kernel for the N4 (fix touch issues again!)

Wish you would make an app motley, I'd buy it in a heartbeat :)
[Nexus 4 Original Android Development] karanrajpal14:
Re: [KERNEL][Mar 9][b48] _motley kernel for the N4 (fix touch issues again!)

Agreed! :) I'd buy it too!
[Nexus 4 Original Android Development] _motley:
Build 49 posted

b48 has now been marked as stable and b49 has been released for testing with faux123's sound control (see a couple posts above).

I'll see if I can get b48 on Goo.im later now that I have an account. I will also get post #2 up to date with all the new configurable options.

Thanks! I was hoping to hear back from you and that you would give the thumbs up:good:

Thanks guys, so many apps out there already though...
[Nexus 4 Original Android Development] :
Hi,

Thanks _motley for the update ;)

For those who want to play with scripts for the new sounds enhancements until _motley edit the second post, here the paths for change the values:

And in attachment an init.d script (with the values wich come when you flash the kernel, I can't test for now so you need to change the values otherwise it will not change anything :D ). Don't forget to remove the .zip extension.

Or there is the app from Faux123: FauxSound Audio/Sound Control

Again thanks Faux123 and _motley ;)

:)
[Nexus 4 Original Android Development] :
EDIT: in Faux's thread it seems that for /sys/kernel/sound_control/gpl_headphone_gain:

30 30 -> for quality

35 35 -> for quality / loudness ?

43 43 -> for loudness (dangerous?)

If I'm not wrong... :)

EDIT 2:

:)
[Nexus 4 Original Android Development] faux123:
30 30 -> for quality

35 35 -> for quality / loudness ?

^ is good range for quality

43~45 is max safe for loudness, higher than those it's dangerous esp with crappy headphones...
[Nexus 4 Original Android Development] Franklin Bernard:
Thanks for the script Viking.

Do u know how can I check if the script is run successfully or not. Is there any logging for all the init.d scripts. Because sometimes I am not sure if the script is run successfully or not after EDITING it.
[Nexus 4 Original Android Development] :
@ Franklin Bernard

Go to sys/kernel/sound_control/****** and for each settings you have changed check the new value.

For example by default /sys/kernel/sound_control/gpl_headphone_gain is set to "40 40". if you set it to "35 35" in the init.d script and you have rebooted, then go to /sys/kernel/sound_control/gpl_headphone_gain again to see if the value is changed to "35 35".

Don't forget to set the correct permissions for the init.d script.

:)

Edit:

Am I crasy or ... :p:confused::D

Maybe it's me but this b49 is smoother :eek:, smoother in some apps than before (XDA, browser, some scrolling)... Same rom before I flashed the b49. Interactive governor.

Is there have been other changes in the kernel :confused:

You'll say I said anything, but I think there is really something "more" here. Someone else?

:)
[Nexus 4 Original Android Development] IAmAN00bie:
Yeah you can just go into the directory using a file explorer and open the files to see if the values have changed.
[Nexus 4 Original Android Development] ceejay83:
Yea but your own app that can customize the screen colors, sound options would be nice. Don't think there's an app out there that can customize your colors?
[Nexus 4 Original Android Development] Audioboxer:
TricksterMod can, great app.

Best thing to do is simply donate to motley :good:
[Nexus 4 Original Android Development] :
Hi,

Trickster Mod works great with _motley kernel.

Also the apps from Faux123...

:)

EDIT: I type too slow :D
[Nexus 4 Original Android Development] ceejay83:
Trickster uses amp 123 right? Motley's uses the same?
[Nexus 4 Original Android Development] Audioboxer:
Yeah, faux's implementation.
[Nexus 4 Original Android Development] Armin_van_buuren:
You need the script?

The kernel has already been implemented and those changes that popr wonder if you need to load the script.
[Nexus 4 Original Android Development] Franklin Bernard:
I tried for touch control to enable it via init.d. Its not working.

I used this script, edited it as mentioned by Viking. I checked the values mentioned in the script via File explorer, the accuracy_filter_enable remained 0.

#!/system/bin/sh

#Touchscreen Accuracy Filter Control

#Turn on

echo 1 > /sys/devices/virtual/input/lge_touch/accuracy_filter_enable

#Adjust the parms

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

echo 4 > /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 1 > /sys/devices/virtual/input/lge_touch/time_to_max_pressure

echo 55 > /sys/devices/virtual/input/lge_touch/max_pressure

I think I have done something wrong while editing it. I have used notepad ++ though saved as unix file and removed the extention '.sh' after saving.

Then I used the default script which was given by Viking with accuracy_filter_enable =0. just to check if the script is working. I checked the other values like

delta_max = 100

direction_count = 13

which was not per the script.

I have given the right permissions after copying it in Init.d folder. And the sound control is working per the Init.d. script.

Can anyone please check and confirm in B49 if touch control is working via init.d

Thanks,

Franklin B
[Nexus 4 Original Android Development] thracemerin:
Stuff to check:

1) you have busybox installed and it's in /system/xbin

2) if you aren't on CM you installed the last base kernel (b37) before installing B49

3) if you saved the script using Windows that you used notepad++ or something similar to save in unix/linux format to eliminate the windows carriage returns, etc...
[Nexus 4 Original Android Development] Armin_van_buuren:
B49 and flashed the permissions on init.d script nongún not notice the sound or change in speaker or with headphones using Poweramp.
[Nexus 4 Original Android Development] Franklin Bernard:
1.Yes

2.Im on ELE ROM AOSP based , flashed 4.2.2 stock/components then b37 and then b49.

3.yep used notepad++ and saved in unix format
[Nexus 4 Original Android Development] thracemerin:
does the script set correctly if you just run it from terminal or adb shell?
[Nexus 4 Original Android Development] ceejay83:
Do you have the donate version? What are the advanced gamma options?
[Nexus 4 Original Android Development] Connor Baker:
I'm slightly confused. I flashed Faux's ultimate kernel and OC'ed the CPU to 1.9ghz with GPU to 487mhz. I experienced a ton of lag and micro stuttering. Then i flashed this kernel. All the lag and stuttering is gone. I'm super confused. Any one?

Connor Baker
[Nexus 4 Original Android Development] Franklin Bernard:
root@android:/system/etc/init.d # ls -l
-rwxr-xr-x root root 246 2013-03-10 20:25 02Sound
-rwxr-xr-x root root 3890 2008-08-01 17:30 91tweaks
-rwxr-xr-x root root 213 2013-03-10 11:02 99fstrim
root@android:/system/etc/init.d # cp /sdcard/01Touchscreen1 /system/etc/init.d
root@android:/system/etc/init.d # chmod 755 *
root@android:/system/etc/init.d # ./01Touchscreen1
./01Touchscreen1
root@android:/system/etc/init.d # cd /sys/devices/virtual/input/lge_touch/
root@android:/sys/devices/virtual/input/lge_touch # cat accuracy_filter_enable
filter_enable
1
root@android:/sys/devices/virtual/input/lge_touch #
C:\Users\IBM_ADMIN>adb shell
root@android:/ # su
root@android:/ # cd /sys/devices/virtual/input/lge_touch/
root@android:/sys/devices/virtual/input/lge_touch # cat accuracy_filter_enable
filter_enable
0

If i run the script manaully its working, but not working after reboot
[Nexus 4 Original Android Development] :
Hi,

Which scripts do you use? Can you post them here? Before b49, which kernel version?

If I remenber right in PowerAmp you need do disable (or enable?) an option like "Direct Volume Control" or something like that... Maybe it's that :confused: (it's in the description on the Play Store about volume issues).

It's the gamma grey / gradient controls like Faux123 interface.

:)

Hi,

Maybe your phone doesn't like the ultimate version of his kernel or you need to adjust some settings or you have made some wrong settings :confused:

I don't know, if you have some issues with Faux's kernel the better is to ask in his thread ;)

If _motley kernel works well for you and suits your needs so... For me no more comparison between xx's kernel versus xy's kernel (I mean about battery / performance / general opinion and mainly "why xx'x kernel lag" and "why xy's kernel doesn't lag" or as such questions), it avoids the war / flamming :angel:.

The only thing I speak about some others kernel is about some features: if it's possible, if it's worth it to implement them in _motley kernel and what _motley thinks.

:)

@ Franklin Bernard, here I'm sorry I don't know why it does not work for you :confused:, the other scripts in your init.d folder works?
[Nexus 4 Original Android Development] sideeffects:
viking37 your 01touchscreen script didn't work for me until i deleted the line breaks and re-added them on my phone using text editor. Think that's caused by windows editors using unsupported line breaks.
[Nexus 4 Original Android Development] senses!:
Good work motley. This version is fast and smooth! Perfect kernel mate

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] Franklin Bernard:
Viking, Yeah..other scripts are working. Thanks

---------- Post added at 04:19 AM ---------- Previous post was at 04:17 AM ----------

Sideeffects,

Hi .. Will you be able to attach the scripts??? Thanks.
[Nexus 4 Original Android Development] :
Hi,

Sorry but my script works just fine (and I don't use widows text editor but Notepad++, never had any issues with my scripts), at least for me :D

I have no issues, the values are changed...

I use this one, with the correct permissions and all is fine: http://www.multiupload.nl/EG51AEA3C0

@ Franklin Bernard try this above it works...

I don't know what is wrong with your setup or what you have changed in the script :confused:

EDIT:

@ _motley,

Do you use A15 -mcpu flag optimization in your kernel?

Thanks :)
[Nexus 4 Original Android Development] chrone:
dear _motley,

been meaning to ask but always forgot and i also could not find proper documention regarding io_is_busy, some said that it will improve performance, is io_is_busy disabled on ondemand governor intentionally?

quoted from AndreiLux:
[Nexus 4 Original Android Development] Franklin Bernard:
Thank you Guys,

I have reinstalled busybox and tried Viking's latest script. It started working.
[Nexus 4 Original Android Development] ‬1‬:
such a good kernel.buttery smooth. i didn't expect this much before install it to be honest. great job.
[Nexus 4 Original Android Development] veyka:
I would think the quote would tell you that you don't want to to enable it, as it's irrelevant on ARM

Krait is not A15, so I am pretty sure it wouldn't benefit from that flag anyway.

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

Yes, you're right... but does not our CPU's take some Cortex-A15 parts? I mean there is some A15 stuff in the S4 Pro APQ8064?

I'm not exactly sure about that, I don't remember where I saw it or maybe it was a false information :confused:

Maybe there will be a gain :confused:

:)
[Nexus 4 Original Android Development] mundixx:
Does anyone notice a faster battery drain with the screen filter on? Or this should be expected :confused:

Sent from my AOSPA Nexus 4
[Nexus 4 Original Android Development] :
Hi,

For me no more battery drain... Battery drain depends of too many factors... Try disable it and see for a few days.

By "screen filter" you mean "Touchscreen Accuracy Filter Control" enable, right?

:)

EDIT: @ Franklin Bernard , glad to see that your issue is solved :)
[Nexus 4 Original Android Development] chrone:
thanks for this. i wonder why google enable io_is_busy on stock kernel. haha. :)
[Nexus 4 Original Android Development] jazzboyrules:
Hey _motley,

I had been silently updating your kernel and enjoying it. But today I realized that the wifi connection breaks when the phone goes to sleep (while charging, I haven't tested it otherwise) on b49 (probably post b40 versions too but not sure). I realized this because my Tasker initiated late night auto backup did not happen yesterday when I was on b49. Before that I was on b40 and the backups happened fine. Conditions for those backups to happen are: time, wifi connection state and charging state. My phone was charging and 2:03am is bound to happen everyday so the only var that has to be false is the wifi connection state.

So my doubt is that the wifi got disconnected when the phone was charging. Now I have enabled log of wifi connection/disconnection states in Tasker and tonight I will get to confirm if that's what happened yesterday night.

I'll keep you posted. btw I tested out the sound control.. loving the speaker and headphone sound quality, when all set to 35.
[Nexus 4 Original Android Development] :
No wifi issues her with b49.
[Nexus 4 Original Android Development] thracemerin:
Other than the issue outlined here: http://xdaforums.com/showthread.php?t=2072930

I'm not having any WiFi issues on b49 or any version since b37 for that matter.
[Nexus 4 Original Android Development] faux123:
https://gerrit.chromium.org/gerrit/#/c/29435/

I think chromium developers for ARM think otherwise ;) I tend to agree with Google engineers :cool:
[Nexus 4 Original Android Development] echo_rc:
how about battery life?
[Nexus 4 Original Android Development] :
Hi,

Perfect!

It must not be forgotten that it's not (only) the kernel or the rom that makes your battery life. It's mainly the user... I mean your settings: kernel related so CPU, mail account / meteo / social networks sync, apps, usage, screen brightness, etc...

Each time people ask these kind of questions as they think it's only the kernel or the rom that depends of the battery life... it makes me smile :D

In any case no issues with _motley kernel about battery life...

But if you set your screen brightness to 100 %, overclock your CPU to 1.67 Ghz, auto sync every 15 mins for 4 account mails, meteo sync every 30 mins and facebook, etc... Don't blame the kernel... :D

Ok it's an extreme example but the main idea is here, that I want to said it's not only the kernel or rom responsible for bad (or good) battery life. But people tend to believe it...

:)
[Nexus 4 Original Android Development] Vlad87do:
is it something similar to voodoo sound ???

how to control it ??
[Nexus 4 Original Android Development] :
Hi,

You can use some init.d scripts or use the apps from Faux123.

In short some example:

For the speakers:

For the headphones:

Here in attachment the script for the headsets (it's for what you asked). You'll need to tweaks the values to your like (see above). Read a few pages back, there is some more informations.

:)

EDIT: it's a "quote soup" what I did :eek::p:D
[Nexus 4 Original Android Development] jazzboyrules:
1-Script-to-Tweak-Them-All

Hey guys,

I am always thinking of the quickest way to tweak any kernel setting and I came up with this approach. It contains all the motley kernel tweaks that I use. I enable the tweaks for only the modules that I want. I call stuff like: vibration intensity control, sound gain control, rgb control, gamma control, etc each of them as a separate module.

The all in one script allows enabling/disabling each of the modules. In addition, it also allows tweaking each of the modules using variables. So you don't have to go edit the echo statements.

I have attached the script in zipped format.

How to use the attached zip file(s) : DO NOT FLASH IT.

Unzip it

Set the *_TWEAK_EN variables to either "y" or "n" as per your choice depending on which module(s) you want to tweak. Setting the value to "n" will use the kernel defaults for that particular module.

Make any changes to the tweak variables for the modules for which you set *_TWEAK_EN="y". All such variables will be found before the 2 consecutive lines with hash/pound signs. So don't edit anything below those pound lines (line 130 in v2 as of writing this).

Test it in a terminal emulator

Copy your custom script to /data/local/userinit.d or /system/etc/init.d

Update: Just to let you know that if you run the script as it is, it will set the gamma values to Mole's "halfbreed" settings. If you do not want that, set the value of GAMMA_TWEAK_EN to "n" to disable gamma tweaking completely or set the g_* variables to your liking before running it in the terminal.

Update 03/21/2013: Uploaded v2 of the same script. Now the script has the following tweak enable switches:

FSYNC_TWEAK_EN #

FASTC_TWEAK_EN # Fast Charge

VIBRT_TWEAK_EN # Vibrator Intensity

C_P_U_TWEAK_EN # Min/max num of cores, min/max frequency, governor, boost control

THERM_TWEAK_EN # Thermal throttling

HOTPG_TWEAK_EN # Auto hotplug

SDCRD_TWEAK_EN # SD Card scheduler, read ahead block size

TCPCC_TWEAK_EN # TCP Congestion Control

TOUCH_TWEAK_EN # Touchscreen accuracy filter

SOUND_TWEAK_EN # Sound gain

COLOR_TWEAK_EN # R G B values

GAMMA_TWEAK_EN # Gamma values

I have yet to add tweaks for ondemand. As of now, setting governor to ondemand will use the default kernel ondemand parameters.

Feel free to suggest any other module that you would like to be added to this.

Update 03/26/2013: Removed the writes to cpu1/2/3 folders. Updated _v2 script.
[Nexus 4 Original Android Development] AirOne70:
This script doesn't work for me.. (I have check the file, and the value is always 0..)

Any idea?

Envoyé depuis mon Nexus 4
[Nexus 4 Original Android Development] faux123:
they will change after music is playing.
[Nexus 4 Original Android Development] :
Hi,

You need to add this at the first line of the script, if you use just the script as it is it will not work:

Test with the attachment, as always remove the .zip extention before putting the script in the init.d folder.

Set the correct permissions then reboot.

Have you some other scripts? Are they working?

Maybe a Busybox issue also...

EDIT: Faux123 is faster :D, maybe it's this.

:)
[Nexus 4 Original Android Development] jazzboyrules:
About changing the sound profile, I am not able to understand how this tweak works. The default content format of those files out_lim, AGC_Max_Gain, ... is different, it is not just numbers.

Example: Default content of AGC_Max_Gain is "AGC_Max_Gain : 0,pdata->AGC_Max_Gain : 12". But the "echo 12 > /sys/bus/i2c/devices/0-0058/AGC_Max_Gain" command will set its content to simply "12".

Update: Looks like those files are recreated on the fly based on their previous content. Correct?
[Nexus 4 Original Android Development] AirOne70:
Oh yes, thanks. When music is playing, the values are different.

I have Touchscreen Script, Sound Script (Headset, Mic) and they are working. And yes, thanks to Faux, but I have some strange values, like that:

Envoyé depuis mon Nexus 4
[Nexus 4 Original Android Development] cpom1:
My first time using motley and I'm highly impressed with it.

Just curious have you ever thought about GPU overclocking?

Sent from my Nexus 4
[Nexus 4 Original Android Development] :
Hi,

I already asked to _motley the ability to overclock the GPU via init.d script or SysCtl interface so the user could have the choice, by default at 400 Mhz and the ability to overclock to 487 Mhz (it seems it's the maximum?) for those who want to play and test... He did not look too agree :D. Maybe later, who knows? Wait and see :D

:)
[Nexus 4 Original Android Development] Simer03:
Very nice kernel man! Actually been using this for a few days (came back to it) and it still is the smoothest experience ive experienced on this phone! No offense to any other kernel but just my experience

Sent from my Google Nexus 4
[Nexus 4 Original Android Development] cpom1:
i actually agree with you. quite surprised. no offense to anyone.
[Nexus 4 Original Android Development] Franklin Bernard:
And also, Is UV possible for GPU ? and can we squeeze little battery by doing it ?

Thanks,

Franklin B
[Nexus 4 Original Android Development] Simer03:
Even Faux admitted he uses this kernel lol

Sent from my Google Nexus 4
[Nexus 4 Original Android Development] thracemerin:
He said he uses it for testing his apps, not the same as using it as his daily driver.
[Nexus 4 Original Android Development] Simer03:
Never said daily driver...I said he uses it...u just repeated what I said in different words lol

Sent from my Google Nexus 4
[Nexus 4 Original Android Development] air2k57:
Not sure if kernel or ROM relates but had a weird bug just now. Battery was at about 11%. Plug the phone in, all of the sudden it shows charged after less than a minute. Reboot, back to 11%.
[Nexus 4 Original Android Development] efan3719:
i've seen that happen on my phone as well. not 100% sure if it's ROM or kernel.
[Nexus 4 Original Android Development] thracemerin:
It's neither, the battery chip in this phone is a bit quirky. It might be solvable with kernel tweaks, but none have been discovered yet.
[Nexus 4 Original Android Development] efan3719:
Crazy. Never knew that. Doesn't really bother me at all and doesnt happen that often.
[Nexus 4 Original Android Development] thracemerin:
Yeah, it occasionally goes out of sync, sometimes badly, eventually it fixes itself if you leave it alone.
[Nexus 4 Original Android Development] DnickDominic:
Ive never looked into the source code for it but on my old device (samsung galaxy s 4g) the audio chip had the improvements and when i opened dsp manager where it says headphones | speaker | bluetooth it had another column that said w98___ something like that but it was the sound chips optimizations. Basicly there was no need for voodoo. I think its on samsung kernels because voodoo is originally created for them.? Dont have much knowledge on sound drivers and what not. So be glad to correct me if im wrong.
[Nexus 4 Original Android Development] faux123:
The wm8994 audio DSP is a full featured codec but Samsung just used the very minimal and basic functionality of that chip (amplification only). SuperCurio discovered this and enabled access to internal private registers for further tweaking, and he called it VoodooSound.

FauxSound also exposed some registers that weren't meant to be adjusted outside of the default drivers for Qualcomm's own wcd9310 codec.

Between the wm8994 and wcd9310 audio codecs, the wm8994 codec is still far superior but more expensive than Qualcomm's own integrated chip. Very few flagship phones used the wm8994 codec, it seems the integrated solutions will become popular due to its competitive pricing and hopefully the integrated solutions will get better with newer revisions (wcd9320 chips are supposedly coming out soon)
[Nexus 4 Original Android Development] DnickDominic:
And oh wait. Im so confused by the installation instructions. Im on matr1x kernel. Im gunna update the new aokp nightly so the kernel will go to faux modified stock. So heres my question. I can just flash over the newest kernel correct? Because of the anykernel script
[Nexus 4 Original Android Development] _motley:
It is now at 255 247 255, only the green was tweaked.

You can see the commit here:

https://github.com/motley-git/kernel-Nexus4/commit/78772228531ba1a66a70d73e2b3337f35e154c8d