yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bryantjopplin:
Just podcast your development so peeps can watch lol j.k but for real just got a 3800mah battery for the gnex and this rom. Loving the phone all over again.
[Samsung Galaxy Nexus] MWisBest:
That's over here: http://xdaforums.com/devdb/project/?id=6111
[Samsung Galaxy Nexus] :
i dont like cwm i use twrp
[Samsung Galaxy Nexus] csking33:
Unfortunately, you have to be on cwm to flash any 4.4 ROM as of right now. Use ROM manager to install cwm if you want to flash this or wait until TWRP updates.
[Samsung Galaxy Nexus] MWisBest:
Unfortunately, TWRP doesn't support flashing (proper) 4.4 ROMs at the moment. I'm fairly certain it's due to the SELinux changes introduced in Android 4.4, and CWM 6.0.4.3 supports these changes just fine. I would honestly prefer to use TWRP as well, but this is the best we can do at the moment.
[Samsung Galaxy Nexus] csking33:
Delete...
[Samsung Galaxy Nexus] :
please tell me that cwm doesnt use blobs on the gnex? it takes up way more space when it does that that is why i no longer use cwm
[Samsung Galaxy Nexus] MWisBest:
I honestly don't know. I haven't bothered backing up anything lately. I checked out TWRP's GitHub, and it looks like they're close to finishing updating for KitKat if they aren't already. If you're willing to wait, I could maybe try building TWRP myself tomorrow, but I need to get some sleep! There comes a point where caffeine doesn't help anymore. :(
[Samsung Galaxy Nexus] :
no sleep.NOsleep, i need it, I NEEDit, haha yeah i can wait. thank you hopefully everything goes smoothly cause id really hate to put cwm on my device.
[Samsung Galaxy Nexus] Enter The Nexus:
Y u no like CWM?
[Samsung Galaxy Nexus] :
i dont like the interface and as i said in the above post, the blobs. i think it was on my nexus 7 they were using blobs and that takes up way too much space and its just annoying.
[Samsung Galaxy Nexus] blarsen1620:
I can't find the original post but, someone chimed in and pointed out as soon as your device boots up the first time from flashing, like when your sitting on the start screen, pull your battery and reboot. Data working every time. I have tried this on multiple 4.4 ROMs and works every time.
[Samsung Galaxy Nexus] AirBoss24K:
Hi there! In addition to the data problem, I'm running into multiple reboots. Typically I'll be bouncing between apps and the device will just hang there. To be honest, it won't reboot until I pull the battery, which is even worse imho. I had this happen 3 or 4 times in the span of a half hour. Notably, I accidentally forgot to format /system before installing (things that happen when you're running on no sleep and up late on the internet) so I'm thinking this may be part of the issue. Reflashing likely needed at this point.
[Samsung Galaxy Nexus] swordrune10:
just wiped cache to see if that helps with the reboots ( probably won't ) but back to the not turning off screen thing.. it's rather consistent now.. on boot can't turn off screen.. so what I do is I set screen of for 15 seconds and as soon as screen turns off it works fine
[Samsung Galaxy Nexus] MWisBest:
Alright, I'm beginning to see the screen freeze issues as well that I believe you guys are reporting. I have a few theories on what this is, the first of which being with using the "big" Fancy Kernel, that being the version which frees up a bunch of extra RAM (70MB or so). Considering the improvements that appear to have been made with regards to RAM in KitKat, I'm either going to skip out on the "big" version entirely or just kind of ease back on the RAM it frees up. I'm feeling a little under the weather today, so I'm not sure how much I'll get done today for dev work but I'll at least attempt to fix the screen freeze issue as well as get a possibly working with KitKat TWRP built.

Thanks again for the feedback, I probably wouldn't have been able to narrow it down as easily without it, particularly swordrune's post stating this issue started with the build that changed up the kernel. It's probably helpful that I don't require logcats with reporting issues, kinda reminds me of some of the reasons behind OmniROM with the annoyance of people not allowing reporting bugs on nightlies and also just shunning away anything without a logcat. IF a dev is stumped and can't reproduce something themselves, THEN they should ask for a logcat! :P

EDIT: There have been some new developments in regards to possibly updated GPU drivers in the latter pages of this thread: http://xdaforums.com/showthread.php?t=2071021

I'm looking into this at the moment before I put out another build just yet.
[Samsung Galaxy Nexus] AirBoss24K:
So your screen actually won't turn off after you boot up? I haven't run into this issue at all. I get the graphical glitches that people talk about in specific apps as well as when I rotate the device, but other than that my only real issue is the device hanging during normal activity. I'll just be casually using my phone and the next thing I know, the screen is frozen and I need to pull the battery to reboot.

I know there were talks of random reboots, but I didn't see anyone saying anything similar to my freezing/required battery pull issue. Any thoughts on what could be causing this?

Also, for people who use 2 step verification for your Google Accounts, when you boot up for the first time, the device will forcibly make you sign in via browser... the stock browser. If you aren't quick about it, the screen to input your info will go dark and not come back. You need to return to the previous screen and be ready to tap that input field right away when you hit "next" to provide your info. If you can manage to click the field and pull up the keyboard, you should be able to get through the sign in process - your graphics will freak the hell out but it will still get you signed in and running. Keep in mind, you will need to make use of a backup verification code because Google sending you your code via text isn't going to work (because you haven't signed in yet to access SMS lol).
[Samsung Galaxy Nexus] swordrune10:
yea that's normal too.. I'm back on cm 10.2 but next release in this rom I will be on a fresh data wipe.. so we'll see how that goes
[Samsung Galaxy Nexus] MWisBest:
I don't know what convoluted problems you're having with 2-step verification, I've always had to just use a application-specific password thing with Android and 4.4 worked just fine with that! :p
[Samsung Galaxy Nexus] AirBoss24K:
That's a simpler solution... Thanks lol
[Samsung Galaxy Nexus] swordrune10:
ya I had the same problem, but I got through it somehow x_X luckily I have my Google voice number as the secondary text receiver
[Samsung Galaxy Nexus] MWisBest:
Sorry I wasn't able to get a new build out today, got a little carried away with working on the newly discovered GPU binaries. If anybody is interested, I put up what I got so far on my GitHub in the kernel and imgtec repos under the branch "android-4.4-exp". It's not building yet and I honestly don't know if it ever will, kernel stuff like this is way out of my league in my opinion but I wanted to see what I can do and maybe get the ball rolling for any other devs that are interested.

The good news was that I've gotten good enough with git to the point where I don't have to struggle much to stash away changes in a new branch (like, I was putting all this new work into the android-4.4 branch I was using but wanted to just stash it away in android-4.4-exp and then restore android-4.4 to what it was beforehand) or completely revert things etc...

So while I sleep I'll have a fresh build run, hopefully this will fix some of the screen freeze things we discussed, and I also have a few other small surprises in there...

In the meantime, I got a tip from aj1140 via PM with a way to possibly fix mobile data if you're having issues:

"Open settings, under Wireless & Networks choose More...

tap on Mobile networks.

Make sure Data enabled is checked, if isn't check it.

Under Network Mode make sure it's set to 3G if it's not change it to 3G

tap the Home button

Open the phone/dialer

Dial *#*#4636#*#*

Tap on Phone Information

Scroll down then in the drop down choose GSM/CDMA auto(PRL)

Tap the Home button

In a few moments your 4G bars should appear and if you go into a low spot it should still switch back to 3G. This is the only mode I found that actually does the hand off."

That reaffirms what I mentioned earlier where the VZW radios treat the Global mode (what I presume is "GSM/CDMA auto(PRL)") as the LTE mode. I'll try and get this fixed tomorrow so you can just use the "Mobile Networks" menu as usual to enable and disable LTE.
[Samsung Galaxy Nexus] MWisBest:
New build up! Check out the changelog before flashing (I hope you do that already, but this time it's very important!). :D
[Samsung Galaxy Nexus] Shilalygawd:
I broke down and got the 5900mah Zerolemon. I only have to charge it every two days of hardcore use when I'm on the stable version of this ?
[Samsung Galaxy Nexus] bryantjopplin:
Yeah I got an s4 with a 5600mah and gnex with that one and I find my self using the gnex more now since I updated it. Just wish the random crashes would subside.
[Samsung Galaxy Nexus] Zeinzu:
Thank you.
[Samsung Galaxy Nexus] MWisBest:
That's too bad, because coming soon...

EDIT: Let me fix that a little:
[Samsung Galaxy Nexus] ataris_kid:
AW YISS. I think I love you.
[Samsung Galaxy Nexus] PicoDeGiao:
WOW!!! That would be awesome. You are a wizard, good sir.
[Samsung Galaxy Nexus] KShion619:
Already!? Man you are speedy!
[Samsung Galaxy Nexus] Alton (Halo 2):
Wish you the BEST of luck. :D
[Samsung Galaxy Nexus] Zer0_Cool:
If you need any beta testers let me know! I don't have any classes today.
[Samsung Galaxy Nexus] Dirty_Jerz:
Tried building from your repos....no go yet...overlay errors using aosp_toro-userdebug. I understand that you are still working. I will try to be patient. Thank you for your excellent and rapid development.

Edit:

Ahha, aosp_toro.mk: PRODUCT_RESTRICT_VENDOR_FILES := true

Let's change to false and see what happens :P

Edit2:

Built cleanly & fastboot flashed system.img but no boot. Need to hook up my debug cable to see whats wrong. :(
[Samsung Galaxy Nexus] rice923:
I miss you guys[emoji22]

I moved to a rooted gs3. The gnexus is still in the family though, so still looking forward to some great advances! Keep it up MW
[Samsung Galaxy Nexus] vladimirhtg:
Definitely had issues with camera on SlimRoms but it worked intermittently and almost seemingly randomly.

What drivers should be in /sys/module?

I looked at the dmesg and the logcat and found a couple of interesting things, but not what I was expecting. Like this from the logcat:

And the kmesg only showed one line about loading anything related to video (pvrsrvkm_sgx540_120), no other drivers. No v4l or anything that looked like video. A friend helped me out bigtime with looking into these things, but I'm getting there.

Backing up a little bit:

I had intermittent camera functionality before FML

My front camera chip/board/thing specifically had water damage a ways back after I replaced my front assembly. So, there's that.

I had camera functionality after replacing the front facing camera, and I currently have proximity and light sensors working

And....that may be it.

So I'm going to think about this a bit more. Might......*sigh*....well I might try going back to stock just for the heck of it, however this is my daily driver. Maybe I'll take the lcd assembly out to check out how the camera looks physically.

Thanks for the help guise!!
[Samsung Galaxy Nexus] mastertech007:
It's MW skipping classes ? [emoji50]
[Samsung Galaxy Nexus] KShion619:
Or he could be remoting in as I am compiling for Grouper (Nexus 7 2012) :p and his current progress in toro
[Samsung Galaxy Nexus] thetakerfan:
Wow, was not expecting to see signs of life of this so soon. SHouldn't be surprised with MW's track record, but still. Damn
[Samsung Galaxy Nexus] MWisBest:
Lollipop says hello! Build available now.

READ THE INFO SECTION IN THE MAIN POST ABOUT IT BEFORE USING!
[Samsung Galaxy Nexus] arukemo:
a.. am i dreaming right now?

n-no.. t-this is a dream, isn't it ;-;
[Samsung Galaxy Nexus] legycsapo:
Is this real life ?
[Samsung Galaxy Nexus] KShion619:
Is this just fantasy
[Samsung Galaxy Nexus] legycsapo:
Caught in a landslide no escape from reality
[Samsung Galaxy Nexus] KShion619:
Bugs List

-----------

Web Portals (StarBucks Internet Signins) dont work on stock browser, actually the AOSP Browser just plainly doesnt work

2 Step Authentication falls under the same issues as Web Portals, i used App Passwords, that worked fine

4G/3G Appears to try to connect, it just doesnt, you have a 4G/3G and ! appear on the status icon, which is equivelent to the brown icon from KK

GAPPS package doesnt automatically mount /system, so make sure you mount system before installing otherwise you're wasting time

Memory Killer is a bit steep, frequently closes pages in chrome
[Samsung Galaxy Nexus] Zer0_Cool:
data is not going to work, he's still working on RIL.

can you mount /system in TWRP recovery options, or do I have to do this through adb?

Also, I'm on the TWRP build initially released to allow F2FS, do I need to update this or will it flash 5.0 without issue? I'll check and get a version as soon as I pull my old backup.
[Samsung Galaxy Nexus] jguerdat:
Should i do a fresh install or try just updating?
[Samsung Galaxy Nexus] KShion619:
just in the mount options is fine

Id say fresh, when i overwrote i ran into many a crash
[Samsung Galaxy Nexus] jguerdat:
Thanks. All went well until trying to use Play Store. Trying to log into google takes me to the browser (I suppose due to my 2 step authentication) and the browser dies. Just running the browser by itself causes the browser to crash. No error, just goes away.
[Samsung Galaxy Nexus] Zer0_Cool:
did you try signing into your google account in settings since there is no setup wizard?

I just reformatted, so I'm still in the middle of flashing everything. I'll report back if I can get it to work.

Edit: successfully signed in through accounts in settings, attempting to sync data now

This runs ridiculously smooth! The animations, everything is super fluid....very impressed. This is going to be insane once the FML tweaks are applied.

Edit 2: Using chrome beta, so far so good in terms of app switching tabs, but it did crash after a few minutes
[Samsung Galaxy Nexus] KShion619:
I used App Passwords for that, worked smoothlyish after that
[Samsung Galaxy Nexus] Zer0_Cool:
Phone calls and texting work, trying to enable google now I discovered that there is no location services available though.

Edit: Changed location services to high accuracy, it's good to go!
[Samsung Galaxy Nexus] RW-1:
Congrats on 5.0!

{Glass raised] May the bugs be ironed out quickly! :)
[Samsung Galaxy Nexus] jguerdat:
Reloaded fresh (data wipe, format system, cache and dalvik). Same problem trying to use settings, add Google account. I choose existing and enter username and password. It says signing in and then a new screen, Couldn't sign in. To access your account, you must sign in on the web. Touch Next to start Browser sign-in. When I go to the next screen, the browser seems to almost start and then dies. Same thing if I just try to use the browser by itself so the problem is the browser itself. The login fails due to Google's 2 step authentication and I'm loathe to turn that off unless someone knows that doing so doesn't cause me to have to re-authenticate my various devices.
[Samsung Galaxy Nexus] KShion619:
Use App Passwords, works fine that way, then remove the AOSP Browser, even bugs out sometimes on my Nexus 7
[Samsung Galaxy Nexus] jguerdat:
Are you using 2 step authentication? I can't authenticate without the browser. I've seen this scenario in the past, just never paid attention to it because it worked.
[Samsung Galaxy Nexus] Dirty_Jerz:
https://support.google.com/accounts/answer/1070457?hl=en
[Samsung Galaxy Nexus] MWisBest:
As others have said, you've gotta use an App-Specific Password for it at the moment. I'm aware of Browser crashing, and have a couple things lined up that at least one of them should fix it.
[Samsung Galaxy Nexus] jguerdat:
I see. I misunderstood what was being said. Trying again and will report back.

Edit: amazing what happens when you do the right thing. Thanks for hitting me between the eyes with that 2x4...
[Samsung Galaxy Nexus] RoxRedEye:
Dude, you're going from KitKat to Lollipop (a beta build), of course you should clean flash.
[Samsung Galaxy Nexus] Dirty_Jerz:
Building

[MENTION=3390093]MWisBest[/MENTION]: I'm building successfully but the OTA generation is only yielding a 5.3MB file (incremental i suppose) how can I force a full OTA.zip generation?
[Samsung Galaxy Nexus] ataris_kid:
I don't understand how this still isn't common sense by now.
[Samsung Galaxy Nexus] jguerdat:
Sorry, brain fart...
[Samsung Galaxy Nexus] Rushead:
Wouldn't boot for me. Stayed on boot ani for 20 minutes before batt pull. Was I impatient? Download was the right size, haven't checked md5. Will re-download.

Thanks [MENTION=4576677]KShion619[/MENTION] for the mount-system-for-gapps-install tip.

EDIT: duh, just read the ext4 only part. Nvm /EDIT
[Samsung Galaxy Nexus] Zer0_Cool:
yeah ext4 only, also I did actually get corrupted download of the gapps the first time, but I always check md5sums so I caught it.
[Samsung Galaxy Nexus] KShion619:
What app(s) do you use for MD5 summing?
[Samsung Galaxy Nexus] Zer0_Cool:
I use the terminal, in this case I had to format all my partitions from F2FS back to ext4, so I wasn't going to boot up before flashing this. I just checked the files before I pushed them in adb since data gets wiped in the formatting.

On linux it's easy, cd to the correct directory or put it in the path, then it's just

md5sum filename

This also works in the terminal emulator on the phone
[Samsung Galaxy Nexus] bagarwa:
Is there any way to obtain root on this right now?
[Samsung Galaxy Nexus] KShion619:
Look at the XDA Portal, the Nexus 9 root method should work here as well
[Samsung Galaxy Nexus] heXacode:
I use this for multiple type file check...
[Samsung Galaxy Nexus] otter34:
Ok 20 minutes is enough looking before I ask for help..how do I enable usb debugging
[Samsung Galaxy Nexus] arukemo:
Is it just me or do browsers like the stock browser and Chrome crash upon opening?

I have a feeling it has something to do with Android WebView service, however force-closing the application didn't help at all, not even rebooting.
[Samsung Galaxy Nexus] heXacode:
Its in developer options in Settings. If you don't have it turned on then go to About Phone and click on build number several times to enable it.
[Samsung Galaxy Nexus] Zer0_Cool:
You need to enable developer options first, go into settings>about phone, then click on the build number until you get a toast notification that 'you are now a developer'.

Go back into settings>developer options(now available)>tick USB debugging

This is a known issue.
[Samsung Galaxy Nexus] Cheetohz:
Is there a changelog?

:rolleyes:
[Samsung Galaxy Nexus] foxdog66:
How can I check what partition type mine is? it isnt in a bootable state right now, so from recovery/terminal/adb would be the options im guessing. And how would I go about changing it?

also, what recovery should be used? the one in the OP?
[Samsung Galaxy Nexus] zzpianoman:
In recovery make sure you mount the system partition. Next in adb type "mount" and it should list all of your mounted partitions and their respective filesystem types.
[Samsung Galaxy Nexus] Zer0_Cool:
Unless you went out of your way to install the specific recovery and re-format for f2fs, you're still on ext4. You would know if you changed to f2fs 100%
[Samsung Galaxy Nexus] foxdog66:
yep, looks like its ext4. I have a CMW-based recoery v6.0.5.1 that was installed from CyanogenMod, they had a option to install recovery along with nightlies... not really sure it will work or not...

I tried installing one of the earlier FML builds with the nano (i thing) gapps and had a bunch of force closes and didnt feel like messing with it so its been sitting collecting dust sense. been using a prepaid moto g in the meantime but this has me excited!!!
[Samsung Galaxy Nexus] Zer0_Cool:
Give it a try, although I would recommend updating your recovery to the latest TWRP in the OP:

KitKat/TWRP Stable 2.7.1.0

http://xdaforums.com/devdb/project/dl/?id=7349
[Samsung Galaxy Nexus] DBISGOD:
This ROM is amazing. Any eta to fix the browser and chrome issue? Id love to use this all the time. Amazing work, super fast for both 5.0 and 4.4.4

Installed Firefox and it works great. Going to try this out for my day to day use.
[Samsung Galaxy Nexus] bush911:
Looks great. Is GSM version available?
[Samsung Galaxy Nexus] Zer0_Cool:
sprint

http://xdaforums.com/galaxy-nexus/sprint-develop/rom-fml-fork-life-10-13-2014-t2903695/page3

other

http://xdaforums.com/galaxy-nexus/development/rom-fml-fork-life-06-05-2014-v2-t2764064/page101
[Samsung Galaxy Nexus] Dirty_Jerz:
fastboot flashall success

So as the title says, building fml_toro-userdebug and flashing using fastboot flashall works but recovery is biffed. Plugging in to charge while the device is off leads to a stalled battery w/ lightning symbol requiring a batt pull. Also, going from bootloader to recovery is no bueno. I cant get any debug messages from the recovery either, my cord doesn't supply +5V0 to trigger charging and there is no FIQ debugging enabled in the recovery image it seems. Gonna fastboot flash a recovery and go from there.

Great to be able to participate though. I'll see if I can't mess around with the recovery in the build process and get it going.
[Samsung Galaxy Nexus] Dvdxploitr:
I am having problems installing the FML-GApps-ASOP-5.0.zip......I am using TWRP and it said "Failed" almost instantly.....

EDIT: I got it working now. I installed the ROM, rebooted the phone and then went back into TWRP and installed Gapps
[Samsung Galaxy Nexus] Zer0_Cool:
you need to mount /system manually in recovery before flashing gapps
[Samsung Galaxy Nexus] zzpianoman:
You have to make sure that system is mounted before you install gapps.
[Samsung Galaxy Nexus] christianpeso:
What's is App Passwords and where can I locate it?

EDIT: Never mind. I found out what its about and got logged in.
[Samsung Galaxy Nexus] MWisBest:
Just got the browser issue fixed actually! Not sure when I can get a build up with it yet though, got other things I'm sorting out here at the same time and it's a bit of a mess...

Actually, from what I've seen, you gotta do the opposite: Make sure system isn't mounted before installing GApps.
[Samsung Galaxy Nexus] Zer0_Cool:
Sweet! The browser crashing and data are probably the 2 most inconvenient things right now. I have wifi on campus/at home though so I've been running this as a dd anyway :)
[Samsung Galaxy Nexus] rgw5018:
The problem with the browser crashing is that I'm unable to log in with two factor authentication, so I can't add my google account or get into the play store to install other browsers.
[Samsung Galaxy Nexus] DBISGOD:
You don't need to wipe to go from FML 4.4.4 to 5. Probably the best idea would be to go back and setup, then dirty flash.
[Samsung Galaxy Nexus] KShion619:
I can start building it and upload it to ya later today , as a sort of "Impatience Beta" if he changes it and isnt in that mess I'll update it ASAP assuming he doesnt beat me to the build

Nevermind... now i see what he's seeing, nothing but a bootanimationless bootloop
[Samsung Galaxy Nexus] jguerdat:
Tried this with the result of a locked up phone after installing the first file and rebooting. Reverted to backup...

---------- Post added at 06:19 PM ---------- Previous post was at 05:36 PM ----------

Read back a couple of pages to my similar problem. You have to use another device to go into yor security settings in your Google profile via the web (like setting up an app on a non-Google device) to generate a code that you use on the phone for the password. Took me a few iterations that I couldn't use anything on the phone to do this. Sort of a terminology issue and/or familiarity with the various methods you can use to authenticate.