yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] AlogarF:
It happened to me too, but only when I couldn't access to my Google account due to a problem with the two steps login. Then I solved with the account and it didn't crash anymore. You can try to not install GApps (but a lot of features won't work, obviously) or install them later, after the first boot (but I don't know if this will solve the problem because I think wizard will appear and crash again).
[Samsung Galaxy Nexus] markitosd:
Personally, I've noticed that performance has greatly improved in 5.1, including multitasking. The only downside is torch tile not working and that brakes down the camera as well, but I see this rom working better than expected.. Thanks to the devs and congratulations for keeping the GNex alive with such success!
[Samsung Galaxy Nexus] alboz83:
Ok today I tried to open camera stock, and not open. After a reboot work again. So the camera problem are the same. For the rest it's awsome
[Samsung Galaxy Nexus] sudeepbaral:
Thanks! I flashed only the Rom at first.. booted into the rom then flashed Gapps later.. It worked...
[Samsung Galaxy Nexus] adamgraver:
Wow..

Wow, this ROM really flies now.. Especially with the animations turned off!
[Samsung Galaxy Nexus] AlogarF:
Nice, you're welcome.

I tried with no animation and it is very fast. I was wondering if with more optimizations our old mate could go better with animations, 'cause I think at this point this is the "problem", the challenge, beyond the known (few) bugs. But even now they're not really bad!
[Samsung Galaxy Nexus] ashish__s:
I seem to be receiving every text multiple times (usually twice). I'm not sure what's going on but thought I'd share.
[Samsung Galaxy Nexus] asheenlevrai:
How do you turn off animations?
[Samsung Galaxy Nexus] AlogarF:
Go to Developer options and search the 3 animation options that allow you to modify the speed and disable them.
[Samsung Galaxy Nexus] asheenlevrai:
I forgot to hit the build number 7 times! What an idiot logic-less dumb unintuitive user I am ;)

:confused:

Thanks :good:
[Samsung Galaxy Nexus] eternal70:
Okay so 5.1 is definitely awesome. Smooth animation in many things, great speed. For batteries, it's very good with R11 and ondemandplus. But unfortunately the battery will great only with wifi. Seems mobile data is a great battery drain since KK :(
[Samsung Galaxy Nexus] carguy303:
Glitching in video

Does anyone else have video glitching and artifacting in apps like vine and Snapchat? It seems to only happen on videos encoded on an iPhone because some vines do not have the issue and all Snapchat videos taken with other android phones work.
[Samsung Galaxy Nexus] zzpianoman:
This seems to only happen when the video is played using the hardware decoder. I used an Xposed module that allows you to save snapchat videos, and when played with MX player using software codec, the videos play perfectly.
[Samsung Galaxy Nexus] carguy303:
Ok well good to know at least I'm not the only one that this is happening to
[Samsung Galaxy Nexus] zzpianoman:
Honestly, I didn't think much of it until I saw your post. Then I went and tried to play the saved videos using MX player, and they played just fine. If you can somehow force Snapchat to use the software codec, they should play within the app itself. I looked at the preferences keys for Snapchat but didn't see anything relating to codec usage - only supported video resolutions for the encoder.
[Samsung Galaxy Nexus] carguy303:
In MXPlayer H/W decoder doesn't even work for me. H/W+ only has audio at least in network streams.
[Samsung Galaxy Nexus] zzpianoman:
Ah, well then if you can somehow get the snapchat videos to save, you should have no problem viewing them in MX player.
[Samsung Galaxy Nexus] BfstMtn:
Wow. Thanks, [MENTION=3390093]MWisBest[/MENTION]! This is so much better than 5.0, it's insane. Been running it for today and it doesn't seem to get laggy over time like earlier builds. Chrome and Facebook (the pigs) are usable. Memory management is just way better.

A few minor bugs still. Mute call doesn't work. The speaker 'pop' is still there. Face unlock crashes on setup too.

