yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] heXacode:
I would advise people to explore ART runtime and give it more time rather than a couple - few hours. In a way ART is a little spotty but it isn't fully at fault. There are apps that require the devs to make it compatible. Everything just needs to be on the same level as ART for it to be smooth sailing. If the Nexus continues getting updates of 4.4.3, 4.5 or whatever Google makes the next number be the ART runtime will be the default and dalvik will be no more. I have not read nor heard of Google adding options to switch back and forth when ART becomes the default. The devs will most likely have to include that option if possible. There is still work to be done in many areas for ART to run without any issues and again all sides, not just Google, have to sort their own issues out on a compatibility level.
[Samsung Galaxy Nexus] Shadow Death:
The latest word from Chainfire is that 4.4.3 will probably default to ART anyway.

I was extremely impressed at the speed that this rom builds dalvik cash. Others seem to take twice the amount of time.

Edit: Can't get mine to switch from Dalvik to ART. I tried both the flashable script and the settings in the developer menu. It reboots and stays in Dalvik.
[Samsung Galaxy Nexus] cujo6801:
Are you using xposed...

It won't switch if you are

Sent from the "DOG" pound
[Samsung Galaxy Nexus] heXacode:
If you're using xposed framework it won't stay on ART. Xposed is only for dalvik runtime.
[Samsung Galaxy Nexus] MWisBest:
I'm extremely impressed with ART and I know it's Android's future. They will not be including Dalvik in 4.5 based on what I'm seeing in AOSP's master branch currently. I don't think ART will be the default in 4.4.3, there's a number of changes they'd need for that to happen and at this point in 4.4's lifecycle I think it's too late for a major change such as that, but 4.5 and onwards it will be the go-to thing yes.

I'm also extremely happy with how fast Dalvik is in this last build though... here's my observations on it:

Going from a previous build to the new build (after running Dalvik on both), it feels as if I switched from Dalvik to ART but with a 10x faster bootup due to not going through all the ART compilation, not to mention the space saved over ART too.

After that experience, I think this whole ART thing might've been unnecessary or at least would've been delayed if Android wasn't compiled like it's the stone age.

Funny you mention the dalvik-cache thing, it's actually multi-threaded so it is indeed about a 2x speed improvement, nice observation. ;)

As others have said, if you have Xposed installed it'll automatically set it to Dalvik when you boot.
[Samsung Galaxy Nexus] osm0sis:
Gasp! All. Over. It. :D

Thanks man! I always enjoy reading your informative posts. Pumped to finally get to try your knowledge in action. :)
[Samsung Galaxy Nexus] JoJoDaClown:
Is there a way to install the FML TWRP without having to use a PC? ie., through goomanager o̶r̶ ̶T̶W̶R̶P̶ ̶i̶t̶s̶e̶l̶f̶? (correction, since 2.7.0.0 TWRP can't decrypt, I can't use TWRP).
[Samsung Galaxy Nexus] Rushead:
Use Flashify from the play store.

Sent from a flashead cracker.
[Samsung Galaxy Nexus] JoJoDaClown:
Thanks for the direction.

Is there a way to verify the installation of the recovery image? I had TWRP 2.7.0.0 installed, and then used Flashify to install the FLM TWRP 2.7.0.0. I'm not sure which one is installed. ie., did Flashify install the recovery correctly.

The reason I ask, is I still can't decrypt the sdcard when booting into recovery. It tells me my password is wrong. (I'm certain it's right, because I have to enter it every time I reboot).

Well, hell... now I'm in a huge pickle. After flashing the FML TWRP image in Flashify, it prompts that i can reboot or flash another. I select reboot and it brings me to TWRP. I send my above message and putt around but can't find my answers in TWRP, so I go to restart. The phone starts up in TWRP every time, I can't get it to boot to ROM. I've tried reboot from TWRP, Power Down, Pull Battery, but nothing boots the phone to the ROM. The only thing I did was install the FML TWRP via Flashify and reboot from the Flashify app.
[Samsung Galaxy Nexus] kinfolk248:
OmniRom vs OmniMetal.....whats the diff lol? i always get confused between the two...
[Samsung Galaxy Nexus] JoJoDaClown:
OmniROM is a ROM from a conglomerate of programmers supporting many devices. OmniMetal is cMetal's (a forum contributor) version of OmniROM for the Galaxy Nexus. He's moved on from toro and now MWisBest is taking over the OmniROM business for toro after working in parallel with cMetal for a while.
[Samsung Galaxy Nexus] kinfolk248:
Oh ok, so one is no better/worse (long as it works) than the other. Just close my eyes and pick one huh lol
[Samsung Galaxy Nexus] JoJoDaClown:
The FML version (this thread) is the only one in support... soooo you should pick this one.
[Samsung Galaxy Nexus] kinfolk248:
Omnimetal has a 5/24 build actually, thats what was throwing me off. but i'll pick one after i get done running a few errands, need the phone while Im out...
[Samsung Galaxy Nexus] Rushead:
Actually, omnimetal might have one more release, & [MENTION=4328678]metalspring[/MENTION] will probably be lurking for a while.

