yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] bleuf1sh:
Franco... Any chance the patches can be applied in a bool flag check that if the screen is being tapped then don't use the patched code and if its not then use the patched code. That way drops occur (for those who have them) while the device isn't being used actively. So the drops for a few min isn't so critical. Is it possible... What do ya think?

sent from my r33-Franco nexus 4
[Nexus 4 Original Android Development] lazinase:
Running r32, the game Chaos Ring from Square Enix sometimes has a 0.5 sec lag...
[Nexus 4 Original Android Development] jundii:
I agree. Franco also said a few posts back that he would update the OP with a clear definition of the data drop issues related to the wake lock patches.

And anyone complaining about the wake lock in r33... It is going to be there again! All of the patches to fix the wake lock have been reverted.

As for the WiFi issue.... Completely unrelated to the kernel. Happens on stock. The fix out there has been said to sometimes work for some people (at least some users claim it doesn't work for them in that thread).

Sent from my Nexus 4
[Nexus 4 Original Android Development] Taxiback:
I can't believe anyone would chose a smooth phone over one with a signal. As for stock, I reverted back to it last night after loosing my signal on r33. I see no reason why 5hrs screen time should be a problem.

Oh, and no signal loss either. :)
[Nexus 4 Original Android Development] veyka:
No, I get the data stop issue while the device is in use, and it doesn't work like that, it's not like these patches are tuning parameters that have user space access, its fundamental parts of the hsic driver, not something that can be done at runtime! (also when I'm not using my phone, it's still connected to push IM services, gtalk etc, and I would also quite like to get notifications for my email etc)

Qcom, Google and LG need to fix this, they have more hardware, all the source (baseband etc as well) and detailed knowledge of how the chips work, and how exactly they are glue together in this device, we have good kernel Dev, but no one wants to reverse engineer the whole baseband solution for an issue qcom et al are working on anyway!

At least with CaF we can see them working on it!
[Nexus 4 Original Android Development] Taxiback:
I could have sworn the Mod last night asked people to PM rather than spam the thread. Why you not listen Vangelis13, feel you're better than everyone else?
[Nexus 4 Original Android Development] bleuf1sh:
Ok but until they fix it I think we shouldn't stop exploring all possible options. If it can't be accessed from user land then through the swipe to bootpulse method the device could be forced to not enter the low level that the patches introduced and 'force a wake' only when the device is being actively used. That can be done from the kernel level.

Its my understanding that the patches allow the driver to run in a lower mode.... Which as Franco mentioned sometimes makes the phone think it has no sim.... or am I way off?

And you'll still get your notifications.... Just a few minutes later

sent from my r33-Franco nexus 4
[Nexus 4 Original Android Development] DowntownJeffBrown:
Yes thank that's the best written post about the issue I've read. Thank you :thumbup::thumbup::thumbup:

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] eagleeyetom:
Thread has been cleaned. I want to poin out few things.

First re-read what AvRS said some time ago.

Wrong thread.

Why don't you fix it yourself then? Are you questioning skills of our Recognized Developer? Hopefully not. :rolleyes:

So stay at stock and don't spam this thread. It's not the kernel you have to use to make your phone boot or be fully functional. If you don't like it, don't use it. Simple like that.

Can you keep your conlicts in private? We don't have to read "love letters" from both of you.

Proceed on topic or things will get nasty.

Thank you.

Tom
[Nexus 4 Original Android Development] veyka:
These patches don't change simple values, they add and remove chunks of code, not something that is workable at runtime. And a lot of what you are talking about is fiddling with the deep inner workings of the driver for a chipset we dont have documentation etc for, so we don't know how the chip likes things done.

(Note I said patch set, its quite possible and was mentioned to me that the cause of the issues is missing other commits that are needed for stable operation).

