yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] RW-1:
I'm sure MW will bake in a new set as well, as we get everything running ...
[Samsung Galaxy Nexus] terminal13:
Once the gnex starts waving white flags at you do have a planned device to continue development of fml with?
[Samsung Galaxy Nexus] RW-1:
I'm sure we'll all jump on the N6 hehehe, or maybe the red colored ba$tard son the Droid Trubo (which would need some undoing first)
[Samsung Galaxy Nexus] zzpianoman:
To be honest, I think phones these days are way too specced out. I mean who needs 3 gigabytes of RAM on a silly phone? I think the goal should be to make everything run more efficiently on modest hardware - which is what we have to do with our Galaxy Nexus. I kind of miss the days of unbloated software where more emphasis was placed on efficiency. These days it's easier to just add more RAM or a faster CPU than to actually streamline the code to make things run more efficiently. </rant>
[Samsung Galaxy Nexus] Nephilim:
Well after 2 days of using 12/6 FML 5.0 I have to say, it's running pretty great. I did however run into another bug that happens on and off, I seem to not get sms notifications on some of my texts. I'll go into hangouts and take a look and I'll have one or two messages from people and I never got a vibrate or led notification. This doesn't happen everytime but it happens enough for me to consider it a bug because there were a few times when I was wondering why I didn't get a response to something and then came to find out I did 25 minutes prior but never received a notification to let me know. I turned off ambient display for now since I didn't want it milking my battery by randomly turning itself on and off all the time when I had no messages, can't wait for this feature to be running right, I really like the idea of just picking up my phone and having it show my notifications or having the screen light up when a new one comes in, that'll allow me to just turn off the led since lightflow works pretty terribly on 5.0.

Now as for everything else, my battery is great, I was on 10hrs and 1.5hrs of screen on when I woke up this morning and still had about 49% battery left, not only that the battery app now tells you an estimated amount of battery time you have left (which is pretty damn cool imo). Like I said in previous posts, I don't know whether my device just needed to settle, if it was the blocking of certain apps from auto-starting or if my minfrees somehow kicked in through trickster but after the reboot I did yesterday afternoon all of my lag has completely disappeared (besides the phone app taking a bit to open the active call after I dial a number) and I barely get any homescreen redraws, maybe 1 out of every 50 times I return to the homescreen it redraws I would say. Camera does nothing and I really have not tried messing with it much, I honestly don't care about it until the problems are worked out, I can live without it when everything else works so smooth and fast.

Final conclusion, If you can deal with not having a working camera and handle a few miscellaneous bugs here and there I highly recommend using this as your daily driver, every function that needs to work does, chrome, sms, phone, gps etc.

GREAT WORK MW!!!!!!! I CANNOT WAIT TO SEE WHAT YOU PUT OUT NEXT!!!! ...But I will patiently wait for it. ;)
[Samsung Galaxy Nexus] RW-1:
Well, Google writes the code, OEM's spec out the devices. The thing is that KK and Lollipop are already supposed to be able to deal with devices such as ours (Ours is a special case, as we lost TI/OMAP support). It's getting the OEM's to place the newer versions onto the devices, or that they are willing to put ICS or JB on the lower end models because they just don't know any better, or don't want to re-tool for a newer OS than was planned for. I do agree with you though, right now the overhead is nice, but not used - it's like ideally trying to get as much free RAM as possible, well ...

Then you have just pure stupidity - for this I'll blast Google and moto to some degree - N6 encryption - Other than what has been brought up in terms of the Qualcomm chip on the thing not having the licences/drivers to do it - placing that load on the CPU - because you have a fast chip and RAM overhead - was just as I said - Stupid.

The only redemption here is if having the HW do it would violate open source guidelines, but in that case why they can't come up with a chip to do it is beyond anyone's guess.

Just as bad is a possible Intel release of Glass - well, I'll leave that and stay on topic :)

