yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] JmPTaz09:
Running at your preloaded values, got to 1 hr screen on (bought 15-20% brightness) with 5.5 hours runtime. Using with Maddoggin ROM. Seems really nice so far; build 38.
[Nexus 4 Original Android Development] guapinoy:
Great kernel on stock rom. I UV - 150 for the most part and using ondemand. Nexus 4 is nice and cool. This was 100% on wifi though.
[Nexus 4 Original Android Development] MatAuc12:
What is the RGB in your new kernel?
[Nexus 4 Original Android Development] ah_long:
just installed the latest build and I appreciate the change in the color profile. There's a slight color bump and made the screen more pleasing to the eyes; for those who are concerned, this is nothing drastic, but it is a welcomed feature for this kernel.
[Nexus 4 Original Android Development] pa.pn2:
strange issue here

flashed new aokp pub build with motley kernel 37 then 45

in previous build i could see the init.d folder in system/etc

before flashing the rom i placed the touch script from viking into the init.d folder

after flashing rom and kernel there is no init.d folder anymore.lol

any idea whre it could be?
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Mmmm delicious wifi multicast wakelock, how I remember you from every over device I have had.

Sounds like nothings being filtered, what do you have McastBcastFilter set to?

Sent via Nexus 4
[Nexus 4 Original Android Development] :
Weird, and if you create an init.d folder with the correct permissions (rwxr-xr-x) then put your init.d scripts inside, reboot, maybe it will work?

Or reflash the kernel, easier...

:)
[Nexus 4 Original Android Development] thracemerin:
0 which is the default for the current CAF version of Prima. I suppose I could mess with it some and see what happens.
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Hmm, according to the notes that won't filter anything, try 1, should kill the windows spam.

Sent via Nexus 4
[Nexus 4 Original Android Development] thracemerin:
I realize that, but I was under the apparently erroneous impression that setting it to 0 and HostARPOffload to 1 would fix this, obviously I was wrong :D
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

No, I don't use s2w. Hmm, so I flashed b45 and then added the two lines to the file. Weird thing, if the phone is idle for say half hour when I wake it, it shows as if I have very low reception, but it does work still and when I initialize data, bars go up to full.
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Well, it will fix the ARP issue, but as you noticed it will bring back the rx wakelock from hell!

The old fix for this was to turn the filter off, causing this sort of drain. So really we need it set back to 3 or at least 1.

I am really not sure how qcom managed to break their wifi driver so badly heh.

The device should have a packet filter that let's ARP stuff though heh.

Sent via Nexus 4
[Nexus 4 Original Android Development] thracemerin:
That's the thing, there are "fixes" in the CAF repo, I just replaced the stock Prima wlan drivers with the ones from CAF prima/master and built, given that CAF set the default to 0 for the filter that gives me the impression that they think they fixed the issue, but clearly they didn't completely solve it or something else is missing to actually make this fully work.
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Well, it fixes the issue, just causes even more problems ;D

Sent via Nexus 4
[Nexus 4 Original Android Development] pa.pn2:
hm reflashing motley 37 and 45 after did not work

still no init.d folder

weird:silly:
[Nexus 4 Original Android Development] thracemerin:
Its also possible that the issue is elsewhere now, they haven't merged this version of prima into their msm kernels yet, so the disconnect could be somewhere between the wlan driver and the kernel.

Edit: setting the filter to 1 re-introduces the delayed notification issue, ugh!

Edit 2: I temporarily give up until someone with a little more knowledge in this particular area sheds some light on the issue.
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Oh my goodness! reverting to b44 and removing those lines. I'm having more and more issues as the day goes on. When phone sleeps, I think my connection drops, or at least data does. Screenshot attached... That's what it looks like when I wake device after 10-15 minutes of idle. It usually stars out on edge.
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

That's means they fixed the ARP offloading but didn't fix up the packet filter, ARP offloading is great, but it seems that not everything is in place to actually fix the problem yet :/

Sent via Nexus 4
[Nexus 4 Original Android Development] _motley:
Looks like you guys have been busy while I was at work today;) Which branch did you pull and build with? "caf-wlan/master" ?
[Nexus 4 Original Android Development] _motley:
Thanks, since I am out of "thanks" for the day:good:
[Nexus 4 Original Android Development] thracemerin:
master branch from git://codeaurora.org/external/wlan/prima.git you can pretty much grab it and slap it in drivers/staging/prima of our kernel and it'll build. The required binaries are in the firmware_bin directory and you need them or WiFi just doesn't work if you build with that nor will the new binaries work with current kernels.

It fixed one thing but introduced a wake lock worse than the msm_hsic_host for wifi, it was terrible, even on my very quiet home network it was hitting upwards of 20% with roughly 50/50 awake/deep sleep percentage. I'm guessing the netfilter isn't set to ignore all the other multicast/broadcast stuff even with ARP offload fixed.
[Nexus 4 Original Android Development] _motley:
Well, it was worth a try! Kudos for that. Did you use all firmware files including /system/vendor/firmware/wlan/prima/WCNSS_cfg.dat?

