yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] coleburns:
Trying to flash L. I am stuck on the Google page and phone keep as rebooting but still stuck on Google screen.

Any ideas
[Samsung Galaxy Nexus] KShion619:
I just thought about this, would it be possible to merge all the ART commits from Lollipop into KitKat? Lollipop's ART speed is quite amazing considering theres no real optimization outside of Google things, it would make a really speedy KitKat
[Samsung Galaxy Nexus] blueoval50:
Just flashed and very impressed.

I just flashed this today and I'm very impressed by how fast and smooth it is. This thing really flies,no shut downs or lag that I have encountered so far. If this could get to DD status by fixing browser and mms it would be so sweet.(get it?) Donating now keep up the great work. :D :good:
[Samsung Galaxy Nexus] coleburns:
OK, I misread 1st post. I'll patiently wait
[Samsung Galaxy Nexus] bagarwa:
Looks like this ROM working really smooth for everyone; except for me. It is running very very slow on my toro. In fact, it is slower than the Paranoid Android kitkat ROM I was running before clean flashing this. Almost all games are now crashing after 3-4 minutes, no app stays alive in the background, swiping away apps from recents panel visibly lags. Guess my phone is just almost dead now.
[Samsung Galaxy Nexus] Nephilim:
I now have to flash this. Making a nandroid backup as I type and preparing to flash immediately after. Android 5.0 on my Gnex is something I cannot patiently wait to try out.
[Samsung Galaxy Nexus] terminal13:
Hey neph how is everything in gnex land?

just for fun I......
[Samsung Galaxy Nexus] jlvlawrence:
I'm also curious as to what app passwords is?
[Samsung Galaxy Nexus] skynet11:
Try dirty flashing the ROM and Gapps again over what you're running now. It greatly improved my phone's performance.
[Samsung Galaxy Nexus] mastertech007:
This is GREAT!! Running unbelievably good. Acquired root via flashing SuperSU v202.zip

Keep up the great work
[Samsung Galaxy Nexus] christianpeso:
What I did was, just a Google search for 2-step authentication because I was going to turn it off for a little bit in order to log in to my Google account. When I got into my Google account on the PC by clicking the link for 2-step authentication and logging in, in the top right corner was the switch to turn off 2-step. I clicked it to turn it off. A verification window popped up. In the verification window, there was a clickable link titled "Application-Specific Password". I clicked that and then on the next screen it asks to chose an app. I didn't see Play Store in the list so I manually typed it. You might be able to use any of them though. I hit "Generate" and it gave me a code. I then went back to my phone and under "Accounts" in Settings I chose "Google". I put in my User ID and the code that was just generated instead of my regular password and I was able to get Google setup.
[Samsung Galaxy Nexus] ataris_kid:
https://security.google.com/settings/security/apppasswords

Generating an application specific password is typically used for applications / devices that don't natively support two-factor authentication. They are randomly generated strings intended for one-time use to authenticate to your Google account.
[Samsung Galaxy Nexus] thetakerfan:
I think MW alluded to this earlier but just wanted to verify. Is the next build going to be compatible with F2FS or is that going to be further down the line? If its coming soon I'll just wait but if that piece is going to take awhile I might play with this a bit tomorrow when I'll be home on WIFI
[Samsung Galaxy Nexus] ruccarucca:
icons

are you eventually going to change the icons to material design?
[Samsung Galaxy Nexus] wkr.mky:
Can't wait for the F2FS friendly build so I can play with this! :victory:

I'm on full F2FS, does anyone know if I change /system back to ext4 if it will wipe my whole SD card? :silly:
[Samsung Galaxy Nexus] Rushead:
My system partition is still ext4. It wouldn't boot.
[Samsung Galaxy Nexus] pattyboi:):
something is up with the f2fs support in the kernel,its glichy in my fork and i havent touched the f2fs side of things

