yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] deepsunzhine:
Nop

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] pedxing:
Thank you, i was about to say the same. I got data drops on stock... I always run stock for at least a week to make sure i have a feel for it. The r30s have been good to me so far. No drops. Stock gave me drops and heat and only 3 hour max battery. Don't know why people think it's magical for data.
[Nexus 4 Original Android Development] franciscofranco:
Grey means no connection to the Google servers, has nothing to do with lack of data/internet connection..
[Nexus 4 Original Android Development] digweed4me:
Been running r33 3 hours ago no data drop or nothing . i also tried turning wifi on and off and havent had a sod yet. Thank u franco for this amazing kernel
[Nexus 4 Original Android Development] nokkenas:
Okay. I get it. What about the delayed notification?
[Nexus 4 Original Android Development] Rivermind:
Delayed on WiFi (known problem on stock) or over cell data?
[Nexus 4 Original Android Development] magictwins:
HSIC is a spec. it standardizes some protocols of communications among ICs. and qualcomm uses it.

shortly after the launch of N4, many found it consumes more battery than it should have (compared to S3 and the like). And some pointed out that

hsic wakelock was causing this phenomenon, meaning that something related to hsic communication(i.e data transfer/overhead etc) keeps waking the device up more frequently than it should.

Later qualcomm made some modification to their code trying to fix this issue. But according to many in this thread, this fix somehow made their phone drop data connection from time to time. Because personally I never had this data drop issue (icon gray and needs reboot), I am unable to provide more useful information about it. Buf from a logic point of view, what I believe is qualcomm, making the fix trying to conserve battery and eliminate unnecessary wakelock in the first place, took it too far and cause it to be less operable with certain carriers around the world.
[Nexus 4 Original Android Development] c_86:
See my issues is data on Facebook. Not sure if its kernel, ROM or app. What happens if data seems stop when in Facebook. But us fine for everything else.

Tried the wipe app data etc.

Anyone else? Or is this related to the data drop issues?
[Nexus 4 Original Android Development] mattkroeder:
Personally, r32 was the first version where I really noticed the issue because I had been using my data all morning without a problem while on r31. I then happened to flash r32 and my data stopped working. Signal was fine but I couldn't load any web sites. Figured it was probably the kernel I just flashed so I downgraded back to r31 and it was fine again.
[Nexus 4 Original Android Development] joshnichols189:
People get that on stock, so it's likely not getting fixed anytime soon. So there's no choice but to live with it.
[Nexus 4 Original Android Development] nokkenas:
So far, I only experience delayed notification on Wifi. I haven't use cell data long enough (might test later). Didn't happen even once on stock kernel and ROM. It started happening on r31 but it was only once. Happening every time on r32.

No I didn't. Weird huh? It started happening since I flashed r32. I know it's the case on some other phone but not my N4.
[Nexus 4 Original Android Development] cobyman7035:
Data drops means your signal bars are Grey out after deep sleep?
[Nexus 4 Original Android Development] iamsmallpang:
R32 the signal will turned to gray suddenly and then is the Blue. But R33 just flashed about 5 hours has not that problem and my device has not heat and working smooth..... THANK!

從我使用 Tapatalk 2 的 Nexus 4 發送
[Nexus 4 Original Android Development] magictwins:
no one has yet provided a clear definition...
[Nexus 4 Original Android Development] albundy2010:
It means your data just completely drops out. Happens at random.

Signal bars and color don't tell the story. You can have what looks like full normal signal and still have no data connectivity at all.
[Nexus 4 Original Android Development] Ballastatuz:
Thank you for all your hard work Franco it is truly appreciated. I have been flashing since r17. This has really made my battery last.
[Nexus 4 Original Android Development] yokuyuki:
It also doesn't happen all the time. It depends on router and how it handles broadcast and multicast packets.
[Nexus 4 Original Android Development] Globespy:
I'm hoping the various carriers release updated radios, or will that still be Google who decides that?

I think it's justa sh!tty radio that needs an update.... would explain why it's different for many people.

I've had the issue where blue bars turn gray, and maybe once where there are no bars anda black triangle.