It might be good to try a stable branch when one comes available with the arp patches. With master, you never know what you are stepping into:eek:
[Nexus 4 Original Android Development] thracemerin:
None of the last 10 or so version tags are marked stable, so you're probably right, we'll have to wait and see.
[Nexus 4 Original Android Development] franciscofranco:
Very good info here. Thanks for the effort guys!
[Nexus 4 Original Android Development] meangreenie:
Apparently the arp requess, notifications work perfectly if you hard set an ip for the nexus 4 on your router. If true, would this show qualcomm are looking at the wrong problem ?
[Nexus 4 Original Android Development] thracemerin:
The problem is that the phone doesn't respond to ARP requests when the screen is off, setting a static arp on your router is a workaround, but qualcomm is working on the correct problem, it just doesn't seem to be 100% solved as yet.
[Nexus 4 Original Android Development] meangreenie:
I did mean when the screen is off. I suffer the same problem since november :)

I'm going to try and set a static ip and test. i know it's a workaround, but thought it odd that it should work fine with a static ip.. of course if true.
[Nexus 4 Original Android Development] thracemerin:
It does work if you set the static IP on your router, the problem is there are lots of public wifi networks where you can't do that, so it's not a complete solution.

---------- Post added at 10:57 PM ---------- Previous post was at 10:16 PM ----------

I realized I didn't answer this part earlier, yes I did. I pulled all 3 binaries from the firmware_bin directory and put them in their appropriate locations.

If you build with the latest prima and don't pull the binaries WiFi is greyed out as off in settings and can't be changed.
[Nexus 4 Original Android Development] obtained:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

I have the newest 3-5-2013 aokp pub and flashed 37 then 45 and I have an init.d folder.... Weird..
[Nexus 4 Original Android Development] karanrajpal14:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Is anyone having problems of the status bar being pulled down partially after waking the device? Having this problem since the touch screen accuracy filter was introduced. I thought it was a bug in the ROM. Tired multiple ROM's I was wrong!
[Nexus 4 Original Android Development] :
Hi,

I think it has nothing to do with the kernel. I'am running AOKP PUB build 5 with _motley kernel b45 and I have not this issue. Running this combo since today with a fresh install (full wipe).

Your issue is rom related, try reflash your rom with a full wipe. Your issue is clearly due to a dirty flash, a theme / mod or maybe a bad download.

:)
[Nexus 4 Original Android Development] pa.pn2:
did you flashed first b37,then b45 @viking?

or directly b45?
[Nexus 4 Original Android Development] :
Hi,

b37 then b45 like it is said in the OP, and I reboot after flashing b37 then recovery and b45 (to be sure all is fine), no issues with init.d folder :silly::D

:)
[Nexus 4 Original Android Development] pa.pn2:
hmm k,did all as in op said.think ill fullwipe and start a clean setup then^^
[Nexus 4 Original Android Development] :
Yes I think it's the right direction to avoid any weird issues. I always do a full wipe when I flash a rom even if it's just a minor update. It takes time for sure to re do the setup but I prefer a clean install each time I flash a rom. And I never backup / restore my apps, settings or whatever, each time I start from scratch :silly:

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

I'll try again. This was a clean flash. I never do it the dirty way :P
[Nexus 4 Original Android Development] brainbeatuk:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

@motley. With the exception of gtavicecity most high end games real racing 3 can play smooth and just use two cores' been using perfmon app. My point is do you reckon you could make an option in thermal config so when core 0 and 3 get to 75c to just switch to core 1+2. Or is the temperature sensor on the whole cpu and not by core. Just thinking may be more efficient for gaming so don't get throttle, although I not experienced any recent using my previous settings still. Two interactive and last two performance,
[Nexus 4 Original Android Development] Remoteconcern:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Don't bother, it's probably a waste of time. I'm sure this a problem related to the touch screen patches. I know some people in the Franco thread had the same thing. I don't get this but someone else here did. I'm guessing as Franco works on the interface, that will be fixed...?
[Nexus 4 Original Android Development] :
Re,

For for those who noticed micro stuttering / lag in transitions, opening apps, switching between apps I think it's rom related (or maybe some kernel settings, I mean CPU governor, etc...).

I noticed that with Vanilla Rootbox rom finally, I did not pay too much attention at the beginning but in fact the transition when opening settings or switching between apps from the multitasking windows are not really smooth, yes I encountered some kinds of micro stutterings. Whatever CPU settings they were there.

Switch to AOKP PUB build 5 (with Linaro / Krait / Bionic optimizations) and no more micro stutterings, I found again the smoothess I had with AOK PUB buid 3.

