yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] kinfolk248:
how is this rom as far as stability and functionality???????

i ask because i travel a lot throughout the day and need my phone so the fc, signal drops, reboots, etc that plague a lot of 4.4 roms are unacceptable...
[Samsung Galaxy Nexus] terminal13:
My daily driver. No issues during standard use. Using the mpokang 1080 kernel with it.

transmission from my forking four.four.two gnex
[Samsung Galaxy Nexus] otter34:
I'm able to move the tiles around but I can't figure out the formula to remove them. I tap it and it gets smaller then sometimes e when I tap again it disappears, only to return. I have removed 2 so far but don't know how? I can't remove anymore. I remember one Rom had a trash can appear. That would help
[Samsung Galaxy Nexus] DR3W5K1:
When you click it and it gets smaller that's disabling the toggle.
[Samsung Galaxy Nexus] otter34:
That's slick. Thanks!!
[Samsung Galaxy Nexus] MongolPup:
LTE works for me too.
[Samsung Galaxy Nexus] terminal13:
Just wondering if anyone has an in-call screen off issue with the mpo 1080 kernel and the omni based roms?

transmission from my forking four.four.two gnex
[Samsung Galaxy Nexus] Philosophre:
LTE been working. In SF area. Wish I live in a non-lead house tho, when I am home I lose all reception. 1 bar.
[Samsung Galaxy Nexus] David 617:
I know the feeling. Its like trying to get reception in a bunker.

I got VZW to give me a network extender for free. At first they wanted to charge me $250 for it. 2hrs later they shipped it for free.
[Samsung Galaxy Nexus] DevVorteX:
Hey [MENTION=3390093]MWisBest[/MENTION],

I just sent you a couple pull requests related to some data updates from aosp. I feel like they help handoff if you wanna add them into the next build.

I also recommend adding: persist.radio.apn_delay=5000

To system.prop for device_samsung_toro/system.prop. That'll lower the timeout delay between apn connection attempts. This helps the handoffs happen much faster than the default 20000 setting.

I'd do a pull request, but github won't let me fork multiple repos that all have the same base.
[Samsung Galaxy Nexus] rbrenart:
battery pulls

This build and the previous one (I forget the date,2/26?) have required a battery pull or two a day because the phone just won't light up.

I've been dirty flashing since the last build in December...is it time for a clean flash, or are others experiencing this too?
[Samsung Galaxy Nexus] terminal13:
Try a clean flash.
[Samsung Galaxy Nexus] midnightdevil66:
Flashed clean this ROM. Running real good especially data handoff. Running it with dirtyV kernel, it's running solid. Thanks

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] furiyk:
Could anyone let me know if this Rom has an option to keep led on when screen is on? Like in omnirom. That's my favorite feature :P
[Samsung Galaxy Nexus] rbrenart:
It does... Never used it, but I just saw the setting moments ago.
[Samsung Galaxy Nexus] Rushead:
Lost data after messing with the data toggle. Had to wipe system, cache, dalvik & reflash. Still best rom from my experience. MW knows his s#it.

Sent from a flashead cracker.
[Samsung Galaxy Nexus] rice923:
So in an attempt to salvage lte again, I decided to wipe everything imaginable and start from scratch. I wanted to back up my apps (no data) via TiBu, but it tells me that I do not have sufficient space in my sd card. I have over 13gb of free space. Has anyone encountered this before?
[Samsung Galaxy Nexus] Shadow Death:
look through your installed apps and see if any are taking up large amounts of storage.
[Samsung Galaxy Nexus] rice923:
I have over 13gb of free space. I also tried to back up 5 apps instead of the whole list. No go and it immediately gives me the error message
[Samsung Galaxy Nexus] Cutterstark:
Play Market Downloads Not Working

May be related to the previous post. I too seem to have space, and I've deleted some large apps. I used to get the not enough space error. Now I just get an infinite download that never finishes on the Google Play Market, no matter how small the app.

I tried clearing the Play app cache and rebooting, same thing.

Anyone else experiencing problems with downloading and installing apps?

I keep coming back to FML as my daily driver, like it better than the rest. Never have had any data issues.

Eric
[Samsung Galaxy Nexus] DevVorteX:
Could it be a tibu access to sdcard problem? Like the backup folder permission being changed? Or some app permission blocker?
[Samsung Galaxy Nexus] terminal13:
Did the power off menu to reboot to recovery go away? Ended up clean flashing after I unwillingly decided to factory wipe in clock work and lost the reboot to recovery option..... downloaded the twrp app to go around it but not sure if the 10 million roms and kernels I've flashed on this thing is starting to take its toll....(crackflashing is bad.. mmmmmmk)....any who. I've got to get back into teaching myself this stuff.....then i can just fix it....Fml.
[Samsung Galaxy Nexus] midnightdevil66:
I think you have to enable it in developer settings.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] terminal13:
Thx. Had to reenable devopts