If we had proper drivers for the GNex, you would see less issues on KK and Lollipop that we are seeing now, and MW's work with Lollipop ( :silly: Nephilim's in love .... see above Nephilim's in love .... :p ) is nothing short of amazing with what he has to work with.
[Samsung Galaxy Nexus] Nephilim:
To play devils advocate.... We would have 1.5mb floppies and computers running on 40mhz processors still if people didn't focus on hardware. Software cannot excel if hardware doesn't first, it may seem silly now for more ram or higher clockspeeds on cpu's or 64bit architecture on mobile devices but in 10 years just think of where we will be. What should be happening is that there should be a team focused on streamlining a consolidated OS that runs efficiently on both high and low end devices while there is another team focusing on the evolution of the hardware tech, this is kind of how it is being that Google is supposed to be streamlining the OS where as the manufacturers like Samsung, LG, HTC, Motorola etc are advancing the hardware tech. Problem is those manufacturing companies are screwing up the natural order of how efficiently the OS's should be running by putting their terrible skins and bloatware onto their devices, this creates a broken unity between devices. The one thing I think Google should take from Apple is to put their foot down and do away with manufacturer bloatware and custom OS modifications. No matter what people want, hardware will always be evolving and because of that the life span of pretty much any type of computer device will eventually be deemed obsolete regardless of the software/firmware refinements. You cannot run Windows 8 on a 1994 PC, doesn't matter what you do, it will not work efficiently. I've hung onto my Gnex for over 2yrs now because I knew the development community would keep it shining until I saw an upgrade I deemed worthy of taking up the mantle, the Nexus 6 is that device, I will still play with my Gnex until I get a N6 but the lifespan of my device has passed, I know not everyone can afford a brand new device (me being one of them) but you have to move on sometime. Because I can't pay a $700+ pricetag for a new phone I am patiently waiting for the Verizon announcement which will no doubt come with probably a $250 2-year contract for the 64gb edition, that I think is well worth it.

Anyway, I kind of went off on a tangent, all I'm saying is that hardware evolution is necessary and important because without it we would not have the power to develop new software to play with.
[Samsung Galaxy Nexus] RW-1:
No you didn't - 99% of us current rocking GNex users are looking at the N6 like you. correct on all points mentioned.

You and I are awaiting VZ, but I may just let them have it on Edge, slightly more if offered, but nothing to put down either.
[Samsung Galaxy Nexus] Nephilim:
Worst case scenario, this is something those of us on Big Red should keep an eye on:

http://bgr.com/2014/12/03/nexus-6-like-motorola-droid-phablet/

- Qualcomm Snapdragon 810 processor and 4GB of RAM “to showcase the 64-bit feature of that CPU"

- 4,000 mAh battery

- Same 5.9-inch QHD display as the Nexus 6

I will jump on the Nexus 6 the second it's announced for Verizon but if that doesn't happen I will have this device for sure, the 64bit processor really has me intrigued.
[Samsung Galaxy Nexus] zzpianoman:
I do agree that advancements in hardware are necessary and should happen alongside those of software but what I was saying is that I think manufacturers are relying too much on hardware to compensate for bloated and inefficient code. Just imagine how well de-bloated software would run on hardware with today's specs.

You also have to figure that the vast majority of mobile apps, at least the most popular ones, are really glorified spyware designed to harvest and collect all sorts of information and constantly send this information back to home servers. A higher specced phone might obscure this process a bit more, because you would be less likely to notice lag induced by all of that background processing and data transfer. That's really my one biggest gripe about the whole mobile ecosystem - and it is certainly a big one.

That being said, I really do appreciate all of the work that is going in to keeping this piece of hardware still relevant amongst the slew of modern phones with many more times the processing power and RAM. I think it should serve as an example of how putting in a little more work to streamline things and make them run more efficiently can greatly extend the lifespan of a device in a world that is already filled with way too much e-waste.
[Samsung Galaxy Nexus] JamesAutumn:
Thought i would post my report on using 11-16-2014 5.0 of this rom. WARNING: I'm just a phone user not a coder or dev but i thought if not posted already, my list of things i tried would be interesting in the least so it's for information purposes only.

Since i've jumped to JB and KK, sending photos over hangouts or other texting apps has been hit or miss. 5.0 Hangouts works awesome....except for group messages i can't send a single reply.

-Netflix, WWE, Twitch, Veetle, and YouTube do not play video for me each app provides a error message.

-Occasional force closes, probly due to phone memory bottlenecking i don't know proper terms so my bad.