Another problem is that Franco stated that he himself cant repo the data stuck issue with the newest set, which makes it even harder!
[Nexus 4 Original Android Development] zFayZz:
yep still facing battery life issues going back to r30 where my battery was amazing
[Nexus 4 Original Android Development] maddoggin:
If I'm not mistaken I think I'd you update you will lose root! I'm pretty sure you will receive the update but you will lose root. However most custom Roms do away with the update settings any way. But I'm not certain about this. I know on my galaxy nexus I received ota while rooted but didn't flash it. So... :confused:
[Nexus 4 Original Android Development] javacody:
The fact that many of us are NOT having issues tells me that the drivers' code is not taking into account network conditions for some carriers.

Like I said earlier, I had issues the first week I had the phone and was bone stock. Phone would even drop calls constantly.

TMobile did something on their end and problem went away. Probably a firmware upgrade on their end or they tweaked network settings to better support N4.

Instead of blaming Franco, try reporting the issue to your carrier. See if the issue magically clears up for you like it did for me...
[Nexus 4 Original Android Development] veyka:
To receive an ota update you need stock kernel and rom, it won't auto flash with a custom recovery, but you may be able to manually flash the zip (generally this will replace your custom recovery with the stock one though), bootloader unlock status doesn't matter, so no point relocking unless you enjoy wiping all your data when you want to unlock to flash a custom recovery, kernel, or whatever.

You will lose root, but root is easy to get back, flash or boot a custom recovery then flash supersu or superuser vis zip or root manually vis adb or toolkit if you really must.

Anyway, this is general rom stuff, so that's enough OT from me, in future these questions are best asked in the q/a section. :)
[Nexus 4 Original Android Development] DowntownJeffBrown:
You can be rooted but all stock (no custom kernel or ROM) and get the update. You won't lose root by just being on stock. I'm pretty sure let me know if in wrong but in just gonna wait for Franco to deal with the 4.2.2 update since his kernel is far superior to stock in all aspects.

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] Monkeybrew:
Probably true. Here in Sweden there seems to be a lot of trouble with data drops on the "tele2" network, but not on most others.

I'm getting the bug that prevents mobile data to connect when leaving a wifi network in which the phone has "gone to sleep".

That is : when leaving certain wifi connections the phone does not switch over to mobile data automatically and the signal bar is grey. It is solved by refreshing ap settings or toggling airplane mode.
[Nexus 4 Original Android Development] DowntownJeffBrown:
This app can be used to lock and unlock a nexus 4 boot loader without getting your data reset and lost

https://play.google.com/store/apps/...=organic&utm_term=bootunlocker+1.3+play+store

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] chrisgtl:
I don't think I was having any data drops on o2 here in the UK.

Which kernel is best for the people who didn't notice any data drops? I'm not saying 100% I did not have any data drops but would like to go back and check for sure if I had any data drops or not.

Thanks
[Nexus 4 Original Android Development] derlotse:
+1

Had the same obsevation on T-Mobile Germany (who have usually a pretty good network here).

On the other hand, from time to time I do have and had data drops .. on my old HTC desire, later ond the One X and also on the (Stock Kernel) Nexus 4. Reasons were manyfold: failed handover between cell-transmitting stations, especially in the subway; cell too full; provider DNS problems..

but so far I did with no version -from r27 till r32- encounter any data issues that could be linked to the kernel only.

I don't want to say that the problem does not exist - but maybe it is not as common as it appears here.. more network diagnostics may be helpful, e.g. a simple "ping -c 2 google.com" can tell you already a lot

.. just some thoughts.

(I really love the r32-Kernel and will stick with it until I encounter heavy problems..)
[Nexus 4 Original Android Development] bleuf1sh:
Hmm... You think there are more patches that we aren't yet privy to that create a stable environment? ... are you implying that we need to make Franco's n4 drop data ? ;)

sent from my r33-Franco nexus 4
[Nexus 4 Original Android Development] Humu Toor:
I've been using this kernal for a while and never had any issues. Been getting some lag for my swiftkey flow beta keyboard as others have mentioned in the 30s builds. Tried to play with the settings but ended up going back to r28 which has had the best experience for me. When flashing, I must've done something wrong, because phone went into a bootloop which caused me to wipe, when other avenues were exhausted, so I'm on stock kernal now. Going to keep monitoring the thread, and if anyone has had the keyboard lag and sees any improvement in the current updates, please share.
[Nexus 4 Original Android Development] TheByteSmasher:
@ Franco: I'm not sure if this is a bug or not... I use titanium backup to clear user and system apps cache when fku gets done, it throws a FC, even if it's not open, after the clearing is done it throws periodic FCs until I open it again and back out.

