yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] thracemerin:
It looks like they made an attempt to fix the problem, but without sources I don't know exactly what they did so we'll have to wait for AOSP sources to confirm if they did it successfully or not but from what I'm reading it's looking very positive.

There aren't usually enhancements you can see when you update the bootloader, but its usually a good idea to run the matching bootloader with your ROM version, so if you use the 4.3 ROM you should update, if you plan to stay on 4.2.2 then you should stick with the 4.2.2 bootloader.
[Nexus 4 Android Development] markd0wn:
I'm optimistic so far. Up until now, the wake-up-device-and-get-tons-of-notifications-at-once scenario didn't happen at all for me with 4.3, but I haven't done enough testing and had several hours of being outdoors with mobile data only so I'm still not calling it fixed.

I also made another test and left the screen off and unplugged for over 30 minutes and then told a friend to send a message via WhatsApp. He told me 'done' and nothing, I was already imagining reporting here that the usual familiar delay is still happening, but the message arrived about 65 seconds after he sent it. Not perfect, not instant, but definitely better than how it was on 4.2.2. Also, this is with Wi-Fi optimization enabled, maybe disabling it would make notifications arrive even quicker but I haven't tested that yet. I'm also not using PNF right now so the heartbeat interval is set to default at 15 minutes. After receiving his message, I went to the gtalk service monitor and there were still 12 minutes left until the next heartbeat (wanted to make sure that's not the cause for receiving the message).

What I am noticing though is significantly better battery life compared to 4.2.2 with gEnableSuspend=2 (that was using CM though and not stock).
[Nexus 4 Android Development] thracemerin:
The delay could be a WhatsApp issue too, I know that sometimes when I email myself something on GMail it takes a while to arrive.
[Nexus 4 Android Development] markd0wn:
Just made a gmail test. Left screen off/unplugged/optimization on just like before, and screen was off from shortly before you made the post, and until just now - over 40 minutes of screen off. Sent a mail from my computer and counted the seconds from the moment it said 'message sent'. 6 seconds later the notification sound arrived.
[Nexus 4 Android Development] oSandmaNo:
Wasn't the same case for me on 4.3.I sent a GTalk message and notification didn't arrive for a while. And this was when screen was off for five minutes
[Nexus 4 Android Development] renna1992:
I also have to report something.

Flashed the leaked 4.3 rom and new radio and bootloader. Tried several times pinging my device when asleep more than 10 minutes, even hours and ALWAYS worked. Whatsapp messages seem to work too (haven't had that close a look but it seems that everything is fine). If this turns out to be true i'm very happy with the new update :)
[Nexus 4 Android Development] thenessus:
Does this affect GSM notification delays or just WIFI? I don't care for WIFI cause I never use it.
[Nexus 4 Android Development] oSandmaNo:
Just wifi
[Nexus 4 Android Development] thracemerin:
GSM notification delay is almost certainly an issue with your providers network and not the N4.
[Nexus 4 Android Development] thenessus:
Why do people keep denying this problem exists?

1) Everytime I unlock my phone the signal bar is full but grey, until a few seconds after and it becomes blue again and bam, I get all the notifications at once.

2) Does not happen on another android phone I have and my gf has.

3) it's a known issue. GOOGLE IT.

jesus effing christ.
[Nexus 4 Android Development] thracemerin:
Not denying anything, I believe you believe you have a problem, I also believe that you believe that it's specific to this phone, what I'm saying is that it's your provider, not the Nexus 4.
[Nexus 4 Android Development] markd0wn:
[MENTION=4303511]thracemerin[/MENTION], I've asked a similar question before regarding getting files directly from CAF, but here's a revised question...

If I miss CM and custom kernels, both obviously based on 4.2.2, but I want the 4.3 Wi-Fi behavior, and I:

Replace CM's /system/vendor/firmware/wlan/prima/ folder with 4.3's

Replace CM's /system/etc/wifi/ folder with 4.3's

Will that also result in not having Wi-Fi at all, or will that work and bring 4.3's Wi-Fi to 4.2.2?

It should be noted that CM's latest nightly only has 1 file in /system/vendor/firmware/wlan/prima/, and that's WCNSS_cfg.dat. The same folder on 4.3's build has WCNSS_qcom_cfg.ini and WCNSS_qcom_wlan_nv.bin in the same folder as well.

Also, CM's /system/etc/wifi/ has 3 files:

WCNSS_qcom_cfg.ini, WCNSS_qcom_wlan_nv.bin and wpa_supplicant.conf

While 4.3's leak has 5 files in that same folder: p2p_supplicant_overlay.conf, WCNSS_qcom_cfg.ini, WCNSS_qcom_wlan_nv.bin, wpa_supplicant.conf and wpa_supplicant_overlay.conf.

