yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] christianpeso:
Dont know if this ROM related so will cross post this in another thread.

After changing DPI using ROM Toolbox and installing Nova Launcher, I restarted the phone for the 1st time. At that point upon booting back up I was greeted with "Please enter your Password to enter". Looked like an Encryption password. But I did not encrypt my phone. No passwords I usually use worked including my regular gmail password.

Booted into recovery and now when I Wipe Data,Cache, and System, I am getting all red unable to mount anything.

Does anyone know if 5.1 encrypts everything by default? Has anyone experienced this before?

I am using the beta newest beta GAPPS by PA that is listed above.
[Samsung Galaxy Nexus] EAK128:
Today I noticed the phone is not going to sleep, just wondering if anyone else has this issue? Reboot didn't fix it. Looks like Android OS is staying awake.
[Samsung Galaxy Nexus] erk1725:
I had this happen the other night as well, and it was a mess to fix, and I did end up losing a lot of saved data from my "sdcard" in the process of getting everything back up and running. I think this is due to the "google backup" not working properly at this time? I don't know.....I had to use adb push and push an old rom to my phone I luckily had saved on my laptop. I was also forced to reformat all back to ext4. I have reached out to [MENTION=4608636]bsmitty83[/MENTION] in regards to this and he said he will look into it. ATM it sounds like it could be F2F or 5.1 related. I have been back on 5.1 since yesterday with ext4 across the board and so far, so good....and I do tend to reboot a good bit......so maybe things work better atm on 5.1 with ext4? I don't know....maybe Ive just been lucky so far this time around. Hope this helps, and sorry to hear you had to deal with the same issue as well....good luck getting everything back up and running.

Lesson learned......backups through TWRP are nice and do come in handy, but backing everything up to another source is without a doubt recommended as well!
[Samsung Galaxy Nexus] christianpeso:
Sounds like a F2FS problem if everything seems to be going fine for you now that you switched back.

No worries in getting back up and running. This is a backup phone that I dont really use except to play around with and occasionally try out new features. Will start from scratch and see what happens. Thanks for the info!
[Samsung Galaxy Nexus] bsmitty83:
Had it happen to me as well the other day installing super user from recovery after dirty flashing . I was also using f2fs for data and cache . I ended up formatting my partitions in fastboot and all was well .

I'm not sure what the cause of it was . maybe not having busybox installed while flashing su from recovery , maybe it was f2fs , I have been super busy at work and haven't had time to really check anything out . but its definitely something to keep an eye on .
[Samsung Galaxy Nexus] RW-1:
Not sure but something strange is going on with all of this, and this morning my phone locked up, though nothing of it, but on batt pull and reboot it began optimizing apps but I hadn't done anything kernel wise, flashed anything, or had removed anything, etc.

Just FYI.

---------- Post added at 03:18 PM ---------- Previous post was at 03:16 PM ----------

Not from encryption, but secure lockscreen, if enabling pin or swipe code, the OS will ask if you want to apply to phone start up as well... not saying you had that, but that's what the prompt is from.
[Samsung Galaxy Nexus] erk1725:
[/QUOTE]Not from encryption, but secure lockscreen, if enabling pin or swipe code, the OS will ask if you want to apply to phone start up as well... not saying you had that, but that's what the prompt is from.[/QUOTE]

I don't use a pin or secure lockscreen or anything......just throwing that out there

Thanks again everyone!
[Samsung Galaxy Nexus] zzpianoman:
Ouch, that sucks. Well, at least you can still make an emergency call!
[Samsung Galaxy Nexus] jcpowell:
Have yet to see any issues resembling all that I just read and I'm still on ext4 for everything
[Samsung Galaxy Nexus] amd_h4x0r:
Same thing happened to me.