-Social media apps such as Facebook and Twitter have worked better on this rom than any other on my phone so i'm soooo happy about that.

-Play store will crash for me when installing on 4g but on wifi it works flawless.

-Spotify and other radio apps work great

-Camerazoom FX is hit or miss for me, sometimes it will work great with photos and other times it'll force close soon as i hit the take photo button.

-Phone dialer is way sluggish. Tried to make an emergency call when my car broke down and the phone wouldn't dial out for a good minute or 2.

-Battery life has been decent. Due to the other roms i may have been running probly ruined my new battery but i still wanted to report that is hasn't changed the life of my battery.

So far that's my report in the past 27 hours i've been using the phone. Hope it helps others and provides something useful.

I consider myself a lowly tester wanting to contribute my findings. Thank you all for creating roms and helping a phones life enhance!
[Samsung Galaxy Nexus] Rushead:
I've been having problems with hangouts on kk, too. Same as you with the lack of notification on last kk FML. Probably a hangouts issue, not necessarily 5.0 I would guess.
[Samsung Galaxy Nexus] Nephilim:
I would suggest trying the current version (12/6) posted a few pages back. ;)
[Samsung Galaxy Nexus] MWisBest:
this this this this this this this this this this this this this this this this this this this this this this

Also, regarding ambient display: there's currently no support for it just showing when you pick up the device. This requires a certain kind of sensor that we don't have. I am however fairly confident that I can leverage our existing sensors with just some new code tacked on to it, similar to how I magically added an ambient temperature sensor that previously didn't exist.
[Samsung Galaxy Nexus] Nephilim:
Honestly, I don't mind ambient display doesn't show when picking up the device, I would just like it to work with incoming notifications. Like I said previously, I have it turned off now because it just kept randomly turning itself on over and over with no actual notifications while I had it sitting on my coffee table, if there is any way you can fix that and get it to turn on with all incoming notifications that would be awesome.

As for the "charging" notification sticking on the bottom of the lockscreen after the device is uplugged from the microUSB, I think you might be able to just tweak the how it senses when it's plugged in or unplugged possibly. What I mean by this is if I slowly unplug the chord (I mean really slowly) the "charging" notification will disappear but when I just take the chord out normally the word sticks on the bottom of the lockscreen 90% of the time. This makes me think the device is not always catching that the phone has been removed from the charger. And just so this isn't asked, my device is only about 7 months old because I had to have my last Gnex replaced and the microUSB port has no issues, I know this because on 4.4.4 plugging it in and unplugging it work perfectly. The other reason I think this has to do with some sort of sensitivity is because if it were a microUSB port issue then it would be having trouble connecting where as with this issue the device plugs in, charges, shows the proper led light etc, it just "charging" notification just doesn't go away a lot of the time.
[Samsung Galaxy Nexus] GaNkSTar:
Not sure what the deal is and sorry if this has already been reported but I notice that my selection in preferred networks doesn't stick
[Samsung Galaxy Nexus] MWisBest:
This is fixed in the test build linked a few pages back. :)