I does not promote a rom but in this case it's not kernel or settings related but it's at rom level in my opinion, at optimization level with the different patch / compilation that the rom is compiled. Or at least a combo rom / kernel well optimized. Maybe the fact _motley kernel is compiled with Linaro toolchain (since b31 if its always the case) like the rom is a perfect combo?

With _motley kernel b45 (and my governor settings) and AOKP PUB all is smooth and fast again compared to my previous rom.

:)
[Nexus 4 Original Android Development] ruzkay:
that wouldn't even make much difference if the sensor wasn't for the whole cpu since the heat spreads mate^^ and i think the temperature problem is more about the battery which also gets a lot of heat

So no, it isn't possible. :p
[Nexus 4 Original Android Development] :
Hi,

How the fact that the status bar being pulled down partially after waking the device can be related to the kernel :confused:

With two different rom and with the same kernel with the touchscreen feature I'have not this issue and I'm not the only one where all is fine. I use the same kernel like you I presume (the b45) why I have not this issue or other users :confused:

Wich rom you use? wich themes / mods? Clean or dirty flash? In which circumstances exactly it appears? In Francisco's thread I have not read much feedback on it...

Maybe you use all the same rom with the same issue :p:D

Check your themes / mods or known issue from your rom.

I don't think the kernel can be responsible... I just made a few tests with the pulldown notification (after unlocking), all is fine. And since I use _motley kernel I've never had a problem like this.

Matr1x kernel also use the touchscreen stuff and there is no issue reported...

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

I'm not sure of the technical details, and I haven't had it since b44. It could be kernel though, because the change log for b44 mentions clearing up touch screen issues.

I'm on total stock, with no modifications :)
[Nexus 4 Original Android Development] karanrajpal14:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Well I'm on stock kernel now. Will test for a few hours. Then flash motley and check again. I've been on motley since I rooted. Never got any problems with it! Best kernel ever!
[Nexus 4 Original Android Development] nextelbuddy:
thanks!

I am on Kernel b44 now and there is no INIT.D in /system/etc

so i made one and gave it all permissions

unzipped the zip file

I then copied over the script halfbreed into my new init.d folder and gave it all permissions as well.

i then set my trickster to set on boot and performed a reboot.

the device boots up now and it "looks" different but I cant be positive... i go into trickster and it still shows UNNAMED in the color settings.

is that normal? do i just trust that it did run properly?
[Nexus 4 Original Android Development] Remoteconcern:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Trickster setting colours on boot will overwrite the scripts values I think. Also, what ROM are you on? I'm on stock, and have never been able to get init.d working with motley kernel
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Hmm seems high for wake locks?
[Nexus 4 Original Android Development] ctfrommn:
Thats only 1 hr worth of data.....let everything settle some. Let it sit overnight and go through a full charge/discharge cycle before making any judgments.
[Nexus 4 Original Android Development] thracemerin:
PowerManagerService is userspace apps, check what apps are keeping your phone awake.
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

I know it isnt the kernel, i saw a major drain last night wanted to start figuring out what was causing it.

Is better battery stats a good app to see that? Xda using 15% of my battery?! Really... Let's see if reinstall of it helps.
[Nexus 4 Original Android Development] thracemerin:
The break down of what apps are holding wakelocks should be in the Partial Wakelock screen.
[Nexus 4 Original Android Development] chrone:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Try not to set trickster mod set on boot, init.d runs first then get overwritten by trickster mod settings if it's set on boot.

Once you boot with the init.d hafbreed preset, or run it in terminal, open trickster and see the display color setting. You need to save each color and gamma profile. Once it's changed, trickster will detect as unnamed profile.w

I'm on stock rom. Have to create the init.d folder and change its permission and all the scripts permissions too to 755 (rwx-rx-x).

Also don't forget to change text editor line terminator or notepad++ EOL convertion set to Linux/Unix/OSX format.

Sent from my Nexus 4
[Nexus 4 Original Android Development] patrickdo:
b44 is causing the top ~100 pixels of my screen to be erratically responsive. I've since switched back to b40 which has resolved my issue.
[Nexus 4 Original Android Development] magestic1995:
Interesting not having any issues on my phone currently
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Me too, it's the ts patches. Specially when you first power the device.
[Nexus 4 Original Android Development] nextelbuddy:
I set the proper permissions on the init.d folder and the scripts and even uninstalled trickster to remove the possibility that it could be conflicting with the script yet i see no change in my screen colors with or with out the script on Motley kernel 24 or 44

I guess i'm not doing something right.

i tried half breed, contrasty and bright and all 3 scripts have the screen looking the same for me.
[Nexus 4 Original Android Development] Kocai:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Try running the script via terminal.
[Nexus 4 Original Android Development] chrone:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Have you installed busybox by stericson the normal installation way?