Transmission from my Forking four.four.two gnex
[Samsung Galaxy Nexus] furiyk:
This Rom is flying. First time trying it. All I'm missing is battery light but that's not a biggy
[Samsung Galaxy Nexus] MWisBest:
Tracked down the issue regarding LTE: The toggle in quick settings messes it up. I'll get a new build out tomorrow to hopefully fix it. In the mean time use the regular way in Settings.
[Samsung Galaxy Nexus] Rushead:
Had a LoD (lag of death) today. Stupidly I forgot to get a logcat before I rewiped & booted up fresh. If it happens again, I'll certainly log it. Running Dirty V 2-27

Sent from a flashead cracker.
[Samsung Galaxy Nexus] otter34:
I know it's not a ROM issue but does anyone have a problem with Google maps where it doesn't tell you the street or highway name? It just says, for example "in a quarter mile turn left" then, "turn left." I used to have this issue in downtown areas where there were lots of tall buildings however now i have the problem on the open road with perfect 4g
[Samsung Galaxy Nexus] MWisBest:
Well for me Maps doesn't even figure out where I am unless I turn on WiFi, it's ridiculous. It thinks I'm in Chicago if I don't, and that's a 4 hour drive away from here, like wtf. Well it's not even Maps, it's Google as a whole, if I search for a business and I don't have WiFi on it'll show me stuff in Chicago. Anything else that gets my location that isn't related to Google works perfectly.
[Samsung Galaxy Nexus] furiyk:
Anyone having an issue with Facebook always expiring your session?
[Samsung Galaxy Nexus] terminal13:
Nope. I cured that by eliminating Facebook from my life. Just sayin...;)

Transmission from my Forking four.four.two gnex
[Samsung Galaxy Nexus] Rushead:
If it's accurate, it sounds like a maps database issue rather than gps.

Sent from a flashead cracker.
[Samsung Galaxy Nexus] Rushead:
LoD source found: phase beam wallpaper. All other live wallpapers seem to work fine, but pb lags like mad.

Sent from a flashead cracker.
[Samsung Galaxy Nexus] DR3W5K1:
Maps, Google dialer with business lookup, and search-googlenow all work fine network and gps location. Im using a different OMNI build-rom though. Try a different gapps?
[Samsung Galaxy Nexus] MWisBest:
Sorry that the new build is taking so long, I've just gotten a little ambitious with what I wanted to cram into this one.

I think I might know why that is, thank you for the heads-up.
[Samsung Galaxy Nexus] rice923:
When connected to my car via bt for phone mode, Google now doors something rather strange. When I prompt Google now with "OK Google," it will begin to listen to my voice, but it also tells the car that I'm making a call (the car's dial pad comes up). This results in a failure to recognize my voice input, and nothing happens in the end (no call placed, no Google now results)

Anyone else have this on the latest build? I never had this for the January build
[Samsung Galaxy Nexus] cujo6801:
Has this ROM added custom navbar

Setting yet?

Sent from the "DOG" pound
[Samsung Galaxy Nexus] otter34:
Reboot when using voice to text and stock keyboard. It's happening with all apps
[Samsung Galaxy Nexus] midnightdevil66:
No rush bro. Take your time. Loving the ROM.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Shadow Death:
Oh yeah this room if my fall back.
[Samsung Galaxy Nexus] MWisBest:
Well after 10 days of figuring stuff out I got everything building again. New build will be up either tonight or tomorrow depending on if I fall asleep.

I'm a little concerned with the stability of it, so I'm going to add something to the changelog: "Estimated Stability: (1-10)"

That way people who might want something that's more daily-driver material can use a more stable build, and those who want to live on the bleeding-edge such as myself can just use the latest version, regardless of the stability, hehe.
[Samsung Galaxy Nexus] MWisBest:
Build from last night got stuck at the boot animation, I think I tracked down the issue but I'm estimating this build will take 6 hours or more as I had to empty out ccache.

(For those who aren't familiar with ccache I'll try to explain it. In layman's terms it's a program that creates a cache of files to speed up building code. The first time something is built using ccache, it takes longer than usual, however on future builds it is much much faster than it would be otherwise. For people with SSDs and 40GHz 1000W billion-core CPUs (exaggerating there obviously...) ccache might not be as noticeable, but on a laptop with a 5400RPM HDD and 2.5GHz 35W quad-core CPU like I use it makes a HUGE difference.)