Sent from my Nexus 4
[Nexus 4 Original Android Development] DowntownJeffBrown:
Battery on r33 looking good for me 75% battery with 1 hour 15 min sceen on time all mobile data with all location settings on.

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] jundii:
Flashed R33 last night and let it charge over night. So far so good. As many have already said, and this is normal behavior, msm_hsic_host wake lock is back at the top of BBS, but I'm still getting 1% / hr battery drain on wifi at idle. I'm happy with that. Also, for some reason, I haven't had any delayed notification issues yet today while on Wifi and coming out Deep sleep as many have reported with the stock kernel. Every time I receive an e-mail in gmail or imap, my phone vibrates soon thereafter. I haven't had a single issue where I bring the phone out of sleep and I get a bunch of notifications delayed. I tested with Gtalk while screen off and the notifications came right through. Coincidence or could those wake lock patches have negatively exaggerated the "stock" issue for Wifi? I will report if it continues this behavior or not at the end of the day.

On CM 10.1 1/11/2013 nightly by the way.
[Nexus 4 Original Android Development] yokuyuki:
I don't recall anyone having data issues with r30. Why were the HSIC patches that were in that one reverted?

Tested r33 overnight and it's just awful for battery life. It just doesn't sleep for as long. Going back to r30.
[Nexus 4 Original Android Development] jdmcivic:
deep sleep fine for me. hsic wakelocks not that much.

data drops are gone for now. my whatsapp doesnt get delayed msges.
[Nexus 4 Original Android Development] elite_gamer04:
This brings up something I've been meaning to ask - do we need to disable Fast Dormancy if our Telco does not support it - I remember doing so on my GS3 before moving to my N4. I used to have a local.prop file with an option setting Fast Dormancy to 0.

Does this apply?
[Nexus 4 Original Android Development] mk92595:
Data drop is gone. Thanks. Didn't test life though.
[Nexus 4 Original Android Development] pedxing:
Just to throw this out there...although there is definitely an issue on the N4 with data drops, there are a number of other reasons for such events to happen.

Reason 1: Network congestion. You have full bars but the local tower is overloaded at that moment. Therefore new requests seem to hang or go through very slowly.

Reason 2: One-way connectivity. At times your device can receive better than it can transmit. This because towers have big, high powered transmitters, and phones do not. If there are obstructions (such as a heavy building) then your device can get a signal but it can't transmit out without lots of dropped packets. The end result is similar...your connection is trying to recover all the packets and so appears to hang or broadcast slowly.

My data drops tended to happen when going suddently from WIFI to no signal to 3G only signal. Like entering an elevator and then coming out. It seems to connect back up (full bars) but no data gets through for a time. On the stock kernel a reboot was necessary for me to recover. On other kernels airplane mode on/off would work. Something in the transition would hang the RIL in a weird state. Since...i don't know r20 or so this has become very rare. I can now usually blame my drops on one of the two reasons above and not the device specifically now.
[Nexus 4 Original Android Development] DowntownJeffBrown:
All I know is no data drops till r32 I've had 0 on r31 or r33 the only times I've data drops is on kernels with the wake lock fix. So take that as u wish to do so. I went to Motleys kernel from r22 through r30 because of battery life and phone temp so those builds Ihave no clue about. I don't use WiFi on my N4 ever just on my N7.

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] Vangelis13:
^^ Reminds me, does it also happen on 2g..? Can someone try that please?

Sent from my Nexus 4
[Nexus 4 Original Android Development] scream4cheese:
It has nothing to do with the kernel. Try to uninstall and reinstall the app.
[Nexus 4 Original Android Development] fetto666:
Data-drop started for the first time for me now, everything just stops working or time-out. Even though it shows full bars and blue bars.

