yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] PainFly23:
After a bit of messing around I really want to say SystemUI seems to in some way be behind a lot of the random slowdowns and spurts of lag I've been getting. It seems like every time things get unbearably slow, they can be made buttery smooth again by either killing SystemUI manually or waiting until it inevitably restarts itself. I'll try to get a logcat next time I see this happening to find out exactly what's going on, but that won't be too easy. These slowdowns are completely unpredictable.

Really hoping 5.1 addressees this. It's literally the only downside to running lollipop on a Gnex right now, and that's already impressive.
[Samsung Galaxy Nexus] RW-1:
I've had lag to that point as well, what we shoould try is whitelisting system UI for the minfree's, some of our other members should know how to perform that.
[Samsung Galaxy Nexus] jguerdat:
How would you manually kill SystemUI, especially if it's severely lagging?
[Samsung Galaxy Nexus] PainFly23:
I don't know, allowing SystemUI to restart has actually helped in my case it seems like. My minfree for visible apps is really low anyway (25 MB) so I don't think it's restarting itself because it's running out of memory.

Rom Toolbox has a desktop shortcut available for doing things like rebooting and restarting SystemUI.
[Samsung Galaxy Nexus] RW-1:
I'm not going to whitelist it yet, talk on the smitty kernel thread is to try Cool Tool to really verify what's going on, is it Ui hanging, or is the CPU getting locked down to the lowest freq causing it.

I typically have about 150-200Mb free, don't want to think that's it, though I only have to worry about it for a couple weeks then the N6 hits on VZ. Neph is drooling too I'm sure. :)
[Samsung Galaxy Nexus] jguerdat:
Installed the lite version to try it out. The restart widget could be useful to try - if I can get back to the desktop. Even using Naked Browser will cause me to have to pull the battery to gain control.
[Samsung Galaxy Nexus] RW-1:
What's the consensus that 5.1 may solve some of this with better memory management? (I'm on the fence, as we can already adjust minfrees)
[Samsung Galaxy Nexus] Nephilim:
We're gonna need a Smitty kernel on N6 because I can barely imagine the epic tweaking I'll be able to do!
[Samsung Galaxy Nexus] pkgnex:
You all know that ain't how Smitty rolls! Being from The D, he comes in late and does the dirty work nobody else wants to, like f2fs and LP kernels for a 3-year old device!

Seems that most all the "glamour devs" are on the N6 already, though, so when Smitty gets to N6 kernels in about another 24 months, he'll have some good code bases to start from (franco, imoseyon, faux, etc...).

;)
[Samsung Galaxy Nexus] bsmitty83:
Lol that's the truth right there......... , except really I just filled in for all the developers that moved from the GNex to the n4 then n5 , etc. It was more of a necessity than anything. I'll most likely buy a nexus 6 when it comes to Verizon , but I will probably still work on the GNex mostly , since there are so many top developers building shamu , my efforts would definitely be best served here .

But that's not to say I wouldn't ever build a shamu kernel , I know it sounds bad , but I really hate running other peoples kernels . not cause I think I can do better . its more the fact that I CAN build , so why not ? Plus I finally bought a new laptop , waiting for it to get here , core i7 , 12 GB ram , should be nice to compile on [emoji7]
[Samsung Galaxy Nexus] KShion619:
Noticing The Change to the overlay/frameworks/base/packages/SystemUI/res/values/config.xml file today when browsing around, does this mean that the next FML build will display LTE in the status bar instead of 4G? I really want that :P

Commit: https://github.com/MWisBest/android...mmit/26469ce393d54db839ed64a0cddbf5f547abe4fe
[Samsung Galaxy Nexus] MWisBest:
No, that overlay was moved to device/samsung/tuna/: https://github.com/MWisBest/android...mmit/86ea6f276f63a696218a93a04634222b1413fa7f
[Samsung Galaxy Nexus] bvsbutthd101:
It's insane the amount of progress this ROM has made. Great work MWisBest. I haven't tried it yet mostly due the fact I hate having to backup my phone. Hoping to get on this ROM soon seeing it's the only one I feel would be a suitable daily driver for me. I'm currently on SlimKat Build 9 and it's becoming sluggish on me. Probably due to me dirty flashing each update, I seriously do not like backing up my phone.
[Samsung Galaxy Nexus] heXacode:
Hey [MENTION=3390093]MWisBest[/MENTION] found something that might make you hate CM even more...

http://www.droidforums.net/index.php?threads/278989/

