yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] :
@ _motley, have you seen my post? :D

No issue here with or without tweaking the touchscreen stuff:

1) Rom -> AOKP PUB build 5 (with Linaro / Bionic / Krait optimizations).

2) Init.d script for adjusting the touchscreen (need some tests, I've posted a scrip test but no feedback).

3) No touch control.

If it was directly kernel related

all

the users of _motley / Francisco / *Matr1x* kernel would reported this issue...

Just my opinion...

:)

EDIT: @ air2k57, thanked you by mistake :silly::D
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

1) I tried with cm10.1 m2 release, as well as linaro kang of it. I also had same problems on aosp build with bionic commits, one that jarjar compiles.

2) no

3) no

To me, the navigation bar is fine, it is responsive. The only issue I have is it pulling itself down when screen first becomes active. Which isn't a big deal when I hit the power key as it only happens for a second. But, when I'm on call, if I take the phone away from my face and screen turns on, notification bar would pull itself all the way down 1 out of every 5 times lol. That second one bothered me enough to flash b40 back lol.

---------- Post added at 07:04 PM ---------- Previous post was at 06:58 PM ----------

Guess what? Lol I did report it. Same issue on Franco r92 and up. That's the weird part, I was at my parents house last night and my step dad has n4 as well. I helped him root it and threw on aosp build + b44. I haven't been able to replicate any problems on his...

Would recovery matter at all? That's the only thing I could think of.... I'm using twrp and his is cwm.

Edit.... I like thanks! Haha even if it was by accident! Makes me feel as if my post was productive :8
[Nexus 4 Original Android Development] :
Re,

It's since r93 he has introduced "Accuracy Filter Control"... The thing I would point out it's that no all the users have been repported the issue, if it was directly caused by the touchscreen stuff, all the users would have this problem and it's not the case. Maybe a mix with a rom / mod / or whatever. Why I have not this issue like many others?

Weird these bugs :p:confused: , it's caused by Cyanogen based rom, change your rom ... -----------> I go out :silly::p:D:D:D

:)

EDIT: no worries for the thanks, so it is with pleasure :D
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Well, maybe it was r93. Because I noticed it right after one of the updates, which made me look into it and the only major difference I saw, was ts control. Same with Motleys, it started right after it was added. Clean install.. .tried that, different ROM... Tried that.

Maybe our ts are different to where some are different? After all, not every ts has yellow tint even, so there could be some hardware difference as well.

Like I stated, I rooted my step dads nexus as well with same combo I tried, no issues on his thus far on b44. Then only difference on his is that I used cwm for recovery.
[Nexus 4 Original Android Development] karanrajpal14:
1) Rootbox switched to PAC now.. testing b44 with it. Will report in a day!

2) No.. should i be using it?

3) No
[Nexus 4 Original Android Development] thracemerin:
I haven't seen these issues on any of the versions since you introduced the Franco touch screen adjustments, nor can I replicate them when I attempt to do so.

1) CM10.1 (my unofficial build)

2) No

3) No
[Nexus 4 Original Android Development] faux123:
Not all parameters can be adjusted in real time or out of sequence. Some needs to be in sequence :angel:
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Just reflashed everything, literally as clean as I can and switched to cwm recovery. Will report... Cm10.1 linaro + b44.

Edit... Flashing everything via cwm seemed to have fixed the issues. Fingers crossed!
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Nope....didn't fix, it is back ;(.
[Nexus 4 Original Android Development] Voltor46:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Cm10.1 + b44 = Really good performance and Battery life. The user experience with this kernel is amazing. Just one issue: when using multitasking with the recent app button, sometimes it gives me a System UI FC, and then recent app button stops to work.

I need to reboot the device to make it work again. Any idea about how can i solve it?

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] Remoteconcern:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

That's probably not a kernel problem. Try wiping and reflashing your ROM.
[Nexus 4 Original Android Development] rlaw:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