++ even before loli caus ei know it dont have f2fs support yet
[Samsung Galaxy Nexus] Nephilim:
Any reason why the lollipop roms launcher doesn't have Google now active upon swiping to the right? Also, yes, I had google now activated. I tried downloading the Google now launcher off play store but that version is the old kit-kat launcher.

Sent from my Android 4.4.4 Galaxy Nexus
[Samsung Galaxy Nexus] christianpeso:
If you used the GAPPS that he linked to in post #1, that package that he made is based on PAs Nano Gapps: http://xdaforums.com/showthread.php?t=2397942

That package does not include Google Now Launcher.
[Samsung Galaxy Nexus] Nephilim:
Thanks for the info, its all good, I'll wait for a more stable working update anyway. Just wanted to see what 5.0 is like my Gnex. :)

Sent from my Android 4.4.4 Galaxy Nexus
[Samsung Galaxy Nexus] maxiv:
So is this working on Galaxy Nexus devices with VYL00M now aswell?
[Samsung Galaxy Nexus] christianpeso:
If that's the version that was having boot problems before, I don't think so. I think that problem might be limited to the GSM version of the Galaxy Nexus as I have not seen any one complain in this thread about it not booting. All the complaints are coming out of the regular Samsung Galaxy Nexus thread which is mostly GSM related stuff. Verizon(CDMA) Nexi(I guess thats the plural, LOL) does not seem to have that problem.
[Samsung Galaxy Nexus] RW-1:
You and I both .... :)
[Samsung Galaxy Nexus] maxiv:
Ooops, Google took me to the wrong SGN forum! Thanks for the reply, though!
[Samsung Galaxy Nexus] MWisBest:
New build up, I haven't had time to check all the posts that've popped up in the thread recently, I'll do that later tonight!
[Samsung Galaxy Nexus] KShion619:
Thanks a ton, I'll try it out

Tapatyped from my Verizon Galaxy Nexus
[Samsung Galaxy Nexus] thetakerfan:
You just made my Sunday, DLing now

So I can just reformat system as ext but leave the others as f2fs?

Edit: Trying now and will report back

Editx2: Yes that worked just fine. I tried without a wipe just out of curiousity and predictably that was a bad idea, lot of hung processes so redoing now with proper wipe, but looking good.
[Samsung Galaxy Nexus] arukemo:
i love you so much

i've been pacing around like a hungry dog all day waiting for the new build :D
[Samsung Galaxy Nexus] christianpeso:
Flashed new build and new GAPPS. Seems like these are actually Lolipop Gapps as the new Setup is included which is nice. On 1st boot I did get a "Google text to speech" force close a couple times, but I just closed it out and it has not came back yet. The Webview issue seems to be fixed as you can now open up the AOSP browser, but when I did it asked me to confirm my account and I clicked yes, and then that same message came right back up. It kept doing this. I then hit cancel on that screen to not associate with my account, and I was able to bypass that. Any other app that used the browser, or Webview now works as well, such as the newest Talon twitter app which is only made for Lolipop as you have to log into your Twitter account to use it. Works great now. The multitask view is running a lot better now. Much smoother.

I have not put my SIM in yet to try out calls.

This is getting better and better. Thanks MWisBest!!!
[Samsung Galaxy Nexus] thetakerfan:
One thing I haven't seen anyone else mention so not sure if its a bug or just my phone, but if I leave it plugged in to my PC via USB and shut it down, it sits at the battery charging icon but can't be rebooted unless I pull the battery out

I also got the Google Text-To-Speech errors a lot during setup but it seems to have calmed down
[Samsung Galaxy Nexus] christianpeso:
I also got that battery icon. If my phone is off, plugged in and charging and then unplug it, the large battery icon stays on the screen and you have to do a battery pull. Also with the phone on, if I have it plugged up and charging, and then unplug it, the lock screen still says charging at the bottom.
[Samsung Galaxy Nexus] rgao007:
Is Google Play Services not working for anyone else on the 5.0 Beta? Anyone know how to fix it?
[Samsung Galaxy Nexus] jjjnmk:
I'm getting the same error. Can't open up the Play Store to download Google Play Services either.
[Samsung Galaxy Nexus] KShion619:
This revision of Lollipop FML is absolutely amazing compared to the older in terms of performance, whatever you did for smoothing the Overview screen out, helped a lot on other things as well, maybe it was something else, but this is now less scary to use as a DD for me, as I dont use much data at all, and i wouldnt have even noticed MMS bugs if you didnt tell me :p