In both cases data had store dropped.
[Nexus 4 Original Android Development] DowntownJeffBrown:
The bars turning grey means u aren't connected to the Google servers.

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] squadz:
I have absolutely no idea where everyone is coming from with data drops, but I've never had a single one in any version I've flashed.
[Nexus 4 Original Android Development] Haomuch:
Tried the r33 last night with all Wi-Fi on and it seems pretty good with battery life and quite deep sleep status. The hsic wakelock come back again for 30m, not as much as I expected. But I guess that's because I was fully on Wi-Fi. Will turn to 3g and see how it perform today. If it goes up very soon after that, will change back to r32.

I am really annoyed by those people reporting data issues BTW. I have never experienced one single data drops since I flashed the r16, no matter on Wi-Fi or 3g. That just means all the data drops for other people may just due to their own stupid Carrie and bad network condition. Could we just ignore those who report their so called data issue without detailed information and comparing with stock kernel at the same place and same time?
[Nexus 4 Original Android Development] LimitsX:
I get that too with R32 and R30. I thought the same, but when it was gray, I never had any data drops though. Sometimes my carrier network's data sucks, but its slow thats it. I've used wifi and no drops at all.

So, I don't think graying has to do with data drops, at least not in my experiments yet. I've been testing this kernel with different AOSP and CM 10.1 based roms, no data drops either.
[Nexus 4 Original Android Development] bleuf1sh:
I've had 3g data issues ever since those Qualcomm patches and the best way I can describe what's probably happening on my device is the app tries to send a packet but the 3g driver is "frozen" and the app waits thinking the packet was sent and that it's waiting for a response from the server. It ends up timing out. I've never had to reboot to get data back.. Only wait a few minutes and hit refresh. Just flashed r33 and data seems more responsive as if the driver is always responding.

sent from my r33-Franco nexus 4
[Nexus 4 Original Android Development] yokuyuki:
Why could carriers release a radio for it? It's not a carrier phone.

No bars and a black triangle means there's no signal. I don't see how this is the phone's fault.
[Nexus 4 Original Android Development] DowntownJeffBrown:
Lol so the people experiencing data drops Like me only when the wake lock fix is in place annoy you and we should just keep ours mouths shut? I think not lol how arrogant are you to say we should just be ignored. Pfft

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] LimitsX:
I have to agree with you there. I haven't experienced any data drops, or call drops. I used to have call drops on my normal mobile phone but thats my carrier fault, they are just not that good. Their towers suck, its congested and etc. So, that issue is with my carrier. Since nexus 4, i never experienced that on stock, nor on franco kernel.

I had weak signal issues, thats it, and no heating issues either. Also, the battery didnt improve much until R28 for me.

But, my battery started to drain fast on R32. So im gonna do more testing and see how it goes.
[Nexus 4 Original Android Development] DowntownJeffBrown:
When I got a data drop they stayed blue just for reference so my phone was still receiving just not broadcasting it to me.

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] Mendanbar:
possible "data drop" sighting?

Not sure if what I experienced today is the "data drop" issue everyone has been talking about, but I am in the unique situation described above. My observations:

My wife has a stock rooted nexus 4. Nothing special installed, just rooted. I have a rooted nexus 4 running CM10.1 (01/11 nightly) and Franco kernel (r31).

I left the house this morning with my wife and both of our N4s. We used her phone to navigate to a location in Seattle without issue. Prior to leaving the house I was browsing the internet (this forum actually!) on wifi without issue. Upon arriving, we switched to my nexus 4 to navigate to our second destination. I unlocked my phone for the first time since leaving the house... no connection. I checked my wife's phone... full bars, H+. We are both on T-mobile. I went back to my phone and long pressed the data quick toggle, and discovered that data was turned off. I turned it back on and I was able to connect with my N4 the same as my wife's.

