yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] swaggerwocky:
After testing for a few days, this looks to have solved the SIP packet issue. Thanks again for adding it! B)

I've posted a link to this kernel's OP in the CSipSimple thread relating to this issue, hopefully anyone else who has had this problem can share their results. I'll keep this thread updated with their findings, if any.
[Nexus 4 Original Android Development] z3r0_x:
Franco seems to have fixed the WiFi drop issues in his yet to be released r97 kernel - could you have a look at this patch too?
[Nexus 4 Original Android Development] _motley:
Yeah, when I saw this particular link, I didn't hold many reservations in disabling SIP in the connection tracker.

http://source.android.com/tech/datausage/kernel-changes.html

Great to hear it is helping solve problems! Thanks for testing and stopping back to let us know.
[Nexus 4 Original Android Development] chrone:
dear _motley,

i've been meaning to ask, are thracemerin's msm_hsic_host patches included in _motley kernel? i found thracemerin's work has the smallest msm_hsic_host wakelock without data and wifi drop. kudos to all devs and to thracemerin for cherry picking the caf patches. :)

https://github.com/thracemerin/Mako/commits/jb-hsic

http://xdaforums.com/showthread.php?t=2102986

btw, b44 works flawlessly so far. your init.d support out of the box even on stock rom makes me always come back to use this kernel. oncei use it, i can't live without it. hehe :good:
[Nexus 4 Original Android Development] thracemerin:
I believe he pulled my patches at exp-v4, but there isn't a lot of difference between that and where I am now.
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Thanks motley! B44 is great, very fast, battery life is very good thus far, and no issues with touchscreen!!!
[Nexus 4 Original Android Development] mko000:
Sounds awesome! I hope it works.

Here are some posts from franco's thread regarding the wifi fix:

http://xdaforums.com/showthread.php?p=38738796#post38738796

http://xdaforums.com/showthread.php?p=38747860#post38747860

http://xdaforums.com/showthread.php?p=38760642#post38760642

http://xdaforums.com/showthread.php?p=38761028#post38761028

http://xdaforums.com/showthread.php?p=38768727#post38768727

http://xdaforums.com/showthread.php?p=38774570#post38774570

Thanks in advance motley!

EDIT: More and more people are reporting that the fix didn't really work for them...:(
[Nexus 4 Original Android Development] thracemerin:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

My latest kernel has it too :D
[Nexus 4 Original Android Development] franciscofranco:
Oi I didn't fix anything, I just merged Qualcomms patch, I did 0 coding ;) Kudos to the qualcomm engineers + help from Google, the patch fixed all the **** I had with Wi-Fi.
[Nexus 4 Original Android Development] Remoteconcern:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Oh wow. Can't wait for that patch, that's my most irritating and probably only issue with this phone. Have to turn the screen on constantly to make sure I'm not missing emails!

Thanks Franco and Qualcomm, and hopefully soon motley :)
[Nexus 4 Original Android Development] :
Hi,

I'am currently testing the touchscreen feature, I tested different random values :D

Does someone could test them?:

I feel the screen more responsive but maybe it's just only the placebo effect :D, So if you can test and report...

Here the init.d script: http://www.multiupload.nl/RC2EGGKR8A

Thanks :)
[Nexus 4 Original Android Development] AcmE85:
I am testing your settings right now. So far I can't tell if it is any better then stock or your previous settings.
[Nexus 4 Original Android Development] _motley:
Thanks guys, good find franco!

Here is b45 (b44 with this wifi patch merged (wlan: Fix for ARP offload issue). Let me know how it works!

View attachment motley_anykernel_422_nexus_4_build_45.zip

Also, you must:

1) edit /system/etc/wifi/WCNSS_qcom_cfg.ini (may have to change permissions to edit)

McastBcastFilter=0

hostArpOffload=1

However, we are missing gEnableActiveModeOffload=1, not sure if it can be added to this file or not. Need to study the source to see when that was added.

2) Reboot

Reference:

https://www.codeaurora.org/gitweb/e...;hpb=2214143009d76d137b5d37aead4d829e38c5c57c
[Nexus 4 Original Android Development] thracemerin:
gEnableActiveModeOffload=1 first appears in this patch: https://www.codeaurora.org/gitweb/e...it;h=9f22e663fc171ac32c63c544a9d157cfa0391cbf probably not necessary if you aren't going to implement the entire thing.
[Nexus 4 Original Android Development] :
Re,

Thanks _motley for the b45 ;)

Here the modified file in attachment for the WI-FI (for lazy people :p :D) , just replace it with the old one and set the correct permission (see after). Remove the .pdf extension before (XDA don't let me to upload the original file).

So I have not added gEnableActiveModeOffload=1...

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

Great. I'll give it a shot now. Hopefully this works. And thanks Viking.
[Nexus 4 Original Android Development] :
Re,

In case it would be necessary, second attachment there is the file like above but with the line gEnableActiveModeOffload=1 added. Don't forget to remove the .pdf extension before replacing the file.

;)
[Nexus 4 Original Android Development] chrone:
whoa it's b45 already? :good:

btw, guys, could you shed me some lights on these following codes:

#enable gpu vsync
echo 1 > /d/clk/mdp_vsync_clk/enable

#set net.hostname
setprop net.hostname chrone

will it hurt to set the vsync enabled? i think it fixes my micro stuttering when entering app center, opening or switching between apps. i'll test further for a day more.

i used to see micro stuttering on stock rom either with stock google factory boot image kernel or any other custom kernels (franco up to r94, faux, thracemerin up to v6.1 - latest wifi patch seems fixes the micro stuttering, motley, and harsh) especially on 3g network only, funny thing is the micro stuttering reduced to minimum when using WiFi.
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Vsync is enabled by default as part of project butter, and there is no valid reason to turn it off.

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

Mine by defaut is set to 0 :confused:, I mean the path /d/clk/mdp_vsync_clk/enable the value is 0 .
[Nexus 4 Original Android Development] trismegistos:
mine is on 0, too :eek:
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Well as per motley a page back, vsync is still on, and in old gpu benchmarks it's capped at 58ish, thus it's definitely still on, so I have no clue what's with that junk, it could easily just be another placebo.

Sent via Nexus 4
[Nexus 4 Original Android Development] _motley:
Yeah, since we don't build the wlan binaries with the kernel, we would need to know if Google updated them in 4.2.2 or not. If they did, then it might work if you turn that option on, granted there may be other kernel patches that would also need to be in place. So many layers that have to be in sync...

Not convinced this change is working, but it is worth a try.
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Just had that swiping thing happen again, to where when you hit the power key the touchscreen acts as if you're touching the top of it. On b44.
[Nexus 4 Original Android Development] trismegistos:
good to read that. i can confirm that 100%
[Nexus 4 Original Android Development] thracemerin:
Are the binaries not in here? https://www.codeaurora.org/gitweb/external/wlan/?p=prima.git;a=tree;f=firmware_bin;hb=HEAD maybe I'm confused.
[Nexus 4 Original Android Development] chrone:
+1, checked with glbenchmark though the mpd_vsync_clk was disabled by default, glbenchmark still reported it was vsync limited on top right of the benchmark screen.

i can only find this one documentation back from year 2010, lol:

https://www.codeaurora.org/gitweb/q...in;h=5a952310b7ff57f1bfa83d44e5ce8aa97f4013fc

so yeah it's off for a reason. sorry for the confusing. i'll try to stick with this enabled to see how the battery consumption goes for another day or two. love the smoothness as it was coming from ics 4.0.4 to jb 4.1.1 on gnex. :)

are you experiencing micro stuttering too even on all stock google factory image reset 4.2.2?

i'm on 212K, cpu binning fast, lcd_maker_id=primary.
[Nexus 4 Original Android Development] trismegistos:
yes i can see it on EVERY ROM out there, BUT i am pretty sure that it depends on what app i am using. gmail, xda app for example always stutter when opening it. google+ or currents is always smooth as hell. so i think it really depends on how the app it self is coded...
[Nexus 4 Original Android Development] chrone:
oh thanks god! :) i thought my eyes are too paranoid.