Sent from a flashead cracker.

---------- Post added at 04:30 PM ---------- Previous post was at 04:29 PM ----------

Try dirty flashing your rom (wipe cache & dalvik only).

Sent from a flashead cracker.
[Samsung Galaxy Nexus] MWisBest:
Did you by chance hit "Boot image" under the flash menu in Flashify? That'd certainly result in the behavior you're describing. As a workaround, try booting into (the actual) recovery (manually via hold down power button and both volume buttons on boot-up to enter the bootloader etc.), you might be able to get into your old recovery, and after doing that reflashing the ROM should fix it.

You'd be able to tell which recovery image you're running (FML vs regular TWRP) by looking in the settings for the backlight brightness control (FML's build has that, TWRP's build does not).

If you're unable to decrypt /data in the actual recovery, you could maybe try seeing if the TWRP the phone automatically boots into right now can do that, if so you might be able to flash the ROM via that.

If you're still having issues after this, please let me know!! I'm so sorry this happened to you :(
[Samsung Galaxy Nexus] Shadow Death:
Maybe it's just me but for some reason Dalvik seems to be faster than ART on this rom. :/
[Samsung Galaxy Nexus] rice923:
I think I'm experiencing the same. Although it might be a placebo from reading about it prior to flashing. Either way, it's really nice!
[Samsung Galaxy Nexus] JoJoDaClown:
I had to wipe everything and adb push. It's no big deal, that's what backups are for.

I'll have to look into what happened.
[Samsung Galaxy Nexus] ashclepdia:
I cant wait any longer...I must try this Rom..

I was trying to hold out until f2fs work was complete and maybe some roms started incorporating it. but I've had my eye on this Rom for a long time now, and this release sounds just perfect to jump in on. and the fact that [MENTION=3390093]MWisBest[/MENTION] is one helluva standup guy AND I believe I know him back from my old DX2 days just has pushed me over the edge.

great work brotha, I love how you are always looking deeper and farther into optimizations and such. just epic. even if I dont understand what it all means, I can see many others back you up on the things you say and do who DO understand. so THANKS for all the time. it really looks like you have a lot of fun doing this! :) :D
[Samsung Galaxy Nexus] MWisBest:
It certainly seems like that's the case right now, but I don't think ART has slowed down!

It still sucks when that stuff happens though!

Oh crap I completely forgot about the F2FS stuff! :eek:

I never had a DX2, it certainly would've been much nicer than my tiny ol' LG Vortex tho. :p

I appreciate the compliments! :D
[Samsung Galaxy Nexus] theshamrock7:
Anybody dirty flash over previous version? Just wandering if any issues?
[Samsung Galaxy Nexus] Moody66:
Google has stated ART full implementation is at least a year away.
[Samsung Galaxy Nexus] heXacode:
According to other articles and Chainfire, Google is speeding up by phasing out dalvik and getting ART as sole default. It isn't fully present in 4.4.3 but will be in the next update. I don't think they are going to wait a whole year for full implementations. It has to be stable enough in order for it to be chosen as default otherwise carriers will have a ton of angry customers with some not fully understanding that Google is behind this. However, I do believe that by your version of full implementations they will be updating it on each release like they've done for dalvik. Maybe their goal, or possible potentials in mind, will continue to be added to what will already be used as a stable runtime.
[Samsung Galaxy Nexus] MWisBest:
99 out of 100 times there won't be any issues doing this, it's just that before somebody reports a bug I prefer they try reflashing with a /system wipe.

I will tell you this: Development on dalvik is non-existent in AOSP's master branch really. ART has been the default there for quite some time already. The next Android version will have ART as the default.

THE AGE OF ART IS HERE.
[Samsung Galaxy Nexus] Moody66:
Problem with that is apps that dont play nice with art. Google is more than aware there will be issues. Thus the delay. In the speech given in ART they are pushing to get people to update apps. People want their apps to run. And will complain if they don't. Even if it isn't Google's fault. This is why it is being said one year.
[Samsung Galaxy Nexus] MWisBest:
There might just be a few stragglers that don't work with ART. Unfortunately, in order to move forward we cannot keep supporting the past. In order to move forward, backwards-compatibility has to be put aside sometimes. This is (in my opinion) shown with OpenGL 3.x, Python 3.x, among plenty of other things.