Sent from my Nexus 4
[Nexus 4 Original Android Development] karanrajpal14:
Tested. Issue happens when i'm on motley b44.. reverting back to b40 to check.. i can just flas over 44 right? Or do i have to flash 37 again?
[Nexus 4 Original Android Development] mko000:
Yes.
[Nexus 4 Original Android Development] :
Hi _motley,

Sometimes the vibrations of the software buttons in the navbar are weird: sometimes strong and sometimes less stronger even with the vibration control is settled to 100 (sometimes it happens also with the keyboard and long press on the homescreen) and without undervolting.

It seems Morfic found the solution (link to his thread HERE).

Is this this commit on Bitbucket? -> https://bitbucket.org/morfic/trinity_four/commits/94538b2475f84711038d6fbe2e39a777f9e8c56a (sorry if I'm wrong, I'm not sure that is the right commit :D).

Can you take a look please?

Thanks in advance ;)

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

Quick update on my ui micro stuttering on window/transition/animator scale animations issues when opening and swiping through app center/drawer, and opening and switching between apps:

1. Enabled the disable hw overlays from developer options. Fixed the issues all the time. Stock and Motley kernels. Same 3G battery life. :)

2. Enabled the mdp_vsync_clk. Didn't fix the issues after several reboots. Stock and Motley kernel. Same 3G battery life. :confused:

3. Flash Google factory image reset and don't even bother to enable developer options. No micro stuttering even after several reboots and cache wiped from stock recovery. Stock kernel. Same 3G battery life.

4. Use superuser by koush instead supersu by Chainfire. Stock rom, rooted, cwm recovery, easter egg and developer options enabled. The issues are still there but much less occur. Rough count so far is only having 1 micro stuttering out of 15 tries entering app center after screen turned off occurs. I also noticed wiping cache and dalvik-cache reduce the chance of micro stuttering, but it kept occurred on next reboot. Stock kernel. Same 3G battery life.

Though the micro stuttering sometimes occurs randomly, it takes the same amount of time to open and switch between apps. So i was not complaining about lack of performance here, only the perceived speed/lag due to random micro stuttering in ui animations. Perhaps i'm expecting too much from this beast. Hehe :p

Will report back later once i'm done testing with both stock and motley kernel. Keep on cooking, motley! :thumbup:

Sent from my Nexus 4
[Nexus 4 Original Android Development] Remoteconcern:
Definitely. I keep having to reboot to get the use of my status bar back.
[Nexus 4 Original Android Development] mundixx:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Thanks! Option #1 seems to be the best and quickest. :D

Sent from my AOSPA Nexus 4
[Nexus 4 Original Android Development] karanrajpal14:
Well, i've been on build 40 for the past few hours and the issue seems to be gone. Now i'm sure it's the kernel. Specifically the ts patches. @motley can you please look into this?
[Nexus 4 Original Android Development] guapinoy:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Thanks for the great update to the kernel. No real issues with rasbean and b44. Great battery life with light to moderate use, about 12 hours off WiFi.
[Nexus 4 Original Android Development] nextelbuddy:
I do have android terminal app installed... How would I run the script via the terminal?

Yes busy box is installed and I opened it and chose to install and it said it installed successfully.

is there a different way to do it?
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

He knows that it is, he mentioned it in reply when I posted about it when b42 was out. Franco merged it into his kernel, that's when I first started having those problems.
[Nexus 4 Original Android Development] chrone:
oh ok, never mind what i posted before regarding busybox, i should have known you have to have busybox installed to run trickstermod. lol :D

to run the script from terminal:

copy the script to your sdcard

from terminal go to type su to log in as superuser mode, and go to /sdcard by typing: cd /sdcard

type "ls -la | grep thescriptfilename" to check if you are in the right path

or type "pwd" to see what your current path is

cd /otherpath/here/if/you/are/in/the/wrong/path

once you're in the right path just type "sh scriptnamehere"

if you might turn off/on the screen or invoke the script to refresh the screen as posted as #2 post here. but it might do a soft reboot, forgot on what kernel build i got rebooted by invoking the refresh screen command line. hehe

echo 1 > /sys/devices/platform/mipi_lgit.1537/refresh_screen

hope this helps. :)

out of topic, just for fun:
[Nexus 4 Original Android Development] _motley:
Tempted to pull the franco touch interface out, but please let me know a couple things if you have this issue. I still have never had the issue, so I find it strange that only a few have the issue.

1) ROM you are using?

2) Are you using the sysfs interface to adjust touch response? (an init.d script in place etc.)

3) Are you using Touch Control?

Thx!
[Nexus 4 Original Android Development] IAmAN00bie:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

I just wanted to say I've had no issues with the touch screen, even after making adjustments using Franco's interface. I don't know what is causing it for others, but if possible please leave it in as an option for those of us who like using it!