I'm having an issue that I reported in the cfx thread (as that's the ROM I'm using) wherein when I first turn screen on, the status bar will pull down when I attempt to swipe to unlock when screen is first turned on (sometimes status bar will also already seemingly be pulled down a bit).

At first thing thought it might've been a ROM bug as this issue only occurred when I first started using the latest cfx release but I also first flashed b45 with that build as well. After reading the comments here, I think it might be a kernel bug related to the touch interface.

I don't use the touch interface nor touch control. I'm gonna the latest build before the touch interface was merged and see if I still have this ever so slightly annoying and completely random bug. I can't ever recreate it. It just happens randomly when screen is powered on!
[Nexus 4 Original Android Development] karanrajpal14:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Well it surely is a kernel bug pertaining to the touch screen patches. I just reported this a few posts above you. And I tried b44 on Pac man ROM too and I still face this bug. Motley, please look into this.
[Nexus 4 Original Android Development] nextelbuddy:
this worked perfectly..

when I run this 91halfbreed script in terminal and then turn the screen off and on.. the colors change to what I want.

but if i put the script in the \system\etc\init.d folder and restart nothing happens and screen looks like stock.

what gives? is there something wrong with motley kernel and stock roms that doesnt support init.d?
[Nexus 4 Original Android Development] thracemerin:
You don't have busybox installed.
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Yea, same. I tried so many different Roms now, same results.
[Nexus 4 Original Android Development] chrone:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Here's my setting on stock rom and motley:

1. Install busybox by stericson the normal way to /system/xbin, busybox 1.20.2 stable.

2. Create init.d folder and make it readable and executable inside /system/etc (chmod 755 /system/etc/init.d)

3. Copy paste the script which worked when testing with sh command before to /system/etc/init.d and make it readable and executable (chmod 755 /system/etc/init.d/youtscripthere)

4. Reboot and profit. :)

Update:

I think I found the culprit why your init.d script didn't work at all. Perhaps you're flashing the CM build 37 kernel and not the Stock/AOSP Build 37 with init.d support. I also flashed the CM 37 and then 40 and found the init.d script was not working. lol :D

Sent from my Nexus 4
[Nexus 4 Original Android Development] AcmE85:
I have tested your script for a couple days and compared it to stock settings daily.

It is definitely more responsive. Especially when scrolling lists (e.g. contacts, titanium backup, root explorer)

I can notice it right away.

Did you tweak further?

btw I am on Linaro CM 10.1 + Bionic with _motley b44

no screen problems whatsoever...
[Nexus 4 Original Android Development] nextelbuddy:
i just checked and the kernel in my folder that I flashed says:

motley_422_n4_exp_build_37_initd.zip

and then i flashed

motley_anykernel_422_nexus_4_build_44.zip

i have busy box installed and it was at the latest v1.21 but i reinstalled 1.20 stericson

placed my script in my /system/etc/init.d/91/halfbreed

reboot

still same colors.

I ran the SH command in terminal and colors changed to what I wanted

doesn't make any sense lol

whats so different about my stock rom motley kernel setup....

for now i downloaded an app called smanager and am having it load the script for me at boot as SU.

sucks I have to do this and it works but the motley/init.d isnt working for me. I hate hack jobs...
[Nexus 4 Original Android Development] trismegistos:
AW: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Try to flash 37, reboot and then 44. If it does not work do a chmod 755 /etc/init.d/yourfile
[Nexus 4 Original Android Development] nextelbuddy:
i dont even have any programs that can set chmod 755

im on windows

and in root explorer i have even tried giving the file all red/write.execute permissions for all groups just to test and still nothing.

and I did flash 37 and rebooted then rebooted back into recovery and flashed 44

also tried flashing 37 first and 44 in the same recovery session and still no change.

i wont waste anyone else s time on this. i have my work around which is using smanager for now. i probably some weird anomaly that cant even be explained. :cyclops:

thanks for everyones help. Ill keep poking at it.
[Nexus 4 Original Android Development] IAmAN00bie:
When you made your script, did you make sure the EOL (end of line) characters were not invalid? You can't just make a script using Notepad or Word, you have to use something like Notepad++ and choose the proper formatting otherwise your script will not run.
[Nexus 4 Original Android Development] ctfrommn:
Is the script you are using in Motleys format? Meaning the lines end with red, green, blue and not r, g, b? Is the checksum at the beginning of each line correct? Either of these will cause issues with color/gamma changing.
[Nexus 4 Original Android Development] chrone:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

If i'm right, you misplaced the script inside 91 folder. Try rename halfbreed to 91halfbreed and put it upward inside init.d not 91 folder and delete the 91 folder.

use chmod 755 91halfbreed from the same terminal as you tested the working script before. or from root explorer checked all 777 (read write execute) just for testing. Also try to chmod 755 /system/etc/init.d folder too. :)

It is also preferred to install busybox into /system/xbin.

Sent from my Nexus 4
[Nexus 4 Original Android Development] rlaw:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Tried older kernel build without touch control interface.

The bug that occurs when screen is first powered on does not exist.
[Nexus 4 Original Android Development] :
Hi guys :)

Please ask to the questions above to help to help isolate your issue :)

But... why nobody might think that it may be caused by the rom itself or a mod or like I said the combo rom / kernel but not only / directly the kernel:(:confused:

Always no issue for me (AOKP PUB Build 5), like with my previous rom (Vanilla Rootbox), no touchcontrol and yes init.d script for touchscreen accuracy...
[Nexus 4 Original Android Development] thracemerin:
It's definitely the kernel.
[Nexus 4 Original Android Development] nextelbuddy:
I didnt make the script, i downloaded it from a post linked by Chrone. I do use notepad++ set to UNIX language as well. teh script runs fine when run in terminal with sh command and also runs fine when using SMANAGER set to boot

just doesnt work with my init.d folder

that was a typo in my text on the forums my apologies.

my directory as is and always has been is:

/system/etc/init.d/91halfbreed

very strange how I cant get it to work other than with terminal and smanager app
[Nexus 4 Original Android Development] :
Hi,

Ok, so why some users have absolutely no issue :confused:
[Nexus 4 Original Android Development] thracemerin:
Your busybox is installed in system/xbin? and includes run-parts?
[Nexus 4 Original Android Development] franciscofranco:
Its probably some of the filter items that is not configured properly. Instead of pulling it could be nice if users tried different settings. My touch responsiveness is much better with the filter, but there could be some timing issue with the values that we haven't found yet.
[Nexus 4 Original Android Development] thracemerin:
I was having trouble reproducing it, but once I managed to get it to happen (this was on stock with just motley kernel, no other mods, no apps installed other than the stuff that comes with stock factory) I could reproduce it pretty much every time, I recompiled b45 without the touch filter adjustments and I could no longer get it to happen. That doesn't mean reverting the entire thing is the correct response, but we need to dig into why it's happening.

People need to post logcats, dmesg, etc...
[Nexus 4 Original Android Development] nextelbuddy:
no, it is installed to /system/bin

I didnt choose where to install it, i downloaded busybox free from google play and used the built in installer.

should it be installed in xbin instead of bin? I will go ahead and choose to install to xbin right now.

thanks!
[Nexus 4 Original Android Development] starscream92:
I know that app gives you choices as to where to install BusyBox. You can easily uninstall it, and re-install into /system/xbin using the app :)
[Nexus 4 Original Android Development] nextelbuddy:
That did it, i installed busybox to xbin, set my permissions for the script for write/read/execute for all groups and reboot and now my colors are loading on boot.

thanks so much!

i had no idea nor did I read anywhere that you have to change busybox to install to xbin not just bin,, why is this? does everyone just know this already and I wasnt aware? as busy box installs by default to bin so its different than expected.
[Nexus 4 Original Android Development] obtained:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