Edit: I can set up a trusted place but it doesn't actually seem to work.
[Samsung Galaxy Nexus] MWisBest:
Good news: offline charging is fixed! :) Will be in the next build.

Oh there's definitely room for improvement with optimizations, these 5.1 builds don't have the usual FML optimizing done yet. I wasn't able to do a lot with 5.0 in this respect because, well, it was a lagfest to begin with. But 5.1 should be on FML 4.4 level performance soon.

Mobile data is always a huge drain for the Galaxy Nexus, and is where nearly every complaint in regards to battery life with it stems from. This is why Qualcomm's Snapdragon is dominating the smartphone market I think, it's not about its speed, it's the modems inside of it. Personally, I turn off mobile data unless I'm actually using it.

Will check into this, thanks.
[Samsung Galaxy Nexus] nachiket_xda:
This is what I was going to ask. You answered before that.lol
[Samsung Galaxy Nexus] Djalaal:
I understand that trying to activate the flashlight tile still makes the whole camera API bug out until reboot. I believe [MENTION=4986658]freshgiammi[/MENTION] fixed this issue in his AOSP ROM? I could be wrong...

You... used an Xposed module? You mean to say you're using Xposed on FML?
[Samsung Galaxy Nexus] zzpianoman:
Nope...different ROM. Sorry for the confusion.
[Samsung Galaxy Nexus] BfstMtn:
Tried setting up a bluetooth trusted device. I can select a device, but the phone stays locked. So it seems like none of the smart lock features are currently working.

I also had google backup crash again on a clean flash -- crashes right after selecting account. Had to switch back from local temp backup from terminal. I've never had this happen on any rom other than LP FML. Kind of annoying but easy enough to fix.
[Samsung Galaxy Nexus] revanmj:
I also noticed that. It doesn't always happen, and times between receiving "doubles" differ - sometimes they come at the same time as the original and sometimes even few hours later (yesterday I got all messages again after 3 or 4 hours).