---------- Post added at 04:42 PM ---------- Previous post was at 04:39 PM ----------

I'd say re-download and re-flash everything other than the normal set of bugs seems to be working properly for me
[Samsung Galaxy Nexus] thetakerfan:
No issues with Play Services or Store, working fine for me here. Make sure you used the updated GApps with the new build, in case you tried the original build and gapps, that could be the issue

I still get the Text-to-Speech error occasionally, seems like more of a nuisance than anything. I was able to dictate a new calendar appointment using the microphone in the keyboard just fine.

Only been playing with it for an few hours but it seems to be working pretty well. If we could get cell data working it'd probably be usable as a daily driver. Battery seems to be draining pretty fast but I've also been playing on it so hard to tell. I also noticed "adaptive brightness" wasn't on by default so I just turned that on, could help.
[Samsung Galaxy Nexus] KShion619:
One likely reason Battery is draining is because it keeps trying to connect to 3G/4G and failing, turning off Cellular Data might help with this issue, noticed a lot (understatement) of attemps in ADB Shell's Logcatting feature, plus it seems to be awake 100% of the time >.> if i get around to rooting and checking for wakelocks I'll have a more useful reason, but those are my observations
[Samsung Galaxy Nexus] jguerdat:
Never mind...
[Samsung Galaxy Nexus] jjjnmk:
I'm pretty sure I used the most updated build and gapps. FML-AOSP-5.0-20141109-toro.zip and FML-GApps-5.0-20141109.zip, right? Would my recovery have anything to do with it? I'm not running TWRP, I'm using cClockworkMod Recovery v6.0.4.3.

Thanks in advance >.<
[Samsung Galaxy Nexus] KShion619:
I'd try using the TWRP posted in the OP, CWM for the Galaxy Nexus is aging fast, so it is possibly your issue
[Samsung Galaxy Nexus] thetakerfan:
I'd echo this statement. I think TWRP has been the only "supported" recovery for awhile now, atleast with FML.
[Samsung Galaxy Nexus] shoelace1999:
bruhhh

i think it was more stable before the 11-9 build it crashes the launcher a lot
[Samsung Galaxy Nexus] thetakerfan:
Google Launcher or Launcher3? I've been using Google only and haven't had it crash once
[Samsung Galaxy Nexus] Zer0_Cool:
Can anyone mirror the latest build/gapps, having serious download issues from the XDA servers...
[Samsung Galaxy Nexus] Dirty_Jerz:
AOSP

[MENTION=3390093]MWisBest[/MENTION]: Sick moves getting 5.0 to the GNex so quick. Any chance making a branch without the PVR drivers? If not Doya mind if I fork ya and try to build.....It's pretty much what were all looking for over on shiny? If you're gonna keep the aosp-toro "branch" going then I'll pump the breaks. Blessings...One.
[Samsung Galaxy Nexus] jjjnmk:
I installed TWRP now but it didn't seem to fix the issue. I just ended up backing up my data and doing a factory reset. Everything seems to be running smoothly now. Thanks for your help though!
[Samsung Galaxy Nexus] jguerdat:
Fwiw, I'm using CWM recovery and Play Store, etc

all work fine.
[Samsung Galaxy Nexus] Zer0_Cool:
Finally got the new build to download, had to do a clean install because I was having some fc issues, but that was to be expected.

Recents is now super smooth, definitely better than it ever was on kit kat in my opinion.