(Although there is still a very minor issue with it, but it's only a visual thing; the selection does stick now.)
[Samsung Galaxy Nexus] jguerdat:
Haven't seen this mentioned so here goes. Every browser I've tried crashes when pushed even a little, such as opening a page and trying to scroll while it is still loading or by selecting something on the page so it has to finish what it is doing so it can perform the new operation. You can almost see the constipation for several seconds and then you are blown back to the home screen or whatever app you were using to call up the browser (I am subscribed to various threads here so use gmail to go to the new posts). I have used the stock browser, which seems to work best, Chrome and Firefox. It does this on all 5.x builds and various Gapps. I am guessing it is memory related.

Bug? Am I doing something wrong?
[Samsung Galaxy Nexus] sagara.sandaru:
Hope you're using the latest build.. Install kernel tweaker app from the play store and change the 'low memory killer' to Aggressive(which is less aggressive than stock settings) profile. I tweak only EMPTY_APP to around 170mb from 128mb. I use these settings and this ROM is much more smoother than 4.4 for me..

Only bug that annoy me is audio glitches when playing music. This only happen when I'm opening an app or switching between apps. [MENTION=3390093]MWisBest[/MENTION] let me know if you want any logs related to this issue. And thank you for all your hard work. [emoji4]
[Samsung Galaxy Nexus] jguerdat:
Yup, latest build. Well, this is getting me somewhere. Just got a Chrome isn't responding error rather than blowing out. V-e-r-y s-l-o-w responding but at least not crashing. More experimentation needed. I'm not sure why it would be fine for you but still have issues with me. The phone is actually just my bedside clock that I putz with so not much is loaded.
[Samsung Galaxy Nexus] sagara.sandaru:
Latest versions of Chrome didn't play nice with my Gnex.. Even on KK. That's why I'm using an older version(v34).
[Samsung Galaxy Nexus] RW-1:
I had left Ambient display off figuring it wasn't going to have the HW to support it for what it's worth ....

Also, here:

http://www.androidpolice.com/2014/1...store-with-support-for-android-5-0s-new-apis/

I think you guys should test it out, if possible .... Update - NM, needs OEM Drivers ...
[Samsung Galaxy Nexus] jguerdat:
Hmph. Not finding any values that make things work well. Some settings work "better" but nothing usable. The best I can do is to wait until the page loads completely which slows things down a lot but seems to work.
[Samsung Galaxy Nexus] Nephilim:
Really? The newest version of Chrome is the only one that has worked without insane lag for me, the build right before it and all previous would either lock up or run so slow I got mad and just battery pulled my device. This new update seems to be a very nice step in the right direction.
[Samsung Galaxy Nexus] sagara.sandaru:
Yes really for me v34 was running smoother than the latest materialized version since KK. Does latest version run smother on fml 5.0 too?
[Samsung Galaxy Nexus] Nephilim:
Yep, it still has it's occasional lag and once in awhile it hangs on loading a webpage but it's waayyyyy better than any past builds I've used. Every other version of Chrome before this one always hung to the point of the little window popping up asking me if I want to close the app or wait. Give it a try, if it sucks for you then you can always revert back to an old version. :)

P.S. I'm not a fan of the way new tabs are merged with the recents menu and found out you can turn that off in settings, just for anyone that feels the same way as I do. :)
[Samsung Galaxy Nexus] jguerdat:
That's essentially what mine is doing with ANY browser. I just tried disabling and uninstalling things I don't use (books, etc). Maybe I effed up my installation but I freed a bunch of memory and initially seemed better. I will know soon enough.
[Samsung Galaxy Nexus] sagara.sandaru:
I used it for few days and came back to old version yesterday. Only now it's usable for me.
[Samsung Galaxy Nexus] Nephilim:
Little taste of something that is soon to come, I assure you all it's running beautifully but not ready for primetime as of yet. Do not ask Smitty if you can have it, he will be releasing a Beta as soon as it's up to his standards. I just had to tease a little. ;)
[Samsung Galaxy Nexus] RW-1:
Well we have confirmed what ive always have known, you are a tease!

Word is: Nice. :)
[Samsung Galaxy Nexus] MWisBest:
OEM drivers? I suppose that'd be a problem if the camera stuff is all closed-source...
[Samsung Galaxy Nexus] Nephilim:
I forgot to mention, I've received about 6 different MMS messages over the last couple days, some on Wifi and some on 4G but neither with any issue, one of them required me to manually select to download it because it didn't do it automatically but that was the only bug I encountered. Just thought I'd share. (Using FML 12/6 version)
[Samsung Galaxy Nexus] jguerdat:
Welp, deleting a punch of apps (preinstalled as well as downloaded) has pretty much solved my browser problems. Still binds up a little but not nearly as bad. It's obvious (to me, at least) that it's a memory management issue. The next update will require reflashing Gapps so I'll just have to see how well it does and start removing apps again if it's still a problem.
[Samsung Galaxy Nexus] RW-1:
I misread that, here's what they had in the post: "Update: The new API also requires OEMs to update drivers, which some have not done, annoyingly. You'll only see the new features on the Nexus 5 and Nexus 6 right now."

so not sure, I still believe we can try that app on 5.0, but ...
[Samsung Galaxy Nexus] Nephilim:
Guys, those of you having trouble with receiving notifications on hangouts lately from the play store download should give this a try. It's been working much better for me.