By the way, if it does work, maybe a v7 fix zip that does just that should be considered until 4.3 is officially out/pushed to AOSP/merged to custom ROMs etc, I'm sure many would find it useful. Again, this is assuming this method will even work. I don't mind trying but if you know for a fact that it won't work I'd rather avoid the adventure :)

******* EDIT:

Did exactly as I suggested, replaced CM's folders with the ones in 4.3 leak. Made a full wipe, but still using 4.3's bootloader and radio (probably doesn't matter though). On initial setup page, it got stock at 'Turning Wi-Fi on...' and couldn't find any networks. Guess it's a no-go...
[Nexus 4 Android Development] thracemerin:
Yeah, I would bet it requires the kernel side changes, you might be able to pull the kernel and firmware files and pack them for 4.2.2 and maybe it would work, but I can't guarantee that it will.
[Nexus 4 Android Development] markd0wn:
I'm up for trying that, have a nandroid for the current 4.3 setup anyway which I restored after the first attempt didn't work. The only problem is I'm not sure how to do that. If it's not too complicated and you're up for writing quick instructions, I could try. I have the unpacked 4.3 folder and unpacked CM folder handy and untouched, and 4.3 installed and rooted.

EDIT: I took a guess. Wiped everything again, flashed the same modified CM with 4.3 Wi-Fi files I made earlier, but this time, immediately after flashing, I restored the boot partition *only* from the 4.3 nandroid backup, thinking it would then have 4.3's kernel and might work. Result was phone not booting at all so restored nandroid again, guess that's not how to do it :silly:
[Nexus 4 Android Development] thracemerin:
Let me see if I can pack you an anykernel version, no guarantees that it will do anything but completely screw up your phone so you have to restore again, but its worth a shot.
[Nexus 4 Android Development] markd0wn:
Thanks, as long as there's no permanent damage and the long-holding power button thingy (and then entering recovery) works, I don't mind trying stuff.
[Nexus 4 Android Development] jakejm79:
@ theracemerin, now that you have conducted tests and received plenty of feedback, will you be submitting these patches to CM? Or are you still waiting for additional feedback/testing.
[Nexus 4 Android Development] thracemerin:
I was sort of guessing that 4.2.2 was going to hit within days, I'm still of that mind, if by the end of this week there is no concrete evidence that 4.2.2 is coming soon, I will reach out to the CM device maintainers for mako to discuss what to do.
[Nexus 4 Android Development] jakejm79:
Awesome, thanks for the good work.
[Nexus 4 Android Development] NardVa:
Re: [Kernel][GPL][anykernel][WIP] msm_hsic_host wakelock fix

I have CM 10.1 from 1/13/13. Can I install this kernel without updating CM?
[Nexus 4 Android Development] thracemerin:
Yeah, should be fine. Use the anykernel version.
[Nexus 4 Android Development] xmecx:
Im Using this Kernel with the Stock Rom. I have come from Franco R34 and it had issues with data dropping. This Kernel seems to fix the battery drain on 3G at idle and actually feels a little quicker than Franco while in use.

:cyclops:
[Nexus 4 Android Development] chrone:
great work devs! and thanks for supplying the stock kernel patches. :)
[Nexus 4 Android Development] mopss:
Very often, when I turn off the WiFi, I do not automatically GPRS (EDGE, 3G). This kernel solves this problem?

Thx.
[Nexus 4 Android Development] jeffmhasty:
Great work. It's really good to see these patches applied and tested on the stock kernel. Which branch are you using for it? I'm assuming it's jb-exp-hsicfix, but jb-exp also looks like it has some of the same patches.
[Nexus 4 Android Development] thracemerin:
jb-exp-hsicfix is the branch this is built from, jb-exp was an initial test I did that reduced the wakelock on WiFi but not as much on 3G, I split them so that I could keep track.
[Nexus 4 Android Development] alphar:
Re: [Kernel][GPL][anykernel][WIP] msm_hsic_host wakelock fix

Great work!
[Nexus 4 Android Development] peterperfect:
Re: [Kernel][GPL][anykernel][WIP] msm_hsic_host wakelock fix

Hey theracemerin, just lined up your kernel into my cm builds. :)

How do you feel about poking a little bit with the kernel? Like adding new linaro routines, updated interactive governor etc. I think would be nice to add just real upstream stuff like that to keep it next to stock without all the bloat from other kernels, without the need of apps to control stuff etc even cause cm already has interface to change the basics.