And it's on r32 - i have now flashed r33 and will see if it's the same there.
[Nexus 4 Original Android Development] scream4cheese:
I had data drops on r27 on edge and hspa+. I tried switching between the two and I still encountered data drops. I know that build was release more than a week ago but data drops are data drops.
[Nexus 4 Original Android Development] yokuyuki:
Data drops are gone relative to what? r32? Did you get any on r30?
[Nexus 4 Original Android Development] Martin_Ro:
I think there is no need for a further discussion about the HSIC Patches and datadrops. Franco removed them because they seem not to be useable in the moment.

I think there are two possible reasons:

1. The patches changes something in the overall handling and some cell towers aren't able to handle this changes (changed timings or what ever) and therefore cancel the communication to free the slot for others

2. The patches are one half of whats needed. I think, most likely there is also a new baseband needed to make them work properly. HSIC is a protocol for communications between different ICs over USB. The patches only change one part (the Android part) but maybe there are also changes needed on the other side (most likely the baseband part). So one wouldn't work right with the other.

So we have to wait for a new baseband first and then maybe it would make sense to test this patches again....
[Nexus 4 Original Android Development] tom619:
any issues with r33 and stock rom?
[Nexus 4 Original Android Development] derlotse:
I am looking for a way to disable fast dormancy since a while.. couldn't find a way to do so, until now - and solutions for LG Optimus G, by modifying telephony.db I could not make work (I did not investigate this too much yet..)..

did you manage with the local.prop file? how (add line ro.ril.fast.dormancy.rule=0 )?

how can i see FD is active or not?
[Nexus 4 Original Android Development] DowntownJeffBrown:
If I was still on r32 I would try it out I've been on r33 and loving it :thumbup:

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] nickownzya:
Got awful data drops on #33.

Really weird, just flashed #28 again and everything is perfect.

Just wanted to give a report :)

Sent from mobile - excuse typos
[Nexus 4 Original Android Development] ItsAaronR:
I seem to be getting kind of the same thing, I don't get notifications for email, chat etc until I turn the phone on (or sometimes they do come but ~5 min after the emails arrive, used to be instant, not a huge deal but never saw this in 31, never flashed 32).
[Nexus 4 Original Android Development] Rivermind:
These are not data drops. There is a bug (on stock) where push notifications are broken on WiFi. Google says a fix is in the works for the next update.

If these delayed notifications are happening over cellular data, that's an entirely different issue (and one I haven't heard of yet).
[Nexus 4 Original Android Development] ItsAaronR:
Yeah, I haven't been using Wifi at work, so these are on cell data.
[Nexus 4 Original Android Development] veyka:
I got a nice pm from another kernel Dev after my long post up there, telling me that there was more CaF patches that Franco may have missed.

Problem with this discussion is that people are mixing the hsic related data issues, and data drops caused by baseband or network issues, with "stock" hsic you won't get any hsic related data drops, but you will lots more wakelock, with what seems like an incomplete hsic patch set from CaF you get less wakelock but data "jam"/" stuck" issues.
[Nexus 4 Original Android Development] Haomuch:
I suggest you stay with r32 for more time to see if it will produce the problem again and again.
[Nexus 4 Original Android Development] nokkenas:
Been on r33 for a whole day and so far there's nothing. I don't experience data drops or delayed push notifications either. r33 seems fixed my delayed push notifications.
[Nexus 4 Original Android Development] Testraindrop:
Maybe you or the other nice kernel Dev are kind enough to tell Franco what patches he may have missed, I'm sure he is open to suggestions ;)

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] nickownzya:
I don't want to be offending, but when I write about data drops, I mean data drops.

I've been at work all time today and wasn't using WiFi. In addition it's not about delayed notifications, it is about opening a web page, which randomly stops loading.

Sent from mobile - excuse typos
[Nexus 4 Original Android Development] zzelinka:
^^^