I also found other bug - apps list in the notification settings (Settings > Sounds and Notifications > Apps notifications) sits on a loading screen forever. I left it for a few minutes and it was still "loading".
[Samsung Galaxy Nexus] NightShadow02:
certainly much faster and responsive than the 5.0 build. inverting color doesn't seem to work yet (trying to save some battery power) battery drains fairly quickly (expected due to the reasons you've mentioned in a previous post) camera does go crazy if you try to use the flashlight tile (didn't know it was the flashlight tile causing camera problems until another poster mentioned it) no other issues to report so far, the giffy video playback problem which i had in 5.0 is gone too :)
[Samsung Galaxy Nexus] michierusama:
About Snapchat glitch

Just to add im on cm11 m12 and im also having the green video glitch in snapchat so it's not Just for lollipop. I stopped using snapchat after that lol. And well I'll be patiently waiting for cm11 m13 and after lollipop gets better I'll upgrade.
[Samsung Galaxy Nexus] CoDe LaZaRuS:
Switched back to 4.4 around 4 months ago due Memory leak issue and hence Lag [emoji20]. Is the lag still there. I'm itching to switch to lollypop [emoji2]
[Samsung Galaxy Nexus] BfstMtn:
I did the same. I found LP 5.0... inconsistent. It'd be quick and responsive then so laggy it was barely usable or unusable. At least once a day, I'd have to pull the battery-- sometimes a few times a day. This release is so much better than earlier builds. Only been running it for around 24 hrs so far though. Few bugs, obviously, but it's mostly minor stuff.
[Samsung Galaxy Nexus] Namautoenx:
Why does it like that? Anybody same? How to fix it?
[Samsung Galaxy Nexus] alboz83:
Oh yes you are right!! I tried now and i can't play videos on youtube, never. [MENTION=3390093]MWisBest[/MENTION] problem with HW decoder?

EDIT: ok yes HW decoder don't work. I can't play videos with Mx player, Gallery, QuickPic and also, after app FC, camera don't start
[Samsung Galaxy Nexus] Djalaal:
As someone who has been on Lollipop ever since the early FML November builds, allow me to tell you 5.1 is indeed an improvement.

How much of an improvement remains to be seen. I'm only running it for the past 4 hours, so I can't tell much yet for the sake of avoiding placebo. But till now, it SEEMS slightly better.

What I DID immediately notice, because it had always bothered me in the 5.0 builds, is that the system (settings>apps>running) correctly reads free memory again (again, as in, like KK). Perhaps as a result of that, I see more apps being cached, which should improve multitasking.

The bugs from the 5.0 builds are still there (but not for long!):

No offline charging (fix available).

Charging text stuck on lockscreen (fix available).

Green bar on the leftmost side in recorded videos.

No native fleshlight. I mean flashlight (fix available?).

Multi-part SMS (didn't it work in 5.0?)

What works (I tested):

SMS, Calls, GPS, WiFi, Data, High Accuracy Location, Camera (photos), HW Playback (YouTube too), etc, etc.

On a different note,

I found that video recording does not like it when you turn off FSYNC (Full Auto R11).

System apps sure use a lot of RAM in LP!

Xposed and FML's optimizations don't play well together.
[Samsung Galaxy Nexus] NightShadow02:
I'm currently finding it impossible to send sms's. I can receive them fine but I seem to be unable to reply. Mobile data is working as well.
[Samsung Galaxy Nexus] Djalaal:
Have you sent a multi-part sms before? I find that when you try to send one, it doesn't, and at the same time makes you unable to send another sms until reboot.
[Samsung Galaxy Nexus] NightShadow02:
Yeah my first SMS was a multipart SMS. I then tried sending a single test SMS to someone else and it doesn't work too like you observed on your device. This needs a-fixin :)
[Samsung Galaxy Nexus] cartman333:
Youtube is still like the camera, it works for a while then it stops playing videos and you have to reboot to get it back. Otherwise great ROM the speed and the multitasking has improved a lot. If these minor issues will be sorted out, i think it's a perfect rom.
[Samsung Galaxy Nexus] Djalaal:
Now I'm not too sure everything is alright with 5.1's ram management... Interesting free memory value.
[Samsung Galaxy Nexus] alboz83:
That's true
[Samsung Galaxy Nexus] thomstrack:
In my tests, the system was always using 400 ~ 500 mb of ram, leaving the direct locking system.
[Samsung Galaxy Nexus] zzpianoman:
The two are actually related: I believe that Youtube stops working when mediaserver crashes - which is caused by the camera failure. Camera crashes mediaserver, which in turn screws up hardware decoding.
[Samsung Galaxy Nexus] Djalaal:
[/COLOR]

Tested this, and it doesn't seem to hold true entirely. I have no problems at all with YouTube or HW Decoded Videos. Even when I crashed my camera using the flashlight toggle. Although when I crashed my camera, my mediaserver didn't crash.

Maybe it's because I use AwesomePlayer (was on by default), instead of NuPlayer?

*EDIT* Nope, it works with NuPlayer as well.
[Samsung Galaxy Nexus] ykom:
For the first time, controls for headsets works fine on FML 5.1. It's a kernel!
[Samsung Galaxy Nexus] Djalaal:
Care to elaborate? Cause I've bought a BT headset today, and I'm having some difficulties.
[Samsung Galaxy Nexus] ykom:
Well, I guess that it depends what you have.

I use;

Logitech BT(just pairing)

Audiotechnica(wired)

They work fine. Never worked with 5.0.
[Samsung Galaxy Nexus] cartman333:
Little OT:

(but good advice [emoji14])

If someone loves Nova launcher and material design then install Materialnova it's really nice and fast with a tons of costumization.
[Samsung Galaxy Nexus] nachiket_xda:
memory leak is still there in 5.1, they say :(

https://code.google.com/p/android/issues/detail?id=159738
[Samsung Galaxy Nexus] madhavs:
Go through #35

https://code.google.com/p/android/issues/detail?id=159738#c35

http://www.androidpolice.com/2015/0...fixed-internally-no-timeline-for-release-yet/
[Samsung Galaxy Nexus] Younex:
The #1 post is outdated and there's no new changelog :/
[Samsung Galaxy Nexus] billyx1:
The Wifi-Connection seams to work perfectly with the new FML 5.1. It was ofeten not working with 5.0 but now it is perfect.
[Samsung Galaxy Nexus] nikodr:
i am on r12 kernel.I tried to install busybox as fml 5.1 does not have it.

First i tried to use trickstermod but said i needed busybox i hit the button to go to playstore and download the busybox that trickster told me,but when i installed that application while it said that it was installed,trickster was not working.

So i reboot,the application still says that busybox is installed,from terminal i can use it but trickster does not start.Then i go to app i uninstall it,and i press the button to install it from recovery (it had an option for that).

I go to recovery installation is ok.Then i had to do 3 battery pulls,because there were bootloops,first time it crashed on the animation,and the other 2 times it crashed on the android logo.Third time i get to the upgrade android screen where 82 apps are updated.After that trickster works,and busybox seems to be ok.

Why did that happen?FML 5.1 was freshly installed no dirty flashed or anything.
[Samsung Galaxy Nexus] eternal70:
You can use synapse tho if you don't have busybox binaries
[Samsung Galaxy Nexus] erk1725:
+1
[Samsung Galaxy Nexus] Keyvannn:
Please give me the 5.1 link

I cant find it

Sorry for my bad english
[Samsung Galaxy Nexus] AvidPhisherman:
Post with 5.1 located here.

Tip: the Most Thanked section on the right-hand side is pretty handy for finding that stuff! Search function too :)
[Samsung Galaxy Nexus] nikodr:
We need something like a dark theme and google made 5.1 again to be white.

Something like this

http://nexus5.wonderhowto.com/how-t...s-5-with-darker-material-design-look-0158907/ it is for nexus 5 that gives dark.Could someone make something like that for nexus?

I dont really like the white theme in settings i want black.Am i the only one?
[Samsung Galaxy Nexus] AvidPhisherman:
Probably best to search/post in the Themes subforum for that kind of thing.

You could also try a different launcher. I use Nova Launcher free version, it makes the app drawer nice and transparent, you can also give a dark background too I believe. Doesn't change the white theme of the Settings app though, which admittedly sucks.
[Samsung Galaxy Nexus] Culex316:
Does anybody know what file I can modify or which .apk I can insert to enable volume rocker wake on this build? I hate having to unnecessarily wear out the power button by waking it up so often.
[Samsung Galaxy Nexus] zzpianoman:
This has to be built into the source. You could either download the sources, cherry-pick commits from another ROM that has this feature and build it yourself, or decompile android.policy.jar and make the appropriate modifications to enable volume rocker wake. If you go the latter route, just keep in mind that there is no easy way to disable volume rocker wake, as there would be no settings entry for it.

Any other solution would require the phone to be constantly awake, thus draining the battery.

Hope this was helpful.
[Samsung Galaxy Nexus] MWisBest:
Been busy with school, new build is taking a little longer than I had hoped. Sorry for the delay!

I was under the impression that the problem was Ducati crashing and not recovering properly, but I haven't fully looked into the matter yet.

If mediaserver didn't restart after crashing, wouldn't other stuff such as music playback go out the window as well?

Oh yeah that's always been a kernel thing. I'll talk with [MENTION=4608636]bsmitty83[/MENTION] about getting it fixed in his kernel, I wasn't aware he didn't have it working.
[Samsung Galaxy Nexus] Culex316:
Thanks for the tips.

I think I will go for the android policy decompilation. I know how to compile kernels and even cherry-pick from sources, but compiling an Android ROM from source requires too much RAM and takes too long and my machine does not have the resources.

Robert
[Samsung Galaxy Nexus] zzpianoman:
If the latest FML build is deodexed, you should be able to get away with building just android.policy and Settings.apk without building the entire ROM. It would also have to compile the dependencies, such as framework, etc, but that shouldn't require too much RAM I don't think.
[Samsung Galaxy Nexus] bsmitty83:
It should work with my kernel , I have the same commits as you for audio , unless I don't have it enabled in my config .... I'll double check that to be sure
[Samsung Galaxy Nexus] seriousia:
There is an easy way

Go to

system/usr/keylayout

Then open Generic.kl with any text editor(dont forget to take the backup)

Find key number

Key 114 VOLUME_DOWN

Key 115 VOLUME_UP

And replace those line with

Key 114 VOLUME_ DOWN WAKE

Key 115 VOLUME_ UP WAKE

Thats it save the file and restart

;););)
[Samsung Galaxy Nexus] Culex316:
key 111 FORWARD_DEL
# key 112 "KEY_MACRO"
key 113 VOLUME_MUTE
key 114 VOLUME_DOWN WAKE
key 115 VOLUME_UP WAKE
key 116 POWER