That's why I don't run CM's crap on my Nexus anymore. TGFOmni!
[Samsung Galaxy Nexus] hexto:
Tried this today and had an issue installing gapps. I used the link for Lollypop gapps in main post them tried downloading two different versions from the Paranoid 5.0 thread but they all failed to install. Everything else worked great.

BTW, I've been away from this phone for a year but broke my Droid Maxx's screen. This phone is faster than the Maxx and still has more development. I only miss the battery life is my Maxx
[Samsung Galaxy Nexus] bryantjopplin:
Reboot system after you install rom then install gapps
[Samsung Galaxy Nexus] hexto:
That worked, thanks! Been using it for a couple of hours now and it's working great! Just wish it had an option for percent battery icon.

This is my first LP ROM and haven't used my GNex in a year so I have some reading to do before I can become active on this forum. Need to figure out what is and isn't available such as Xposed and Gravity Box.
[Samsung Galaxy Nexus] bryantjopplin:
OK, so the GPS is keeping the phone awake all day. You can get a fix and it will be good to go until you reboot it and have to get a fix every time. Is this like this for everyone.
[Samsung Galaxy Nexus] rajputrajat:
Well I've been getting this since kitkat and thought it's random.

But happened today again and i think i know the reason.

It's happening when after your work is done and you try to disable gps from quick settings before app that is using of closed.

I think that app keeps wakelock on gps and never release it until tile is again on/off.

No need to reboots anyways...
[Samsung Galaxy Nexus] RW-1:
I haven't had issues with GPS, however is it just 5.0 that when one unlocks the phone, each time it takes a short note of your position (icon comes on and then goes off)?

I figured this is new to 5.0 itself.
[Samsung Galaxy Nexus] pkgnex:
Nope, it's not just 5.0!

I've been having the same thing on Shiny 4.4.4 for a few weeks now. Seems to only happen when I travel somewhere more than a few hundred feet and then turn the screen on, as it doesn't occur if I haven't moved since my last screen-on. In a way, that's kind of creepy...