Why does everyone have to post saying they are reverting back to rXX or whatever? You need to flash the kernel and then let it settle. Let it go through a few charging cycles and then decide it you want to switch back. There is no way you can judge a kernel in the 3 hours you "tested" it this morning.

It seems that people can't be patient enough to wait... Franco is doing a fantastic job with this kernel. He doesn't get paid to do this, nor does he get the recognition that he deserves. The best thing you can do is post logs if you're having trouble or maybe even throw a donation his way. His app is great and well worth the $5. Give the man a break!

For what it's worth.
[Nexus 4 Original Android Development] frozndevl:
This isn't the first time I've heard someone say "let the kernel settle in". Can someone explain to me why a kernel, which is static code that it is the same every time you boot would need to settle in? Is this just placebo effect or something else?
[Nexus 4 Original Android Development] Hanny:
I agree with you. Totally. Sometimes, things might go wrong and Franco has already done his best to suit the demand of the majority of users. He himself should be enjoying his no-wakelocks no-datadrops environment but what? He built and is now using a version with all the wake lock patches reverted. I also did not have any data drops nor wake lock issues since forever, did I say anything?

I've seen multiple "Don't fix when its not broken" above. It isn't applying here so please stop saying that guys. That applies to useless updates of i-hv-da-most-functions-apps but not this amazing kernel. If you really love that statement stock is really the best to suit it. Moreover, the wake locks were the "broken" thing before and data drops are now the "broken" thing, so when did Franco fix when its not broken? And when something new comes in and Franco merges them, its not fixing the unbroken, its called development.

Btw here +1 for veyka or the good kernel dev to give suggestion to Franco so he can try something out. Also @franco wish you best of luck in regard to the current millions of reports... Please don't let them discourage you because people with no problem are very usually silent.
[Nexus 4 Original Android Development] Sim-1:
If I wanted to revert to a previous version how can I do it? Should I download the version of choice from HERE, and flash it in recovery mode via fastboot?
[Nexus 4 Original Android Development] Luigiesin:
O

When I mean don't fix it when it's not broken, I'm talking about MYSELF! If the kernel is working for me, then no need to change until I find a new build that works better FOR MY PHONE! Right?

All I'm saying is that YES! I let the kernel settle... 12 hours is quite enough to figure out how the kernel is going to work in YOUR PHONE regarding the apps you use and the settings. Cappice?

I'm loving the process of trying each build Franco releases... So don't judge me for saying I'm staying on r31 because it works better on my phone.

Cheers

Sent from my Rock & Roll Nexus 4

ROM: MINCO

Kernel: Franco r31

T-Mobile
[Nexus 4 Original Android Development] Hanny:
Yes, just that simple

Also if you prefer recovery flash you will notice a directory called "zip" at the bottom.

@Luigiesin: sure that's good if you're not directing to Franco but I think that's not necessary to report your revert of kernel version when you don't even tell what makes you choose to do so but a simple subjective "battery drains much faster".

There's someone else ago saying the same statement too so I was not pointing at you. Cheers mate ;)
[Nexus 4 Original Android Development] frozndevl:
Not trying to be the semantics police, but if this is what is generally meant by letting a kernel settle in, we are using a horribly incorrect version of the word. Settling in usually means getting comfortable, adjusting, letting something work the kinks out. What you described is observing the behavior and determining if it works for you. I tend to subscribe to your philosophy, install, see if it works for a full charge cycle / day, then draw conclusions. The reason I brought it up is by using the word settle, it implies that the kernel will work differently on the first boot from later boots because the system is changing.
[Nexus 4 Original Android Development] yokuyuki:
I always test a kernel by letting it idle overnight after a full reboot to remove any running apps. I've found that testing it for 7-8 hours overnight is sufficient to gauge kernel's performance and letting it run any longer has never changed what I found initially.

Actually, I think don't fix when it's not broken does apply here. After test versions for r24/r25/r26/r27 and before r32, there wasn't anything about data drops anymore while certain wakelock patches were still in it. So it seems like fixing something that wasn't broken before by reverting all wakelock patches when it was working perfectly fine before.