http://www.apkmirror.com/apk/google-inc/hangouts/hangouts-2-5-81636427-apk/

I will say though, I'm pretty sure hangouts isn't the only culprit for missed notifications, I've had about 4 or 5 emails that I was never notified about in the last few days also, I'll click the power button and see an email on my lockscreen but I never received a vibrate or led notification. I'm wondering if this has to do with the fact the Nexus 6 does not have a notification led and that Google might be trying to do away with that and rather use Ambient Display.
[Samsung Galaxy Nexus] urphonesux:
Have you seen this?

http://www.xda-developers.com/android/google-nexus-6-notification-led/
[Samsung Galaxy Nexus] dbt816:
Finally had the time to sit down and get the 12/6 build loaded along with bsmitty's beta kernel. So far, besides the camera issue, the only things I've noticed are that Titanium Backup doesn't seem to be able to freeze apps and there is a little bit of lagging from time to time. Darn good for all beta software! :D

One question... where is the setting to turn off the LED when the battery is charging? I can't seem to find it.... maybe it's not in the settings app yet?
[Samsung Galaxy Nexus] Nephilim:
I'm aware of the hidden led, it is not active natively and only glows green or red so its quite useless. I have grown to love Light Flow but with that LED it would be useless, also, ambient display is actually really a great integration if we can get it working properly on the Gnex. :)

You should probably read the last few pages of the thread. The led cannot be turned off but light flow will override it when the screen is off. Titanium Backup works fine if you disable the superuser in settings and download SuperSU instead. ;)
[Samsung Galaxy Nexus] dbt816:
Yeah, SuperSU lets TiBu work perfectly :)

I setup Lightflow to only let the notification light flash for a minute and then turn it off. It goes right back to the battery charge light when the minute expires. I'll keep messing with it... this is my first time to play with Lightflow
[Samsung Galaxy Nexus] Nephilim:
I have it set to blink green while charging and turn green constant when fully charged. The only time you see the lollipop stock led lights is when the phone is awake on the charger. :)
[Samsung Galaxy Nexus] p34rp34r:
It's true the LEDs do nothing out of the box, but I just wanted to point out that it actually is red, green, and blue. TricksterMod can control the 3 color LEDs for a few limited situations, like "default-on" (basically always on), wifi on, usb plugged in, charging, etc. I do agree with [MENTION=2853378]Nephilim[/MENTION] though, once you have a properly working ambient display, you don't even notice the LEDs aren't working.

Edit: wow, that picture is horrible. You get the idea though...
[Samsung Galaxy Nexus] rester555:
Well it's been a long way coming and I can wait no longer. I just got a nexus 6 coming from a galaxy nexus. This change is going to be epic.
[Samsung Galaxy Nexus] RW-1:
Well I KNEW that VZW 13th release announcement would be vapor ... WTF is wrong with thise idiots, my opinion is;

1. They'll announce they will allow it but you have to get elsewhere.

2. They'll sell it adn we'll have a ton of crap in the OEM partition to remove.

3. We'll hear nothing until March.
[Samsung Galaxy Nexus] Nephilim:
Yea, this is really beginning to piss me off, I cannot afford $700+ for a phone and I'm getting real sick of Verizon pulling this crap just because they can. I get it, Verizon has the best connectivity on average in the country but that is no excuse to keep your customers waiting for a device I'm sure quite a lot of people want. I have been holding out since my contract ended in August. If they indeed stuff the device full of Verizon bloat it'll be a stupid choice on their end because anyone purchasing this will most likely be aware it's a developers device and immediately root and remove everything. What I'm expecting is a large ugly "Verizon" logo across the top or bottom bezel of the front of the phone, they seem to really like doing that now days.
[Samsung Galaxy Nexus] RW-1:
Right with ya buddy.

The thing I love is that for those with the logo thing, or more specifically, going for the thinnest and lightest phone - the first thing you do is slap a case on that sucker - there goes your thinness and Lightness hehehe.

Maybe after Christmas when they realize no one really wants a locked down turbo, at least from our caliber of Android user. Not knocking it, I figure if it were unlocked and not exclusive to VZ there would be plenty going to that instead of the N6 - those who wanted all that in a slightly smaller package.