At any rate, I suspect it was one of the Play Services updates or the Google Now changes a few weeks back that started causing this behavior, but that is just an unsubstantiated guess.
[Samsung Galaxy Nexus] MWisBest:
What's kinda frustrating is that the "gps-lock" wakelock only manifested itself after I fixed the Google "Location Services" crap. I'm going to see if I can just forcibly turn off the GPS after boot-up; as long as I run an app that accesses the GPS, the wakelock goes away until the next boot-up, so I'm thinking it's just a matter of the GPS being told "OK I'm done with you gtfo".
[Samsung Galaxy Nexus] dbt816:
No, you're exactly right... it wants to be noticed on boot-up, and it's going to wreak havoc (which I tend to believe was Google's intent) until you issue the GTFO order :) Folks that keep location services on all the time don't have the issue... that says a lot IMHO.
[Samsung Galaxy Nexus] bryantjopplin:
OK didn't want to be the only one that had the problem.
[Samsung Galaxy Nexus] bryantjopplin:
Anyone notice the xposed is available for lollipop now. Well I can't get it to work with our phone yet but hopefully soon
[Samsung Galaxy Nexus] zzpianoman:
You can create a tasker script to run this shell command every time the display is turned off to get rid of the gps-lock.

# echo "gps-lock" > /sys/power/wake_unlock

You may only need to issue the command once at startup, but when I was having the gps-lock wakelock issue, I found that simply executing this on display off will ensure that the wakelock is released.
[Samsung Galaxy Nexus] bryantjopplin:
Is this a command that's being used in the os by another app?
[Samsung Galaxy Nexus] zzpianoman:
nope. It simply releases the gps-lock wakelock. Usually that does not work for kernel wakelocks, but it seems to work for the gps wakelock.
[Samsung Galaxy Nexus] bryantjopplin:
Thanks, just wasn't sure if there might be some other useful commands to find. Can't wait for the xposed to work to get greenify and amplify onboard.
[Samsung Galaxy Nexus] zzpianoman:
I actually just installed Xposed on my CM12 ROM and it seems to work great so far. It's going to require a good bit of testing I'm sure, but so far so good.
[Samsung Galaxy Nexus] bryantjopplin:
I'm using fml and bsmittys kernel and it bootloops.
[Samsung Galaxy Nexus] DR3W5K1:
Ext4 or f2fs?

AFAIK only ext4 works with it
[Samsung Galaxy Nexus] bryantjopplin:
It is f2fs
[Samsung Galaxy Nexus] PainFly23:
For the record, I'm using FML and the FA kernel on ext4 and xposed bootloops as well. I would guess it's some sort of incompatibility with art on this rom; other roms are reported to work just fine.

We'll probably just have to wait until rovo gets around to putting up a few more releases and see if any progress is made. I've got a logcat of the bootloop if anybody with a little more experience than I cares to take a look though.
[Samsung Galaxy Nexus] KShion619:
At what point does it bootloop? after xposed gets installed? or after a module installs? (Havent gotten around to trying it yet)
[Samsung Galaxy Nexus] wmarcin:
Bootloops for me too. After flashing zip and rebooting, the four colored dots just keep flying around.

I tried installing apk first, then flashing zip. And I tried flashing zip without installing apk prior to flashing. Same result.

I'm on FML ROM and kernel that came with the ROM. TWRP 2.8.5.0.

... moto x vzw ...
[Samsung Galaxy Nexus] zzpianoman:
How long did you let it boot? It has to rebuilt the cache so the initial boot after flashing Xposed will take a considerable amount of time depending on how many apps you have installed.
[Samsung Galaxy Nexus] wmarcin:
At least 30 min. Maybe longer. I don't have a lot of apps.

... moto x vzw ...
[Samsung Galaxy Nexus] PainFly23:
I had the bootloop immediately after installing the framework from TWRP. After about 5-10 minutes passed the bootanimation was still going with no indication of the caches being rebuilt.

I've attached a logcat in case anybody here wants to take a look at it. It's mostly just 50,000 lines of ART and dex2oat throwing a fit, but there might be some useful information in there.

Also, has anybody tried wiping cache and dalvik when trying to install the framework? I didn't wipe anything just assuming it would work, but now that I'm thinking about it, giving it another shot with a cache and dalvik wipe might be worth the time.
[Samsung Galaxy Nexus] zzpianoman:
I wonder if the ROM being odexed has anything to do with it?
[Samsung Galaxy Nexus] bryantjopplin:
This was what I was thinking as well. Was going through the files looking at it. Just the each file installed one at a time and the bin and lib files seemed to be the ones affecting (effecting) it. Lol
[Samsung Galaxy Nexus] KShion619:
Not to derail the XPosed topic here, but there's aparently a fix for one memory leak of the boot animation on the portal, any input?

http://xdaforums.com/android/software/arm-arm64-android-5-0-lollipop-t3032247
[Samsung Galaxy Nexus] bsmitty83:
Check out the source , the commits should explain the hackery that is xposed lollipop , personally I'd never use it but to each his own

https://github.com/rovo89/android_art?files=1
[Samsung Galaxy Nexus] bryantjopplin:
For people like me with not much knowledge of what we are looking for, or at in that matter. Could you explain please? Sorry not to sure, I looked. Lol
[Samsung Galaxy Nexus] bradg24:
I just replaced my USB connection super easy.. Check YouTube and follow the steps. Its like building with Legos.
[Samsung Galaxy Nexus] swordrune10:
and..? we've been working like this for a while now.. and I will provide a logcat when asked by the op
[Samsung Galaxy Nexus] swordrune10:
I'm very aware.. thank you for ur wisdom.. back to the topic..

I also while using the chronus app couldn't use the weather portion.. it couldn't find my location and also location was stuck on the system bar.. was able to get rid of it by force closing the app
[Samsung Galaxy Nexus] MWisBest:
[MENTION=4244313]MBQ_[/MENTION] I don't really appreciate you coming in here and kinda acting like this is your thread.

Here's my stance on logcats and related things, which I have explained briefly before:

Requiring a logcat to post a bug is a turn-off to lots of people that otherwise would report something useful. A logcat should only be needed if:

-The developer can't reproduce the issue.

-The developer doesn't own the device he's developing for (which ties into what I said about being unable to reproduce the issue in 95% of cases).

-The developer CAN reproduce the issue, but nothing shows up in his logs to be of help and he absolutely needs logs to track it down.

If a developer can reproduce a reported bug, then there should be no need for a logcat from users. Look at how any other computer program is developed, there's no logcat function yet people are usually still able to report a bug without being ridiculed or something.

Part of what "enlightened" me to this was that I haven't always been on the developer side of things in the Android world, as a user of ROMs I found it ridiculous that a logcat be mandatory to report a bug, especially if it's something easily reproducible.

EDIT: BTW, I was supposed to get my battery today, but UPS ended up loading my package on the wrong truck it seems. It went from WI to MO and then back to WI again. :(
[Samsung Galaxy Nexus] MBQ_:
My apologies.

All comments have been removed.
[Samsung Galaxy Nexus] Rushead:
Got mine today & already seeing an improvement. FWIW, I bought my gnex used with an included 2100 battery. I think it's going bad, though.

Thanks again for the recommendation. :D

Sent from a frequent flasher.
[Samsung Galaxy Nexus] clnzx2:
Got my 3 today :) lol
[Samsung Galaxy Nexus] MWisBest:
LMAO! No wonder we emptied them out so fast!

BTW, something I forgot to mention with the new build is that it includes the enabling of the ambient temperature sensor built in to the BMP180 barometer sensor the phone uses. It tends to be inaccurate if the phone has been used a little as the heat pollution from the rest of the components effects it, but outside in cold weather it's pretty close to the actual temperature, something definitely useful for me up here in Wisconsin! I use the app "Sensor List" in the Play Store for it, it'll show up as "BMP180 Temperature sensor" and it reports in degrees Celsius with an "accuracy" to 0.1C. Just for those who are curious :)
[Samsung Galaxy Nexus] taz1458:
Does this rom have the black boxes with Gmail as well? Trying to see if there is one without it.
[Samsung Galaxy Nexus] dirtsky:
I did. Which i was really impressed how easy they made this phone to take apart. A lot easier than my Incredible 2 was. I actually tore my nexus down for the hell of it the other night.
[Samsung Galaxy Nexus] thetakerfan:
Yes, al 4.4 roms for the galaxy nexus have the same webview issues
[Samsung Galaxy Nexus] know8677:
Switched to the 11/12 version from SlimKat based on the hope that the Re-boots would be a bit better. I did a clean install and used the Slim GApps.