That's a really strange issue. I never had to manually install busybox. Just aokp pub, b37 and b45 and used a halfbreed script someone posted on the "let's calibrate mako" thread and worked like a charm. ?
[Nexus 4 Original Android Development] thracemerin:
A lot of source built custom ROMs include busybox, stock doesn't.
[Nexus 4 Original Android Development] obtained:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Oh I think someone was having the same issue on aokp pub. Probably a few pages back. I just assumed it was the same person.
[Nexus 4 Original Android Development] thracemerin:
You might be right, I just assumed he was on stock since he didn't have busybox installed properly, to my knowledge source built ROMs always ship with busybox in /system/xbin
[Nexus 4 Original Android Development] chrone:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Great!

_motley did posted about this on first post.

another color preset from faux123's accurate preset zipped as per attached translated by copi, more natural, enjoy! :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] IAmAN00bie:
Franco's latest kernel has added volume boost for the headphones, and I know Faux has already been cooking up his own solution before that too. I wonder which of these two will we see from Motley. ;) ;)
[Nexus 4 Original Android Development] thracemerin:
Why does every kernel have to have every feature that appears in another kernel?

Not saying that having volume boost is bad, but I don't get why people go in all the threads and point out features that were added in other kernels.
[Nexus 4 Original Android Development] IAmAN00bie:
Sorry, it's just that Motley's has been the best of both worlds for me (between Faux's and Franco's) and I was just being a tad giddy for these new features. It's totally up to Motley if he wants to add it of course, I'm not going to demand he do it (and even if he didn't, there's no way I'm going to switch away thanks to how comfortable I've gotten with my setup on his kernel). I didn't mean any disrespect.
[Nexus 4 Original Android Development] thracemerin:
There's no need to apologize, my question was probably a bit on the snippy side which wasn't my intention.

For the record, I'm not against adding anything to Motley kernel, nor is it ultimately up to me, but if every feature ends up in every kernel, then they might as well be 1 kernel is all I'm saying.
[Nexus 4 Original Android Development] faux123:
I never believe in kang bang kitchen sink kernels anyways.

TBH, I use motely's kernel as well for testing compatibilities with my apps :D It is quite nice of a kernel and I like it.. If I didn't have my own, I probably run either motely's, Harsh or Ir's kernel.. (It's a toss up between the 3 of them for me, but each has his own take on things which I like).
[Nexus 4 Original Android Development] Audioboxer:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

I think FauxSound works on all kernels :)
[Nexus 4 Original Android Development] trismegistos:
AW: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Hi, perhaps some one is interested in this. I don't like to use apps for my kernel settings. So I made an init script for color (moles HB ), governor, sound and other settings. Here is a flash able zip for it.

https://docs.google.com/file/d/0B9uFoypS48QTQUI5ajdBclhqRGc/edit
[Nexus 4 Original Android Development] yukkio:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

We need access to open the file.

Edit: Pk, I got it. It will be great if there was a setting to change CPU interactive settings like main sample time, go hi speed...
[Nexus 4 Original Android Development] trismegistos:
AW: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Access should be there now for everyone:

you can put this at the end of the init.d file:

echo "80" > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load

echo "1400000" > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq

echo "40000" > /sys/devices/system/cpu/cpufreq/interactive/min_sample_time

echo "20000" > /sys/devices/system/cpu/cpufreq/interactive/timer_rate

and set your own values in there.
[Nexus 4 Original Android Development] karanrajpal14:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

I'm using the CM kernel. Will it work on that?
[Nexus 4 Original Android Development] trismegistos:
AW: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

I don't think that cm has the sound an gamma interfaces integrated in there kernel. So some settings will not have any effect. You can execute the init script in a terminal on your phone and see if you get error messages.
[Nexus 4 Original Android Development] karanrajpal14:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Umm I actually meant motley's CM based kernel. Sorry for not being clear!
[Nexus 4 Original Android Development] trismegistos:
AW: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Oh OK. That will work then
[Nexus 4 Original Android Development] _motley:
Build 48 posted