from the first time i booted up this nexus 4, i saw this micro stuttering though it had twice or quad the hardware advantages of galaxy nexus. even on my old galaxy nexus the animations are way smoother. :/
[Nexus 4 Original Android Development] trismegistos:
AW: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

I have the gnex too.I think they are the same regarding the smoothness thing. But I always get a little bit angry when I see the micro stuttering on my device
[Nexus 4 Original Android Development] Remoteconcern:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

I still get the grey-->blue wifi icon + notification flood on b45 with recommended config change. Unfortunately, it might be that this is only a partial fix from code aurora? I don't have the extra line in my config file.

Thanks anyway motley.
[Nexus 4 Original Android Development] thracemerin:
Yeah, I don't think it's working as intended, I think there may be more needed to get it to work, like a full bump to the latest Prima.
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

I have compared the N4 to two gnexui, one running stock 4.2.2 and the other on cm10.1, and the N4 is so much smoother it's not even comparable o_O

Sent via Nexus 4
[Nexus 4 Original Android Development] trismegistos:
the overall performance is muh better on the nexus 4 that is right, but opening and closing apps is not 100% smooth on the nexus 4 (as i said not on all apps). that is not a hardware problem, it is an app-coding problem.
[Nexus 4 Original Android Development] Remoteconcern:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Agreed. My galaxy nexus is horrible in comparison, especially after 4.2.2.
[Nexus 4 Original Android Development] chrone:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Does this happen with swipe 2 wake enabled?

Couldn't agree more. I sometimes a bit disappointed when trying to make nexus popular in my office and someone with ip4s show off her animation transition smoothness. Hehe

Totally agree the smoothness when scrolling long on contact list or gallery. I only found the micro stuttering when the transition animation kicks in when opening home screen after long idle or sometimes when switching apps.

Perhaps i got different batch here in indonesia, that's why i took glbenchmark, vellamo, and androbench just to compare with legitimate reviews that i don't get bad chip or so on. My boss' nexus 4 still running stock has this issues too, and it's transition animation feels smoother on my previous galaxy nexus. We both purchased the same date when the pre order opened last january through different stores. :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] _motley:
Yep, those are it. Size matches with our 4.2.2 ROMs. Lot's of recent changes. It is hard to know if these kernel changes are release ready or not. It would be interesting to merge them all in and see if it builds (full duplicate of /CORE/*

https://www.codeaurora.org/gitweb/external/wlan/?p=prima.git;a=tags

No problem. Are you guys running all three updated settings in the .ini file, or just the two that were there already?
[Nexus 4 Original Android Development] Remoteconcern:
Re: [KERNEL][Mar 4][b44] _motley kernel for the N4 (fix touch issue in last beta)

Just the two. I didn't manually add the extra line.
[Nexus 4 Original Android Development] thracemerin:
We could in theory just pull the entire codeaurora prima git and replace /drivers/staging/prima and see what happens, worst case it doesn't build.

the 3rd parameter isn't checked anywhere in the current setup, you would have to merge the patch i linked earlier for it to do anything but take up additional space in the .ini file.
[Nexus 4 Original Android Development] _motley:
Thanks, I hadn't compared our source yet to see where we are at in comparison to when that setting came into play. I think we are still 3 months back with prima merges:( Sure would be nice to knock off the notify delay.

I will also try some of your other hsic/usb patches you added since my last merge as they seem to be working for you. Someone PM'ed me and suggested a few patches. I will see if you have those included in your set as well.
[Nexus 4 Original Android Development] thracemerin:
I just replaced my drivers/staging/prima with the master branch from codeaurora, I'll let you know if it builds. If it does I'll try to put together an update including the binaries that people can give a go. I'm building it against google stock so we eliminate any other potential issues.

The patches I merged on hsic lately were fixes that Harsh and franco picked from CAF, there seems to be no adverse effect, though the benefit is marginal at best, I can't see the harm in keeping them.

Edit: well, the kernel still builds with the CAF version of prima. I'll do a little testing.
[Nexus 4 Original Android Development] thracemerin:
Well, good news and bad news.

Good news: updating prima seems to have solved the delayed notification issue (possibly because the phone stays awake due to the bad news)