The browser has still had a few crashes, once every 2 hours tops (using chrome), but it's almost perfect, especially compared to the first build where you could only use it for 15-30 seconds at a time.

A few minor issues I noticed for the list;

On the lockscreen after the phone is fully charged and removed, it will sometimes still say 'charging' or 'charged', even when it's unplugged/not charged.

The flashlight toggle (at least on my device) is not functional.

Google text-to-speech FC on occasion/in maps.

No GPS/location services anymore.
[Samsung Galaxy Nexus] ataris_kid:
Just wanted to report an issue that I came across.. I was looking at the Google-hosted backup and restore service -- the one that pretty much all of us use with Android, much improved in Lollipop upon initial install as we can now select a specific device and its apps to restore -- and I noticed that by default after a clean install (FML-AOSP-5.0-20141109-toro.zip & FML-GApps-5.0-20141109.zip), the backup service was not as it should be. There was no account listed in the settings page, as follows:

Going into an ADB shell, I could see that the incorrect Backup Transport provider was selected, as follows:

shell@toro:/ $ bmgr list transports
com.google.android.backup/.BackupTransportService
* android/com.android.internal.backup.LocalTransport

Long story short, any device data was being "backed up" to a local cache instead of Google's servers. I had to manually select Google's Backup Transport Service by typing the following in an ADB shell:

bmgr transport com.google.android.backup/.BackupTransportService

Now it seems to be working correctly as my Google account shows up in Settings --> Backup & reset --> Backup account.

Additionally, the correct Transport is now selected:

shell@toro:/ $ bmgr list transports
* com.google.android.backup/.BackupTransportService
android/com.android.internal.backup.LocalTransport
[Samsung Galaxy Nexus] RW-1:
Very nice find AK, I'm sure the dev appreciates that find.

I'm waiting on cell data issues to be resolved and I may jump over to this.

My glass is still raised as to how far this has come in just a short few weeks, lots of hard work all around! Well done!
[Samsung Galaxy Nexus] bothgoodandbad:
used google launcher and nova and had no crashed, only ran into known issues of data, camera - browser seemed to work flawlessly though.:good:

---------- Post added at 01:09 PM ---------- Previous post was at 01:09 PM ----------

me too!
[Samsung Galaxy Nexus] ruccarucca:
sim

anyone else trying to pry into the data/ sim card not mounting issue? i got it mounted for a second but it unmounted itself.
[Samsung Galaxy Nexus] blueoval50:
GNL working for me.