b48 has now been posted (see OP).

For those that were having touchscreen issues, they should go away. But, we can still allow those wanting to turn on the accuracy filter for tweaking to do so. The safest way to adjust settings is to turn off the filter, adjust parameters, and then turn back on, especially if editing from a file explorer while interacting with the screen.

Here are somebody's tweaks (viking37's perhaps?).

To use:

#!/system/bin/sh

#Touchscreen Accuracy Filter Control

#Turn off
echo 0 > /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

#Turn on
echo 1 > /sys/devices/virtual/input/lge_touch/accuracy_filter_enable

P.S. Good news...Goo.im accepted my application, so I can start posting stable kernels there. If b38 is tagged as stable, I will build full versions and use that as a test.
[Nexus 4 Original Android Development] :
Hi _motley :),

Yes it's my test values :D, but I have not tested other yet... I don't really know what is "ignore_pressure_gap", "direction_count" and "delta_max", I Googled without result. And the values I used was a bit random... so I think we could found better.

It seems there is an improvement for me with these values, another user reported too (thanks to him):

Maybe not a placebo effect, but not really confirmed :confused:

Thanks for the update ;)
[Nexus 4 Original Android Development] :
EDITED: attached an init.d script directly for lazy people :D. Don't forget to remove the .zip extension, it's not a flashable zip.

Touchscreen Accuracy Filter Control is off by default so for activate it don't forget to modifie this line:

From:

To:

Or maybe easier: http://www.multiupload.nl/155CJZXFOH

:)
[Nexus 4 Original Android Development] _motley:
Using these values in my testing thus far when I have the filter turned on. They do seem to work well for general usage:good: I haven't tried playing games yet to see how they work in that type of environment.
[Nexus 4 Original Android Development] faux123:
@motley

Introducing FULL WCD93xx SOUND CONTROL, 100% GPL'ed (Just like my Speaker Amp Control FULLY GPL'ed a couple of weeks ago!)

Source Code available here:

https://github.com/faux123/mako/commit/911a80eb10df7b1f0c120ae29137e1b682f8ab7e

This will allow you to CONTROL:

1. Headphone Gain Left / Right (independent controls)

2. Handset Microphone Gain

3. Camcorder Microphone Gain

4. Speaker Gain

With wide range and high fidelity!

Enjoy!
[Nexus 4 Original Android Development] IAmAN00bie:
You are an amazing person! Love the work. But your link leads to a 404, probably has something to do with the shortening of the link. Here's the full link: https://github.com/faux123/mako/commit/911a80eb10df7b1f0c120ae29137e1b682f8ab7e
[Nexus 4 Original Android Development] karanrajpal14:
Re: [KERNEL][Mar 9][b48] _motley kernel for the N4 (fix touch issues again!)

I think this has been asked before but how do I edit the script? Just rename it to text and edit it? I want to change it to interactive governor
[Nexus 4 Original Android Development] :
Re: [KERNEL][Mar 9][b48] _motley kernel for the N4 (fix touch issues again!)

@ faux123, very nice from you to share directly here your source code and awesome work ;)

Maybe a new _motley kernel b** will come in a short time :p:D

This new sound improvement will be a great feature like for the speakers :)

Thanks ;)
[Nexus 4 Original Android Development] benrees21:
Re: [KERNEL][Mar 9][b48] _motley kernel for the N4 (fix touch issues again!)

Nice. B48. :thumbup:

Sent from my Nexus4™
[Nexus 4 Original Android Development] franciscofranco:
Thanks for the settings, they work great.
[Nexus 4 Original Android Development] :
Re: [KERNEL][Mar 9][b48] _motley kernel for the N4 (fix touch issues again!)

Hi francisco :),

Glad to see you here, thanks for the feedback ;)

Thanks also for the find ;)

So it looks like it's not a placebo effect :D, happy to have found these settings (I mean the values) :p :D

Thanks for the feedbacks, if someone have another settings, you can share them, will test :)