Bad news: it added a new wakelock called qcom_rx_wakelock which is absolutely destroying my battery life on a noisy WiFi network.

Overall, I wouldn't recommend this, we're talking multiple % drop per hour while on my work WiFi. It might be better on a quieter home WiFi network, but since the majority of WiFi networks with windows machines on them are noisy this solution will result in much much worse battery life.
[Nexus 4 Original Android Development] morfic:
I agree, in theory it seems bad, but then again, PowerHAL has been crying about not being able to write to sysfs for some time now all over JB devices and all without any penalty.

I choose to let it cry so i don't have to replace power.devicename.so in roms.

Works the same here, no binaries are removed or deleted, no libraries replaced.

The boot.img is the only thing that changes.

Talking to cayniarb tonight, i'll be adopting his modified anykernel, which unpackes the ramdisk, modifies it and repacks and rejoins with new kernel, i actually fear that this would be more confusing, since the term anykernel would then be misunderstood as not modifying the ramdisk when it still is.

The convenience there is that there is only one build for all roms, instead of me splitting ramdisks, modifying them and joining at build time the various ramdisks (right now only 2, but I'm sure that's going to change soon)

What i mean about PowerHAL crying about not being able to write to sysfs is that apps in an effort to get around PowerHAL set the cpufreq files 444 after changing frequencies.

So PowerHAL will be chatty if you like it or not.

There are of course kernels who come with a modified PowerHAL. So you have that too.

And before you ask people to create new ways of reversal other than the existing proper ways of restoring to rom defaults, think of the amount of variations you would have to cover, what if they run my reversal after they tried a few others, what if they run a stock reversal on a custom rom because they don't pay attention what it is for.

If there aren't constantly new ways to reverse things, there will be less chances for things to go wrong.

People could even make a backup of their kernel and restore the backup, i mean that is what those recovery features are for, again, not a new method.

And FYI, i really suggest you try running 384/1026 on a kernel that sticks to that policy (after you made sure 1026 still uses the higher L2 index, else it would feel like poo)
[Nexus 4 Original Android Development] morfic:
A standard way? How would they get their intellibuzz words in?

Crazy talk!

;)
[Nexus 4 Original Android Development] Imppy:
Hey anyone know what the default stock voltages are?
[Nexus 4 Original Android Development] Locksmith81:
Flashed over PA beta 7 and hung on the goggle splash screen.... Going to try again

I'm using Franco 9.... will try again
[Nexus 4 Original Android Development] meangreenie:
Hi, been reading through the thread and this kernel sounds like the one i want to try.

Would just like to know if the gpu clock speeds have been kept to default and not clocked up 487.. i feel 487 just heats up quicker and will make the phone thermal throttle quicker for not much initial performance gain.

If it is clocked up to 487, can I reset the max gpu clock speed back to 400 easily?
[Nexus 4 Original Android Development] _motley:
I have now provided my own reset kernel on the OP. If this is an AOSP based ROM, then it should help. I have also put some other instructions there that may help as well for other ROMs.

You could reset the stock kernel and take a look.

Interesting stuff...agreed on most. I need to come back and read again when I am not so rushed. I hate having communication chatter failing that doesn't provide any purpose, but I do understand that it may not have too bad of consequences. At least when I have an app doing stunting the PowerHAL, I can choose to do this or not to do this. I would rather just build a PowerHAL and shut it up LOL.

The new method for Anykernel sounds interesting. We used some stuff on the galaxy tab like this that went in and modified init scripts etc. (just sed). Of course we all will deal with these contamination issues when users are coming back and forth trying things out and often people look at us as doing something wrong in our builds when really it is contamination and them not understanding how things work. They expect it always to be the same from device to device, but there are always variations and exceptions that make it tough. What is easy for some to sort out, is next to impossible for others. I don't really expect much, just for each dev to give a means or instructions for their customers to go back easily to where they came from. Restoring a full backup from recovery is great.