It does seem as if the phone locks up a little less, but when it does it's a battery pull instead of just an automatic re-boot.

I haven't tried to switch to just 3G yet (because that's what I keep my phones on), but I will try that eventually.

One thing I noticed: The keyboard doesn't seem to have the swiping feature. It's probably some setting I'm missing, but I use that a lot.
[Samsung Galaxy Nexus] MWisBest:
I honestly didn't even know Gmail used that. I don't have any black boxes in Gmail at all, unless maybe it's only for e-mails with heavy HTML formatting or something. I don't think I have one of those to test with.

The keyboard is indeed missing the swiping feature, and it's something I plan on adding soon. Again, the freezing was more of a priority for me first. I think I'm going to get started on just using a barebones kernel of sorts, leaving out most of the bells and whistles but hopefully making it more stable. One thing I had noticed is that with CyanogenMod, it appears that the swiping thing is just built from source, and with SlimRoms they have a prebuilt thing for it. I'd think building it from source would be better, but the prebuilt thing would probably be easier in the short-term at least.

In the mean time, I'd suggest getting the Google Keyboard from the Play Store, they updated it a little while ago to have the KitKat theme to it and it has swiping as well.

As for switching to 3G, I'm going to warn you: currently that's what is messing up 4G LTE connections on (most?) 4.4 ROMs. By that, I mean there's no way to get back 4G LTE really at this point. There's a temporary fix I posted a few pages back that apparently can get 4G LTE working again if you do switch to 3G-only, but it has to be done again every time the phone reboots.

Anyways, I appreciate you giving FML a try. The more people that use and test it, the more feedback I end up getting, and the easier figuring out bugs and whatnot becomes. I also end up learning more, which is always one of my goals when doing a computer programming project like this.

To all users who are experiencing lock-ups (I've only had one since the 11/07 build, so now at this point I'm willing to take any logcats you guys might have for this), I'd suggest possibly giving TinyKernel a try; you might still end up with some freezes, but apparently it results in an automatic reboot instead of requiring a battery pull. Do note that with the freezes I've had, the phone is technically still responsive it seems: pressing the power button to lock the screen results in the sound playing for it, so it should still be possible to get a logcat. Now I'm thinking it's more related to the outdated GPU drivers instead of a voltage starvation. One thing I do like about TinyKernel is that it uses the AnyKernel method of updating a kernel, which is in my opinion better for custom ROMs. One thing I might suggest if you use another kernel would be to move or even delete the 00fml file in /system/etc/init.d/ as it's more suited to FancyKernel in what it does, and might cause issues with another kernel. In the next build I'm planning on adding a check to that script to make sure it's on a compatible kernel for it so it doesn't cause issues for other kernels, which would result in me learning something new and was only brought to my attention by the feedback you guys gave on using different kernels, it was something which I hadn't thought about it all! :highfive:
[Samsung Galaxy Nexus] thetakerfan:
If you have pictures off by default you probably wouldn't notice it, I didn't at first until I clicked "show pictures" on an email that was very picture heavy. Some are worse than others.

