yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] thracemerin:
You're absolutely right, it's not. Faux123s solution to the data problem was to decrease the USB bus suspend time by 20% from the original, my solution from 4.2.1 was to use the CAF patch that set it to 0 as soon as the data stopped, this caused a problem if the data stream stopped momentarily it would get permanently stuck. I added a few additional patches to make sure that this wouldn't happen if it were just a momentary stop in the stream, so Faux123s solution reduces the wakelock time, but not to the same degree as mine, his patch is safer from a data drop standpoint though.

Edit: The new HEAD in my git has all my old patches from 4.2.1, I'm running a few tests on it to make sure we're good to go before pushing a test release.
[Nexus 4 Android Development] jakejm79:
OK, that makes sense, I never really suffered from the data drop issue, maybe we could get a little more aggressive than just 20% (assuming you are saying it was reduced by 20% i.e. from 10 to 8 and not reduced to 20% i.e. from 10 to 2)

EDIT: OK sounds good, I will sit patiently.
[Nexus 4 Android Development] thracemerin:
Yeah, 20% from original (ie 200->160).

See here: https://github.com/thracemerin/Mako/commit/e5b918aa41059e05ee3851fd117d20dd761e8526

I know it looks like I raised it from 0 to 160, but there was a previous patch that set it to 0 from 200 here: https://github.com/thracemerin/Mako/commit/56d96a8b55adc6ed005f35f06ef705ea8c812c3c
[Nexus 4 Android Development] jakejm79:
Is that number a specific time measurement, i.e. seconds?
[Nexus 4 Android Development] thracemerin:
Miliseconds.
[Nexus 4 Android Development] thracemerin:
Experimental v4 is now available in Post #2 (see changelog)

All of the changes that were in the last version for 4.2.1 are now in this version, it should behave exactly like the 4.2.1 version in terms of wakelocks.

Happy Flashing! :victory:
[Nexus 4 Android Development] chrone:
thanks god i found this thread. :)

well skipping the v3 test and jumped to v4. rock on! :good:
[Nexus 4 Android Development] thracemerin:
That's fine, no need to flash v3. But, those who did and then switched to v4, I'd like your impression of the differences.
[Nexus 4 Android Development] rycus86:
For me v3 was working good on 3g but had connectivity problems on Wifi.

Will test v4 now.
[Nexus 4 Android Development] thracemerin:
The wifi problems are in every kernel, if you flash one and don't have them you're lucky but it's not because something is fixed.
[Nexus 4 Android Development] rycus86:
Oh I see. Didn't notice the problem on your 4.2.1 v2 fix.
[Nexus 4 Android Development] thracemerin:
Yeah, it has to do with how the phone receives broadcast and multicast packets while the screen is off, there is a fix in another thread (link in post 1), but that fix basically allows all broadcast and multicast packets to wake your phone which depending on what else is going on on your network may cause you tremendous battery drain while on WiFi, Google acknowledge the issue and claimed they were going to fix it, but there is nothing at all in the new kernel to address the issue and it's been confirmed to still exist on stock.
[Nexus 4 Android Development] Razertje:
Does this kernel also fix the delayed notifications issue? Sometimes WhatsApp messages on WiFi and 3G come in 20/30 minutes after ther where send to me.
[Nexus 4 Android Development] chrone:
Re: [Kernel][GPL][anykernel] msm_hsic_host wakelock fix (4.2.2 sources!)

I can confirm that v4 kernel didn't have delayed notification bug on WiFi and 3G when screen was off for more than half an hours. Both whatsapp, gtalk, and gmail notification still gave notification sounds this morning the same time as the notification on gtalk for windows popped up. I use tp-link router though.

As for the battery life, tested for 2 hours idle on 3G with autosync enabled only took 2.8% drain per hour. While on 30 minutes of active use later at noon browsing engadget via chrome, g+, fb, tweetdeck, tapatalk, whatsapp, gmail and gtalk only took 5% drain per hour.

Msm_hsic_host wakelock is reduced to 5% coming from the usual 10% of stock kernel wakelock.

So far so good. Will update later with bbs log after full day use. :thumbup:

Sent from my Nexus 4
[Nexus 4 Android Development] thracemerin:
There is no specific fix to the delayed notification over WiFi issue as it would require a significant rewrite of the ARP offload part of the WiFi driver and that's beyond my level of expertise, so we'll have to wait for Google to get their act together and do what they said they would for 4.2.2 and didn't. As for 3G, I'm not getting the delayed notifications while connected to mobile data so this seems to be a problem that's related to your phone or provider.
[Nexus 4 Android Development] chrone:
Re: [Kernel][GPL][anykernel] msm_hsic_host wakelock fix (4.2.2 sources!)

V4 really reduces wakelock to 2.6%. I've been on for 6hr 25mn with only 9mn of wakelock. No data drop and wifi issues so far.

Sent from my Nexus 4
[Nexus 4 Android Development] Fr33L4nc3r:
Re: [Kernel][GPL][anykernel] msm_hsic_host wakelock fix (4.2.2 sources!)

Here's my data.

Did not use much the phone (BT streaming)

Almost only 3G. Same result as above

Sent from my Nexus 4
[Nexus 4 Android Development] bradm23:
Re: [Kernel][GPL][anykernel] msm_hsic_host wakelock fix (4.2.2 sources!)

Testing out build 4. My msm wake is about 4.5%, however signal seems strong than it did with other kernels. On a contradicting note, when I look up my signal in battery stats, it shows that I was 33% without signal over 2.5 hour testing. I'm not sure how this can be since every time I turn on my phone it has signal and I haven't been moving around much. Could I be losing signal while in deep sleep? At this point it is the only thing that makes sense
[Nexus 4 Android Development] thracemerin:
BBS only shows a signal when you're not on WiFi, it looks at your mobile data signal, and you aren't connected to mobile data while on WiFi.
[Nexus 4 Android Development] bradm23:
Re: [Kernel][GPL][anykernel] msm_hsic_host wakelock fix (4.2.2 sources!)

Thanks for the quick reply, I didn't know that however I was using the "cell standby" meter under battery stats in android settings. I have not been on Wi-Fi at all the entire time since a full charge
[Nexus 4 Android Development] thracemerin:
If you click on "cell standby" what does it say under "time without signal"?
[Nexus 4 Android Development] bradm23:
Re: [Kernel][GPL][anykernel] msm_hsic_host wakelock fix (4.2.2 sources!)

27% it says when up time has only been 2h15m, again no Wi-Fi was used in this time

---------- Post added at 04:43 PM ---------- Previous post was at 04:42 PM ----------

Crazy because I noticed a stronger signal than ever with less fluctuation so far with your patches but still have the % without signal high. :confused:
[Nexus 4 Android Development] thracemerin:
Hmmm.....I haven't seen anything like that, it might be your provider or area.
[Nexus 4 Android Development] bradm23:
Re: [Kernel][GPL][anykernel] msm_hsic_host wakelock fix (4.2.2 sources!)

I usually look at this and have never seen it this high to be honest.... Hmmmmm
[Nexus 4 Android Development] thracemerin:
Do me a favor, flash experimenal v1 (aka stock) and see if it continues to do that to you.
[Nexus 4 Android Development] bradm23:
Re: [Kernel][GPL][anykernel] msm_hsic_host wakelock fix (4.2.2 sources!)

K. I will flash it tonight and report back tomorrow from work again
[Nexus 4 Android Development] thracemerin:
Ok, that's the only way I can think of to determine if it's something with the patches to the kernel or something specific to your situation, but Murphy's law says that it wont happen tomorrow for some other reason like they were doing tower maintenance today or something.
[Nexus 4 Android Development] bradm23:
Re: [Kernel][GPL][anykernel] msm_hsic_host wakelock fix (4.2.2 sources!)

Yup that is how our always is. Running test one now and will report back. Just curious, if you are not on Wi-Fi is there any other reason you should have anything other than 0?
[Nexus 4 Android Development] thracemerin:
Well even while on WiFi that should be 0%. The only reason it would be above 0% is if your phone can't acquire a signal (in the case of the report in the system battery info I believe it's any signal not just 3G data) for some reason.

Occasionally I have trouble with mine in Walmart occasionally where the roof is made of corrugated metal, I guess the metal roof and the already somewhat spotty 3G service in my area make it so that I lose connection in there, something like that could be happening to you, I'm not sure.
[Nexus 4 Android Development] bradm23:
Re: [Kernel][GPL][anykernel] msm_hsic_host wakelock fix (4.2.2 sources!)

Just weird that this would happen, I always have a signal, every once in a grey moon it drops to edge but H comes right back quickly. Never had I tried to do something where I didn't have signal to accomplish it. Over 20% seems high. Doing some testing with latest zylon ROM that runs stock kernel for testing. I'll keep my eye on signal and wakes
[Nexus 4 Android Development] chrone:
Re: [Kernel][GPL][anykernel] msm_hsic_host wakelock fix (4.2.2 sources!)

Hello thracemerin,

What's your take on v4? Is it 3% to 5% battery drain normal in 3g mode for moderate use?

Perhaps it's just me or my provider, but sometimes it got stalled when browsing xda via tapatalk. Chrome, fb, g+, twitter seemed good though. :)

Sent from my Nexus 4
[Nexus 4 Android Development] thracemerin:
You mean the XDA app? It has issues sometimes that seem to be app related, I'm not sure that it not working is an actual problem.
[Nexus 4 Android Development] bradm23:
Re: [Kernel][GPL][anykernel] msm_hsic_host wakelock fix (4.2.2 sources!)

Little update on my % without signal from yesterday. What I did was charge battery to 100% so stats could reset, then I put my phone with screen off and checked it in 30 minutes and it showed that it didn't lose a signal at all during this time. Then I started using the phone for 15 minutes with intensive web usage using a lot of h+. When I went to check that percentage again the % shot up to 25%. Weird part is that I was getting signal the whole time and was never "without signal".

I tried .33 radio and .48 radio with the same results. Very strange results, I'm just going to ignore that stat because my phone works fine with .33 and .48 radios
[Nexus 4 Android Development] thracemerin:
That's very strange, but I guess if it's happening on stock I can safely rule out something in my kernel as the cause.
[Nexus 4 Android Development] chrone:
i used tapatalk 2, pretty much the same as xda app i supposed since it's a tapatalk custom build for xda. yeah, perhaps its my isp connection to xda forum that's all. hehe

how's your battery life, thracemerin?

my best max testing was 3% drain/hour when idle on 3g, and 6% drain/hour on 3g moderate use. screen time always reach 4 hours before reaching down to 20% capacity. the best battery life compared to stock kernel, and latest faux and franco kernel. :good:

are you using the latest bbs rc10? bbs rc9 and above are more compatible with android 4.2.2 build. i didn't encounter the no signal issues on stock rom 4.2.2 with v4 kernel. :)
[Nexus 4 Android Development] bradm23:
Re: [Kernel][GPL][anykernel] msm_hsic_host wakelock fix (4.2.2 sources!)

I use the bbs 1.9.2.1 which is the xda version posted here somewhere.

The read outs I was posting before was from battery stats in settings under % without signal
[Nexus 4 Android Development] thracemerin:
Mine is about the same, but my N4 has been idle a lot lately because I ended up with a BB Z10 for work, so I only use my N4 for non-work related stuff which means it doesn't get a lot of even moderate use right now.
[Nexus 4 Android Development] chrone:
whoa cool! nexus 4 3g data power consumption is a beast. haha. guess i have to invest wifi router. *sigh

out of topic, how is the bb z10? is it trully great compared to nexus or iphone? nice phone you have there! :)
[Nexus 4 Android Development] thracemerin:
The Z10 has a lot of potential, whether it lives up to the potential long term has yet to be seen, right now I like the phone but I don't love it like I love my android devices, we'll see what happens with it in a few months once the new device hype is done.
[Nexus 4 Android Development] chrone:
Re: [Kernel][GPL][anykernel] msm_hsic_host wakelock fix (4.2.2 sources!)

Aha, try update your bbs to 1.12rc10. Rc11 will be out soon in a few hours to fix the since boot detection on android 4.2.2.

Awesome! I do still love nexus 4 despite the battery drain gate. :)

Sent from my Nexus 4
[Nexus 4 Android Development] thracemerin:
It would be nice if LG and Google actually tried to fix the issues with the N4 instead of saying they would and then doing zip, the WiFi delayed notification issue is the most annoying to me, but we'll see, if they're really gearing up for the KLP launch maybe we'll get all the fixes we want eventually. The 3G power drain at this point is mostly in the baseband which unfortunately isn't something we can modify unless you can find someone who is extremely amazing at hex editing, but that's probably way too time consuming and potentially dangerous for anyone to actually try.

The other major battery drain problem is mpdecision, I get that they want a smooth and responsive UI, but bumping the CPU clock up to 1Ghz every time the screen is touched is probably unnecessary and drains the battery much more than it would drain if there was a better implementation of this system, the kernels using hot plug (faux, franco, motley, matr1x, etc...) still have excellent responsiveness without the battery drain that comes from mpdecision.
[Nexus 4 Android Development] chrone:
totally agree! :)

looking forward for the project roadrunner on key lime pie. i do hope your kernel will be around if the bug still exist on KLP. hehe
[Nexus 4 Android Development] thracemerin:
I just had an issue exactly like what bradm23 described, where the signal indicator was blank and the cell idle screen in Settings->Battery showed more than 0% no signal, but the funny thing is while it was like this I was able to do a speed test, stream music, made a phone call and other things, so it was obviously connected. Too bad I was out so I didn't get any good logs of it, but it looks like something is wrong between the RIL and the OS, but I'm not sure if it's kernel related or not, I was on v1 aka stock at the time.
[Nexus 4 Android Development] floepie:
Roadrunner? Wasn't that a debunked myth?

http://www.androidpolice.com/2012/1...ate-hoax-and-excellent-rumor-mill-case-study/
[Nexus 4 Android Development] thracemerin:
Things get leaked as rumors, get debunked then end up being true, I'm not saying that this is the case here, but some of these things end up being true despite the fact they seem extremely unlikely.
[Nexus 4 Android Development] bradm23:
Re: [Kernel][GPL][anykernel] msm_hsic_host wakelock fix (4.2.2 sources!)

I just ignore that % with out signal part in battery stats now because it doesn't make sense. Maybe my signal isn't the strongest and will bounce to edge every once in awhile but it is weird that number is so high. Battery life has been great on Franco r83 so im not to worried about it
[Nexus 4 Android Development] bradm23:
Re: [Kernel][GPL][anykernel] msm_hsic_host wakelock fix (4.2.2 sources!)

Just a quick update regarding my % of signal without coverage. I totally do not think it is registering properly for some reason. I am currently running xylon HD nightly and franco r83 and have 56% battery left, with two hours of HSDPA and 8 hour since charged. Here's the kicker, in battery option in settings it shows that my % without a signal is 24%. There is no way that this could be right and to achieve these types of results.

Maybe this is a xylon HD issue. Might flash modaco tonight and keep and eye on things tomorrow. Just wanted to report my latest findings. I haven't been without signal at all that I have noticed other than the quick switch to edge and back. Every time I have used my phone I have had great signal and was never able to not complete a task due to lack of signal. 24% of 8 hours means I didn't have signal for 2 hours! Cannot possibly be!
[Nexus 4 Android Development] thracemerin:
Are you using the 4.2.2 baseband (.44)? if so, try reverting to the one from 4.2.1 (.33) and see if it happens, I'm starting to think something is wrong with the new baseband.
[Nexus 4 Android Development] bradm23:
Re: [Kernel][GPL][anykernel] msm_hsic_host wakelock fix (4.2.2 sources!)

I will have to give that another try also, I didn't get much use with other radio because I only had phone for two days before it came out. What problems are you suspecting?
[Nexus 4 Android Development] thracemerin:
Well, I'm not sure, but I experienced a similar issue to yours while running the new baseband and the stock kernel, see my post a couple of posts back. It seems there are sporadic reports of other unusual radio behavior on the new baseband where there were no troubles before.
[Nexus 4 Android Development] bradm23:
Re: [Kernel][GPL][anykernel] msm_hsic_host wakelock fix (4.2.2 sources!)

Did u update with an ota or push the ota manually or flashed a rom, new kernel and radio at different times? Wonder how it would be if I had gotten the update "naturally"
[Nexus 4 Android Development] thracemerin:
I flashed the factory images via fastboot. Then reflashed TWRP and CM after that, so it was a completely clean upgrade to the new bootloader and radio.
[Nexus 4 Android Development] bradm23:
Re: [Kernel][GPL][anykernel] msm_hsic_host wakelock fix (4.2.2 sources!)

So I just ended up buying BBS in play store and noticed that under network it says my time without signal was 43 seconds .1%, comparing it to 18% in "time without a signal" in battery settings.

I would believe the BBS stats more since I got good battery life today
[Nexus 4 Android Development] veyka:
Re: [Kernel][GPL][anykernel] msm_hsic_host wakelock fix (4.2.2 sources!)

Cm10.1, newest baseband, new bootllader.

No issues with data freezes on v4, and they normally hit me hard and fast.

I have noticed that on this new baseband (on a kernel without the patches) that at one point the data "response" got really really slow, almost like the stuck issue.

So don't rule out baseband or provider issues.
[Nexus 4 Android Development] thracemerin:
Thanks bud, I appreciate the help. :D
[Nexus 4 Android Development] veyka:
Re: [Kernel][GPL][anykernel] msm_hsic_host wakelock fix (4.2.2 sources!)

Just wish that Google would fix this blasted wakelock for once and for all! ;)
[Nexus 4 Android Development] thracemerin:
Doesn't everyone? It's clear the fix is available to them, but they don't bother to merge it? They added some of the more minor fixes from CAF, I don't get why they couldn't add the whole fix.

Same with the delayed notification on WiFi issue, I don't see a fix on CAF, but they claimed they were going to fix it and instead did absolutely nothing and changed the priority on the ticket to "Future Release".

I dunno about Google these days, as much as I hate OEM skins and closed source devices, you know Samsung, Sony, HTC, etc... wouldn't have left this like this for this long.
[Nexus 4 Android Development] agalvin13:
I completely agree. I feel like Google is over extending it's self and putting all available resources into major feature upgrades like google now but neglecting a ton of small but extremely necessary bug fixes and seemingly standard features. People say iOS is boring but at least they have covered all the small things you expect your phone to do. These types of things would smooth out and improve the entire UX more than getting a new Google now card that tells me my dry cleaning is ready. Not only do we have to deal with not having LTE, but the HPSA+ radio we get kills the battery at an alarming rate. Lovely.

The galaxy s4 or HTC M7 + a custom launcher will likely not have these type of issues and will feel not much different besides the capacitive and physical buttons (ewww). Seems like two steps forward and one step back every time they release a new nexus or OS update.
[Nexus 4 Android Development] franciscofranco:
Oh really, do you know many months Samsung kept releasing software updates and new devices while the eMMc erase hard brick bug was present in the kernel and they didn't give a ****?
[Nexus 4 Android Development] peterperfect:
Re: [Kernel][GPL][anykernel] msm_hsic_host wakelock fix (4.2.2 sources!)

No disrespect man but you clearly lost some points on this one and obviously don't know what you talking about at least when it comes to Samsung.

To add another bit to Franco's, Samsung advertised i9300 as if it supported BT 4.0 (its in the freaking box!). Comes out that their implementation is broken out of the box. They know about it for about 8 months now. Started answering the forums, telling a fix was coming and than subtly started to ignore it. No fix dropped, no word about it. Samsung is scam. Google is awesome, bit obviously has lots of things to work out and yes they could be faster and more transparent on the updating process.
[Nexus 4 Android Development] bradm23:
Re: [Kernel][GPL][anykernel] msm_hsic_host wakelock fix (4.2.2 sources!)

Getting great msm_hsic_host results with latest Franco release that included the fix, currently at 1.4% which is by far the lowest I have seen. I also reverted to the .33 radio for testing purposes

On a side note, now radio-interface is my highest one, is this a normal wake lock for reg phone use?

Thanks
[Nexus 4 Android Development] thracemerin:
Ok, I'll admit to having misspoken about OEMs (particularly Samsung), having previously been a primarily Samsung user I shouldn't have included them in my rant for sure. It was however simply an expression of frustration on my part, not intended to suggest that Samsung or any other manufacturer is without flaws or releases better/less buggy products than those released under the Nexus brand.

It does continue to bother me that Google doesn't seem to be able to fix this bug in the best possible manner (I'll give them some credit for fixing some of the problem) when the code for it seems to be readily available on CAF among other places.

Yeah, and you'll generally get better battery life from a kernel that doesn't use mpdecision too.

radio-interface is normal, its the wakelock held during data transfer.
[Nexus 4 Android Development] bradm23:
Re: [Kernel][GPL][anykernel] msm_hsic_host wakelock fix (4.2.2 sources!)

Does Franco use mpdecision? Isn't that part of project butter with the boost feature?
[Nexus 4 Android Development] thracemerin:
No, I haven't been following his thread that closely but I think he uses a variation of auto hotplug with tweaks that keep the butter without the problems that you run into using the closed source mpdecision binary.
[Nexus 4 Android Development] bradm23:
Re: [Kernel][GPL][anykernel] msm_hsic_host wakelock fix (4.2.2 sources!)

Did Franco implement the same patches that you had in beta 4?

I was getting 4%+ with beta 4 and with Franco I currently have 1.3% which is by far lowest I've seen to date
[Nexus 4 Android Development] thracemerin:
I believe so, yes.
[Nexus 4 Android Development] bradm23:
Thanks for all the reply's! I believe the patches are working great in Franco's kernel. I only got 1.2% wake lock today one all H+ which is amazing. I did revert back to .33 radio for testing but it seems about the same. My battery setting 'time without signal" still says 23% without signal which def isn't correct. I will test out the .33 radio for a few days and then .48 and report my findings in regards to signal and behavior.

Does anyone know an app that will monitor signal for me? I really don't know when I do not have signal 23% of this time, especially since BBS showed .1%.

Is there anyway to whip up a stock kernel with Franco gamma interface with the wake lock fix and a modified mpdecision? I want to try the stock kernel again and see if I can get the 1.2% I got today but miss my colors.. :)