yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] christianpeso:
I had got this when Bsmitty posted his build version of this ROM a few days ago. I thought it was specific to the ROM that he had built. I had to flash supersu in recovery as all root apps were saying I was not rooted when I tried to run it. Havent tried this latest version yet.
[Samsung Galaxy Nexus] kinleyd:
Thank you [MENTION=3390093]MWisBest[/MENTION]. Hope you are fully recovered now and enjoying the New Year. I look forward to running v3 on my trusty maguro.
[Samsung Galaxy Nexus] Alton (Halo 2):
Can anyone else flash the gapps with the ROM? Mine says error and told me to free up space in the recovery.
[Samsung Galaxy Nexus] kbluhm:
I flashed the previous Gapps which were still on my device with no apparent issues... but yeah, had the same issue.
[Samsung Galaxy Nexus] applerulez1:
Yeah I wrote about this somewhere. You have to flash the os. Do your first boot. Go back unmount system and install gapps.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] TheYoz:
I just use PA micro Beta 5 with no issues.
[Samsung Galaxy Nexus] Mach3te:
I tried on my Galaxy Nexus, and system wasn't mounted in the recovery, so I remounted it and unmounted once more and tried to install pa mini and got the same error.

---------- Post added at 10:17 AM ---------- Previous post was at 10:15 AM ----------

I did this as well and it worked fine. PA Modular Micro did the trick. Not sure why that error popped up
[Samsung Galaxy Nexus] RW-1:
Size/space left in recovery becomes an issue on smaller, older devices, you cant run the full apps installer, as there won't be enough free space. the micro works because it installs a minimum of GApps, of course then in the OS itself, you can add whatever you want from the GPS ...
[Samsung Galaxy Nexus] JoeSyr:
Out of curiosity, is the work being done in the "samsung_omap4_common" project line on Omni relevant to this device? I see that the maintainers for the Galaxy Tab 2 and Galaxy S2 variant that use OMAP 4430 have bee cracking away at bringing up 5.0 for their devices and working under this header a bit recently. Just trying to wrap my head around how the android open source communities and projects end up linking together.
[Samsung Galaxy Nexus] szale9001:
Things are working pretty well here. Charger light is annoying, but not a deal breaker. Even able to take a picture now and then with the Google Camera from the Play store.

Had the issue too will the FML gapps. Didn't think to use micro so I went for broke and removed the free space check in the update-binary lol. It worked, but I had 31K of system space until I uninstalled a few unneeded apps from Titanium. Guess micro would've been easier :p

Question for anyone though, or [MENTION=3390093]MWisBest[/MENTION] , is there any way to get the lollipop Google Dialer on here? I used the Caller ID and search functions pretty regularly and I am starting to miss it. I tried using the N5 apks but no dice. Just wondering if anyone might know something
[Samsung Galaxy Nexus] RW-1:
Lately, with most of the major GApps available in the play store, you can go micro and just let the phone reinstall the ones you use anyways, just the core play services and store to get you up and running :)

I'd love to see the lolli dialer as well ....
[Samsung Galaxy Nexus] erk1725:
I just have to ask what Im doing wrong here......I read the thread and noticed some people are having issues flashing the new gapps. Having to have the system unmounted, or flashing the rom first and then booting into rom and then back to recovery to flash the gapps. I flashed the rom and booted and then rebooted to recovery to flash the gapps and everything went fine, except for when I tried to flash smittys latest kernel. Everything flashed fine, but some of my apps disappeared. Im looking forward to trying the new "messenger" app included for messaging, so after I tried to install the kernel, and rebooted, that was one of the first apps I noticed was gone, and replaced with the normal "messaging" app?

Should I flash the rom and kernel and then boot, and then reboot to recovery to install the gapps? I hope this made sense.....sorry if it didn't

Thank you so much to MW and everyone involved with this.....its running great! I just need to get some stuff on my end ironed out

Thanks again!
[Samsung Galaxy Nexus] RW-1:
I've always flashed rom, flashed GApps, then booted it up ..... The release prior to 01/04 MW had corrected the issue where /system has to be mounted AFAIK ....
[Samsung Galaxy Nexus] pkgnex:
Yep! Flash ROM, Flash PA Micro GApps, Flash SuperSU, then boot system has worked for me since the 12/7 build (wiping /cache, dalvik, and /system before flashing a new version, as well as /data the first time going to FML).
[Samsung Galaxy Nexus] Christopher8989:
Where's is that? You mean factory reset while still in recovery?
[Samsung Galaxy Nexus] erk1725:
Thanks RW......I usually flash ROM gapps kernel then boot. I just went this route because it seemed like some were having issues with the gapps. I'm not sure how I go about it now but I'll keep playing :)

I would like to run the newest FML with mW gapps and bsmittys kernel. I guess I'll make a backup and flash some stuff and see what happens. I'll report back tomorrow

Thanks again everyone!

Edit. I can't seem to send MMS through this "messenger" app :( so I'll try another gapps package
[Samsung Galaxy Nexus] RW-1:
No problem ... I try when I can to assist, sometimes I'm even right about things hehehe.

For the MMS thru messenger, have to selected it as the default messaging app, instead of hangouts? Could still be related to the camera issues on the ROM though ....

"Where's is that? You mean factory reset while still in recovery?"

Format /data is in the advanced part of TWRP, however be warned, that will kill ALL of your data - the factory reset function in TWRP will leave media intact but wipe the rest of /data/ formatting it kills it all.

One more time - formatting /data kills it all. Kinda like formatting /system kills the ROM itself.

Just so that there is no misunderstanding :)
[Samsung Galaxy Nexus] Christopher8989:
There's delay when start something but then it'll zip alone quickly.

I use donated TricksterMOD version.

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

I select Wipe, then instead of swipe the blue ball to format I select Advanced, then check davik, system, data and cache, leaving internal storage and usb something alone. This works fine.
[Samsung Galaxy Nexus] hawk687:
I'm on toro clean flashed 1/4 build, no root at boot. Flashed SuperSU, still no root. Any advice?
[Samsung Galaxy Nexus] cujo6801:
See if root is checked in the developers options

Sent from the "DOG" pound
[Samsung Galaxy Nexus] christianpeso:
I had same issue dirty flashing over BSmittys built version of FML that he released last week to test his newest kernel at that time. Using Micro gapps from the PA team labeled 12/25, beta 5 I think. Wiped both Caches and System, kept data. Flashed the ROM,Gapps, and BSMittys newest kernel in same session. Upon restart, all root apps were stating that my phone was not rooted. Flashed Supersu v2.43 beta in recovery and after restart I have root now.
[Samsung Galaxy Nexus] applerulez1:
I wish we could sticky comments because this could help many others on the other carriers of this ROM.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] dbt816:
So I spoke too soon here. The gps-lock wakelock issue is still present in the latest build. It seems that it prevents deep sleep until an application actually "touches" the GPS, then everything is fine until the next reboot. Note that if you always have Location Services enabled, you'll never see the issue. Maybe something with the way the 5.0 ROM initializes the GPS that isn't quite right on the GNex? I really don't know...
[Samsung Galaxy Nexus] Meticode:
Glad to know it wasn't just me. In my case I got a 2013 Moto X and love it. It goes into deep sleep constantly.
[Samsung Galaxy Nexus] MWisBest:
The GApps package I put together is very close on the size limit. I'm guessing those having issues flashing it are flashing SuperSU. I'll slim it down for the next build.

The built-in Superuser is working fine for me, but I think you have to enable Development Settings for it to work, so if you're having issues with it, make sure you've done that. It should be in the bottom of the Settings app list...

I'm not totally sure what's going on with the GPS wakelock.

Charging light should be fixed for the next build, and the camera will have some progress made.
[MENTION=2853378]Nephilim[/MENTION] WTF, 2564 storage I/O?!?!
[Samsung Galaxy Nexus] Mach3te:
Beware that the root/SuperSU issue may be caused by people flashing SmittyV's Beta 3 Kernel. I noticed a few of us in here having this issue and it was related to flashing this after the rom flash.
[Samsung Galaxy Nexus] Rushead:
I just installed this using PA gapps micro beta3 and everything works like it should (except titanium b/c of its SuperSU issue). All my other root apps work w/o having to do anything with dev options. Rebooted and installed Smitty's latest. So far so good. Gonna try some Neph settings...
[Samsung Galaxy Nexus] Nephilim:
So you like my settings? ;)
[Samsung Galaxy Nexus] Dirty_Jerz:
[MENTION=2884059]MWizBest[/MENTION]: how much of an improvement in build time do you see with a prebuilt chromium?

EDIT:

Also I'd like to request a pick if you could. The advanced reboot menu from omni is 5.0 ready. It is only enabled under dev settings, not by default so it shouldn't bother anyone.

It's two parts:

frameworks/base:

[1/2] base: Reboot Recovery & Reboot Bootloader in Power Menu

and packages/apps/Settings:

[2/2] Settings: advanced reboot menu

I'll also submit a pull request on GH but for future reference, which method would you prefer?
[Samsung Galaxy Nexus] erk1725:
Just wanted to post how I made out last night. I ended up wiping everything and starting over. I first tried to flash all 3 zips at once, but got the error about the GApps being too big, so then I wiped everything again and flashed ROM and the latest Smitty kernel, then booted up, then rebooted to recovery, wiped dalvick and cache, and then flashed MWs GApps, and everything went fine. Back to downloading all my apps and settings.

Thank you everyone!!
[Samsung Galaxy Nexus] Christopher8989:
I noticed sometime the gps icon on the upper left pops up for maybe 5 seconds then off. Which means gps wa trying to locate. Is that what you're talking about?
[Samsung Galaxy Nexus] Meticode:
Thanks for all the help guys. After a long-over duo decision I finally dumped the Galaxy Nexus. It's 3 years old, and most importantly the battery life just plainly sucks. Even after upgrading to the official 2100 mAH battery. If you're curious I switched to the Motorola Moto X (1st generation) and I love it so far. It goes to sleep constantly, I left data on 4G all day, used it moderately and I'm at 55% with 2 hours of on screen time. If you're thinking about buying a phone out right, it's not a bad decision for this one. They're running around $200 brand new.

Again, thank you guys.
[Samsung Galaxy Nexus] dbt816:
No, that's normal behavior with GPS enabled. This issue is when you boot with GPS disabled, there's something going on that keeps hammering a kernel wakelock named "gps-lock". The net effect is that it drains the battery prematurely.
[Samsung Galaxy Nexus] hawk687:
This fixed it for anyone who can't get root. I had the wrong SuperSU version. Thanks all my bad on noobishness
[Samsung Galaxy Nexus] fivefour:
Does this newest build have a proper reboot menu?
[Samsung Galaxy Nexus] Rushead:
I'm getting @ 6500 on Antutu with Neph settings. My phone simply won't run above 1.5 ghz cpu. At 1350, I get @ 17000 range consistently.
[Samsung Galaxy Nexus] christianpeso:
No. I did read somewhere Omni ROM has implemented it and someone was requesting MWisBest pull it and incorporate it. But its not there as of yet.
[Samsung Galaxy Nexus] fivefour:
Thanks, I appreciate it.
[Samsung Galaxy Nexus] Mach3te:
I also saw the Unofficial CM12 builds use the reboot menu as well. Its sitting in the Developer Options.
[Samsung Galaxy Nexus] hexhead:
Had the same issue with gps-lock wakelocks. Happens for me on KK ROMs too. Disabled "Location Reporting" in Maps/Settings/Google-location-settings/Location-services and all is well. After 6 hrs unplugged, BBS shows gps-lock wakelocks at 0%.
[Samsung Galaxy Nexus] dbt816:
I never had the issue. on KK. The wonders of the GNex never cease to amaze :) lol!

So you went into the Google Maps app and disabled location services there and it stopped the wakelock issue?
[Samsung Galaxy Nexus] poo706:
I used to get it on slim, both jb and kk. Never could figure it out and never ran slim because of it.

[poo]
[Samsung Galaxy Nexus] hexhead:
Left location services on, just turned off location reporting. Had to do the same on some KK ROMs.

Of course the gps-lock wakelock still occurs, but waaaaay less and it's not an issue for me:
[Samsung Galaxy Nexus] shwise:
Lollipop booting up without System UI.

My phone just boots to the launcher, without any wallpaper, softkeys, status bar, or lockscreen. I've had this same issue on all of the Lollipop builds.
[Samsung Galaxy Nexus] rohitece06:
The provided gapps fails and says "not enough space left" :(
[Samsung Galaxy Nexus] Rushead:
Have you not read any of the last few pages?
[Samsung Galaxy Nexus] Dirty_Jerz:
[MENTION=3390093]MWizBest[/MENTION] I know you're working on the camera as of late.

I've been looking into getting the active display to come up on motion. It requires a sensor to send a wake-up (either SENSOR_TYPE_SIGNIFICANT_MOTION or SENSOR_TYPE_PICK_UP_GESTURE) ref: DozeService.java

Unfortunately our HAL MPLSensors.cpp doesn't implement it. There is an implementation in the 65xx/libsensios_iio/MPLSensors.cpp so I took a look at the product spec sheets of the two chipsets (65xx 60xx) and there is a wake-on-motion interrupt for the 65xx. I'm pretty sure that's how they use it as it wouldn't be sucking down power all the time. It still could be done another way though. Looking through the 65xx's method in MPLSensors.cpp and SIGNIFICANT_MOTION in general, it seems as though the sensor is turned off(?) after a SM is detected. I'm going to keep looking into it but it doesn't look promising.

I reference this based on your commit msg. What did you have in mind when you were on this topic?

Thanks!

-dirt
[Samsung Galaxy Nexus] MWisBest:
HUGE work on the camera. There's going to be both improvements and regressions... (EDIT: Removed temporarily) this zip is not flashable, it's a couple .so files that need to be placed in the same location on the phone as they are in the zip (e.x. /system/lib/hw/camera.tuna.so in the zip, goes to /system/lib/hw/camera.tuna.so on the phone). If somebody wants to make this zip flashable, be my guest.

NOTE: You may need to clear the data of your preferred camera app.

My thought was that there must be something I can come up with for it... I was able to make a temperature sensor out of the barometer, so maybe I can make a 'pick-up sensor' out of the accelerometer?!
[Samsung Galaxy Nexus] RW-1:
Awesome if camera gets corrected, I'm a patient guy .... I'll be on that build in an instant.

I don't know if you want to try making the accellerometer the pick up sensor, only in general because what tolerances would you apply to it ? My thoughts being that how large a motion wold then be perceived as a pickup, lest the thign is going off all the time, in pocket, etc. (which may be happening now on stock, etc.)
[Samsung Galaxy Nexus] Nephilim:
I don't even care if it turns on when I pick it up, that really doesn't matter. I just want ambient display to wake my device properly on incoming notifications. That's just me though, not trying to sound demanding or anything, just saying no worries if the sensor doesn't turn it on by picking up the phone.

BTW, great work on the latest build, your optimizations along with Smitty's beta3 kernel and my custom settings have this phone flying with great battery. :D
[Samsung Galaxy Nexus] MWisBest:
New build up. Give the camera a try!
[Samsung Galaxy Nexus] RW-1:
MW,

Awesome as always, I'm going to try this one, wirgw the latest PA micro GApps package.

However, of note, while the new build link is god on the OP, the link itself needs editing, as it still lists the jan 04 timestamp, this may cause some confusion. Humbly submitted.
[Samsung Galaxy Nexus] MWisBest:
Thanks for the heads-up, should be fixed now :)
[Samsung Galaxy Nexus] RW-1:
You're welcome ....

Awaiting my current TWRP Backup, and the fun may commence (unless my daughter's homework gets in the way, argh ....)

UPDATE: Ok, don't do homework with your child and flash, I made a noob mistake - I had grabbed the 4.4.4 version of PA Gapps hehehe. Booted without but wouldn't do anythin on usb to teh computer (dev options and usb on), so ...

Restoring from my backup and will hit it again, already grabbed the proper 5.0.1 beta 5 from their site, will use micro and allow my other stuff to come in thru GPS restoration.

It happens .... Facepalm on my self ....
[Samsung Galaxy Nexus] Maximinus I:
Tried it out camera worked the first time I used it but never again. YouTube did the same or worked for a while then it errored out and stopped working. Everything else seemed fine. Good job as always MW
[Samsung Galaxy Nexus] PainFly23:
Same. I was able to take a few pictures using Google Camera (white balance seemed off though), but now it can't connect. Camera Zoom FX, which I've been using the past little while, has the same issue. It's nice to see progress being made though. Hopefully we'll have this sorted out in no time.
[Samsung Galaxy Nexus] zzpianoman:
Try to copy over your own calib.bin file if you happen to have it. If not, flash a KitKat ROM and copy it from /data/misc/camera/R5_MVEN003_LD2_ND0_IR0_SH0_FL1_SVEN003_DCCID1044/calib.bin

This build includes a prebuilt camera calibration file which may or may not work with your individual camera.
[Samsung Galaxy Nexus] PainFly23:
Thanks, but I'm headed back to the 1/4 build right now. I don't quite have the time right now to go through another flash, and I can make do with Camera Zoom until the next build.

Also, I noticed hardware video decoding in the new build seems to be broken again and is acting like it was before the December(?) build. YouTube doesn't work and MX insists on using the software decoder.
[Samsung Galaxy Nexus] Nephilim:
1/08 build is working great, camera is taking crystal clear pictures even in low light and I'm having no issues viewing HD videos on the Youtube app.

Thanks MW, every new build is better than the last!! :D
[Samsung Galaxy Nexus] ibenjakinov:
The latest Lollipop build supports F2FS?
[Samsung Galaxy Nexus] KShion619:
Yes, all builds of FML support F2FS
[Samsung Galaxy Nexus] otter34:
I noticed the discussions about the camera then later you posted an update. With the new update is it ready to go or do I have to move files around to get things working? I've been afraid to try lollipop but it's time to take the plunge I think. Thanks
[Samsung Galaxy Nexus] otter34:
Can I just disable the camera with titanium and use Google camera or would that cause problems?
[Samsung Galaxy Nexus] amd_h4x0r:
I dirty flashed from 1/4 to 1/8 and now I don't have any issues with the camera (previously was taking green pics) or other apps that use the camera. I removed the aosp camera with titanium and just use google camera.
[Samsung Galaxy Nexus] Nephilim:
I should've mentioned that I dirty flashed, I always dirty flash unless it's a substantial OS update (i.e. 4.2 to 4.3 etc). I figure that's how the updates work with legit ota's and the roms wipe system when updating anyway so no point in losing all my settings and homescreen setup etc.
[Samsung Galaxy Nexus] zzpianoman:
hehe and just look at all of the issues regular users have after those ota updates ;)

But you're right.....shouldn't be much of a need to do a full wipe between incremental OS updates.
[Samsung Galaxy Nexus] pkgnex:
The Google Camera (from play store, not ROM AOSP camera) works fine for me on the new build.

Thanks MWisBest!

I also dirty flashed, with the addition of wiping /system. I rarely wipe /data unless it's a android letter version change or a ROM switch.
[Samsung Galaxy Nexus] ice20978:
I'm also having location issues - not just in google now either, but weather apps, and even google maps.

It seems to be a problem with location from wifi/cellular data not working - when it gets a GPS lock, everything is fine, but inside, where it could normally get my location accurately from wifi, all sources just say "location unavailable" (or something similar).
[Samsung Galaxy Nexus] MWisBest:
Jeez, yet another glitch to look into! FML, lol.

Iiiiin other news, I did get the temperature sensor working (worked first try actually, I thought I'd have to do a bunch of tweaking and recompiling the code etc. :eek:), however as I suspected there is too much heat "pollution" given off from the innards of the phone to really make it of any use. It tends to be fairly close to the reported temperature of the battery actually. There might be some sort of way for me to apply a "filter" on it to make it useful maybe, but it was nice to at least try it out! :victory: I'll probably just leave it enabled for now, no harm in just letting it sit there really.

I also slimmed up the build a bit by removing some useless crap, shaved off about 16MB or more. :highfive:

I'll continue to post updates on how dev stuff is going tonight and maybe get up a new build. :)
[Samsung Galaxy Nexus] mrcooter:
Thanks. Never even thought about the kernel factor. Wasn't sure if it was something that could get added in sorta like a cherry pick or what. Ha. Thanks for the info :)
[Samsung Galaxy Nexus] MWisBest:
Sorry about the lack of updates, was busy yesterday watching the Packers lose and also doing some work around the house (raking, cleaning out the gutters, etc.). I have a request from you guys... could you by chance let me know some of your favorite things from CM and other AOSP-based-but-heavily-modded ROMs? Either in a post or in the Feature Requests section at the top of the page. I myself want to add in off the top of my head right now: 180 rotation, status bar brightness adjustment, disable noise when adjusting volume. Of course, this will all be put in as options and not forced on you. And of course, the screen freezing and other bugs will be more of a priority, I just want to plan ahead here. I haven't had a screen freeze in a while, and I think it's because I set my minimum CPU frequency to 537MHz, so I'll probably disable the 192MHz frequency and also make the minimum screen on frequency 537MHz. Hopefully I can get a new build with that added in tonight.
[Samsung Galaxy Nexus] Rushead:
Cfx has a cool weather status bar option and an sms confirmed receipt thing. I like the idea of a black list and permission editor. Nav bar height, long press, always-on (or completely off) menu.

Obviously these are seriously not important, but thanks for asking!

Sent from a frequent flasher.
[Samsung Galaxy Nexus] metalspring:
If possible it would be great to see navbar customization added in like number of soft keys plus custom targets

(Personally I like having a big menu button so I don't have to hunt for the settings button in some apps and the search key so it's easier to search in certain apps like music apps)

An additional option that would be nice is off screen volume controls for music (I'm a big music fanatic)

Btw, don't feel too bad about the packers, my team is Dallas and their game yesterday was downright embarrassing...
[Samsung Galaxy Nexus] thetakerfan:
This. The main reason I've stuck with AOKP so long is the navbar options. Personally I like Back (with kill process long press), Big Menu, Home, Recents, Search. 5 centered buttons. I hate the way CM does it with 4 buttons and the silly little menu button to the side.

That, and full rotation are the two things I like most from AOKP.