Just my two cents. Cheers.
[Nexus 4 Android Development] jeffmhasty:
Re: [Kernel][GPL][anykernel][WIP] msm_hsic_host wakelock fix

Do you know what patches were causing the 3g data drops? I just experienced one with my own kernel

I merged commits a3483db8c4 - 636fc1d4c6 with AOSP android-msm-3.4-jb-mr1. Basically the only difference between my build and yours would be that mine is missing the commits for prima: release v3.2.1.11h and v3.2.1.13
[Nexus 4 Android Development] thracemerin:
This particular project was mainly to keep it bone stock in order to ensure that the problem was actually fixed, since sometimes introducing too many variables makes it difficult to track the problem down if it doesn't actually work. I'd be open to another project that includes some additional tweaks, etc...

That should cover you, the prima driver update should only affect WiFi. What sort of data drops are you experiencing?
[Nexus 4 Android Development] peterperfect:
Ok, thanks! Remember to link us if you start this other project. It would be good to have a close to stock tweaked plug and play kernel.

On what is related to this thread, my drops stopped. The most noticeable one was after waking up device while one 3G (signal bars went gray)

Cheers!
[Nexus 4 Android Development] jeffmhasty:
Re: [Kernel][GPL][anykernel][WIP] msm_hsic_host wakelock fix

I booted the kernel this morning at home and was connected to WiFi. When I got to work the phone said 3g, but the signal strength was grey instead of blue. I couldn't get the data connection back by toggling airplane mode or toggling data. I ended up rebooting my phone (and losing the kernel until I get home)
[Nexus 4 Android Development] thracemerin:
Well, grey bars means no Google services connection not necessarily no data connection, you're sure that there was no data at all?
[Nexus 4 Android Development] jeffmhasty:
Re: [Kernel][GPL][anykernel][WIP] msm_hsic_host wakelock fix

I'm pretty sure I had no data at all... I tried a few different apps (twitter for one), but I don't think I tried anything in Chrome. It sounds like it must have been an isolated incident. I'll try to reproduce it later, but hopefully i wont be able to.
[Nexus 4 Android Development] NardVa:
Re: [Kernel][GPL][anykernel][WIP] msm_hsic_host wakelock fix

Stock kernel I get 3 hours screen time before the battery dies and on the modified kernel I get 3 hours screen time before the battery goes dead. Both cases is with HSPA+ on all day. It appears the only way to get more screen time is to stay on Wifi.
[Nexus 4 Android Development] chrone:
Re: [Kernel][GPL][anykernel][WIP] msm_hsic_host wakelock fix

Couldnt agree more. This bug on 3g is a dent in nexus 4 brand image. I get 4 hours screen time on 2g and minimal msm_hsic_host wakelock. :)

