yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] zzpianoman:
Try using 3C Toolbox to set minfree values. This worked for me. The default settings are pretty aggressive, so after I tuned them back a bit, multitasking seemed to improve.
[Samsung Galaxy Nexus] erk1725:
Thank you zz....I tried to mess with minfrees in rom toolbox pro and trickster, but as mentioned, they don't show up in trickster, and they didn't seem to stick or apply in rom toolbox, but I will try again later tonight with the 3C Toolbox as suggested and see how it goes. The most recent 4.4.4 FML runs so good on my phone, I see great potential for 5.0 in the near future! The devs and community here are awesome guys!! I cant thank everyone enough for all the help and quality of work they provide us with!!:)
[Samsung Galaxy Nexus] DroidDioxide:
This ROM is awesome and all, but I am tired of my device losing support from the manufacturer and am switching to Apple. It's also annoying how iOS apps are always ahead and I just don't see Google ever standardizing app design like Apple has. When iOS gets bumped up a version, there are so many app updates. Android goes up and there are only updates from Google really. Glad to see my last days on android will be awesome though.
[Samsung Galaxy Nexus] Zer0_Cool:
3g works

4g works

google camera works

google play music works (couldn't select artist and misc. other things without fc before)

chrome crashes

chrome beta crashes

aosp browser crashes (fc if you go into settings)

Still using this as my daily, very impressed! I'm going back to firefox as that lasts longer without crashing.
[Samsung Galaxy Nexus] erk1725:
I couldn't get google camera to work.....I was using zoomFX like in 4.4.4 I will give it another shot, along with firefox this time
[Samsung Galaxy Nexus] RW-1:
Hmmm. May hold off for now, mainly until memory use gets optimized, for reasons I outlined before. (But I'm backed up in TWRP and soooo ready to pull the trigger, ROM's loaded and GAPPS as well)

Stock camera working for some but not for others ... Could be that particular memory loadout and how the OS is killing off stuff could it not?
[Samsung Galaxy Nexus] erk1725:
Thanks RW......I made a backup last night before restoring my nandroid back to 4.4.4 last night, so I can restore 5.0 whenever an update comes out, and hopefully dirty flash that. I did a clean install of it last night, and this was my plan all along, so hopefully it works out when the next update comes out and I don't have to set everything up again, and Im sure after the next update, I will consider it a DD for me
[Samsung Galaxy Nexus] RW-1:
You're welcome, I'm so ready to flash it.... It also makes me wonder what Google is really doing with AOSP lately, it has to be driving the Dev's crazy, and that's even for devices slated to receive the new OS.
[Samsung Galaxy Nexus] zzpianoman:
Google Camera opens for me but crashes immediately after I take a photo and when I try to restart the app, it can't connect to the camera at all. Camera 360 or Camera Zoom are the only apps I've used that are able to actually take a photo - but the photos are grainy and very poor quality (not focused). Also, none of the barcode scanner apps work. I would use this as a daily driver if it weren't for the camera issues.

Also, I mentioned in a previous post that I noticed some of the framework jar files are only 309 bytes - but now I'm thinking that perhaps the code and resources are all compiled into a separate location and the jar file is just a placeholder? This seems to be new with this build, as the previous build had jar files that contained all of the necessary code and resources and I was able to pull them, decompile into smali, rebuild, and push back to the phone.

I actually tried to build telephony-common.jar before the latest release to see if that would fix mobile data, but I ended up with a file that was only 309 bytes, so I figured something went wrong but couldn't figure out what exactly.
[Samsung Galaxy Nexus] RW-1:
You've been doing great IMO, I only have my one phone, so can't really jump on just yet, even though I'm dying here to get on it and try out stuff to help ....
[Samsung Galaxy Nexus] DroidDioxide:
This is so slow
[Samsung Galaxy Nexus] xMoment:
Working, but slow

Clean flashed 11/9 and made a nandroid then restored what I was using before until today. Then restored the 11/10 5.0 nandroid and dirty flashed 11/16 build, Gapps, and SuperSu and now have 4G. Terrific. Fixed the TTS FC message in Maps by changing to Pico. Location wasn't fixing until I went outside my office. No camera regardless of app. I get an image using google camera then an error after it appears to take the photo, "can't connect to camera".

Other things I've noticed: Battery drains fast and takes a very long time to charge (USB). Kernel doesn't (yet) support Fast Charge. Noticeable lag when trying to go home from an app, or launching some apps. Recents is very cool but takes a long time to load. Chrome beta works for me but I don't to a ton of browsing. Not noticing the memory issues/ FCs. All email apps I use work just fine (inbox, gmail, stock email).

It's all very exciting and it's keeping me on this phone for a bit longer. Thanks for all your efforts.
[Samsung Galaxy Nexus] zzpianoman:
Is your battery drain with screen off while idle? Have you checked Alarms and wakelocks? I know with the initial build I had a mysterious gps-lock kernel wakelock that I ended up killing manually on boot (echo gps-lock > /sys/power/wake_unlock) but that seemed to go away with the most recent build. Battery life was actually pretty good for me on this latest build (on par with a heavily tweaked kit-kat ROM). I did notice a somewhat abnormally high CPU load which usually happens when handing off from 3g to LTE (rild and netd seem to be the biggest culprits) but this is also prevalent in Kit Kat ROMS due to the poor RIL support for our particular hardware. Overall, mobile data connectivity with this ROM is right on par with ShinyROM on 4.4.4. Omni 4.4.4 seems to give the most reliable data connection. I'm not sure what they're doing differently, but I'm sure those fixes can be applied to 5.0.
[Samsung Galaxy Nexus] RW-1:
A few weeks ago a member on RW with shiny compared and updated our APN's on Shiny for handoffs, for me and a few others it worked much better, others not so well. It hasn't yet been incorporated into the ROM because BWG is busy at the moment with life. :)