You mean like this? It's worth a try, thanks for the tip!

Have you tested it on a maguro before?
[Samsung Galaxy Nexus] seriousia:
Yes like that only.

Not on maguro but on my old device running on gingerbread and ics :D
[Samsung Galaxy Nexus] Culex316:
I just tried your method on my Nexus 7 tablet running a Stock 5.0.2 Lollipop ROM and all it did was make the power and volume buttons completely unusable, so I assume it will do the same for my phone..thanks anyway.
[Samsung Galaxy Nexus] zzpianoman:
I'm actually not 100% sure myself - just going from what I saw happening in the logs. I just know that once the camera crashed, youtube would no longer play videos - and the stock gallery video player didn't work either so the two seemed to be related. Whether it was directly related to mediaserver, I have not fully determined because it definitely restarts itself after the crash.
[Samsung Galaxy Nexus] ashish__s:
SMS problem.

screenshot here: https://drive.google.com/file/d/0BxEtYACls7xCaV9wSGdGN3ZYSUE/view?usp=sharing

Unsure what to do to fix.
[Samsung Galaxy Nexus] linkermix:
I'm using Hangouts and so far so good. It might be a problem with your SMS app or maybe with your network provider, but considering some other people have the same trouble it's probably the first one.
[Samsung Galaxy Nexus] ashish__s:
if i reboot my phone after receiving a text, i receive i multiple times once the phone is booted up. i'll try and see if it's my messaging app (Google Messenger). thanks for your input! :)