I would normally chock this up to user error (maybe I turned off data for some reason I can't remember?) except the same thing happened to me last night as well. The difference being that last night I really did think it was my fault (didn't have my wife's N4 to double check), and went on my merry way. ;)

I'm on wifi 90% of the time, so this is the first time I've seen any data issues. I'm also unsure if this could be considered the "data drop" issue. I've been watching this thread and have yet to see a post describing exactly what I saw yesterday and today. Maybe someone else can confirm or deny? Unfortunately I have no logs to provide, since I thought I was one of the lucky ones without data problems.

Final note: I've been using Franco kernel since r23, and I couldn't be happier. I'm just trying to provide some info that may help make it even better. I easily get 150-200% better battery life than my wife does on her stock N4. Thanks for all the hard work Franco!
[Nexus 4 Original Android Development] zFayZz:
So called data drop didnt drop any of my data just drained by battery lol but but now r33 seems great.. When did this data drop occur? because by drains started at r30
[Nexus 4 Original Android Development] Globespy:
Well, T-Mobile sells the N4 on their network, and while mine is an unlocked full price phone, they have folks on contract who will probably be sending feedback any connectivity issues.

Every other android phone has had multiple radio updates over its life, so why wouldn't the N4?

Additionally, to the guy who mentioned that people should stop talking about data drops and that it must be their "stupid carriers", I've been with T-Mobile for 9 years and never had the data inconsistencies that I'm seeing on the N4.

So it may well be a crappy radio that Google needs to fix, or a carrier update?
[Nexus 4 Original Android Development] franciscofranco:
Data loss is simply having the connection cut for X periods of time, usually few seconds. Grey bars means the device is not connected to Google services for some weird reason, but you'll still have internet connection. r33 uses the same HSIC (usb modem/radio) drivers as stock so if you're having data losses just like I described its something else than this kernel.

I'll post this into the OP FAQ so I don't have to repeat it again :)
[Nexus 4 Original Android Development] albundy2010:
T mobile or any other carrier can't issue any updates what so ever to this phone period,
[Nexus 4 Original Android Development] Haomuch:
Don't get me wrong. I am not saying ignore all the people having data issues. But at least please provide more detailed and logical description with proper comparison instead of just loudly saying hey I lost my data connection! Otherwise it will also annoy Franco a lot.
[Nexus 4 Original Android Development] fetto666:
I have tried r23, r28, r32... no data drops on any of these.

Just my report - using facebook, google reader, e-mail etc.. many times a day.

Never had any issues. 2012 december model of nexus.
[Nexus 4 Original Android Development] drawde40599:
It dose not happen to every1
[Nexus 4 Original Android Development] franciscofranco:
Yeah unfortunately its very random. I took a look into some logcats with the so called data loss and seems like the HSIC modem/radio is not very fast to react if the interface goes into low power mode or something and it thinks the device doesn't have a SIM card for that period of being confused. I can be wrong, but thats what I think it is based on the logs :)
[Nexus 4 Original Android Development] drawde40599:
There are data issues with those patches , every dev that added them removed them cause of it , people did send logs , logs didn't help , the patches are gone he's not putting them back till either he understands them better or 4.2.2 my guess 4.2.2. . your 30 min wake lock that cause no phone issues besides visual , and small amount of battety, is on back burner sorry ;)
[Nexus 4 Original Android Development] darkamikaze:
The only data issue I've encountered is when my phone goes to sleep after a couple minutes when the screen is off there is no data (Tested this using AirDroid). Yes, wifi is set to never sleep.

Other than that this kernel has been pretty solid
[Nexus 4 Original Android Development] drawde40599:
This is the best description of the data issue , if your experiencing something else its not the kernel .
[Nexus 4 Original Android Development] maisi:
As far as I know there was a big update a bit time ago , which sounded like they finally got rid of it.(like they did months ago on iOS)

