yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] swordrune10:
I would really suggest to use cm as a base.. now u say u don't want someone else's code to possibly break something but as long as it cherry picks are good u should be fine.. I built for tilapia and it runs better than with aosp, actually fixing rotation and whatnot
[Samsung Galaxy Nexus] MWisBest:
Well... I'll have a look at it tonight I suppose. I was based on CM with 4.3.x, however one thing I'm liking about AOSP is mobile data... CM was always giving me issues with it, and AOSP has been flawless for me hand-off and connection wise, as long as you don't mess with the Mobile Networks menu at the moment.

Also, I'm not talking cherry-picks, I'm talking my own changes. With CM I had 40+ forks, most of those however were related to enabling a lot of the optimizations and fixes Linaro does. Speaking of Linaro, I could also just use that as a base now since they're just based off of AOSP. I haven't enabled any of the optimizations I was doing with 4.3.x and 4.4 is already faster, although that could be just from not having a lot of the things CM adds.
[Samsung Galaxy Nexus] swordrune10:
it could be.. but I use aosp from time to time and I'll have to say as it stands KitKat just can't be bogged down.. no pressure, it's ur ROM do what u like right?

now for features I look for quick settings changeability, I used to use themes but I love kitkats look.. there's a commit in cm where they put the arrows back in the WiFi and mobile data which is a good idea.. I really personally like the nav buttons stock, but at one point I did have them in reverse.. I like the battery indicator to say a percentage and I don't mind the style of it as long as it's readable at a glance.. I miss hitting the clock in notification and going to the clock app.. oh and I personally like the clock to say am/pm..
[Samsung Galaxy Nexus] MWisBest:
Sorry I wasn't able to get a new build up tonight. Need to get some sleep! I did do a new build, however there's a little tiny but somewhat serious bug in it that'll have to wait til tomorrow.

Here's a quick preview of what'll be in the new build:

init.d support

Possible mobile data improvements (seems better to me, but I'll let you be the judge)

Switched to using Launcher3 instead of Launcher2 (Launcher3 is more similar to the new Google launcher, just without Google Now on the very left among other things)

Slimmed down the build by removing some useless junk (about 17MB of savings)

Added an init.d script which should help with the freezing. This script sets things like minimum screen on frequency, maximum screen off frequency, etc.
[Samsung Galaxy Nexus] sonic147862:
I'm on the 11/6 build and I've only had to pull my battery due to a random freeze once. This has been I great ROM so far and the only thing that really bothers me is apps that use the stock browser and have black everywhere :P
[Samsung Galaxy Nexus] MWisBest:
New build up! I hope this finally stops the screen freezing once and for all, let me know how it works for you! :fingers-crossed:
[Samsung Galaxy Nexus] swordrune10:
seems a bit speedier, ill be using it for a day or so to see about if the cpu is too high ( using too much battery ) and about the lockups.. oh i also sent u a pm
[Samsung Galaxy Nexus] dirtsky:
Got my free battery today in the mail. But, now my USB port is going bad. Just ordered that to replace it off Amazon. $7.00 is better than paying the insurance.
[Samsung Galaxy Nexus] swordrune10:
phone froze while messing with lockscreen widgets
[Samsung Galaxy Nexus] swordrune10:
gee thanks.. I was under the impression that this was a thread for the FML build for the Verizon galaxy nexus and that the op would like to know that the hopefully no freezing ROM from today does in fact freeze.. so yes cool story indeed
[Samsung Galaxy Nexus] AirBoss24K:
On the latest build I'm guessing? I'm still on one of them from like a week ago.

I saw someone suggest using Tiny Kernel as a way to avoid the freezing. To a certain extent they were right; however, rather than freezing, my phone is rebooting at a fairly similar rate as the freezes. I find this preferable to pulling the battery every damn time, but the experience I'm having also isn't nearly as fluid. The 4.4 game is one of pros and cons from kernel to kernel.
[Samsung Galaxy Nexus] RW-1:
On the Lolli now ... Camera didnt connect (goog or aosp) however before panicking about modules, I rebooted it, and poof! Working.

Removed AOSP stuff I didnt want/need and looking good so far. Have to get used to it :)