edit: reinstalling Messenger doesn't solve the problem and i haven't had this issue except until i updated to this rom (5.1). couldn't this problem be with the RIL?
[Samsung Galaxy Nexus] BfstMtn:
Same thing happens to me. Also using Messenger.
[Samsung Galaxy Nexus] Culex316:
This has been happening to me since Jelly Bean.
[Samsung Galaxy Nexus] klanistok:
First of all that you for ur hard work to build this rom.

Are graphical glithes on rotation and camera recording still present?

Thank you

BR
[Samsung Galaxy Nexus] BfstMtn:
I've used stock SMS (whatever it's called)/hangouts (JB/KK/LP) and messenger (KK/LP). Never had this problem before.
[Samsung Galaxy Nexus] asheenlevrai:
Hello,

For some reason it seems like I cannot connect to 5GHz WLAN anymore (SSID are found and ask for password but I never get an IP, the WLAN SSID is "saved"). Only 2.4GHz works.

I remember I could connect on 5GHz with stock ROM but 5GHz was not working either with other custom ROMs (so this is not FML specific at all).

Any idea? is my phone damaged maybe or could it be some kind of driver issue?

Tx

-a-
[Samsung Galaxy Nexus] wbedard:
I have the same problem. Researching the issue shows it to be a result of some of the early kernel development ( [MENTION=4608636]bsmitty83[/MENTION], et al) around Mar 2014 that supported getting the post-JB releases of AOSP working on our device. While a few were frustrated by this issue (most people use 2.4GHz WiFi?), some did notice that they could get a connection if they hold their device very close to the access point anntenna (less than a few inches). That seems to reliably work for me, too. Hope this helps!