EDIT: Nope, guess I didn't fix it entirely. If I don't have it fixed in the next few hours I'll probably just temporarily revert what I've been working on so I can at least get a build synced up with the latest OmniROM changes.
[Samsung Galaxy Nexus] rice923:
Thanks a bunch. All good now!
[Samsung Galaxy Nexus] MWisBest:
Yeah it looks like I'll have to resort to plan B for now (temporarily reverting what I was working on). I keep making progress on it every day, but it's approaching 2 weeks since the last build, and that's just way too long. I'd ideally like to do at least one build per week...
[Samsung Galaxy Nexus] MWisBest:
Aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaand there's the new build. As usual check the changelog.
[Samsung Galaxy Nexus] rbrenart:
MW, I clean flashed 3/10, and they once and awhile my phone just won't wake up. I'm sure it's just some rogue app, do you have any recommendations on how I can track down what may be causing it?
[Samsung Galaxy Nexus] midnightdevil66:
Running 3/22 all good. Great combo with Smittyv kernel. Thanks!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] MWisBest:
Actually it might not be that, I occasionally had this issue as well. What I had to do to wake the phone up when it was being difficult with me was hold down the power button until the power menu came up, as soon as that came up the screen would turn on. Try the 3/22 build to see if it is any better?
[Samsung Galaxy Nexus] rice923:
Do you guys recommend any other method to batch backup and batch restore apps besides TiBu? My TiBu is refusing to work with me even after some attempted aid from another member.

I need to backup and do a completely fresh install to get my LTE back
[Samsung Galaxy Nexus] MWisBest:
Did you see what I had mentioned a page or two back? The LTE issue was from the quick toggle messing it up (which I still haven't figured out >.<). Going into the Mobile Network Settings (the old long way ya know, before quick toggles were a thing) menu and selecting LTE a couple times should fix it. If that still doesn't fix it, then I'll help you get a logcat for me.
[Samsung Galaxy Nexus] rice923:
OMgizzles! I haven't had LTE for a month and it's finally back. I just thought that wasn't the issue since the problem stemmed from so many builds ago. My phone is awesome again!
[Samsung Galaxy Nexus] MWisBest:
Glad it's all working again, hopefully I'll get the quick toggle fixed in the next build.

How I discovered this?: Went shopping with my dad to help him with getting a new phone (he had a Droid RAZR, and it was sooooo slooowwww, idk what he did to it or if there was some sort of hardware defect or what!), and for some reason I couldn't look up the phone number for BestBuy, internets on my phone just refused to work. Tried toggling airplane mode, tried using the LTE quick toggle, tried rebooting, nothing. Then I accidentally long-pressed on the LTE toggle, which took me to the Mobile Network Settings menu. So I'm like whatever, while I'm here I might as well use this menu, and to my surprise neither LTE nor 3G had the blue bubble thingy by it. After I pressed LTE a couple times, VIOLA! It was fixed!

As for my dad, he ended up getting a Droid MAXX at the Verizon store. I would be jealous, but he can't root it, let alone unlock the bootloader. :P

P.S: I switched all the phones in the store that were running KitKat to the ART runtime. Shhh!
[Samsung Galaxy Nexus] cujo6801:
Lmfao......

Sent from the "DOG" pound
[Samsung Galaxy Nexus] rice923:
Trolling like a geek. Love it[emoji106]
[Samsung Galaxy Nexus] DroidDioxide:
Does this have multiwindow?
[Samsung Galaxy Nexus] David 617:
No
[Samsung Galaxy Nexus] terminal13:
So who is running art here? Like everyone?

Transmission from my Forking four.four.two gnex
[Samsung Galaxy Nexus] qendadar:
Art here and running buttery smoooooth
[Samsung Galaxy Nexus] rbrenart:
Not me. I haven't felt the performance improvements, but I have seen the force closes so I leave it alone.
[Samsung Galaxy Nexus] Rushead:
Art here & not a single reboot, fc, or anything else.

Sent from a flashead cracker.
[Samsung Galaxy Nexus] terminal13:
I ran art since last night and was laggy. Had that issue before with art so I switched back. Guess my device doesn't like it? Not sure why tho....

Transmission from my Forking four.four.two gnex
[Samsung Galaxy Nexus] MWisBest:
Generally I use ART, however when I'm testing new builds I generally switch it to Dalvik and only after everything checks out OK with Dalvik will I switch back over to ART.

When 4.4 was first released, ART definitely had some issues, but with the release of 4.4.1 they fixed some bugs in ART and the main things that FC'd (GApps, Titanium Backup, most popular apps) don't FC anymore, be it due to the 4.4.1 ART fixes or updates from developers to their apps.

As for performance improvements, it varies from app to app, but overall Android itself (the UI, etc.) feels much more responsive. I can actually scroll through all my home screen pages without a single bit of stutter, something I've never been able to do before.

ART usually behaves like that when you first switch over to it, but after an hours time and maybe a reboot of the device it speeds up tremendously.
[Samsung Galaxy Nexus] rice923:
I switched to art for the past 2 days. Everything runs well after a day and a few reboots, but I still get TiBu FC's. Has that definitively been fixed, and I have an isolated case?
[Samsung Galaxy Nexus] MWisBest:
If you're on the latest official version of TiBu you definitely shouldn't be getting any FCs.
[Samsung Galaxy Nexus] rice923:
Alright. I'll go reinstall and see if it goes away.
[Samsung Galaxy Nexus] Moody66:
Last update nailed it. Battery is excellent and data is fine. Thanks for the work MW!
[Samsung Galaxy Nexus] MWisBest:
New build should be coming either today or tomorrow.

Current plan: "Operation Buzzkill" (squash as many bugs as I can find).

Since it looks like Android 4.4.3 is on its way, I'm (probably) going to hold off on any major changes until after 4.4.3 is released and merged into OmniROM, so I'll (probably) stick with the bug fixing stuff again.

I'm trying to get some code (that isn't specific to the optimization stuff FML does) merged into OmniROM as well in an effort to reduce the amount of forks I have, e.x. https://gerrit.omnirom.org/#/c/6428/