I'm sure we'll nail these down, just takes time ....
[Samsung Galaxy Nexus] zzpianoman:
I did some investigating, and it looks like the APN file on Lollipop has more fields such as MTU - which is pretty interesting. We will have to look further into this.
[Samsung Galaxy Nexus] RW-1:
I knew it! :)

I can only speak for myself, but on Shiny until we compared APN's for current AOSP and what the ROM had, handoffs between 3G/4G took on average like 2 minutes (and I mean by the stopwatch).

It has been much better since the change, as far as handoffs, but I still have zones where I know it will go nuts. Of course then the batt goes way down while it tries to find a connection, but you know that song and dance.

Let us all know what you find out etc.
[Samsung Galaxy Nexus] zzpianoman:
The hidden APN list editor in Lollipop doesn't allow you to change all of the available values such as MTU - but if you SQLite into the database "data/data/com.android.providers.telephony/databases/telephony.db", the APNS are all listed in "carriers" and from there you can see all of the editable fields - including MTU.

Edit: Another thing I noticed is that if you ever for some reason wish to change your apns-conf.xml file, the APNS on the device don't actually get updated until you go into the hidden APNs settings editor and select "reset to default" from the settings menu so all those times we were changing our apns-conf.xml file and not doing a full system wipe or manually clearing the telephony.db database, the APNs never actually got updated.
[Samsung Galaxy Nexus] RW-1:
I never fooled with the editor, but I do know when we uploaded the new DB's we had wiped the old ones, so on reboot those new ones were the only thing for it to draw on, so I'm told.
[Samsung Galaxy Nexus] Dirty_Jerz:
The apns in this ROM include the fix I posted over on RW. AOSP apns_Verizon was updated in aosp then merged into one single apns_conf.XML file in the device/sample repo that this ROM uses so we should be all good on the APN front.
[Samsung Galaxy Nexus] RW-1:
Yes, good to hear DJ, you still rule for that in my book. :)

Hope this gets sorted this week, I wanna flash!
[Samsung Galaxy Nexus] Nephilim:
This is feeling like the Baldwinguy Rootz thread all over again hey? I'm just impatiently lurking and waiting for the first DD I see lol.

Sent from my Android 4.4.4 Galaxy Nexus
[Samsung Galaxy Nexus] zzpianoman:
Do we at least have some idea as to what is going on with the Camera? Is it related to the new GPU drivers?
[Samsung Galaxy Nexus] ganggreen30:
A buddy's phone I flashed this on weeks ago camera has been force closing also
[Samsung Galaxy Nexus] KShion619:
Yes, this is the GPU Driver conflicting with the Ducati Chip related to Media Processing and Camera things
[Samsung Galaxy Nexus] RW-1:
Yeah, the camera is an interesting one, isn't it?

They just dropped a new GP Svcs, might be good for Lollipop, not avail yet for my version I have on KK though. 1557022-036
[Samsung Galaxy Nexus] zzpianoman:
ugh more wakelocks to kill! I really wish they wouldn't automagically push Play Services updates without even so much as to informing the user of the update. I understand that it provides a lot of crucial frameworks for the system, but it should still be opt-in or at the VERY VERY VERY least, they should push a notification saying "Google Play Services has now been updated".
[Samsung Galaxy Nexus] ataris_kid:
FYI for those of you doing your own custom builds -- Compiling the public FML code with the following 3 modifications makes for a build with working Google Location Services (GPS and mobile) as well as working Google Backup Transport service (restoration of previous Android installation settings). It even restored the layout of my Google Now Launcher, which I have never experienced before.