At this point though, they're probably at least 99.999% compatible with all apps. There have been a LOT of changes to ART since KitKat.
[Samsung Galaxy Nexus] 47th_Ronin:
@ MW

Does this have busybox?

Looked through thread, used search blah blah blah.

Didnt see it mentioned so thought id ask.
[Samsung Galaxy Nexus] nitsua98:
Nah, the icons are the same from what I've seen of pictures of the N5.
[Samsung Galaxy Nexus] jsgraphicart:
Do we have root for this ROM?
[Samsung Galaxy Nexus] justen7723:
Sure, go for it.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] jlvlawrence:
You can flash the newest version of supersu. I believe it's version 1.65.
[Samsung Galaxy Nexus] sivarticus85:
My PRL is wrong, and I don't know how to update it. It shows 53243, when it should be 15256.
[Samsung Galaxy Nexus] MWisBest:
No, I don't have that or root included.

Not by default, but I'm sure you could flash it yourself.

Just FYI, I do plan on adding Superuser and whatnot later, along with ironing out the issues I can.
[Samsung Galaxy Nexus] jsgraphicart:
This ROM is pretty awesome. Can't seem to get 4G though. 3G works. And the stock keyboard doesn't swipe for me. Other than that, all is great.
[Samsung Galaxy Nexus] Zer0_Cool:
That might be an AOSP keyboard change. There isn't even an option to enable/disable it in the settings. Install the google keyboard (proprietary) from the play store, it has that functionality included still.

https://play.google.com/store/apps/details?id=com.google.android.inputmethod.latin
[Samsung Galaxy Nexus] MWisBest:
Yeah I noticed the swipe thing as well, putting it on my 4.4 To-Do list I have going...
[Samsung Galaxy Nexus] MWisBest:
From what I've found it looks like it's in AOSP but disabled by default, and custom ROMs have basically just been flipping a switch to enable it. Was so used to it myself from CM that I figured it was just there by default as well.
[Samsung Galaxy Nexus] nnbengboy2:
So...not sure what's up with my ROM, but I flashed it and it doesn't really work at all. I don't have the Play Store, my home button doesn't work, the google experience launcher won't open, no quick settings... I'm going to try and reflash without root and report back.
[Samsung Galaxy Nexus] Zer0_Cool:
Did you use the updated CWM recovery and/or did you do a full wipe? Check md5sums on downloaded files?
[Samsung Galaxy Nexus] nnbengboy2:
I checked the md5 on the rom itself but not the gapps. I did a full wipe. Factory reset + wipe dalvik cache + format /system. The only thing I did extra was install rom / gapps from OP / then install root. I'm going to try again without installing root, at least not until initial reboot.
[Samsung Galaxy Nexus] Zer0_Cool:
What recovery are you using? Root could be the issue, I haven't flashed supersu yet.
[Samsung Galaxy Nexus] nnbengboy2:
I'm using the latest CWM. I verified that before wiping my previous ROM.

Ok, just finished flashing. I haven't flashed Gapps yet and everything except the known issues seems to be working. Now let's see what happens when I flash gapps...

I still don't have the play store, google experience launcher doesn't find google search. I'm going to redownload.
[Samsung Galaxy Nexus] Mars196:
Is it just me or is the GNex getting faster with every update, especially this one, just opening up settings you can see the difference, its instantaneous, while on 4.3 you usually get like 10-15 ms of black screen before it actually renders.
[Samsung Galaxy Nexus] nnbengboy2:
I think the problem was 4.2. It was a joke. 4.3 fixed a lot of that, but I think with 4.4 we finally see how things SHOULD be running. :)
[Samsung Galaxy Nexus] Mars196:
yea 4.2 was pretty buggy, but still amazing how this device is 2 years old now and works at the very least twice as fast as when it first launched, up until now its always been the other way around, the iPhone 4S was released a week earlier than the GNex and that thing is a laggy mess on iOS 7.
[Samsung Galaxy Nexus] jsgraphicart:
I installed the one from the play store. I also tried to install the one from the leaked N5 leak but it didn't seem to install. The play store keyboard works though.
[Samsung Galaxy Nexus] metalspring:
Plus that's one of the reasons the whole nexus program exists, to release an early os update on one device (whatever the new nexus device happens to be) so that developers, specifically app developers can use that nexus device to test how their app performs on the new os update and fix any issues before that os version becomes widely used.