We'll see how that goes >.<
[Samsung Galaxy Nexus] GohanBurner:
Are the 3G/4G data handoff issues resolved in the latest release?
[Samsung Galaxy Nexus] hsypsufan:
Thanks MWisBest!!! The ROM is running great. Your hard work is greatly appreciated.
[Samsung Galaxy Nexus] heXacode:
From what i read nobody knows the full package of 4.4.3 other than confirming a major bug fix for N5 camera. Ive been keeping a close eye on what all 4.4.3 is bringing.

Both OmniMetal and FML Omni shouldn't have data issues. As for handoffs I do remember devvortex providing a couple fix commits for that issue that both Omni builds do have already. CM is finally getting around to doing major data fix affecting all CM based ROMs. Keep your eyes open for that discussion.
[Samsung Galaxy Nexus] Shadow Death:
Omni is by far one of the slickest ROMs I've used.
[Samsung Galaxy Nexus] MWisBest:
New build will have to be tomorrow, been busy dogsitting tonight, this little guy's quite the handful.

In the mean time I took the money I got for dogsitting and ordered some stuff on Amazon:

Atheros AR5B22 | Technical Specs

I needed a better WiFi card for my dev laptop, and this also has Bluetooth 4.0 built-in, so now I'll be able to thoroughly test and improve Bluetooth for FML finally.

Note: I got mine for $15, not the $30 on that listing.

I also ordered a USB OTG cable and an MHL adaptor, again more things to help with FML dev. :D
[Samsung Galaxy Nexus] Shadow Death:
Strictly for development purposes right? [emoji6] lol
[Samsung Galaxy Nexus] heXacode:
I'm waiting on the new credit card to come in and then I'll be out shopping for a new laptop finally. Can't wait to get it set up and get to learning to be a developer.
[Samsung Galaxy Nexus] MWisBest:
Yes, strictly. ;)