https://github.com/MWisBest/android...rameworks/base/core/res/res/values/config.xml

https://gitorious.org/replicant/vendor_replicant/commit/4bb51731bee6a4712e8b191f5c35f10e0149654e

Also, this is the one that will enable Location Services using both GPS as well as the mobile network by default (so that it "just works" -- it was previously set to allow just GPS). Modify the file frameworks/base/packages/SettingsProvider/res/values/defaults.xml as follows:

- Find this line:

<string name="def_location_providers_allowed" translatable="false">gps</string>

- Change it to this:

<string name="def_location_providers_allowed" translatable="false">[B][COLOR="Red"]network[/COLOR][/B],gps</string>
[Samsung Galaxy Nexus] RW-1:
I believe that is the thing about 5.0's new restore thing - it even does your background and icon layout in your launcher, isn't that cool? :)

Might be our last hurrah on the GNex, making use of NFC to allow a new phone running 5.0 or later to grab it's settings, not applicable here though I'm supposing that you selected your current device from a choice, which is the second option (as you can't NFC to yourself updating hehehe)

Is it me or when you look at GP Svc's, you now get a manage section for it and storage? Sounds good because you wouldn't want it setting aside storage for wear if you didn't have a wear device, etc.

Hoping MWisBest can something cooking on the compiler box :)
[Samsung Galaxy Nexus] zzpianoman:
I wonder how soon until we see some useful backports from Lollipop to KitKat. I think it would be great to figure out how they fixed the screen off audio glitch in Lollipop that was plaguing all of the KitKat builds. I don't think it was specific to our Galaxy Nexus because I've read complaints from people who experienced it on other hardware as well.
[Samsung Galaxy Nexus] ganggreen30:
If u have xprivacy for xposed when play services updates u will know because it will ask u to set permissions for it... Bam!
[Samsung Galaxy Nexus] zzpianoman:
No Xposed on ART.

That's why I have to decompile it myself and remove the wakelocks manually.
[Samsung Galaxy Nexus] RW-1:
Hey ZZ, wasn't automatic, I had to grab it from AP, I'm sure the rollout is happening though, sorry :)
[Samsung Galaxy Nexus] Christopher8989:
Just tried the 11/16 version and it's nice, not fast enough for me so i installed DirtyV and Fancy kernels. Both won't boot, just stop at google screen.

I forgot to test gps.
[Samsung Galaxy Nexus] p34rp34r:
yeah, it shouldn't boot. neither of those kernels support the new GPU drivers.
[Samsung Galaxy Nexus] KillerVamp09:
Wow for me this ROM is blazing fast. I must say I cannot honestly wait for it to see the FML optimizations. It does however get sluggish at time but as of now it is DD material. Even more so when battery life gets optimized and we see some Linaro goodness.

Anyway long of the short, great work and please keep it up. You given my Nexus new life and as long as you keep producing builds I'll keep recommending them.
[Samsung Galaxy Nexus] Dirty_Jerz:
packages_services_Telephony

[MENTION=3390093]MWisBest[/MENTION] When you create an aosp-5.0 branch for packages_services_telephony, I have a pull request set up that should fix the mobile network settings.
[Samsung Galaxy Nexus] brose111:
Bugs?

I've got a couple of bugs that I have seen.

1) When I try to open an album in Google Play Music, it force closes.

2) When I try to download anything in chrome, the download is unsuccessful, but it works fine in the AOSP Browser.

3) Memory leaks everywhere (as others have mentioned, also lots of launcher redraws and apps being forced out prematurely).

4) GPS Lock, it takes around 5 minutes to get a lock. On KitKat it rarely took more than 30 Seconds, so I wouldn't think it's hardware.

5) When I lock the screen it flashes max brightness for a split second.

There's a good chance these are just some individual bugs, but I figured I'd let you know the few I have found.
[Samsung Galaxy Nexus] amd_h4x0r:
For a quicker GPS lock, install Faster GPS, set your Region to North America and United States. Then open GPS Status to get a lock.
[Samsung Galaxy Nexus] KShion619:
Is it possible the APN info we need is in the AOSP code for the Nexus 6? Because its using all the formatting needed for lollipop and is on Verizon?
[Samsung Galaxy Nexus] Zer0_Cool:
Tried this, still can't get a lock.
[Samsung Galaxy Nexus] MWisBest:
No worries, I've got the fix ready. :P