So really whatever the next nexus device is (if there is one), if that version of android defaults to ART runtime, would be the last chance for developers to adapt their apps to work properly with ART.
[Samsung Galaxy Nexus] kinfolk248:
soooooo, Im guessing since everyone is so busy talking about Art that there arent any bugs in this rom ? please say no bugs lol
[Samsung Galaxy Nexus] Shadow Death:
I haven't seen any yet and sleep battery life is insane.
[Samsung Galaxy Nexus] Shadow Death:
Edit: Damn I had hoped that it would combine my posts like tapatalk does.
[Samsung Galaxy Nexus] Brad92:
Only bug I have found is that WiFi hotspot doesn't work, and the long press back to kill is broken
[Samsung Galaxy Nexus] kinfolk248:
cool cool
[Samsung Galaxy Nexus] Shadow Death:
A thing to keep in mind is that I'm also using dirtyv rsr 5/3. My reason for using it is so that I can get lower than stock clock speeds for sleep modes.

My main settings are :

Read ahead buffer =512

Scheduler = Zen

Min clock speed = 230000 (if I go lower the phone has a hard time waking up)

Max clock speed = 1500000 (no noticeable battery drain over 1200000)

Max screen off = 700000 (so that apps will update fine while it sleeps and not take until tomorrow)

Min screen on = 230000 (response time)
[Samsung Galaxy Nexus] dlabadie:
Interesting - I dirty flahed the most recent FML over OmniROM's 5/25 nightly and I have long press back/kill app working. Have yet to see if WiFi hotspot works.
[Samsung Galaxy Nexus] rice923:
My Wi-Fi hotspot works fine. I also encountered some stability issues with dalvik, so I'm back on ART again. The background would randomly become all black, and I had 2 random reboots within a day
[Samsung Galaxy Nexus] Rushead:
+1 to wifi hotspot. I had it going for 6 hours while my mother-in-law tethered her tablet.

Sent from a flashead cracker.
[Samsung Galaxy Nexus] h_10:
SIAP

does anyone know how to get the notification light to work? i'm using light manager and my notification light doesn't work, at all.
[Samsung Galaxy Nexus] MWisBest:
"Settings --> Display -> Notification light" is the only place I can think of...

TIL SIAP.
[Samsung Galaxy Nexus] h_10:
thanks. i've toggled that on and off a million times to no avail.

anyone else? bueller? bueller?
[Samsung Galaxy Nexus] RXG9:
I'm having problems with the brightness settings from the notification pulldown menu. It will stick but when I turn off the screen and turn it back on again the brightness reverts back to the previous setting.
[Samsung Galaxy Nexus] MWisBest:
This has occasionally come up for me too and it's something to do with ActiveDisplay from what I can tell. ActiveDisplay has its own brightness setting (when automatic brightness is not enabled, that is), and when you unlock the screen ActiveDisplay is supposed to put the brightness back to where it's supposed to be. I'll see if I can track this down or not, it's tough to figure out things that are so intermittent like this.
[Samsung Galaxy Nexus] domenci:
heyoo lovin this rom. I upgraded to 5/26 the other day. My long press back to kill does work, but it didn't til after I rebooted. I had to reboot because I lost use of my camera ("can't connect to camera" message) after switching to video mode. It showed a preview for a second and then crashed. Then no more camera at all until after a reboot, then same behavior. Everything else seems solid. I posted a couple days ago asking if there was an option to display cell signal in dBm that I couldn't find but it seems to have been overlooked, I figured since I have the camera issue I might as well ask again.

thanks!
[Samsung Galaxy Nexus] Rushead:
Set camera to 720p.

Sent from a flashead cracker.
[Samsung Galaxy Nexus] RXG9:
Ahh that's what was causing it, Active display. I actually had just turned that on to test it out. Normally I never use it and didn't realize that it was causing the brightness problem. I turned it off and now the brightness setting works properly. :)

Thanks for clearing that up.
[Samsung Galaxy Nexus] MWisBest:
Are you on the stock FML kernel? If so I might need to adjust the amount of RAM freed up (the RAM is added by freeing up some RAM that is reserved for other hardware and stuff, one of those things pertains to the camera and if you take too much from it 1080p stops working). I thought I had it pretty conservative but not all devices are the same!