My phone also locked up again after that so I did a battery pull. On startup the dots would circle for a while and then freeze, so I did another battery pull and the same thing happened again. I booted into recovery and wiped cache and rebooted. This time the bootup dots went super fast for quite a while and when it finally loaded it looked like a new flash with everything reset and without any gapps or any of the apps I had installed previously. So I rebooted into recovery to restore a nandroid but my sdcard was blank too. No zips, empty TWRP folder, and my TitaniumBackup folder was gone as well. I don't know how everything got wiped. :confused:
[Samsung Galaxy Nexus] RW-1:
3 years and finally ....

I ordered my N6 on edge, thru comcast for the $200 gift card a moment ago, I couldn't pass that up. Having it shipped to my IT office so someone will sign for it, can't wait! :)

Now to order my case ...
[Samsung Galaxy Nexus] arigr:
ive been wondering to jump too..wife and i both have gnex s we bought more than a year ago..been unlimited data for almost five years i guess and the wifey wants something new...toss up tho is nexus 6 or wait to see the benchs on htc m9..we may go with different phones this time :P still hate the idea of going off unlimited but datas cheaper nowadays
[Samsung Galaxy Nexus] RW-1:
Seriously, I have the 10Gb plan, and being on wifi at home, IT office, and other locations, I'm not hitting anywhere near 10Gb, the account hit 3Gb, and that was when my daughter would use my wife's GS5 (which kicked me off unlim) over a weekend doing utube videos int he car. (I set warnings at 3Gb on my GNex and her GS5 so I'd know when we got close.

In fact, I'll likely drop it down to 8 or 6Gb to offset the N6 edge payments that will be added tot eh account to keep it equal, or slightly less, and then modify later on if need be.

So unless you are not on wifi at home, work, etc. IMHO, you could lose it and not suffer, it depends on how much you and your wife are using, I compared the OS on both to VZ's site and they matched up fairly close, and I haven't worried about it.
[Samsung Galaxy Nexus] MWisBest:
We had a couple VZW APN APKs (VZWAPNLib, VZWAPNService) for a long time, but I removed them not that long ago because I found they really didn't do anything except take up space in /system.

Sounds like the gps-lock issue. Run the GPS Test app until you get a fix, then close it. This should fix the wakelock.

For those of you having issues like these^, what kernel are you using? I'm using F2FS with the stock FML kernel and haven't had any issues like these.
[Samsung Galaxy Nexus] amd_h4x0r:
Sorry forgot to mention I was using bsmitty's FullAuto R11 kernel (f2fs cache and data)
[Samsung Galaxy Nexus] christianpeso:
Same. BSmittys R11. Cache and Data.
[Samsung Galaxy Nexus] jguerdat:
Yup. Haven't had time to work it out yet.
[Samsung Galaxy Nexus] jguerdat:
Sorry, maybe I missed it. Which GPS test app? Many shown in Play Store. Or just any of them?
[Samsung Galaxy Nexus] wkr.mky:
I normally see this one being used all the time, and I use it myself. Great app. :good:

https://play.google.com/store/apps/details?id=com.chartcross.gpstest
[Samsung Galaxy Nexus] jguerdat:
Well, installed and tested once. Working right now, we'll see how it goes...
[Samsung Galaxy Nexus] fivefour:
I noticed if Ambient display is enabled the phone doesn't sleep correctly.
[Samsung Galaxy Nexus] Christopher8989:
I think it's my phone but every time I mess around with kernel settings the phone doesn't work right, even if just OC the CPU. Maybe like someone said the hardware is not quite the same in all phone.
[Samsung Galaxy Nexus] MWisBest:
Question... were you guys using the 'FML' FullAuto version? Reason I ask is that with my 5.1 build(s) this shouldn't be used anymore, the regular version is what needs to be used now.
[Samsung Galaxy Nexus] bsmitty83:
Even if they were , the only thing that should be messed up would be no sound , i haven't switched back to f2fs to test yet , was holding off till the end of the week until the nice people at Verizon let me upgrade my non unlimited data line to a n6 while keeping my unlimited line. You cant do it online .

But it reminds me of when I was first messing with f2fs and the fstabs and recoveries , I would run into that scenario where the system wouldn't recognize the partitions , just crypto since its ext4
[Samsung Galaxy Nexus] RW-1:
N6 tomorrow, may be mute point for me if I switch and activate, but will use the Gnex in reserve on wifi sans sim.

MW, can you post a separate like to just the included kernel itself, in case we want to flash back to it?
[Samsung Galaxy Nexus] dbt816:
I had bsmitty's 3/4 FML build running with the FullAuto R11 AK version... upgraded to FML 5.1 (dirty) with the same kernel... no issues... loaded FullAuto R12 AK when it came out and it booted to the screen asking for a password.
[Samsung Galaxy Nexus] amd_h4x0r:
I only saw one version of R11 available for download at the time (Full_Auto_R11-Ak.zip) and that was what I was using. Now I'm kinda scared to try new Lollipop rom/kernel builds if my entire phone might be wiped again. :eek:

Don't let that discourage you all though...you're doing excellent work!
[Samsung Galaxy Nexus] bsmitty83:
I flashed it fine , it only messed up when I flashed supersu 2.4 from recovery not when I actually flashed the ROM and kernel , I also didn't have busybox installed either so idk if that played into it , but the other 2 reports were from installing .apks I believe as well so I think as long as you install busybox first before installing any apps that use it , you might be OK.

Again its speculation on my part as I haven't tested it , but a dirty flash would also do it as some apps need busybox that are already installed from the dirty flash.

I'm gonna switch back to f2fs and clean flash , and see if i have problems. But Im betting it will be OK .

Edit:

So I just formatted /data and /cache to f2fs , wiped system , then flashed FML, gapps , busybox , supersu 2.46 , and full auto r12 , booted fine , no issue , no encryption screen .
[Samsung Galaxy Nexus] Rushead:
Just dirty flash the rom & gapps... Easy enough.
[Samsung Galaxy Nexus] zzpianoman:
....or extract boot.img and fastboot flash......or make a nandroid.....
[Samsung Galaxy Nexus] 67jeffh:
What are you using to format to f2fs? twrp doesn't have the option anymore for toro. I've been looking but have not found anything recent.

Thank you,
[Samsung Galaxy Nexus] bsmitty83:
Check the dirtyV kernel thread ,I'm still using twrp 2.8.0.0

It gets the job done
[Samsung Galaxy Nexus] 67jeffh:
OK, thanks! I appreciate the quick reply!
[Samsung Galaxy Nexus] erk1725:
Thanks [MENTION=4608636]bsmitty83[/MENTION]

When I went through this, if I remember correctly, I was all setup and had flashed everything (clean) and I was using rom toolbox to uninstall some system apps I don't use, the same way I always do. I use nova launcher and after uninstalling the system apps, the apps will still show in the app drawer, I've tried to just restart nova launcher, but that doesn't work, so I rebooted so they would disappear from my app drawer, and upon reboot, I got that password screen.

Are you going to continue to run with the setup the way you have it now? I would be curious to hear how things go for a few days, or after a couple reboots?

Anyways....thanks again for reviewing everything! R12 synapse injected on 5.1FML with ext4 partitions is running really well for me, so I'm not in a hurry to go through reformatting to F2F right now, but I'm sure the bug to flash some stuff will eat at me as time goes by:D

All of you are amazing!!:good:

---------- Post added at 11:35 AM ---------- Previous post was at 11:29 AM ----------

Just wanted to post to let people know I just updated my Netflix app through playstore, and the video plays no problem!! Sound works great! Its been a long time since Ive been able to watch Netflix on my toro!

Im thrilled!:good:

Thanks!
[Samsung Galaxy Nexus] christianpeso:
Been back up and running for a couple days now without any issue. No password screen on boot. Formatted back to ext4 on all partitions while running r12 kernel from BSmitty. Gonna reformat again back to F2FS on /cache and /data and see what happens.
[Samsung Galaxy Nexus] bsmitty83:
Just make sure you install busybox before installing any app that needs it , like supersu . I honestly think that was the cause .
[Samsung Galaxy Nexus] RW-1:
I'll do that, re-dirty flashing the ROM itself is easy, but when I have removed what I don't want on it, etc. It becomes easier to just re-flash a kernel itself IMHO.

N6 is nearby at the local fedex facility, it will be in my hands shortly! :)
[Samsung Galaxy Nexus] Christopher8989:
The twrp 2.8.0.0 from twrp doesn't have f2fs option (I just flashed it to see, I was curious) but fml-twrp-2.7.1.0-20140705-toro link in the OP does. I used it before.

bsmitty83

Does your 2.8.0.0 supports accessing the sdcard while in bootloader and recovery? If it does then please let us have it too. :)

I ask because the fml 2.7.1.0 does not but 2.8.0.0 or 2.8.5.0 from twrp does and it's a real convenience in case I forgot to copy something to the sdcard but already wiped everything :p

---------- Post added at 06:09 PM ---------- Previous post was at 05:41 PM ----------

How do you flash busybox in recovery? Do you have busybox only flashable zip?
[Samsung Galaxy Nexus] amd_h4x0r:
Here's 2.8.0.0: https://www.dropbox.com/s/qcsfm1qfqfbouek/TWRP-2.8.0.0-TORO.img?dl=0.

It has F2FS support and you can also adb push/pull/sideload from recovery.
[Samsung Galaxy Nexus] bsmitty83:
Yes I found a thread for a flashable busybox package . just search for it , I'm sure it'll come up
[Samsung Galaxy Nexus] jcpowell:
I flashed SuperSU and had trickstermod before downloading tricksters busy box installer and had not this issue that's plagued y'alls devices.

Ext4
[Samsung Galaxy Nexus] christianpeso:
2.8.4.0 F2FS .img compatible Recovery courtesy of [MENTION=3377012]DeadMetaler[/MENTION]

https://www.dropbox.com/s/ydfzvn3f9jpaj0t/recovery_2.8.4.0_f2fs_toro.img?dl=0

Flashable Busy Box:

http://www.mediafire.com/download/h2ox7jzff5avsa6/BusyBox-v1.23.1-Stericson.zip

http://xdaforums.com/showthread.php?t=1929852
[Samsung Galaxy Nexus] 67jeffh:
For some reason that recovery file would not flash using flashify. Said there was an error in the file..
[Samsung Galaxy Nexus] christianpeso:
Try flashboot flash recovery in Download mode. Didnt try it with Flashify.
[Samsung Galaxy Nexus] 67jeffh:
It was the name.. It downloaded with a set of quotes in the front of the name.. All good now..

Thanks for the quick response!
[Samsung Galaxy Nexus] kb8no:
Did it then flash with Flashify after you fixed the name?
[Samsung Galaxy Nexus] bryantjopplin:
Use fastboot its safer. Fastboot flash recovery twrp2.8.?.img
[Samsung Galaxy Nexus] 67jeffh:
Yes.. Worked great!
[Samsung Galaxy Nexus] kb8no:
[MENTION=5127887]67jeffh[/MENTION] Flashify worked great flashing recovery_2.8.4.0_f2fs_toro.

I've been lurking for a long time now cuz the GNex is my wife's daily driver on FML-4.4.4 and she always looks at me skeptically when I tell her I'm going to flash a new ROM on her phone. It's time now and this seems stable enough for her and I have got to get my hands on Lollipop. Thank you again MW.

I could now format f2fs using this recovery before flashing but I want to limit changes and stick with ext4 for now and get this working first with as few variables as possible. I will do f2fs later. So, now, please confirm for me. I flash all these zips and they should be in this order. Please confirm I can flash these serially in one flash sitting without booting and then reboot when I have flashed them all.

FML-ASOP-5.1-20150311v2

pa_gapps_modular-mini-5.0.1-20150315

Full-Auto-R12-Ak

BusyBox-v1.23.1-Stricson

UPDATE_SuperSU-v2.46

VZW-Lollipop-MMS-Fix

Have I got this right?
[Samsung Galaxy Nexus] past_pluto:
Use the gapps in the downloads for 5.1. I'd flash ROM and SU then boot and set it up then flash gapps set them up then flash kernel, busybox, and MMS fix. But for me the best ROM for battery life is the CM 12 with DDK 1.9 drivers using stock kernel.
[Samsung Galaxy Nexus] kb8no:
Please give me a link for gapps "in downloads for 5.1". I'm not finding anything for pa gapps specifically for 5.1. Neither am I finding any links to which pa gapps to use in this forum. Earlier in this forum there was problems with f2fs and flashing the SuperSU without first flashing BusyBox which caused the ROM to lock up. Lots of discussion above. I know I am not planning to use f2fs but it would be a good plan to do it in this order preparing for when I am going format f2fs. Any thoughts?
[Samsung Galaxy Nexus] Rushead:
There's a link to FML gapps in the op.

As for order, most of it doesn't really matter as long as you flash the rom 1st since most roms wipe /system on flash. Otherwise, obviously flash any dependencies first (e.g., busybox before su, tho I'm not sure even that matters so long as you don't boot before flash).
[Samsung Galaxy Nexus] christianpeso:
Their should be an active GAPPS package released in this thread along with the 5.1 ROM. You might have to search for it. If not, here is a link to the beta version of the PA 5.1 GAPPS I got before they pulled it.

https://www.dropbox.com/s/dubbyfs2ogulw3x/pa_gapps-modular-micro-5.1-BETA2-20150313a-signed.zip?dl=0
[Samsung Galaxy Nexus] kb8no:
Thanks all for the help. These questions may be helpful to others also.

If I choose to use f2fs formatting, the first flash needs to indclude FML5.1, busybox, and SuperSU all together before booting for the first time. The ROM needs to be flashed first, of course. Busybox is a dependency for SuperSU if using f2fs formatting. Without busybox on the first boot the ROM will lock with f2fs formatting. The order of flashing busybox and SuperSU probably don't matter but it doesn't hurt to flash busybox before SuperSU if for no other reason it is at least philosophically a dependency. When MW gets around to baking busybox and SuperSU into the ROM this will all be a moot point. Do I have this right?

If I choose to use ext4 there aren't much restrictions and I could flash the ROM and download both busybox and SuperSU from the playstore after I have flashed the ROM. On the other hand, it doesn't hurt to use the same process as the f2fs formatting above. Is this right?

In all my years of flashing ROM's it is usual to flash the ROM and gapps on the first flash. Is there any reason not to include gapps on the first flash with FML 5.1? I know it doesn't hurt to flash gapps after the first boot but it is necessary?

Regarding which gapps to use for FML 5.1, does it matter much as long as it is gapps 5.x. So I now have the following gapps options available below. Can I really use any one of these? Is one any better than any other?

pa_gapps-modular-micro-5.1-BETA2-20150313a-signed (pa beta)

pa_gapps_modular-mini-5.0.1-20150315 (pa official)

FML-GApps-5.0.x-20150101-tuna (from the OP)

The kernel and MMS Fix can be flashed at any time so maybe best left until after you get the ROM working. But is there a rational reason to wait? I have flashed ROM, gapps, and kernel together on the first flash for years as well. Any thoughts?
[Samsung Galaxy Nexus] Rushead:
The only reason to not flash all at once is if the op says so. Sometimes certain levels of development require special procedures based on how far along the rom is.

For gapps differences, see here: http://xdaforums.com/paranoid-android/general/gapps-official-to-date-pa-google-apps-t2943900
[Samsung Galaxy Nexus] kb8no:
Thanks. I get the difference between different Gapps packages. My question is related mainly to the difference between pa gapps 5.1 vs pa gapps 5.0. rather than the different pa packages. To me, this forum is not clear about which Gapps to use after going from FML 5.0 to FML 5.1. There are different messages. So the question is more about what is working for people. Does it matter?

The OP says to flash the ROM, flash gapps, then boot. Earlier post in the last 24 hours says not to flash gapps on first boot. Does it matter?
[Samsung Galaxy Nexus] Rushead:
Flash the gapps in the op. You don't need to boot between flashes. 5.0 is different from 5.1. Not sure what exactly makes them different. Some 5.1 roms won't boot with 5.0 gapps.
[Samsung Galaxy Nexus] kb8no:
I did a factory reset and then wiped system as MW directs but doubt it is needed cuz flashing the ROM reformats system. I then flashed FML 5.1, busybox, SuperSU, and pa gapps 5.1 beta all in one flash together. It booted perfect and works flawlessly. The FML gapps is 5.0. Maybe it works but I felt better using the 5.1 gapps for a 5.1 ROM.

I then flashed the kernel and MMS fix together no problems. I bet I could have flashed everything all together at once.

Its a super nice ROM. Very smooth. Better than FML 4.4.4. I like what I see so far. No wailing from my wife. I'm jealous cuz she has Lollypop on her GNex and I will never get past 4.4.4 on my S3. She won't trade.

I'm missing settings for the off menu options (like boot into recovery) and can't find them. Any work around? This is just great.
[Samsung Galaxy Nexus] eriscentro:
I'm running the V2 ROM with the gapps listed in the OP, the mms fix, and the stock kernel, with ext4 partitions. The phone is running beautifully, although I'm having issues with network drop outs. I believe it's between 4G/3G handoffs - I'll completely lose cellular connection. I'll show white network bars with a triangle next to the indicator. I can't place calls, send or receive texts, or use the data. I fresh flashed everything listed above, and am still having issues. Not sure what's causing it. A reboot seems to fix the problem (an airplane toggle does not).
[Samsung Galaxy Nexus] erk1725:
+1

It does seem to fix itself after a short period, without a reboot.....at least for me. It is rather frustrating, but the ROM is awesome! I think I remember reading a post somewhere by MW stating he had a "handoff commit" somewhere, that needed to be added. Hopefully it will be in the next build

Thanks
[Samsung Galaxy Nexus] MWisBest:
Hey guys, been a little busy. I got sidetracked with improving the audio HAL... again...

List of upcoming changes:

- Built-in Superuser and busybox.

- Offline charging fixed.

- Audio HAL improvements:

Previously, our audio HAL has always required some sort of resampling to be done on audio, which can cause pitch shifting (among other things), and has been a dumb limitation on what is otherwise fantastic audio hardware. This ends now. It's not perfect yet; our hardware supports sampling rates of 44.1kHz (most music) and 48kHz (most movies and TV shows) without resampling, but so far I've only been able to get the audio HAL to do one or the other, not both. For now I'm going to use 44.1kHz, as music is what's primarily played I'm sure. (NOTE: This doesn't mean you won't hear movies or something, it'll play just fine, but it'll run through a resampler first. I've added a higher quality resampler to make it less noticeable, if not undetectable, but it'd just be nice to not have to do resampling at all is the idea.)

I also figured out something that will help me cut down on build times (and release new FML builds faster!).
[Samsung Galaxy Nexus] MongolPup:
Using the 5.1 on F2FS with the gapps you posted etc, no problems. Then I flashed full auto R12, no problems for a few days, then this morning I decided to charge while off because I didn't have a lot of time and when I rebooted the phone (after it had booted itself to recovery after charging for a bit), I got the password screen. And I assume the fact that I had uninstalled Google Keyboard a long time ago to use swiftkey, there is no way for me to enter my non-existent password anyway. Recovery tells me the internal SD card has no free space, that there is nothing on it and that it can't mount the data partition, which I imagine is how things appear if you have it encrypted.

What did I do wrong? Not sure if this should be in this thread or the kernel thread so I thought I would start here.