1. That's on Play Music.

2. That's on Chrome.

3. There's not memory leaks, the kernel was configured in a 'stable' form where there it takes up some more RAM for itself. The next build will have some kernel features added as well as less RAM carved out. With the test build I did with this yesterday, I have yet to have a launcher redraw. Chrome FCing and whatnot is simply Chrome being a memory hog... Firefox is far superior in this regard. Personally, I use Nightly.

4. If you didn't do a factory reset before flashing Lollipop, remove the "/data/gps" directory(/file?). A first fix after doing this and/or after a factory reset takes a little while as well...

5. I haven't experienced this. Have you tried with and without adaptive brightness?

Did you do a Factory Reset before flashing Lollipop? If not, you'll have to at least remove the "/data/gps" directory(/file?).
[Samsung Galaxy Nexus] Zer0_Cool:
Yeah, I've even been wiping between builds. I'll try to delete the file and report back though.

Edit: not seeing one
[Samsung Galaxy Nexus] brose111:
I actually completely wiped the entire device before flashing, so I'll have to try that /data/gps trick, thanks.

Yeah I've tried with and without adaptive brightness. Seems to actually be a Lollipop bug since it's happening with my Nexus 7. However, your latest version fixed the flash, so it may have been something up with the version of AOSP.
[Samsung Galaxy Nexus] dj-bilbo:
Very happy user of kitkat FML.

Decided to try beta lollipop build! ! woot woot, can't wait

Edit: "Google text-to-speech engine" FC's alot. i don't use it so I don't care but the FC pop-up is annoying.

And for some reason, my phone says i am not rooted when I'm sure I am... weird. it could be a CWM-related issue since I am not use TWRP on my toro.
[Samsung Galaxy Nexus] zzpianoman:
ROM is not rooted by default - flash SuperSU in recovery. Google TTS FC'ing is a known issue but I think someone in an earlier post said they solved it by changing TTS engine to pico.
[Samsung Galaxy Nexus] dj-bilbo:
yup, thanks zzpianoman about pico vs tts. It seemed to have helped.

Although I am getting same issue with gps lock as other mbr stated a few posts above. I also did a factory reset prior to install and installed 'faster gps' & 'gps status' to no avail. Can't find /data/gps file or folder (unless it's hidden somewhere).
[Samsung Galaxy Nexus] zzpianoman:
It should be noted that it seems to take "a really long time" to get an initial fix. My gps eventually started working, but it did take a long time to get a fix. Also, make sure you have location set to device only, as network location doesn't seem to be working yet.
[Samsung Galaxy Nexus] ataris_kid:
I can upload a build with fixed Location Services (which I referenced here) if you would like.. Unless [MENTION=3390093]MWisBest[/MENTION] objects of course!
[Samsung Galaxy Nexus] zzpianoman:
What is the fix? Is it a new library? If so you could just upload the library and that could hold us for now.
[Samsung Galaxy Nexus] oman0123:
Is mms working for everybody else? I haven't seen anybody mention it in a while. I tried the 11/16 build but wouldn't send for me. If you guys say it works Ill give it another go.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] KShion619:
Nope, that aint working

There needs to be a section somewhere for bugs >.>
[Samsung Galaxy Nexus] HaRdC0r3:
hey [MENTION=3390093]MWisBest[/MENTION] when you build your next update do you think you could also build and release a new FML TWRP I feel your recovery is faster than Smitty's....(no offense). I know he was asked to build an updated recovery with F2FS support.
[Samsung Galaxy Nexus] Ken Chan:
Well, I think there's many people who have problems with Google Apps, I know this is kinda advertising my own thread, but I want to help with you guys as I have a Galaxy Nexus(maguro, though!) as well.

Here's the link to my Google App package. I have personally tested this on my Galaxy Nexus with this ROM, and I can tell, apps like GoogleTTS doesn't crash.

And don't worry, after installation, the /system partition still have 78MB.
[Samsung Galaxy Nexus] daytonahemi08:
picking up a nexus tonight looking to run this rom! cant wait for stable build!
[Samsung Galaxy Nexus] ruccarucca:
MMS has been working fine for me.
[Samsung Galaxy Nexus] androidreviewguy:
Me to
[Samsung Galaxy Nexus] ruccarucca:
wifi keeps cutting out, didn't seem to as much on the last build. but then again the gnex has always had terrible WiFi.
[Samsung Galaxy Nexus] androidreviewguy:
No problems here .
[Samsung Galaxy Nexus] zzpianoman:
Let's say I wanted to make a build using the old GPU drivers - how would I go about doing that?
[Samsung Galaxy Nexus] Dirty_Jerz:
I'm have been trying that now for a week. (well...port shiny to L). It's not as easy as you think.