As Rushead said, a temporary workaround would be to just switch to 720p. I prefer 720p anyway because 1080p only records at 24 frames-per-second while 720p records at a much much smoother 30 frames-per-second.
[Samsung Galaxy Nexus] domenci:
Well thanks, that got it working. Has this been an issue in just this ROM or is it an Omnirom thing in general? I was on CM11 until I switched after getting fed up with mobile data issues, but the camera had no problems so I know it's not a general compatibility issue.

---------- Post added at 02:07 AM ---------- Previous post was at 02:05 AM ----------

Yeah I only rock stock I'm too busy to futz around. I didn't know 1080 recorded at 24, that's actually a cool feature. Too bad you don't have the option to switch to 30 or 60 though.
[Samsung Galaxy Nexus] MWisBest:
Teaser for the upcoming build attached...

EDIT: This is working quite nicely: https://github.com/MWisBest/android...mmit/3aad99a1c8842a4dea1e2ff5b750d5d7d57c3b86

Still a couple minor things to fix with it but it works overall.

So here's why the stupid GPS can take forever on a lock...

The GPS has some extra information it downloads and uses to help with locking onto GPS satellites. I don't quite understand exactly what that information does or what is contained in it, but without it I can't seem to get a lock on the GPS. Android is supposed to assist with downloading this information when the GPS is activated. It seems that after a while (a few weeks?) the data used by the GPS can go "stale" and has to be updated too, it's not a permanent thing really.

The problem? Upon testing that out, it can take Android forever to get that information. It took 30 minutes before I got it. The file size for that is less than 40KB. I tried to see what the underlying cause was for Android taking forever to get it but I was unable to diagnose it, so instead I decided to resort to the blasphemy in the git commit I linked.

After deleting the file it had originally downloaded, I flashed a new build with the changes I made included. Time to GPS lock? A few seconds.
[Samsung Galaxy Nexus] smokeydriver:
So I have an off-topic question, but I'm running this ROM so thought there might be something specific to this ROM. Sorry if you think I'm posting in the wrong forum.

I'm going oversees for about 3 weeks, and taking my VZW GNex with me. I've seen plenty of places people say to turn off roaming data, turn off data, turn on airplane mode, and turn on Wi-Fi. This seems like super overkill to me. Years ago I took this phone to Israel and all I did was turn off roaming data. I was able to use (incredibly surprising to me!) google maps with no problems. I had no fees or anything.

I installed Phone for Google Voice, and I'll play with that over the next few days to be certain I can make calls to the US with that when I'm on WiFi. I'll also probably download a few maps in google before going.

So, to my question- can I just double check that roaming data is off and be good to go?

Any other suggestions?

If the where is important- Italy (Rome and Florence), Spain (Barcelona), and less than a day in Istanbul.
[Samsung Galaxy Nexus] h_10:
MW,

First thank you for an amazing ROM. I have a loki'ed S4 but am loving the GNexus running this ROM. The only "issue" that I have is that the notification light blinks too slowly. Is there a way to freeze the built in Notification light tweaks and use an app from the Play Store like Light Manager or Light Flow?

Thanks.
[Samsung Galaxy Nexus] MWisBest:
I don't know... personally I would be turning off all data.

You can adjust the notification light speeds in Settings. I previously had it on a slow default, in upcoming builds the default will be 1s on 1s off (which correspond to the "Normal" speed settings), but I don't think that'll effect anybody unless they do a clean flash (Factory Reset), they'd have to change it themselves. That was one of many issues I found whilst reviewing all my old code recently.
[Samsung Galaxy Nexus] h_10:
thank you. i found the option to change the speed.
[Samsung Galaxy Nexus] auad:
Does anyone knows if the whatsapp problemas was fixed? I miss this ROM so much, but whatsapp is really important to keep in contact with friends and family...
[Samsung Galaxy Nexus] rice923:
I use whatsapp. I've been doing so for the past few build without a problem.
[Samsung Galaxy Nexus] Shadow Death:
I've been using stock MMS for a while. My favorite is Sliding when it works. MMS seems to always be broken for Verizon with them.

Edit: HW have you seen what aosp has been doing in the vinir thread? I know you mentioned f2fs.
[Samsung Galaxy Nexus] Shadow Death:
Already on it? Lol

I had a friend of mine who had a N7 and claimed that there wasn't any benefit over ext4 according to the benchmarks he saw.. Either way progress isn't made unless you move forward.
[Samsung Galaxy Nexus] creaky:
Not sure about Turkey but Spain and Italy are on GSM networks so you won't be able to use your GNex except on WiFi.
[Samsung Galaxy Nexus] h_10:
you could just give us peak and give us a flashable zip of this. :D