Hopefully the reset zip I just posted that restores the stock PowerHAL, thermald, mpdecision, ramdisk and kernel will help keep things simple for people moving back and forth between kernels, at least for AOSP based ROMs. Other devs are welcome to use it.
[Nexus 4 Original Android Development] _motley:
No GPU overclock in this kernel, it is stock.
[Nexus 4 Original Android Development] _motley:
Yeah, I don't mean anything complicated as I stated above. It is kinda funny...guy has Trinity kernel or Franco kernel. Flashes motley kernel and it is running slow due to some unknown issue that shouldn't happen if it is all stock. Has to flash faux123 kernel reset zip and then flash motley kernel to make it work correctly. What a wicked web we all live in LOL.

Again, everyone can find a stock reset zip in the OP. I hate to repeat, but I want everyone to know that it is there so we don't have to visit this over and over as we move forward.
[Nexus 4 Original Android Development] aventu:
really nice cpu freq with interactive!
[Nexus 4 Original Android Development] Cyb3rGlitch:
I'm not sure having a default colour 'tweak' is a good idea. The reason people's devices have a yellowish tinge is because the adhesive hasn't set 100%. My display is perfect, so this change is not helping.
[Nexus 4 Original Android Development] 0.0:
Not quite true...I flashed a kernel by another dev a while back, and it fixed my yellowish screen issues instantly :D. So that color tweak may help

Sent from my Nexus 4

---------- Post added at 02:03 AM ---------- Previous post was at 01:07 AM ----------

ah, i see. as long as it will get added back in :fingers-crossed:, that'll be good. i dont want it in for bragging rights, but just for intensive stuff that can happen to my phone :)

edit: not working on cm rom
[Nexus 4 Original Android Development] MatAuc12:
The "glue effect" is not the only reason for yellow tint. It also usually is an area of the screen. A yellow tint covering the whole screen is usually the color preset.
[Nexus 4 Original Android Development] boykioy:
+1 for the color patch.
[Nexus 4 Original Android Development] Cyb3rGlitch:
That's not the point. By changing the defaults to fix some devices, you're affecting others. It should be an opt-in feature.
[Nexus 4 Original Android Development] _motley:
One of the things reported by many after the device shipped was that the colors were washed out and had a very slight yellowish-greenish tint (not to be confused with yellowing of part of the screen edges etc. due to manufacturing defect). This patch was aimed at the latter issue (tint) in a very subtle way.

I appreciate your point of view, however please understand that the color change is very subtle. So much so that most will not even recognize it. I could have easily lived with it the way it was, but testing shows it looks better to multiple sets of eyes on multiple N4 devices. It would have been a nice psychological experiment to release without telling everyone, but I wouldn't do that LOL.

The RGB tweaks were tested on three different devices with several combinations. None of these devices had an uneven tint of any kind (manufacturer defect), i.e. the screens were considered to be working fine and looked identical to the naked eye when set to the highest and lowest brightness levels.

We used 4 pictures (woman's face, grassy meadow scene, and the dark gray default background in ES file explorer, and another grayish background pic that showed the tint issue as compared to other devices). We narrowed it down like they do at the eye doctor (choice 1 or choice 2, choice 2 or choice 3 etc.). This was all done via ADB so you can see the picture change on the phone while you are looking at it.

When we made our final decision between tweaks, we then went back one more time and compared the chosen tweak with stock to make sure that it really did show an improvement (choice 1 or choice 2)

Just wanted to share my 2 cents on this. Feedback is

always

welcome. I typically let the masses vote on whether something works or not. It looks like two others have voted "yes" since I posted this last build, so that makes confirmation on 5 devices now that would vote "yes". Its hard to argue with this, but we'll see what the others say as testing continues. Having an app to adjust color is cool for some, but my goal is to have a kernel that works well out of the box without needing an extra app to control it (and running in the background) if you don't really want to deal with it..
[Nexus 4 Original Android Development] _motley:
Please let me know which kernel you were using with CM and see my notes in the OP about a reset. Unless CM recently changed to a new ramdisk/kernel combo that is incompatible with my AnyKernel install (doesn't use mpdecision, thermald, PowerHAL etc.), then there shouldn't be a problem. I would dirty flash your same CM zip for your current version (should lose any data, apps, or settings) and then flash my AnyKernel zip and see if it fixes it.