If you can live without pictures in the email messages it seems fine like that, at least as far as I've noticed.

As for freezes, I don't think I've had any since the new build except one after I decided to try enabling ART with new gapps. Seemed fine and optimized (took like 20 min), then after awhile when I was trying to reboot the phone anyway it got stuck. Haven't had any issues since then though. I also took the recommendation from some others and disabled all the animations in the dev options too, dunno if that made a difference or not but worth mentioning.
[Samsung Galaxy Nexus] ricola1989:
My little thing for getting around the black boxes is quickly hitting show/always show pictures, back out, then reenter the message. Somewhat tedious, but keeps from blacking out our freezing up.

I want to try out that ART compiler but an still feeling out 4.4 and am kinda nervous :S

As for the keyboard not swiping. I thought that was due to devs using AOSP keyboard instead of the Google/custom keyboards. I DL the G keyboard, delete the LatinIME and paste the newly DL'd one to system/app
[Samsung Galaxy Nexus] vitokes:
So what are people using for the kernel on 4.4? I was reading about fancy kernel. Has anyone used it and noticed any changes?
[Samsung Galaxy Nexus] MWisBest:
This ROM is actually built with Fancy Kernel at the moment.

EDIT: While I'm at it, might as well post a quick update on things. I haven't had much time for dev work the past couple of days, but I did get my extended battery on Wednesday! UPS was kind enough to ship it on the priority delivery truck (the one that makes sure all the businesses gets their packages before they close), so I ended up getting it a good 4 or 5 hours sooner than I would've if it went out on the normal truck, makes up for the mix-up that delayed it a day. I just took a knife and cut away at the extra tab bit by bit so that it looked flush, and the fit is alright, in part due to the XDA-themed CruzerLite TPU case I use. It's raised up a bit around the camera (the case helps to minimize this), and removing the back cover isn't as easy as it fits more snugly at the top of the case, but overall I can't really complain. After all, it was free, and I'm sure if it was enough of a problem i could just buy a VZW extended back cover for a few dollars on Amazon or eBay or something. Oh also, the color of it is a tad darker than the phone, and again, the case makes this a non-issue.

EDIT2: I'm working on some dev stuff today, should have a new build up soon. I'm now recommending using the Paranoid Android GApps, I've updated the link in the OP. Their GApps work with the ART compiler, however one thing NOT working with the ART compiler is Superuser, but that will be fixed in the new build later today. I did some testing with the ART compiler and it's extremely fast, feels like I'm using a quad-core Snapdragon or something, absolutely amazing.
[Samsung Galaxy Nexus] MWisBest:
New build up! As usual check out the changelog and flash away. :D
[Samsung Galaxy Nexus] Rushead:
Basically, if [MENTION=4608636]bsmitty83[/MENTION] says don't use it, don't use it. [emoji43]
[Samsung Galaxy Nexus] bryantjopplin:
I understand just wanting to know the technical reasons
[Samsung Galaxy Nexus] hexto:
Been using 5.0 for about a week now and while it's nice and works pretty good, the issues I've had have been pretty bad. The ROM works 98% great. The lag is something that was warned about in the OP and I can live with but I was in need of navigation today and it kept crashing which made for a long trip home. The browser, stock/Chrome/Chrome Beta crashes randomly as do other apps like Twitter.

I am only posting as feedback, not complaints. I always enjoyed the FML builds and I'm flashing 4.4 tonight. Just thought I'd give some feedback from a heavy user's perspective.

All the issues I had are hardware related and not a reflection on the dev. I'm impressed with how well this phone still holds up so I don't want this to be taken in any way as an attack in the builds.
[Samsung Galaxy Nexus] Shadow Death:
God I miss this rom.. I'd love to see it running on my M8. :crying:
[Samsung Galaxy Nexus] zzpianoman:
Can someone verify if in-call mute is working on this ROM?
[Samsung Galaxy Nexus] RW-1:
I'd post that in smitty's thread, as that build was his, not MW's ....
[Samsung Galaxy Nexus] wmarcin:
Sorry to derail this back to xposed. Just wondering if anyone had any luck with this fix: http://xdaforums.com/showthread.php?t=3038758

{{GUIDE}}DEBUGGING Xposed Installation

... moto x vzw ...