Eval today in progress.
[Samsung Galaxy Nexus] AuroEdge:
Does the OS run trim on a regular basis in this ROM? It's been my experience with Galaxy Nexus custom ROMs that it typically doesn't.
[Samsung Galaxy Nexus] gorillabiscuit:
issue adding google account

So I flashed this... and when I add my google account it doesn't recognize the app-specific password. I've tried several. Inputting my normal password brings up a 2nd factor prompt, but my authenticator was on my last build... I installed TiBu from the web, but can't get it to move past 0%. I like the way 5 looks, but I would appreciate if anyone can point me in the right direction.

*UPDATE* - I reverted to SMS for 2nd factor and was able to add my account. TiBu is still sticking on 0% and isn't doing anything.
[Samsung Galaxy Nexus] dbt816:
Anyone else unable to send MMS messages? I can't send with WiFi enabled or only connected to the 4G network. Looks like there are problems resolving the IP address for the host "mms.vtext.com".

E/Mms ( 4768): java.io.IOException: Cannot establish route for http://mms.vtext.com/servlets/mms: Unknown host

E/Mms ( 4768):	at com.android.mms.transaction.Transaction.ensureRouteToHost(Transaction.java:230)

E/Mms ( 4768):	at com.android.mms.transaction.Transaction.sendPdu(Transaction.java:173)

E/Mms ( 4768):	at com.android.mms.transaction.Transaction.sendPdu(Transaction.java:152)

E/Mms ( 4768):	at com.android.mms.transaction.SendTransaction.run(SendTransaction.java:113)

E/Mms ( 4768):	at java.lang.Thread.run(Thread.java:818)

E/Mms ( 4768): Delivery failed.

I don't necesarily think this is a ROM issue....maybe some kind of weird DNS problem. I recall this happening before.
[Samsung Galaxy Nexus] erk1725:
I've managed to send one MMS through Verizon messages and it took a long time. Camera has been working well tho :) thanks mW! You are a genius!

Dirty flashed 1/8 from a clean 1/4 install with Smitty r1 and nephs latest settings since 1/8. All good except MMS on mw's stock "messenger" app and the stock "messages" app from pa beta 5 micro. I don't send many pictures so whatever....still my DD!

Edit: Netflix from play store just loads and an old apk I had saved plays but the audio is very crackly. I'm sure it isn't meant for 5.0 tho.... Just saying

Thanks again!
[Samsung Galaxy Nexus] Nephilim:
Hey guys, if any of you are like me and don't really like the photos app and would prefer to still use gallery I found a flashable zip of the moto gallery which is a material skinned version of the stock Google gallery. Its great, just gotta make sure you have 35mb free in your system/app folder so it will properly install. Let me know if you would like it and I'll post a link.
[Samsung Galaxy Nexus] jcruz942:
Yes that sounds awesome thanks!
[Samsung Galaxy Nexus] KShion619:
It should, but just run F2FS on data and cache and you should not need to care much, as F2FS has its own trimming functionality
[Samsung Galaxy Nexus] dbt816:
My AnTuTu scores have dropped by 3,000-4,000 points on the 1/8 release and Full_Auto_R4 kernel with [MENTION=300441]nephlim[/MENTION]'s settings. This is across 3 benchmark runs. The culprits within the benchmark tests are are "Multitask" and "Runtime". We're still light years ahead of KK performance, but it's interesting to see that difference.
[Samsung Galaxy Nexus] AuroEdge:
I've gone back and read a bunch of posts. So we just format all the partitions, besides /system, as F2FS using the TWRP recovery prior to flashing FML?
[Samsung Galaxy Nexus] dbt816:
Yep!
[Samsung Galaxy Nexus] KShion619:
Yep! This takes a bit of space on each partition, but speeds up the partitions quite a lot, as it trims more actively than ext4, but with /system, it takes enough space to make most ROMs no longer fit, and f2fs helps with writes, which most people don't do on system making f2fs not really worth using
[Samsung Galaxy Nexus] Nephilim:
That's odd, my scores are exactly in the same area as they were with Beta3, no problems with runtime or multitasking, if anything this rom and the latest Full_Auto have improved them.
[Samsung Galaxy Nexus] dbt816:
Gotta love the Gnex....it keeps us all interested :) I will keep picking at my scores...
[Samsung Galaxy Nexus] KShion619:
Try stock voltages and lower the clock speeds, some devices don't get along with certain clock speeds/voltages, what kind of scores you pulling? And at what frequencies?