Awesome!
[Samsung Galaxy Nexus] MWisBest:
As usual I'm running on Valve Time. New build tonight or tomorrow, I promise.
[Samsung Galaxy Nexus] rice923:
You should really set up a donation link. Not necessarily for compensating your software (since I know you don't like that), but just to offset some of your time and hardware purchases. All of us here greatly support the things you've done for us [emoji106]
[Samsung Galaxy Nexus] MWisBest:
I will definitely consider that. I've had some family and friends suggest doing that as well, especially since I'll be needing money to pay for college come this fall. Yeah, as for just the code and stuff like that I don't think I've done anything that somebody else couldn't do, but the time put into it has been enormous.

EDIT: New build will be out tonight for sure. I mainly did a lot of work on the RIL so the mobile data flip tile thing in quick settings should work properly, among other things.

EDIT2: Or not. And no it wasn't an April Fool's joke, or at least wasn't intended to be! It was just one of those days where I broke more things than I fixed, haha. But um, yeah... sorry about that. :( At least there hasn't been anything particularly intriguing adding to OmniROM since the last FML build, so there's not much advantage to a new build at this point anyway I guess.
[Samsung Galaxy Nexus] peterlemonjello:
Are there any known issues dirty flashing this over Omnimetal? I don't mind clean flashing but thought I would ask since they're both Omni ROMS.
[Samsung Galaxy Nexus] MWisBest:
Well, you can certainly give it a try! If you have any issues though (only for the first couple of FML builds you flash at least), please do a clean flash before reporting it to make sure it isn't the cause of the issue.

EDIT: Yay, the build I just did boots, unlike the ones from last night. Just gonna give it a quick test drive and upload it if everything checks out.

EDIT2: One little nitpick I had with the build, so I'm gonna fix that and then do a full rebuild so everything is fresh. New build will be up in a few hours!
[Samsung Galaxy Nexus] MWisBest:
New build is up! Make sure to read the changelog, especially if you use ART.

Thanks for your patience. :)
[Samsung Galaxy Nexus] iwasaperson:
I flashed between the two for a while with no problems.
[Samsung Galaxy Nexus] dbt816:
I switched back to FML late last night...it was time for a ROM shakeup ;) The latest build with the DirtyV kernel (SmittyV, actually) is running flawlessly! :good:
[Samsung Galaxy Nexus] MWisBest:
Has anybody tried the TWRP build? If so, any feedback on it? Just wondering how it's working out for people since it's the first time I've included that. The reason I've been using it myself is the fixed support for encrypted data partitions as I've been using encryption for a few months now. BTW, encryption makes debugging problems that occur on boot more difficult for various reasons, that was part of what contributed to this last build taking so long to do. :(

For those who aren't familiar with how to flash a .img, it's usually done in fastboot, however if you don't want to deal with getting fastboot set up on your computer or something, check out the Flashify app on the Play Store, it should let you flash the .img right from your internal storage. I haven't tried Flashify personally but I've heard only good things about it. Just make sure to flash to recovery and not boot, and make a backup with it while you're at it.
[Samsung Galaxy Nexus] Shadow Death:
I'm using PhilZ Recovery 6.

That being said I had a strange issue using the latest FML with Dirtyv-RSR 4/2. Even while on the charger and being used the phone was eating battery. Also I have no effing idea what this process is:
[Samsung Galaxy Nexus] MWisBest:
After nearly 8 months of working FML, I am now accepting donations. I have updated the main post with some information about it.

I'm not seeing that... weird.

As for the phone eating battery, the only thing I can think of would be the Battery Life Extender thing, have a look at Performance under Settings, and look at the Battery tab. Check the "Charge Limit" there.

Since I can't reproduce any of this on my end, it'd be helpful if you could provide a logcat please. :)
[Samsung Galaxy Nexus] MWisBest:
I've recently become aware of a bug with ART in the latest build where every time the phone is turned on and/or restarted a number of apps might have their dalvik-cache unnecessarily regenerated. I hope to get a new build out tonight or tomorrow to address this.
[Samsung Galaxy Nexus] smokeydriver:
Never used this ROM, but as soon as you get the newest up, I'll be installing it ASAP...looking forward to it!
[Samsung Galaxy Nexus] MWisBest:
Working on the new build, in the mean time I discovered that another bug I tried to fix in the last build was indeed fixed, I wasn't expecting it to be fixed so I didn't even test it until now:

ROM/Recovery: Fixed MTP (access to internal storage via USB) and ADB not working in TWRP (shouldn't require usage of my TWRP recovery build, just the ROM should be sufficient to fix it in official TWRP builds as well, I'm not certain if this bug is in TWRP 2.6.3.2 but it definitely is in TWRP 2.7.0.0).
[Samsung Galaxy Nexus] rice923:
So recently Google maps asked if I wanted to dim/turn off the screen while navigating, and come back on automatically when it reaches a turn. I accidentally declined, but want this feature desperately. Anybody know how to turn this feature on manually?
[Samsung Galaxy Nexus] smokeydriver:
Yeah, I also said no since it said that I could turn it back on at any time...but I don't see it anywhere. I even tried to clear maps data and it's not asking again.
[Samsung Galaxy Nexus] ashclepdia:
while I haven't been able to try this directly myself, or seen this pop up yet, my first immediate thought, if it didn't show in settings anywhere, is to try clearing defaults/data on app(which second post mentioned tried already)

OR see if you can install updates for maps app. then reboot, then update it and open and see if it asks you again.

could be a bug within maps that you may want to report/feedback to Google about directly
[Samsung Galaxy Nexus] Philosophre:
"quietly" waiting for the update. still on the early march update.