Sent from my Nexus 4
[Nexus 4 Android Development] thracemerin:
Its highly unlikely that it would brick your phone permanently, I'm certainly not going to edit the bootloader or anything dumb like that :D
[Nexus 4 Android Development] markd0wn:
Yeah I hope that upcoming anykernel is not hex-edited :laugh:
[Nexus 4 Android Development] thracemerin:
Here, since my N4 is still out of commission for the moment I can't test it, but the worst thing that could happen is that it won't boot (I suppose it could cause your phone to explode, but that's highly unlikely)
[Nexus 4 Android Development] markd0wn:
Great! Just to make sure, this means my test should be flashing a normal CM, not one I modified (since you already included the WiFi things), and then flash this anykernel version over it (and then optionally gapps), right?

Also, I assume this is basically like a full kernel with the 4.3 Wi-Fi, correct? As in, flashing custom 4.2.2 kernels and then flashing this would be redundant..
[Nexus 4 Android Development] thracemerin:
Yeah, just flash a ROM (and gapps if necessary), then this.
[Nexus 4 Android Development] markd0wn:
Looks like it's not booting, but it did 'react' differently than how it did when I tried restoring boot partition.

The screen was on but with a blank black screen, and it's like there's no display but it almost seemed like the phone did go through the initial start-up routine without me seeing it on screen (it 'flashed' one time, as in turned screen off and then on again with a blank-but-on-blacks). Also, when plugged in, the green notification LED turns on to let me know it's charged (the CM option) - this didn't happen before with my test.

This is just a guess and possibly not the reason - but I wonder if this is somehow related to the OpenGL changes. Since the kernel and system(4.2.2) don't match, maybe I'm not seeing anything (thinking that because almost all video players aren't working in 4.3 due to such an error).
[Nexus 4 Android Development] thracemerin:
Yeah, sounds like graphics drivers, gonna have to wait for 4.3 sources probably. We could keep trying to mix and match bits and pieces but the chances of finding the problem is low and there is an increased risk that we do something irreparable. The 4.3 sources should appear sometime next week, I think it would be better to wait until then.
[Nexus 4 Android Development] markd0wn:
Yeah I agree, it was worth a shot anyway. If we had to wait weeks or months I'd say lets test everything, but since we waited this long for a solution I guess we could wait a few more days :)
[Nexus 4 Android Development] zerohunk:
i am also facing data issue that when screen is turned off on data mode after 5-10mins approx the notifications get delayed to 5-10 mins ...is everyone else facing the problem too or i am the only one?? I bought my nex one week back..
[Nexus 4 Android Development] DenyDarko:
Google 4.3 Image: https://developers.google.com/android/nexus/images#occam

Binaries: https://developers.google.com/android/nexus/drivers#makojwr66v
[Nexus 4 Android Development] markd0wn:
Factory image page has JWR66V, yet Binaries page says "JWR66V and JSS15J". JSS15J is supposedly landing in AOSP. No idea regarding differences.

EDIT: android-4.3_r1 might be JWR66V while android-4.3_r2.1 is possibly JSS15J

EDIT2: AOSP pushing android-4.3_r0.9, android-4.3_r0.9.1, android-4.3_r1, android-4.3_r2 and android-4.3_r2.1. Maybe last three are JWR66N, JWR66V and newest (r2.1) is JSS15J. Just guessing.
[Nexus 4 Android Development] DenyDarko:
https://android.googlesource.com/device/lge/mako/+/android-4.3_r1
[Nexus 4 Android Development] markd0wn:
Yep many ARP related stuff in AOSP log now..
[Nexus 4 Android Development] thracemerin:
I'm going to let people test things for a few days before I add or change anything.
[Nexus 4 Android Development] oSandmaNo:
I'm on official 4.3 now and WiFi seems to work fine now. Notifications arriving instantly
[Nexus 4 Android Development] thracemerin:
I tried to backport the 4.3 prima drivers again for 4.2.2, this time from sources. Here's the test.
[Nexus 4 Android Development] endursa:
So far it works on latest cm10.1 nightly! I will report on wifi tomorrow!

Gesendet von meinem Nexus 4
[Nexus 4 Android Development] sNoxious:
Can you do a version that the user can use any kernel that you want? Like a patch, something like that.

Sent from my Nexus 4
[Nexus 4 Android Development] kara mustafa:
We need to uncheck WiFi optimisation in WiFi settings to make it works properly, right?

Nexus 4 - Stock 4.3
[Nexus 4 Android Development] nguyen47:
I believe the situation is not fixed though. I just have some missed calls on Viber
[Nexus 4 Android Development] thracemerin:
No, has to be a full kernel.

You shouldn't have to, but I think I identified a problem with the 4.3 driver that wasn't in the leak.

Yep, see above.
[Nexus 4 Android Development] markd0wn:
So the drivers are not the same on JWR66N as they are on JWR66V? And can the problem you identified indeed be solved by disabling WiFi optimization, or is that not clear yet?

I'm currently using the stock official 66V and haven't noticed a difference yet in terms of WiFi compared to the leak. A secondary device (which I have temporary access to until tomorrow) is now running CM + the prima fix you ported from 4.3 to 4.2.2. Seems fine so far as well.
[Nexus 4 Android Development] thracemerin:
In the leak ARP offload is enabled, in the official it's disabled, I don't understand why Google did that. Turning off WiFi optimization seems to fix it anyway, but that's not really the solution to the problem it's a nice workaround.
[Nexus 4 Android Development] markd0wn:
That explains all the commits from https://android.googlesource.com/device/lge/mako/, tons of "revert wcnss config", then revert the revert, then revert again, etc...

Looks like they indeed settled on 'off' for host arp offload.

Here's something interesting though...

https://android.googlesource.com/device/lge/mako/+/android-4.3_r2.1/WCNSS_qcom_cfg.ini

Does this mean that if one builds from source (r2-JSR78D, or in linked case the newest r2.1 - JSS15J), the setting will be on again? I assume most if not all custom roms will be based on JSS15J since that's the newest build, and if the setting is indeed back on in that newest AOSP build, the semi-problem you discovered will only affect those who use stock JWR66V
[Nexus 4 Android Development] BlueFlame4:
I actually don't get why there are 5 versions of 4.3.

Why doesn't Google simply roll out this latest one as OTA update? m( I really hope that WiFi problems will be gone since this is the only thing I've been waiting for. But I think it's too early to complain, even though I'm a bit upset at the moment :/
[Nexus 4 Android Development] markd0wn:
JBQ explained it, sort of

JWR66L = Android 4.3 r0.9. Not intended for official release to users.

JWR66N = Android 4.3 r0.9.1 - Leaked for the Nexus 4 and the Google Play Edition of the Galaxy S4 - Also not intended for official release.

JWR66V = Android 4.3 r1 - This is the official build for devices, OTA update and factory images out, this will presumably also be the build for the Google Edition devices.

At this point, per JBQ, they split the JWRXXXX builds and made another family of builds, the JS builds. This was to "shield existing devices from the risk of destabilizations introduced by last-minute changes for new devices", like the new Nexus 7.

The newer builds are:

JSR78D = Android 4.3 r2

JSS15J = Android 4.3 r2.1 - Newest version of Android, available on the new Nexus 7 (I think) and via manual building from AOSP. Even though there are no OTA/factory images, one could still build JSS15J for the Galaxy Nexus and Nexus 4, 7 & 10 as the source and appropriate drivers have been posted.

When I initially read JBQ's statement, I thought the JS builds only have changes that affect the Nexus 7, and that for Nexus 4 specifically, JSS15J should be identical to JWR66V anyway. But as we can see now in this (sort of important) example, there are differences for Nexus 4 as well, so using a build from source could have advantages over the 'official' JWR66V.
[Nexus 4 Android Development] thracemerin:
JSS15J is for Verizon Galaxy Nexus ONLY
[Nexus 4 Android Development] markd0wn:
Are you sure? JBQ specifically said "JSS15J is 4.3_r2.1 - that's the latest one, on the new Nexus 7." He also said the JS family were split to protect existing devices from changes to new devices, and the Verizon GNex isn't new...

In the AOSP announcement message, he spoke of JSS15J generally - "We will be taxiing for a few minutes to our gate JSS15J while ground support guides us to the public git server."

Also, the drivers page, https://developers.google.com/android/nexus/drivers, states "Binaries for Nexus 4 ("mako") - Android 4.3 (JWR66V and JSS15J)"

And of course the android-4.3_r2.1 tag appears in device/lge/mako... unless I'm missing something here.
[Nexus 4 Android Development] thracemerin:
The only official build of JSS15J is for GNex on Verizon as far as Google searches will tell me.
[Nexus 4 Android Development] markd0wn:
Maybe it's like with JDQ39E, there was no official build for it for a while, it was AOSP-only until some new Nexus 4 devices came with it and with the .54 radio. Custom roms like CM merged JDQ39E before that happened. The question is, is JSS15J build-able from scratch with the drivers etc and results in a fully functional build for mako or not. The fact that AOSP has some mako-related r2.1 stuff including WCNSS_qcom_cfg.ini with hostArpOffload set to 1, tells me it might be buildable.

I'm not surprised that there is plenty of development for JSS15J on the Verizon GNex, because Google did not release any factory images or OTA updates for it at all for 4.3, they just posted drivers, so the only way to have 4.3 on Verizon GNex is to build it, which is why people rushed to do just that.

EDIT: Yep, JSS15J is for mako as well. With Host ARP Offload back to 'on'. Custom rom with it already underway:

---

JSS15J changelog (has a few mako-related changes):

http://www.funkyandroid.com/aosp-JWR64-JSR78D.html

http://www.funkyandroid.com/aosp-JSR78D-JSS15J.html
[Nexus 4 Android Development] archibald_schlick:
I've got a little experience in building CM 10.1. I read the instructions for AOSP and it is almost the same. So I will try to build it tonight.

I am not a developer, but I am interested in those things. Maybe I can help some of you with an "newer" AOSP build than the Google release. Together we find a way to fix this annoying "notification delay bug" :laugh:

So wish me luck on my journey :D
[Nexus 4 Android Development] kara mustafa:
Has anyone a zip with 4.3 r2.1 bulid from AOSP?
[Nexus 4 Android Development] ckret:
[MENTION=3332811]faux123[/MENTION] released a first build of the 4.3 kernel

you can look it up in his thread
[Nexus 4 Android Development] markd0wn:
Some more info regarding kernel building from AOSP: http://xdaforums.com/showpost.php?p=43947732&postcount=40896
[Nexus 4 Android Development] thracemerin:
There were no changes between JW and JS in terms of how WiFi works kernel side, I just looked.
[Nexus 4 Android Development] markd0wn:
Yeah franco just said there are many commits related to GPU drivers. I guess the only WiFi-related change might be the .ini that comes with the JS build
[Nexus 4 Android Development] archibald_schlick:
My PC is compiling the build. I will test it in the morning (now it is 00:30a.m.) and hope to get a fresh, fully functional JSS15J build for us.

Good Night! :fingers-crossed: