yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] archibald_schlick:
Build JSS15S

Android AOSP 4.3 Build JSS15S 26.07.2013

Compiled on my Mac and cooked with dsixda's android kitchen.

It is the newest branch "android-4.3_r2.1", so there are maybe bugs (branch is in development).

This is the AOSP build I compile last night:

AOSP BUILD JSS15S

MD5: ae7e07c9543f7825cf08dd6d10f6bb09

AOSP Builds came without Playstore/ GApps, so you have to flash them manuelly in custom recovery.*

I use the banks ones: Banks GAPPS

Just flash the packages you need.

Important: Only flash GApps for 4.3!!! At first I flashed older ones for 4.2.2 and getting a lot keyboard-fc's.

You need to

1.backup all your stuff (nandroid/ adb pull internal sdcard/ whatever)

2.reboot into custom recovery

3.factory reset/ wipe data

4.wipe cache/ wipe dalvik

5.flash rom/ flash gapps

6.reboot and (hopefully) enjoy it!

I hope it fixes our notification-delay-bug, i am testing it right now on my own device.

Big thanks to:

Google

Banks for his GApps

dsixda for "dsixda's android kitchen"

This ROM is only a test, flash at your own risk!!!

On my own mako everything works for now.
[Nexus 4 Android Development] Rsoub:
Mobile Data gone

Hey guys, I flashed the 4.2.2 version on CM 10.1.2 and now I can't get mobile data. I tried everything, from full wipe and reflash of ROM, checking APNs. I don't know what to do. Can't get any mobile data. Please help!!

Update: I flashed the revert zip and mobile data is back. Freaked out a little there :P
[Nexus 4 Android Development] kelah:
I took .ini from jss15j. For me it completely fixed notification delay on jwr66v builds.

I tried on aosp but I suppose it will work on stock too.

There is flashing zip with it (for zip thanks to kalo86).
[Nexus 4 Android Development] markd0wn:
Looks like the drivers page has been updated: https://developers.google.com/android/nexus/drivers

It says "Last updated July 25, 2013" (was July 24 before).

I'm not sure if the actual drivers have changed since I don't have the MD5/SHA1 checksums for them. However, it now says "Android 4.3 (JWR66V)" and doesn't mention JSS15J.
[Nexus 4 Android Development] thracemerin:
Well that makes no sense since AOSP is JSS15J and that's what those libs are for....freakin Google.
[Nexus 4 Android Development] markd0wn:
Yeah I think they kinda messed up a little on this JSS15J vs JWR66V mess/the kernel thingy, but human errors happen and JBQ barely got any sleep supposedly so it happens.

It will be quite messy for developers when more ROMs arrive and the kernel mismatches become more noticeable. In a perfect world, Google would have pushed an OTA from JDQ39 to JSS15J and one from JWR66V to JSS15J. I bet most non-XDA people haven't even gotten the notification yet and it's not too late to fix this. But maybe developers aren't as important as December missing from the calendar so it's unlikely we'll get a quick fix like with 4.1-4.1.1 (or whatever version that was) and the calendar thingy.

Anyway. drivers might still be identical to what the page had yesterday, the same ones that do work with JSS15J and maybe no change has been made, maybe they just removed the mentioning of JSS15J for some reason due to flooding in groups or something, I don't know. If someone downloaded the drivers before the page was updated we can compare hashes.

---------- Post added at 01:02 AM ---------- Previous post was at 12:46 AM ----------

Apparently the kernel tree has been updated yet again about an hour ago.

https://android.googlesource.com/kernel/msm/+/android-msm-mako-3.4-jb-mr2

https://android.googlesource.com/platform/manifest/+/android-4.3_r2.1_^!/#F0
[Nexus 4 Android Development] thracemerin:
You could check by downloading the AOSP build that's in this thread and pulling the libs to see if the hashes are the same since the ones in that build were pulled last night before this stuff got messy today.
[Nexus 4 Android Development] archibald_schlick:
I try to check the MD5 Hashes and compare them, when I come home later this night. If they are different, I will repo sync and change the drivers and build a new ROM. So we can check the libs and changes. Its always worth a try ;)

---------- Post added at 03:18 AM ---------- Previous post was at 02:20 AM ----------

I checked the MD5 hashes and they are exactly the same I used in my build. But now I noticed one thing: I sync the build JSS15S (branch: android-4.3_r2.1) but used the "older" (but only available) JWR66V (branch: android-4.3_r1) binaries for the Nexus 4. :eek:
[Nexus 4 Android Development] markd0wn:
Before the drivers page updated, it said that the binaries are for both JWR66V and JSS15J. After the page update today, it looks like they simply removed the mention of 'JSS15J' but if as you say the files are the same, the drivers should still be good for JSS15J.

There were also some branch/tree changes as mentioned before to separate the kernels. There's a android-4.3_r2.1_ (with a _) tag for kernel and normal android-4.3_r2.1 tag for the device but it looks like they just re-arranged things.
[Nexus 4 Android Development] thracemerin:
Do you have visual tearing when you scroll on your build? Can you take a screenshot of the Phone Info screen with the kernel info visible?
[Nexus 4 Android Development] archibald_schlick:
When I first flashed it with fastboot yesterday morning, before I cooked it and made it a flashable .zip, I had those tearing artifacts and only "Disable HW overlays - Always use GPU for screen compositing" checked, made them disappear.

I don't know why they are now gone, but in the .zip I flashed, everything accept GPS (not working at all), is running smooth.

I compare it to the other JSS15S build by KALO in android development section, because he used also used branch android-4.3_r2.1.

I attached two screenshots showing the two kernel infos.
[Nexus 4 Android Development] markd0wn:
Yep that's the same kernel as the one in jarjar124's synced build that was made less than 12 hours ago.
[Nexus 4 Android Development] thracemerin:
That includes the patches for the JSS builds, so that means that the blobs are JSS compatible.

Makes me wonder if I can figure out which adreno blobs I need and make a flashable zip for stock with them to update the blobs to work with newer kernels.
[Nexus 4 Android Development] jakejm79:
Not to get OT (or maybe back on the original topic), but is there still the MSM_HSIC wakelock issue with 4.3, or did Google also address that?
[Nexus 4 Android Development] thracemerin:
Haha, yeah it seems much better than 4.2.x to me, I haven't really looked into whether the patches are worth it yet since it doesn't seem to be as much of a problem.
[Nexus 4 Android Development] jakejm79:
Yeah I only checked today, and it seems about the same as 4.2.2 with the fix, but I was on wifi 90% of the day. I do have other random wakelocks that I didn't have before, but overall my awake vs. deep sleep seems similar. Was just curious if anyone else had noticed it was an issue or not.
[Nexus 4 Android Development] jakejm79:
So I have about 1.5 hours of MSM_HSIC wake lock for a 10 hour period today, was away from wifi for about 7 of those. Comparably on 4.2.2 with the fix I would get about 20 mins for the same 10 hour period. So if definitely still seems like an issue.
[Nexus 4 Android Development] markd0wn:
Do you use the stock JWR66V or an AOSP-based JSS15J rom?

I'm not sure if there's even a difference regarding the msm_hsic wakelock between the two, but it's worth checking out (WiFi fix for example is applied to JSS15J but not JWR66V)
[Nexus 4 Android Development] jakejm79:
I'm using a rooted JWR66V build, but I did edit the wifi ini file to reflect the two changed regarding ARP that is standard on the JSS15J roms.
[Nexus 4 Android Development] stevensoaj:
Can you tell me where/which ini file that is?
[Nexus 4 Android Development] thracemerin:
/system/etc/wifi/WCNSS_qcom_cfg.ini
[Nexus 4 Android Development] Kocai:
I didn't have the WiFi notification delay issue when I was using JWR66V. Tested it on my home and work WiFi.

WCNSS_qcom_cfq.ini on /system/etc/wifi
[Nexus 4 Android Development] jakejm79:
Yes it's that file, I just changed the two lines that are different between the two builds. Honestly I didn't check to see if I had the notification delay prior to making this change since I did it in the rom before flashing it.
[Nexus 4 Android Development] jbrizz:
I still have the issue too. I see about the same msm_hisc_host wakelock as I did on 4.2.2, and I'm fairly certain it's affecting my battery. When using 4.2.2 with _mplus kernel it basically went down to nothing and I have amazing battery life on 3G. Now it is fairly crap unless I'm on wifi. I hope it can be fixed in the 4.3 _mplus kernel.

At least the wifi ARP offload bug is finally fixed :good:
[Nexus 4 Android Development] jakejm79:
Yes I hope thracemerin can port the same patches to 4.3, I think it definitely is having an effect on battery life, If I am out for the day (out of wifi) I now have a low battery by the end of the day, previously I would normally still have about a 1/3 left.
[Nexus 4 Android Development] thracemerin:
All the patches from 4.2.2 that I used are in the kernel for 4.3, i double checked this the other day.
[Nexus 4 Android Development] jakejm79:
Really, that sucks, because my wake lock performance on 4.3 is definitely prefix 4.2.2 comparable.
[Nexus 4 Android Development] thracemerin:
Well, let me rephrase, all the stuff I believe actually did something is in. There were a few patches from the 4.2.2 final version that caused the hsic host controller to hard reset at random times resulting in total signal loss for a few seconds at a time, that stuff I don't want to move forward even if it did reduce the wakelock.
[Nexus 4 Android Development] jbrizz:
I have just dirty flashed Show-p1984's AOSP ROM and _mplus alpha 4. Quick test at work got me 4 mins of msm_hisc_host wakelock in 1 hour on 3G. That seems better than using the other AOSP 4.3 ROM I was using before. Maybe something in that ROM was using 3G more? Hard to say yet as it always seemed to be worse when I was moving around, probably due to location services.

Edit: and 5 minutes 23 seconds wakelock when going for a 30 minute walk at lunch time, so that's 15%. Definitely worse than the older 4.2.2 post fix was.

Edit2: added screenshot wakelock during my cycle to work. Only thing syncing is Google account and location services it on, so should be relatively small amount of 3G activity. This is pretty much what the stock kernel was like on 4.2.2 whenever I was not on wifi.
[Nexus 4 Android Development] rycus86:
Hi!

My Wifi performance is really bad. It was this bad on stock/CM kernel on 4.2.2 but I could make it ok with your kernel. Now I'm using CM 10.2 and the performance sucks again.

Aren't the wifi drivers in the current CM10.2 the same as they were on your 4.2.2 kernel? Could it be just some parameters set to different values?

If your kernel did something else than stock CM then have you compiled one for 4.3?

Thanks!
[Nexus 4 Android Development] Ok_Kaleidoscope5109:
So can I understand something properly regarding the msm_hsic wakelock? The issue is taht we're seeing high kernel wakelocks but this is not being reflected in partial wakelocks correct?

So for example over 1 hour of screen off, I'll have 10 minutes of awake time. Usually, checking WLD or BBS, I'll see partial wakelocks of 1-2 minutes total from Gmail, Whatsapp, etc. But it seems most of the 10 minutes comes from msm_hsic. Is this the problem we're all talking about?

I haven't really been observing the deep sleep time on my phone until recently, but then what constitutes an actual fix? If the awake time finally equates to the total partial wakelock time? And that the kernel wakelock time isnt' excessive for msm_hsic?
[Nexus 4 Android Development] thracemerin:
The Nexus 4 has a hardware flaw in that the SoC used is actually a tablet SoC and not a phone SoC, as a result the cellular modem is attached to a USB bus. The msm_hsic host wakelock is held when this bus is active which happens anytime the phone needs to use the cellular modem, on some of the original firmware (4.1.x & 4.2.x specifically) there was an issue where when the phone went into suspend the msm_hsic host controller wouldn't suspend resulting in an extremely long wakelock for no reason, this has been corrected for the most part in 4.3. Keep in mind that the cellular modem has to be active a lot even on WiFi to ensure that you get proper tower information from your provider so that when you receive a phone call your phone actually rings, the wakelock will be increased while on 3G since all the data transactions also have to happen over cellular radio, it will also be increased if you are travelling while on 3G since it has to handle tower handoffs, etc... these things are handled better by SoCs that have internal modems, but the current state of the N4 as it relates to this issue is about as good as you can expect given the hardware limitations, any attempt to make it better would likely result in data drops or connectivity issues.
[Nexus 4 Android Development] Ok_Kaleidoscope5109:
Thank you! Very informative!

Is "sns_async_ev_wakelock" related?
[Nexus 4 Android Development] chrone:
thanks for this! i wish i knew this valueable information before purchased one 8 months ago. hahaha
[Nexus 4 Android Development] MuadDib_II:
Thanks again for the very informative answer, i wish I had 10% of this knowledge ;)

Just a few days ago I decided to update from CM10.1 RC3 to cm10.2 (now with the 20130902 nightly) because the Google Services OTA problem, and since then this msm_hsic_host wakelock is killing all my battery; I just loose 10% in the last half hour:

Total time: 35 minutes

Screen on: 1minute

awake: 27 minutes (24 minutes of msm_hsic_host et 4 minutes of radio-interface, the two biggest wakelocks)

sleep: 9 minutes

Do you think it's normal? With the CM10.2 update I updated also the modem and the bootloader, so I'm starting to think that it might be modem related (at least a little related), as I didn't have it with this intensity and you're saying that it should be better in CM10.2...

Thanks in advance for your help

:good:
[Nexus 4 Android Development] io53:
Poor signal?
[Nexus 4 Android Development] MuadDib_II:
It's not awesome, but as I didn't suffer this much before I thought that maybe the modem may be a factor that contributes to this wakelock...

EDIT: For information, I figured out what was causing my msm_hsic_host wakelock. It was the app BitTorrent Sync. I froze it with Greenify and the wakelock went away (26min/30min to 3min/30min), witch I think is perfectly acceptable :D
[Nexus 4 Android Development] IgnacioZippy:
Great… now I can't even return it to the store (it’s just 1 month old) because it’s scratched on the back, software has been modified and I lost the charger. I think I might not even buy another Android phone ever again because of this flaw.
[Nexus 4 Android Development] thracemerin:
Because of bad hardware on one device? That's a little silly.
[Nexus 4 Android Development] runderekrun:
Is it really "bad hardware"? I am honestly asking because I am still within my window to return mine. I mean when I took my phone off wifi and started driving around yesterday the wakelock showed up and my battery drained like crazy. Kept my phone awake for like an hour and a half. Is this typical? Can I not lessen this at all? If not, how is there not more of an outcry?
[Nexus 4 Android Development] IgnacioZippy:
Totally. But now a lot of devices are Snapdragon-based and I already have a bad perception of them. I don’t know what to do.

---------- Post added at 03:44 PM ---------- Previous post was at 03:40 PM ----------

I’m joining an eventual outcry. How is it that nor LG nor Google did NOTHING about this for almost one year? My phone is overheating and I’m worried, even if it could stand double the internal temperature it reaches, like [MENTION=4303511]thracemerin[/MENTION] told me —thanks again—
[Nexus 4 Android Development] thracemerin:
It's this specific version of the Snapdragon S4 Pro, not all Snapdragon SoCs.

Define overheating, is your phone CPU over 80C? is the battery over 60C? if not you are nowhere near overheating.

msm_hsic_host wakelock itself does not, I repeat

does not

increase battery drain significantly, what does is the things that cause this wakelock to happen, network location, tower pings, mobile data, etc... In isolation, with just the hsic bus active the device might burn an additional 2-4% per day.

#1 battery drainer on any smartphone is Screen, you may not see this if you rarely have your screen on, but under normal conditions it will be #1

#2 3G/4G radio operations, simple fact, the 3G/4G radio burns 3-4x the battery that the WiFi radio does, when you turn off WiFi you should expect higher drain, that's life.
[Nexus 4 Android Development] runderekrun:
Thanks so much thracemerin!

I gather from what you're saying is if I see msm_hsic_host keeping my phone awake too much I need to investigate what app or service is polling my data connection? Phew looks like I don't need to return it.
[Nexus 4 Android Development] thracemerin:
I added a few additions to my post above, but you are always going to get additional burn from the 3G/4G radio.

I'll give you an example, on my XT1058 (Moto X Rogers edition) I do not have the msm_hsic_problem because it's build on a Snapdragon platform with a proper modem inside, but I still get significantly more battery drain (roughly .5%-1% additional drain per hour depending on the quality of the connection) while on LTE or HSPA+ than I do on WiFi, that's life it happens on all phones.
[Nexus 4 Android Development] runderekrun:
I see. So would Nexus 4 be worse then other phones while off the Wi-Fi because of the USB modem (msm_hsic) problem?
[Nexus 4 Android Development] thracemerin:
Yes, but not significantly worse based on my testing.
[Nexus 4 Android Development] IgnacioZippy:
OK, you solved all my concerns, thanks for everything. It’s awesome to have people like you who can help us to learn and save us from silly conclusions. :D
[Nexus 4 Android Development] thracemerin:
Glad I could help, keep in mind too that all the heat from all the chips in your phone is directed out the back of the device away from the display and that the glass back conducts heat better than a plastic back would so it may feel warm or even hot, but this is not necessarily dangerous.
[Nexus 4 Android Development] IgnacioZippy:
I even thought of an aluminium case... but it would absorb all signals, LOL