Sent from my Verizon LG G3
[Samsung Galaxy Nexus] Nephilim:
My scores differ on occasion because I/O scores are not always the same, usually they are in the 2500 range but sometimes they dip down to like 600 or 700, I think it might be because of the times I run the test or maybe I might have forgotten to close the apps open in recents. Either way, 98% of the time my score is about 20100 to 21000 on Antutu with my settings. As stated in the post before me though, some people are encountering issues with 1.5ghz cpu frequency on Lollipop and others it works fine so if 1.5ghz is causing you lag use my settings on 1.3ghz instead and see if that fixes it.

BTW guys, I forgot to say, I did research on zram and it's useless on mobile devices so I once again have it turned off for my custom settings.
[Samsung Galaxy Nexus] zzpianoman:
Do you keep your temperature ceiling at 70 when you run your benchmarks?
[Samsung Galaxy Nexus] Nephilim:
Yep, I only benchmark the settings I use on a daily basis. To me anything else is cheating because if you don't run your device the way you ran your benchmark the benchmark is useless. Anyone can set the max CPU frequencies and set the governor to performance to get a high score but you cannot use your device on a day to day basis with those settings so they serve no purpose. I really only benchmark to see the improvements made ROM and Kernel side using my preferred settings, nothing more.
[Samsung Galaxy Nexus] churche0:
Sorry for the stupid question, but with the new FML Lollipop builds, is there a Power Menu option list? I can only see "Power Off" in my menu and can't find anything about advanced menu options in Developer Options menu. Am I missing something or is it just not there yet? Thanks.
[Samsung Galaxy Nexus] zzpianoman:
You could download one of the many third-party shutdown menu apps that are out there. Should work in the meantime until the power menu gets added into the build.
[Samsung Galaxy Nexus] churche0:
Yeah, thanks, I'll do that. Just wasn't sure if I was missing something or not. This ROM is so good with R4 kernel, seriously...keeping my old Nexus still in business. Thanks so much.
[Samsung Galaxy Nexus] dbt816:
Getting in the 17,000-18,000 range when I was previously over 21,000.

I never mess with the voltages... my device doesn't like that at all. I also have to keep all my min frequencies at 350MHz... I get lots of random reboots at 200/250MHz, which is odd since back on KK/SmittyV I had no issues down to 190MHz.
[Samsung Galaxy Nexus] Reviz:
[cut] sorry
[Samsung Galaxy Nexus] RW-1:
You really don't have many choices there right now, either the stock that came with it, or BSmitty's Full Auto. Use that with Neph's settings and tweak for your specific device.

http://xdaforums.com/galaxy-nexus/d...r1-aosp-cm-t2994371/post57974343#post57974343
[Samsung Galaxy Nexus] dbt816:
Just picked up my phone at random and ran a benchmark.... 20,886... lol! No changes, reboot or anything since the lesser scores yesterday. Must have been a little GNex PMS or something ;)
[Samsung Galaxy Nexus] Reviz:
[cut]

sorry
[Samsung Galaxy Nexus] Nephilim:
I've noticed sometimes the kernel needs to settle for a bit to get normal scores, like I've said, sometimes my scores would be low as well, like 18000 or something. Usually due to the I/O scores. That only happened off a fresh install when I was impatient to run Antutu. Ever since I've been back to dirty flashing my scores rarely drop below 20100.

Glad to see it worked out, after all, a benchmark score is just a number, what matters more is that the settings are giving you a good user experience. ;)
[Samsung Galaxy Nexus] dbt816:
This is true... the GNex would be as worthwhile as the Dallas Cowboys are right now without your settings :D LOL!
[Samsung Galaxy Nexus] rippedwarrior69:
Would like to try this rom. Does data work or do you have to flash the APN fix?
[Samsung Galaxy Nexus] Nephilim:
Please read the OP and use the XDA search option before asking questions that are already answered in the thread.
[Samsung Galaxy Nexus] Christopher8989:
How do you guys get it this fast? I can't get more than 14K even at 1500MHz.
[Samsung Galaxy Nexus] zzpianoman:
Photoshop?

TOTALLY KIDDING!

....but seriously, it depends on a lot of factors. Do you have a lot of background processes running? Are you using F2FS or EXT4? Also, higher CPU speeds do not necessarily lead to higher benchmark scores as you may be experiencing more overheating which causes the CPU to throttle back significantly. There are also some variations in manufacturing quality of the various hardware components as well as the overall age of the device (flash memory tends to degrade over time).
[Samsung Galaxy Nexus] rippedwarrior69:
Just flashed this ROM and it great. Everything works so far. Does the 5.0 messaging app crash is that why its the non 4.4 one? Also is there any setting for ambient display it goes off before I get to see what it says. This ROM is great thanks for the hard work guys.
[Samsung Galaxy Nexus] Christopher8989:
I think it's on EXT4 since I didn't manually change it. I had problem with F2FS when on KK but I can try again on L. Should I change it for all partitions or just system, or all except system?

I tried Niph's v4 settings and it was lagging so I didn't benchmark test it.
[Samsung Galaxy Nexus] zzpianoman:
Currently only ext4 is supported for /system but /data and /cache can be F2FS. Don't forget though that converting /data to F2FS also wipes your internal storage (/sdcard) so make sure you have backups!
[Samsung Galaxy Nexus] grim281:
I am getting an error saying I have insufficient storage space in my system partition after wiping from your KK FML. I am using the GAPPS in the original post for Lollipop. Any ideas?
[Samsung Galaxy Nexus] RW-1:
Use the PA 5.0 micro install ....

http://xdaforums.com/paranoid-android/general/gapps-official-to-date-pa-google-apps-t2943900
[Samsung Galaxy Nexus] RW-1:
Hmm, on R5 and trying to send a photo, stuck on sending ....
[Samsung Galaxy Nexus] grim281:
Thanks!.
[Samsung Galaxy Nexus] jcpowell:
Try booting into the OS once then boot back to recovery and flash. I had this same issue.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] dbt816:
Anyone else noticing that apps that play audio (live stream from the Internet or music on the local SD card) are running at high CPU use and draining the battery?
[Samsung Galaxy Nexus] pkgnex:
I'm having the same problem. MMS won't send, regardless of whether it's a picture or just a group message, and regardless of whether wifi is on or off. I know others say they aren't having the issue, so I'm not sure if it is carrier dependent (I'm on Verizon), or just hit-or-miss on an individual device basis.
[Samsung Galaxy Nexus] zzpianoman:
Fixed MMS for all messaging apps:

(flash in recovery)

VZW-Lollipop-MMS-Fix.zip
[Samsung Galaxy Nexus] dbt816:
Nice :) I added and entry for mms.vtext.com to /system/etc/hosts.
[Samsung Galaxy Nexus] zzpianoman:
Does that work? b/c when I tried that it didn't work.
[Samsung Galaxy Nexus] dbt816:
Yes, It did for me.
[Samsung Galaxy Nexus] pkgnex:
Thanks!

I'll give that a try.

Update: It worked! Thanks zzpianoman!
[Samsung Galaxy Nexus] RW-1:
Hay ZZ,

Will try when I get home, I did however narrow it to being on wifi for me, because I tried on 4g while out and it sent, but doesn't hurt ...

You're the guy!
[Samsung Galaxy Nexus] jerflash:
[MENTION=3390093]MWisBest[/MENTION] This is by far the quickest and most stable rom for the VZW Galaxy Nexus i have used.

It is not my everyday phone but i still like it to try things out on. have been running cm11 official nightly and it was terrible. tried a cm12 rom and it was worse.

The phone is actually usable with this rom...some slowdowns sure but for an over 3 year old device this thing is running like a champ.
[Samsung Galaxy Nexus] otter34:
When I used those I got errors that the AOSP keyboard was force closing constantly.
[Samsung Galaxy Nexus] otter34:
Can't install 5.0 with any of the PA 5.01 gapps packages
[Samsung Galaxy Nexus] RW-1:
TWRP 2.8.4.0 out.

Look at item #2 in the changelog hehehe ...

MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that

Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)

Fix some MTP related crashes and bugs

Eliminate TWRP toggling USB IDs during boot if MTP is enabled

Fix various adb sideload issues

Improve threading of actions

Eliminate separate thread for screen timeout

Update libblkid to 2.25.0

Use power button as back button on watch themes for easier navigation

Add mutex locking to data manager

Improve custom theme handling on encrypted devices

Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens

Get it while it's hot! :

http://techerrata.com/browse/twrp2/toro
[Samsung Galaxy Nexus] christianpeso:
I got the same thing as well flashing latest FML,latest bSmitty kernel, and latest beta gapps all in the same session. Haven't looked into it that much since then.

EDIT:

Appears to be an issue with the latest version of GAPPS beta from the 11th. He released a test version with possible keyboard FC fix,but it is Full, not micro, and therefore gives the "insufficient storage" message. Will try to use an earlier beta from the beginning of the year.
[Samsung Galaxy Nexus] zzpianoman:
It doesn't support F2FS?!?!
[Samsung Galaxy Nexus] Dirty_Jerz:
I don't think DeesTroy's builds ever have. Hence MWiz's build.
[Samsung Galaxy Nexus] zzpianoman:
Yeah, I know that's how it used to be - but I figured at this point it would have been implemented. I mean this is the 21st century and all...
[Samsung Galaxy Nexus] otter34:
I don't see a file from 2015 on that page.
[Samsung Galaxy Nexus] :
2.8.4.0?

Look again...it's there. (3:27:37pst)
[Samsung Galaxy Nexus] Christopher8989:
I used TWR's own app to install. It installed from within android even though it said it couldn't because it can't access sdcard. I booted into recovery and saw that it is 2.8.4.0

---------- Post added at 07:11 PM ---------- Previous post was at 07:04 PM ----------

That could very well be. I bought mine new but only about a year ago, excess inventory I guess. I had stability problem with f2fs on cache and data back on KK and I never got good result like others did, with various recommended settings even when on KK.
[Samsung Galaxy Nexus] otter34:
You used the goo manager app?
[Samsung Galaxy Nexus] Christopher8989:
uh I think so... I searched google market for "goo manager" and in the auto suggest came back with that but when I selected it I got twr's app show up first and nothing for "goo manager".
[Samsung Galaxy Nexus] Zer0_Cool:
I had this issue as well with the micro install, which I tried because of insufficient storage. I wiped and tried this method with the gapps from the OP and it flashed successfully, no force closes either.
[Samsung Galaxy Nexus] Christopher8989:
I just reflashed anew and applied bsmitty83's FA_Lollipop_beta3 kernel, TricksterMod donated version, and set to Neph's v4 settings.