No problems with latest build and GNL,browser works fine,gmail,gallery,calender,photos and play store all ok. I can stream radio stations on play music but can't play from library,no camera still. Performance is excellent.Anyone try mms or making calls?
[Samsung Galaxy Nexus] govee:
Posting in case someone else runs into this. I was able to install 5.0 and GAPPs from 1106 and all went fine. When I tried to install 1109 I tried a number of methods with varying degrees of success. I had to wipe caches, data and system as is i tried a dirty flash I would get play services crashes. When I wiped system the the 1109 would fail to install. Long story boring is I had to manually mount /system after a wipe and everything installed and runs like a top.
[Samsung Galaxy Nexus] bothgoodandbad:
nicee, i havent been able to do mms yet and i don't think i had a call but i didn't try before backing it up and going back to LS (for now:/ lol
[Samsung Galaxy Nexus] 7175:
Roflcopter flyby... I just dirty flashed from 4.3.1 and dragged all my 150 apps(1GB of /data) to 5.0 lol. Can't believe that s*** worked! Even my system settings are ok, wow. The only thing that crashed is Clock as usual with a platform change. Just wiped the data and good to go.

Before testing this out, I was in Android Studio and was thinking, man it would be cool if I could actually test this on Android 5.0 on my Galaxy Nexus. Then I came over to xda and saw that MWisBest had updated the title to his thread!.. Nice job getting this pushed to the Galaxy Nexus so quick.

[MENTION=2403915]ataris_kid[/MENTION] : Wow, what a great example of how to make a solid report. Let's all thank him guys: http://xdaforums.com/showpost.php?p=56643068&postcount=2299\

edit: Thought I'd also report about the radio. It looks like rild is looking for /dev/ttys0, which doesn't exist, so that's probably an issue. I haven't tried using other tty's but you can start the rild daemon and try a different <tty> like ttyGS0,ttyGS1, etc. with:

rild -l /vendor/lib/libsec-ril_lte.so -- -d /dev/<tty>
setprop rild.args '-d /dev/<tty>'

You might need to kill rild daemon first if you try this with:

kill `pgrep rild`

Just thought I'd post that to see if anyone wants to try to find a rild device that works.

edit2: Still experimenting with the radio problems. It looks like there's a new "radiooptions" binary in 5.0. The first option you give it is the same as before, a number 0-10, but the 2nd and 3rd option pertain to a SIM number and a socket option. The 2nd and 3rd option that works for me without throwing an error are 1 and 1, so you would use it like:

radiooptions <0-10> 1 1
[Samsung Galaxy Nexus] thetakerfan:
I use GVoice/Hangouts so no normal MMS but phone calls were working fine for me.
[Samsung Galaxy Nexus] chevycam94:
Is it just me, or is anyone else having trouble flashing the Lollipop zips in TWRP (2.8.1.0). Fails every time now. And the Gapps has YET to flash at all... The only one I got to flash, was the Lollipop zip from the 6th.

EDIT:

Wipe everything

- REBOOT

Install ROM

- REBOOT

Install Gapps

- REBOOT

WAIT......

YAY!

LONG way of going about it, but thats what I had to do to get it to flash.
[Samsung Galaxy Nexus] ataris_kid:
So.. I was in the middle of testing each of the other TTYs (some are owned by "radio" so I started there), but I had no luck. And then I came across some interesting information.. Replacing the /system/bin/rild binary with the same from a Kit Kat build makes the RIL play nicely.. I just tested this and I can confirm that I have 4G data connection on this ROM.. So it's definitely an issue with how the new version of rild is built. This is not a "clean" or permanent fix, but it will surely do the job while we investigate the underlying issue.

All credit to [MENTION=3483826]rjwil1086[/MENTION] for his post regarding the temporary workaround.. By way of [MENTION=3046910]miji2[/MENTION] in the other FML thread!

Edit

: Yeah, I'm not so sure about this anymore.. I did have a data connectivity indicator when I first applied the 4.4.4 rild binary, but I can't seem to replicate it (using all sorts of combinations of TTY devices and binary versions). May have been a false alarm.. I don't know enough about rild yet to know what exactly is going on. Research time.
[Samsung Galaxy Nexus] 7175:
Nice!!! I was just thinking something similar and testing the 5.0 rild on 4.3.1 cause I noticed a size difference, and it works weirdly?? Not quite good enough thinking on my part lol. Excellent job man and the people you gave credit to. Headed back to 5.0 now!

edit: Damn, maxed out how many thanks I can give per day. Damn damn.
[Samsung Galaxy Nexus] ataris_kid:
The version of rild on Android 4.4.4 seems a bit unstable / unreliable. Data connection is intermittent. I'm testing a few other versions now. At the very least, it seems as though the issue may be related to the way rild is built.

Edit: And now I can't seem to get data back.. The plot thickens.
[Samsung Galaxy Nexus] zzpianoman:
When you replaced the rild binary, did you also change the tty device in build.prop?
[Samsung Galaxy Nexus] asianrage:
So I wiped data/factory reset/system last night and loaded the new Lolipop build. Runs better than I expected.

I wanted to update to the latest supersu binary from within the SuperSu app and it failed. I tried to boot into recover (Power+Vol Up) and it didn't take either. Is this an issue or am I just missing something here?

Hmmm, using adb reboot bootloader got me to boot into recovery mode.....
[Samsung Galaxy Nexus] ataris_kid:
I can't seem to replicate the original data connectivity indicator using multiple combinations of binary versions and TTY devices.. It may have been some kind of fluke.. though I don't know enough about rild yet so I can't say for sure what happened. I edited my original post to reflect that.
[Samsung Galaxy Nexus] zzpianoman:
From recovery, mount system then using adb , chmod 777 /system/xbin/su. Then reboot the system and install supersu from the Play Store and install binaries using Normal method.

---------- Post added at 01:25 AM ---------- Previous post was at 01:20 AM ----------

I can see that once I replaced the rild binary with the one from a KitKat build, using Advanced Signal Status, all of the 3G/CDMA and LTE signal fields show readings whereas they were not all showing readings with the Lollipop rild.

The network signal bars show an "!" but when you pull down the notifications shade, it reads 4G with an "!".

Edit: Turns out there is no difference in the signal readings using the KitKat rild.
[Samsung Galaxy Nexus] Zer0_Cool:
Just download this zip and flash it in recovery. Just tested this so I can confirm it works.

http://download.chainfire.eu/452/SuperSU/

I also put the old RILD file from my FML 4.4.4 backup that I made prior to flashing 5.0 in system/bin/ of the rom zip file before clean flashing it again, no go on the mobile data front.
[Samsung Galaxy Nexus] 7175:
I haven't gotten the 4.4.4 replaced rild binary to work for me yet, but I made a recovery flash-zip for anybody that wants to try it and flash it on top of their rom. This will only replace the /system/bin/rild binary, nothing else, so no worries.

Another thing I would try now that I think about it is replacing the libraries that are linked to rild, specifically /system/lib/libril.so and /system/lib/libreference-ril.so. The other ones are /system/lib/{liblog.so,libcutils.so,libdl.so,libc.so,libstdc++.so,libm.so}. I'll try it out and see how it works out.

Btw, you can usually find a binary's linked libraries with

strings <binary_directory> | grep \\.so

That goes for libraries linked libraries as well.
[Samsung Galaxy Nexus] brandonabandon:
5.0 evervolv/port

hello all. my source build of evervolv broke. i was able to port from this aosp build and i have asked mwisbest permission to host. as the baseband is showing, i believe data may be working. i dont have data personally to test. fyi, the current build is for l700 and could easily port to yer device. firefox works and same bugs as base. teaser screeniez
[Samsung Galaxy Nexus] MWisBest:
Thanks for the report about TTS FCing. I'll see what I can do about that.

Yes, offline charging is an issue, it's a little low on the priority list though.

Yeah the launcher seems to have redraw issues occasionally, I'm looking into it...

There's no chance of me making a branch with the old GPU drivers. When CyanogenMod and OmniROM are ready to go for Lollipop nightlies, they'll be switching to the new GPU drivers too, and with that much of the custom ROM market being on the new GPU drivers I'm expecting the kernel devs will be switching as well...

THANK YOU. This has got to be the best bug report I've seen in my entire life. I'm not kidding. I'll get this fixed for the next build.

Can somebody see if /dev/ttys0 is there on KitKat?

You've just gotta make sure /system isn't mounted when attempting to flash the ROM.

I tried the old rild now as well and it seems to get closer to a data connection at least.
[Samsung Galaxy Nexus] Dirty_Jerz:
No. There is a 'ttyGS0' though.

shell@toro:/ $ ls /dev | grep tty
tty
ttyFIQ0
ttyGS0
ttyGS1
ttyGS2
ttyGS3
ttyO0
ttyO1
ttyO3
[Samsung Galaxy Nexus] andreadec:
On FML 4.4.4 on my Maguro I have: tty, ttyGS0, ttyGS1, ttyGS2, ttyGS3, ttyO0, ttyO1, ttyO3.
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
I am having the exact same issue on CM11, but typing this command doesn't help. Any ideas?
[Samsung Galaxy Nexus] boldfilter:
Anyone got link to old gapps?