However i won't install the app as well, drains battery a lot and constantly wakelocks the phone. The mobile site is great too.
[Nexus 4 Original Android Development] franciscofranco:
The iOS app is miles away from the Android app :(

The problem is not really the native/HTML5 - which seem fixed now - the issue is that they have like 4 or 5 services always running for no reason at all. Those services hold wakelocks all the time which prevent the device to idle, then ruining the battery and rom and kernel devs get ****ed because users blame us :D I wish they would fix their crap and make it as enjoyable as the iOS counterpart.
[Nexus 4 Original Android Development] shadowcaster31:
Well maybe install an app like autostarts/gemini to disable every single thing related to the facebook app.

Do you think this can prevent some of the running services and thus reducing some wakelocks?
[Nexus 4 Original Android Development] jdmcivic:
you guys should stop bickering on the facebook app. i have it running with whatsapp and my battery life is excellent.
[Nexus 4 Original Android Development] Luigiesin:
Well, you're lucky brother... But it's known that Facebook app sucks and goes all the way to the way it's coded...

Sent from my Rock & Roll Nexus 4

ROM: MINCO

Kernel: Franco r31

T-Mobile
[Nexus 4 Original Android Development] mjehan:
Moving from R32 to R33 i noticed that data drops are gone but wakelocks are back. Something is not letting the phone go to sleep in idle mode. Plus for some reason there is a lag when launching applications and within the apps themselves.
[Nexus 4 Original Android Development] biffsmash:
I also have zero issues with Facebook app and to be fair I never have. Battery shows no difference whatsoever for me with or without it and I have no wake locks to speak of that I would worry about. Phone is deep sleeping like a baby.

Then again I turn off facebook location and notifications and have GPS off so I imagine that makes a difference.

Nothing on IOS impresses me, still looks and feels like an o.s. from 1989.

As for facebook app on ios, ive never heard anything but complaints from my poor deluded iphone using mates about it when i seem to have no issues at all.

As for this kernel, r33 running great, even with Facebook :D
[Nexus 4 Original Android Development] magictwins:
I guess we should stop talking about facebook app. it's an app anyway.....

if you have no problem with it. stick to it. if there's problem with it, disable it...
[Nexus 4 Original Android Development] fetto666:
It's an app yes, but it may cause people to blame something else - thus causing grief for developers of other apps/roms/kernels for no reason.

And correctly debugging and showing logs seem to be easy to forget.
[Nexus 4 Original Android Development] mbolinao:
i have to agree with the lag... i spoke too soon about r32 solving it, it's still there.

No lag when using r29, but my phone signal on that build disappears randomly.

So i have to choose between lag and signal: im currently on r32 LOL.

I just can't go back to stock kernel because battery life with Franco is really good.
[Nexus 4 Original Android Development] jdmcivic:
these are my settings for Facebook.

i still get live notifications even though refresh is disabled.

i still can check in to places by just toggling on gps.

never had a problem with batt life with these. i too used to believe that the running services on facebook would cause wake locks /batt drain but then i was wrong..
[Nexus 4 Original Android Development] Hanny:
exactly the same, and no problem (after reinstalling for once since i got endless "network errors")

what i meant was continue when you're good, get rid of it when you got errors, and never relate the derp to kernels :laugh: period.
[Nexus 4 Original Android Development] SacredAce:
Been using Franco's kernel since r23, and never had any issues. This morning, while I was waiting for a car service, I was reading this topic (Taptatalk app) and some news, and, voila, data drop. Just to make it clear, full bar signal, always blue color. One minute everything was working, then everything stopped. I tried turning data on/off, but that didn't do ****, so i rebooted and everything fine.

Although this is the first time I see it happen, can't stop wondering if it has something to do with the network signal rather then kernel/stock.

So far, everything works peachy, no lag, no heating, just smooth and nice experience over here.

Plan to stay on r32 for a while, to see if the data drop repeats. I guess that one data drop in one month ain't so bad...

Oh, and I don't really like Facebook app (old and new), and using oStream and FBtouch, since they are way lighter and faster, don't seem to be any problems with wakelocks or services.
[Nexus 4 Original Android Development] Haomuch:
Finally got a full day test for the r33 battery and wakelock performance. Totally run for about 10 hours for more than 50% battery consumption. About 1 and half hours with 3g and the rest with Wi-Fi. 2 and half hours of screen on time. HSIC wakelock for 1 hour. Really hope some future patch could fix the wakelock and data issues together.
[Nexus 4 Original Android Development] akhan47:
Tested R33 today but it was horrible for me. Battery is back to terrible. R29 worked best for me personally so I'm going to stick with that.

I've never experienced any of these 'data drop' issues I hear people mention...
[Nexus 4 Original Android Development] Zaihanzainal:
I'm beginning to think this data drop issue is a baseband thing.... Anyone in the US facing it? If I'm not wrong different carriers use different bands...

Back when I was using the OB I had a similar problem but it was worse... Fortunately OB had smart flash tools and kdz extractor so I was able to flash the baseband(fls file) for my region and my data problems went away....
[Nexus 4 Original Android Development] SupWiz17:
I am in the US and last night for about an hour I experienced data drops for the first time ever.
[Nexus 4 Original Android Development] Zaihanzainal:
Hmm I'm gonna try find a way to flash a v20 or v30 baseband for my region and see if that works for me...
[Nexus 4 Original Android Development] republicano:
how long are you guys on data before you get a drop?, I have been using data off and on during the days and haven't experienced it yet, on r32,I will leave it data on tomorrow and see if poor service affects it

anyway how do you modify temp threshold?, I know where's the directory module/msmthermal/parameters.

I guess I will modify and compile tomorrow
[Nexus 4 Original Android Development] Vaxx93:
msm_hsic_host wakelock

I'm experiencing a wakelock in r33, the known msm_hsic_host, it is keeping the phone awake for 5 minutes while it is 35 minutes on battery. This wakelock wasn't present on the r32
[Nexus 4 Original Android Development] veyka:
Let me be clear about my experience with these data issues.

I'm sitting in the same place, not moving, with r31 or r33 data works fine, speed tests load and are quick, Web pages work, Tapatalk works poorly but it's a Christmas miracle when it works well.

I flash r32, works fine for a bit, then things just stop responding, speed tests time out, Web pages load, and even a deity couldn't get Tapatalk to load a thread.

If i reboot, r32 works for a bit, then does the same thing, it's not the traditional baseband crash where the whole signal drops (bars go black), the h/h+ icon shows, maybe some arrows, but nothings getting though.

This is not a few people on supposedly "crap" carriers having issues, it seems to happen to basically everyone more or less randomly.

And as noted by the CM kernel Dev when he merged these patches, they also cause issues with the slimport video out chip, and in some cases the gps, where they just fall off the bus, its just that most of us will be using data more than the other two, so won't notice the other issues.

HDCI is the usb high speed inter-chip interface (used for connecting different chips on the motherboard, like, hmm, our SOC (cpu, GPU, ram, bluetooth, wifi, etc and our baseband as LG didn't go with the MSM version with the built in baseband, but instead with the APQ version, maybe because they wanted to use a different baseband, or maybe because the MSM version wasn't ready, who knows) and these patches seem to put the bus into the low power/sleep mode too aggressively, great for killing the wakelock, terrible for anything hanging off it, aka our bloody baseband.

The baseband itself has issues, randomly fluctuating signal (though that's more likely to be a carrier/location issue) and poor performance and very occasional "traditional" connection drops (where the whole thing goes, signal icon goes black, no bars, airplane more toggling fixes) but these are not kernel related, and have been reported on stock.

There is also the wifi doesn't work on screen off issues, which is related to the packer filter blocking all multicast and broadcast packets when the device is screen off (great at stopping the wlan_rx etc wake locks due to noisy **** on the network, like any windows computer, bad for wifi actually working when the screen is off), this issue also seems to vary depending on the router you have, but is NOT the same as the data drop issue, and there is a fix out there, where you change the way the packet filter works.

Well, that's enough tl;Dr from me, if you bothered to read that, good on you ;)
[Nexus 4 Original Android Development] bakedcricket:
Running on r32:

• Data seems to turn off once every minute.

• Data seems to turn off after a min when it's locked.

• Data connection seems to run for a while even with full signal bars and suddenly just drops/lags for a few seconds before connecting to the site/app again.

I hope this helps!

ps: data would grey out during deep sleep. Is this already happening on stock kernel? I don't recall.
[Nexus 4 Original Android Development] mobilehavoc:
Franco, can you look at Motleys b12 change log and commit history. I have zero data issues and no one else is reporting it either but he has some hsic patches in there but from earlier on. Good just be luck but I did have data loss on your kernel with the newer caf patches. Worth a peek?