You can do what I have done so far but I still don't have a booting system.:

fork MWiz's repo manifest, device/samsung/tuna, kernel, and samsung vendor. Then checkout the commits before the new PVR build was added, then cherry-pick all commits for those repos to make lollipop work.
[Samsung Galaxy Nexus] zzpianoman:
Ah That's what I figured. I was just hoping there would be an easier way because MW said he booted with the old GPU drivers - so I thought it might just be a simple revert.
[Samsung Galaxy Nexus] Dirty_Jerz:
If he has an easy revert, I would be VERY eager to hear.
[Samsung Galaxy Nexus] zzpianoman:
Or we could just fix the camera issues - but I don't even know where to begin.
[Samsung Galaxy Nexus] braddock84:
FML

is this only for team win recovery project because I can't get the ROM to flash in clockworkmod I've tried onmounting system partition as you say but afterwards it just says installing update but never does. Thank you for any info
[Samsung Galaxy Nexus] quickdraw86:
CWM for toro is far outdated. You really should be using TWRP anyway...
[Samsung Galaxy Nexus] jguerdat:
I had no problem with CWM. I did do a factory reset and started fresh, if that's your issue...
[Samsung Galaxy Nexus] Dirty_Jerz:
If you're having issues with MMS as I was, use Verizon messages app instead of hangouts. It's working well for me on 11/16. I'm sure the issue will be resolved in time as it was on KK.
[Samsung Galaxy Nexus] thetakerfan:
I'm pretty sure its been said the memory issues with app closing are going to be fixed in the next build, anything we can do to the devices in the meantime to help out? Specifically Chrome and stock browser both like to close out pretty constantly. Think I'm going to try firefox for a bit becuase I seem to remember someone mentioning it earlier, anything else?
[Samsung Galaxy Nexus] zzpianoman:
Try using 3C Toolbox to change OOM values. They are set pretty aggressively by default.
[Samsung Galaxy Nexus] mastertech007:
Can you throw out some good working values???
[Samsung Galaxy Nexus] zzpianoman:
I'm actually currently on a KitKat ROM and haven't done too much testing with minfree values on Lollipop, but I think lowering them to something a bit more reasonable should be a good starting point - in particular the foreground App and Visible App settings. Maybe try 48 for Foreground and 60 for visible app and lower them if things continue to close undesirably. Like I said, the default settings are very aggressive and are pretty useless for our devices having so little RAM in comparison to the newer devices.
[Samsung Galaxy Nexus] terminal13:
Have you guys resolved the data issues? There is a working Verizon cm12 port that involves defaulting the APN and manually selecting lte for the vs985. I flashed this on my gnex the other day worked well... Running cm12 on my g3 and its close but has a few kinks.....
[Samsung Galaxy Nexus] RW-1:
We're all patiently awaiting word from OP on that and a new build in the works, I'm sure he'll chime in when he has something for all of us ....
[Samsung Galaxy Nexus] terminal13:
Yeah he is. When I had my gnex full time, mW was on top of his game. FML definitely the best ROM I've run on any phone I've owned. Not trying to badger just thought I'd toss it out and see what came back.
[Samsung Galaxy Nexus] thetakerfan:
Data is working for me on toro since last build without issue. I believe the maguro version still requires manual APN entry (possibly fixed in next build).
[Samsung Galaxy Nexus] RW-1:
I'm hoping MW also has a possible handle on tweaking memory management, the general online blogs are awash with mainstream Lollipop users experiencing the issue on devices with way more ram than we have, it's nice to see them getting aggressive with it, but geez, even those with 2-3Gb RAM are having issues ....
[Samsung Galaxy Nexus] foxdog66:
Anyone having problems with YouTube? Every video tells me there was a problem and won't play.
[Samsung Galaxy Nexus] sm_x:
Same here
[Samsung Galaxy Nexus] shadow_empire1:
same here :)
[Samsung Galaxy Nexus] sagara.sandaru:
This is a known issue.. Hopefully, this will be fixed in the next build.
[Samsung Galaxy Nexus] PainFly23:
For anyone interested in a workaround for the meantime, opening the video in Tubemate then playing it with MX Player works fine. It requires a few more button presses, but it works.
[Samsung Galaxy Nexus] RW-1:
I'm bummed, was hoping for a helping of Lollipop with my turkey yesterday :)

Maybe thru the weekend with leftovers?