Anyway, can I try your kernel (http://xdaforums.com/showthread.php?t=2385840), could it help me?
[Nexus 4 Android Development] mko000:
[MENTION=4303511]thracemerin[/MENTION]:

I have a question about wifi on JSS15Q. On 4.2.2, my wifi would stop working as soon as I turned off the screen. In the default configuration of JSS15Q it is almost the same. When I turn off wifi optimization it works, but uses a lot of battery (about 10% during the night with everything else turned off).

Can you please summarize the status of the wifi on JSS15Q for me? Is there a better solution than to turn off wifi optimization?

Thanks!
[Nexus 4 Android Development] chrismalla:
Ok [MENTION=4303511]thracemerin[/MENTION], I showed up because of the msm_hsic_host wakelock keeping my phone awake 1h out of 8 (at night) with mobile data enabled. I quickly read through the last two pages. Am I right when I say that apps and location services are the problem (along with this specific SoC)? Or is it simply a kernel issue since you at first tried to solve it by modifying the kernel. I'm running CM10.2, therefore I cannot flash your kernel. So, even though I know having all location services turned on drains (a lot) of battery, I still have them turned on because I like it.

I guess I'll try having WiFi on all the time instead of 2G/3G, if you don't have any suggestions. It's sad that the manufacturers don't understand that wee want 3000+mAh batteries rather than unnecessary specs, on the other hand, it makes us aware of the importance of energy efficiency.
[Nexus 4 Android Development] thracemerin:
If you have bad 3G signal it can cause the msm_hsic wakelock to be worse as well since it takes longer for all the data (not just internet traffic, but tower information, location data, etc...) To get nt and received every time its necessary to do so. It's almost never a good idea to use 3G when you have a WiFi network available on any phone, even the iPhone burns more battery on 3G than it does on WiFi and you have to give it to Apple, their devices always have superior battery life.

Anything that was in the 4.2.x kernels in this thread to mitigate the problem is included by default in the 4.3 kernels from Google and they behave in roughly the same manner based on testing of my device under the exact same conditions, so there is no need for a new kernel to solve the problem that initially existed on the 4.2.x kernels.

The problem with adding larger batteries is that well....they're larger, and people want thinner, smaller phones so that makes it more and more difficult to jam everything in and still have room for all the other stuff people expect to be in there. The real question here is do we really need 4 or 8 cores in our devices for them to provide the proper user experience, after using my Moto X with its dual core processor for just a few weeks, I can safely say that it is the smoothest experience I have had on an android phone ever (and I'm in possession of a HTC One, Xperia Z, Galaxy S4 (octa), Nexus 4 and others), it also holds its own on even the most CPU/GPU intensive games, and since its a lower red screen and AMOLED the battery life is terrific, I personally think that other manufacturers should begin to think along these lines in the future.
[Nexus 4 Android Development] chrismalla:
Great, yes I can confirm that I got really bad indoor signal with my current carrier (Tele2 Sweden). Most often running on edge at home. I'll check tomorrow morning if the drain has diminished. Thanks!
[Nexus 4 Android Development] jbrizz:
Thanks for the info about the msm_hisc_host, thracemerin. The annoying thing for me is that in 4.2.2 with your kernel I had very low msm_hisc_host wakelock and my battery lasted only slightly less than on wifi. When the phone was left alone all day I saw anywhere from 80 - 85% deep sleep on 3G, wifi was around 88 - 90%. From my perspective 3G was more or less totally stable (as stable as any other phone I've had) and my battery would do a day easy on 3G, even with moderate use.

Since going to 4.3 I can barely even go a day on 3G if I use the phone fairly minimally. Deep sleep is usually around 60% (still 85+ on wifi), even if I barely touch the phone. If I'm traveling around, so moving between lots of towers, my battery absolutely sucks and I may as well not even have my phone, it's dead by the evening and I'm SOL if I want to organise a beer after work. I think this is more than an issue with deep sleep, that much awake time on it's own probably wouldn't kill my battery, but whatever the USB bus and/or baseband is doing is absolutely raping it.

I've tried .33/.84 hybrid radio, .33, .48, .54, .84 radios and I've tried heaps of kernels, they are all the same in 4.3.

I know you said that there was a patch that caused data drops on the 4.2.2 kernel, so is that the only reason I had good battery life back then? Is what I'm experiencing now normal and what you and everyone else expects from this phone? I don't expect you to be my personal bug fixer, so I'm not asking for a solution to this, but I would be nice to know if LG were actually this stupid when they designed the phone or if perhaps it's something my carrier is causing.
[Nexus 4 Android Development] Ok_Kaleidoscope5109:
[MENTION=4303511]thracemerin[/MENTION] is this an issue with the Optimus G?
[Nexus 4 Android Development] thracemerin:
Don't know, but the Optimus G has a different SoC because it has officially supported LTE where the N4 doesn't.
[Nexus 4 Android Development] BuffMcBigHuge:
Has anyone noticed that the phone is always at 384Mhz with this kernel? TricksterMod and Rom Toolbox Lite both say that the device is always running at 384Mhz. I've also notice substantial lag. My max Mhz is set to 1512.