R/

wbedard
[Samsung Galaxy Nexus] bsmitty83:
I pull 5ghz off my belkin router at home on my gnex with no problems on FML 5.1 and R12 , and I've never had a problem with WiFi connecting on my kernels .
[Samsung Galaxy Nexus] wbedard:
I recall that you were (understanadably) unable to replicate the problems some users were having connecting to their access points. Although I imagine it's likely a moot issue as you transition to working on the 3.4 kernel, diagnosing the problem will likely remain difficult since it depends at least in part on the user's access point hardware and it's configuration.

R/

wbedard
[Samsung Galaxy Nexus] bsmitty83:
Yes on DirtyV kernel this was true , as I was using WiFi drivers from 3.4 kernel , which kills wep support . but both stock FML and full auto kernels use the 3.0 WiFi drivers , so there should be no issues[emoji6]
[Samsung Galaxy Nexus] wbedard:
While I have not tried the latest combo of FML + R12, I am using R12 with CM12 and the previous poster is a apparently using FML. Again, while I'm not certain if it's an issue you want to spend time on, it does appear that at least a couple of users are still having issues related to 5GHz WiFi.

R/

wbedard
[Samsung Galaxy Nexus] AvidPhisherman:
Do you think that the 5Ghz WiFi connection issues could be more of an Android problem in general?

The reason I mention this, is that I recently got a new Gateway (modem/router combo) from my ISP. I set it up from scratch, and modified all the appropriate settings/SSIDs via the Gateway's IP address. Myself and my wife both own Nexus 4s running Stock 5.0.1 (mine rooted, hers not), which connect normally to the 2.4Ghz broadcast, however both our phones can't hold a connection to the 5Ghz network. The network credentials are definitely correct, but the 5Ghz network continuously "saves" and never fully authenticates or connects. Tried connecting my old GNex as well, which runs freshgiammi's AOSP 5.1, and I get the same issue there too.

Just my two cents :)
[Samsung Galaxy Nexus] wbedard:
It's certainly possible that some aspects of the problem are "inherited" from the AOSP codebase, rather than any fault of developers making modifications to the same. In the research I did to troubleshoot the issues with my own device, I noticed that Google does make occasional changes to AOSP to fix various issues with 5GHz WiFi. While somewhat "ephemeral" issues like signal congestion might not be typical problems for 5GHz WiFi (like it is much more often with 2.4GHz), it's seems obvious that 5GHz WiFi has a level of difficulty that affects many developers, both "hobbyist" and professional alike.

R/

wbedard
[Samsung Galaxy Nexus] Culex316:
We recently got ourselves a new Linksys router with support for broadcasting both 2Ghz and 5Ghz signals and my Nexus 7 2013 tablet running stock Lollipop 5.0.2 and my Gnex that ran KitKat both were able to connect fine to 5Ghz.

At first it wouldn't work but it took deleting the Wifi network and re-adding it for it to work. 5Ghz was not very useful for me anyway, since the range was significantly shorter than with 2.4Ghz
[Samsung Galaxy Nexus] nachiket_xda:
What is this icon besides wifi icon?
[Samsung Galaxy Nexus] asheenlevrai:
Well actually I cannot connect to ANY 5GHz SSID with my GNex... while I can connect to those using other devices
[Samsung Galaxy Nexus] Culex316:
So, I downloaded apktool and decompiled android.policy.jar, but all I found for the 5.1 Lollipop ROM's android.policy.jar's output was android.policy.jar.out/original/META-INF/MANIFEST>MF in other words, just a single manifest file..whereas I was able to successfully get more files out of an earlier 5.0.2 build of Lollipop for the Gnex....so I guess the corresponding functionality has now been shifted elsewhere?