Then I ran AnTuTu twice and got 18K+ total score. I didn't reboot though would that matter?
[Samsung Galaxy Nexus] bsmitty83:
Beta3 is old as hell lol we're on release (R) versions now grab it here

http://xdaforums.com/showthread.php?p=57974343
[Samsung Galaxy Nexus] Christopher8989:
1st time seeing this thanks. Will try soon.

It's DDK 1.9. Wouldn't that break camera?
[Samsung Galaxy Nexus] bsmitty83:
If your on beta 3 , your using ddk 1.9 now
[Samsung Galaxy Nexus] TheBigSizzler:
Flashable?

I'm still very new to the rooting scene. Is the 1-08 build flashable yet? I couldn't quite understand how to install it otherwise. Same with the Smitty kernel (can't find what to delete). Thanks for your patience with a beginner. Great mod though, thanks!!!
[Samsung Galaxy Nexus] erk1725:
I wanted to attach some screenshots from the battery sections in /settings/battery showing my usage with and without WiFi from today. Phone was connected to WiFi at work and charging but anyways......I cant seem to attach any images? I'm not sure if I ever posted a picture on here before :-o

the point to this is that the line for cellular network signal under the graph that shows up when u press the graph itself is more or less dark orange to red the entire time even tho data works and I am writing this from my phone now. Status bar says 4G and /settings/about phone/status says -96db 44asu. The 4G signal in status bar will get an exclamation point and go dim and blank and go to 3G and then repeat back to 4G.....it just kinda cycles like that with no apparent reasoning i can decipher on my own. My battery life is not that great either and I have the zerolemon battery? If someone could tell me how to post a pic I will post them to show what I'm talking about as I'm like bsmitty420 I mean 83.....so I'm sure this is a rather confusing post. Latest FML and latest Smitty with nephew settings except no UV and I run GPU at the 384.

Also I get this "over-counted" section in /settings/battery at the bottombottom that says 24%. This would be a good image if I could post it. Is my battery messing up my signal? Does everyone have this "over-counted"

Any advice is very appreciated....still love the setup... Everything works now that zz posted that MMS fix!!

Thank you very much everyone!

P.S.......I took so long typing this my status bar says 4G but the triangle is blank and /settings /about phone/status says -104dbm 99asu and I haven't moved?!?

Thanks again!!
[Samsung Galaxy Nexus] otter34:
Tried installing every single pa 5.01 gapps and no luck. Either it's a keyboard issue or not enough memory. I tried all the tricks too. Also tried installing a 4.4.4 gaps
[Samsung Galaxy Nexus] Zer0_Cool:
Did you try flashing the rom, booting the phone up, rebooting into recovery, then flashing the gapps? This worked for me, I had a lack of memory when I tried to flash them together.
[Samsung Galaxy Nexus] otter34:
I flashed ROM +gapps then booted up, then into recovery and flashed apps again. Didn't try flashing ROM only at first... Back to the well. Thanks I'll let you know!

Just to be clear I flash these tuna gapps on the first page for my toro ROM? I've tried so many I can't remember what's what. Thanks
[Samsung Galaxy Nexus] Zer0_Cool:
Yes, you will be flashing:

FML-AOSP-5.0-20150108-toro.zip

FML-GApps-5.0.x-20150101-tuna.zip
[Samsung Galaxy Nexus] RW-1:
I find that interesting, I had 0 issues with PA micro 5.0 and the ROM, if I went larger than that, yes, I'd have no space, but basically since most of the /system installed apps I take out so the GPS can update them, it was no big deal as far as space.

But for your issue, may I suggest that you simply log onto your Google account on a desktop and temporarily turn off two factor auth, then retry? you can always go back and turn it back on ...
[Samsung Galaxy Nexus] Zer0_Cool:
The micro gaoos gave me keyboard fc from the get go, couldn't even get on my wifi.