yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] smokeydriver:
Hi all- in all this back and forth about F2F, I've gotten a bit lost. If I wanted the newest ROM on my phone, could I just do a clean or dirty wipe with the same TWRP I've been using (2.7.1.0 I believe)? As in, must I do something with F2F?
[Samsung Galaxy Nexus] Zer0_Cool:
you do not have to format to f2fs, but if you want to, you must use the new recovery, which supports f2fs. f2fs is supported on the latest build, but is not necessary. Depending on which partitions you choose to reformat, you would lose data.

If you stick to ext4 then you could probably get away with a dirty flash, but make a backup just in case. I do not believe that you would need to update your recovery unless you wanted to reformat to f2fs.
[Samsung Galaxy Nexus] smokeydriver:
Great, thanks! If I did want to go to F2FS, would the easiest/quickest/best method to just follow MW's directions previously? They seemed to be quite a few steps and I'm getting lazier with my phone lately. I just want one ROM that's working the way I want and I'll probably not flash anymore. Been ready for a new off-contract phone for a long time now! I have the Verizon unlimited data and want to keep that. I played with the S5 and M8 a bit, and they seem really nice, but both are missing just a few things to be perfect for me. Hopefully there's something in the works that'll be just right!
[Samsung Galaxy Nexus] Zer0_Cool:
I'm waiting to see what's good with the moto x+1 personally. And yep, just follow his directions it's pretty easy. Update recovery, do the wipes listed, go to advanced settings and change the filesystem of system/data/cache (whichever you choose, or all) one at a time , then get the rom/gapps back on the sdcard (I used adb and pushed them while I was still in recovery), flash and reboot, then set up as normal. Before proceeding,

make sure you back up any documents/pictures that you don't want to lose to your computer

.
[Samsung Galaxy Nexus] rice923:
If I wanna do a fresh flash of an older version, where can I find it? Specifically the version just before this one
[Samsung Galaxy Nexus] Shadow Death:
It wouldn't be so bad but the guy who made an Unlock Boot Loader and S-Off for the HTC One M8 decided he wanted to charge 25 bucks a pop for it. You could also go through HTC's website. While Verizon wants the bootloader locked HTC does offer the ability to unlock it for developers through their HTCdev site.
[Samsung Galaxy Nexus] MWisBest:
At the top of the FML thread there is a "Downloads" button/tab of sorts, but I'm guessing you're on Tapatalk or something so I'll link you right to it:

http://xdaforums.com/devdb/project/dl/?id=6701

I thought the HTCdev stuff usually wouldn't let you unlock Verizon devices. I remember there was a slip-up where they allowed unlocking the Droid DNA but within a few days they stopped allowing that, figured that was the case for all the HTCs on Verizon.

To be honest I'm not a huge fan of HTC. At first they were probably the best OEM for Android devices, but they went downhill around 2011 in my opinion. They've certainly made a decent comeback with the HTC One and are continuing that comeback with the HTC One M8, but I'm not convinced just yet.

Here's kinda my observations on Android device OEMs at the moment...

It seems like any time a company gets a foothold with the open-source community and treats them well, they eventually end up cutting them off pretty bad. First it was HTC, then it was Samsung. Right now the most dev-friendly OEM is probably Sony, given that they release AOSP device trees and have a bunch of stuff up on GitHub, and they're on a good streak and considering they are only getting better it seems that they may be the OEM to break the open-source back-stabbing I've seen from others. A problem I have with Sony devices though, is that last I checked they don't have a separate partition for the recovery, instead it's integrated into the boot img with the kernel and all that, so if you screw up flashing the boot.img you have to use fastboot to recover. While it's certainly not the end of the world since you can just use fastboot to flash a new boot img, it sucks that they eliminate a line of defence. And if you hose the bootloader, you won't be booting into the recovery any time soon as it is obviously, but still I can't stand that system...
[Samsung Galaxy Nexus] rice923:
You guessed it. I'm on tapatalk and only saw the change logs for the older builds. Thanks again MW!
[Samsung Galaxy Nexus] Shadow Death:
I know they allowed it for a little while at least. There are several threads about it on the forums. Most have found work around because once you do use that site it voids hour warranty and they keep track of it.

BTW..
[Samsung Galaxy Nexus] Rushead:
Go ahead, rub it in...
[Samsung Galaxy Nexus] Shadow Death:
Lol I call it the benchmark. With enough phones going for battery life I suspect nexus phones will start doing it now too.
[Samsung Galaxy Nexus] rice923:
Take your fantastic battery life and jump off a cliff!
[Samsung Galaxy Nexus] execute_method:
I recently jumped ship from Verizon to an mvno and a nexus 5.

My nexus 5 consistently gives me 5! Yes five! Hours of screen on time and I usually get well more than 18 hrs out of it. With light use I can go 2 days on a charge pretty easily.

It's really nice not having to be worried if I don't have a charger in my pocket or vehicle. I used to ration my use of my gnex because of the battery life if I was out and about for the day.

At this point, I only wish I made the switch sooner.
[Samsung Galaxy Nexus] quickdraw86:
AIO, straight talk AT&T, or...?
[Samsung Galaxy Nexus] Shadow Death:
Lol
[Samsung Galaxy Nexus] execute_method:
Cricket/AIO.

AT&T owns aio, bought cricket and is now combining the 2 into just cricket.

2.5gb of data

Unlimited everything else

$45/mo for first line and $10 discount per line added. So 2 lines $80/mo. 3 lines $105.

Still uses the aio apns for the gsm service.
[Samsung Galaxy Nexus] MWisBest:
I have no problem with battery life.

Then again I got a free 2100mAh battery and back cover for it from Sprint (throwback... friday?), and bring the 1850mAh with me on trips... and I have this MONSTER 1300mAh external battery pack (which I got on sale for like, $30).

So... I have no shortage of power, that's for certain! :D
[Samsung Galaxy Nexus] Philosophre:
Well I guess the question is how quickly do you swap out of your 2100mAh battery or whatever main battery you use?

Of course depending on use. I am on the previous version and I last about 4 hours with constant web surfing on the standard battery.

Is there another update coming in a week or so? If not, I'll jump on this one.
[Samsung Galaxy Nexus] Rushead:
Definitely jump on this one. This is by far the best iteration of FML (and I've tried them all).

P. S. Don't ask for etas [emoji6]
[Samsung Galaxy Nexus] MWisBest:
I usually don't have to swap them out actually. I don't really keep track of battery life much, my phone is usually plugged in a lot as it is.

I was hoping that the next build would have the new PVR drivers, but I don't think they'll be ready in time... also been busy with some stuff for official OmniROM builds. If anything interesting shows up in OmniROM soon then there will be a new build within a week, otherwise probably not.

Thanks!

^This, luckily I was going to give an update on how things are going anyway...
[Samsung Galaxy Nexus] domenci:
Hey homie, 7/5's running great. Any way you could take a look at the photosphere rendering issue for the next build? Thanks again.
[Samsung Galaxy Nexus] Philosophre:
alright. this phone is gonna be updated tonite.

sms backup+ seems to not work nicely with the omni, did work well before omni. i cant backup properly or restore at all.

any recommendation for one? what i liked about sms backup+ was that it saved my txt to my gmail account.
[Samsung Galaxy Nexus] demlv:
"SMS backup and restore" has always worked well for me. I'm pretty sure it has plugins to upload backups but I have always restored from my SD card.
[Samsung Galaxy Nexus] otter34:
Titanium backup works best for me. It takes longer to restore the messages but they are all always restored. For me the same can't be said for sms backup and restore
[Samsung Galaxy Nexus] otter34:
If someone could check battery stats and see if Google location services is high on the list or not, I'd appreciate it
[Samsung Galaxy Nexus] dbt816:
Have you tinkered with the Neutron music player?
[Samsung Galaxy Nexus] MWisBest:
Hadn't heard of it until just now, looks pretty nice but I'm going to wait a bit before I give it a spin. It's just a 5 day trial and then I gotta cough over $6, would rather wait until I get this other stuff going first and I could compare it then.
[Samsung Galaxy Nexus] Philosophre:
welp... I flashed fml-twrp-2.7.1.0-20140705-toro and now I am in a loop. Just shows the google logo then it restarts back to it every 30 seconds.

i can't get into recover. i can get into fastboot kinda. Odin Mode. The only option is to "start" which leads me into the boot loop. In odin mode, it shows the green android and below him says "downloading..... do not turn off target!!"

ADB device not found.

Thoughts?
[Samsung Galaxy Nexus] MWisBest:
I'm almost certain you aren't supposed to be in ODIN, if I remember correctly it doesn't even work on the Galaxy Nexus.

Can you not get into fastboot? Hold down power+volume up+volume down and don't let go until fastboot shows up?

If you can't even get into fastboot there's something else going on here. I'm almost wondering if your eMMC is hosed somehow. If that's the case there's a chance it can be fixed with a utility called OMAPFlash, else you can get a 32GB eMMC for just $10 and it'd just take a few minutes to swap out.
[Samsung Galaxy Nexus] Philosophre:
LOL. I totally forgot about HOLDING BOTH volume up and down. I alternated. My brain farted for a long time since it happened this morning. I shoulda known this beginner stuff. Do Da! I just restored and i'm back to normal.

now back to the issue. why did fml-twrp-2.7.1.0-20140705-toro not work... trial and error is fun. especially if you can restore. mucho sadness if not.
[Samsung Galaxy Nexus] MWisBest:
Can you boot into recovery from fastboot, and are you sure it's the FML recovery (especially the one from the 07/05 build!)? Are you flashing a different kernel at all?

Being stuck on the Google logo sounds like /system isn't mounting. If you are using the DirtyV kernel (any variant), or probably any other F2FS kernel in general, you have to format to either all F2FS or all EXT4, as it doesn't support mixed formatting. If you aren't using the proper recovery, I can't guarantee it will format the partitions properly.

[MENTION=4544860]osm0sis[/MENTION], if you could add support to the DirtyV flashing thing for detecting if the ROM supports the fallback fstab system and to use a fallback fstab if so that'd be awesome.

Right now the only way I can think of checking for that is to read the build.prop and check something in there. I'm thinking to at least check for FML you can check ro.modversion has the suffix FML and if possible make sure the date of the build is 20140705 or later. ro.modversion on the current FML build (first to support the fallback fstab) is "OmniROM-4.4.4-20140705-(ro.product.device)-FML"
[Samsung Galaxy Nexus] osm0sis:
Hmm I was hoping to not overcomplicate it since everyone was gravitating towards all or none, but yeah, I'll definitely figure something out for different combinations. Maybe something like keeping only one fstab, but swapping f2fs into it more surgically using grep and sed for each partition before the mount_all. Heading on vacation Wednesday so I probably won't be able to get to it until the end of the month. Sorry.

There's another possibility too, Vanir did like a reverse AnyKernel thing, where the ROM repacks the custom kernel to add what it needs. Pretty cool but it might be too much work. :)
[Samsung Galaxy Nexus] Philosophre:
I am only using the items provided in the first post.

Prolly a bad d/l. I redownloaded the twrp and went through fine. Flashed omni-4.4.4-20140705-toro-FML then pa_gapps-modular-mini-4.4.4-20140708-signed.

I kept it simple. Play store is reinstalling all the apps for me as I type. boy oh boy it sure takes forever.
[Samsung Galaxy Nexus] MWisBest:
I'm going to be getting some beta builds going soon.

Won't have the new GPU drivers, but it will have a heavily updated kernel courtesy of [MENTION=2633638]Ziyan[/MENTION], that isn't far off of the changes that'll be required for the new GPU drivers. My hope is that this will get more testers in order to find any bugs that aren't because of the newer GPU drivers.

This will also be helpful for my audio project, as there are differences between the older kernel and the newer kernel so I don't want to write the same code twice or anything stupid like that. Plus, most other OMAP4 devices will be more up-to-date as well, so it'll be good to go for plenty of other devices too.
[Samsung Galaxy Nexus] MWisBest:
Here's the first test build.

THIS IS PROBABLY NOT 'DAILY DRIVER' MATERIAL.

I really need some feedback on this. I'd suggest only testing it in a um... 'controlled environment' (at home, where it's not a big deal to flash back to a previous build).

F2FS IS SUPPORTED AS USUAL!

HOW TO HELP REPORT BUGS:

1. Get a logcat. I'd do it like this:

Open up a terminal emulator on your phone.

Type in "su" to get root. Allow it if you haven't already.

Type in "logcat > /sdcard/LOGCAT_NAME_HERE.txt"

After about 10 to 15 seconds, press volume down and the C key on the keyboard. This should stop the logcat program.

Grab the logcat file off of your device, and attach it to a post. Note: You might have to do a media rescan thingamajig, the Trickster Mod app has a thing for it.

If for some reason the bug is severe enough that you cannot do anything on the device, you'll need adb set up on your computer, and then do it this way:

Open up a terminal window on your computer (with the phone plugged in already of course).

Run "adb logcat > LOGCAT_NAME_HERE.txt"

After about 10 to 15 seconds, press Ctrl+C on your keyboard to stop the logcat program.

Attach the logcat file to a post here.

2. Get a dmesg output. I'd do it like this:

Open up a terminal emulator on your phone.

Type in "su" to get root. Allow it if you haven't already.

Type in "dmesg > /sdcard/DMESG_NAME_HERE.txt"

After about 10 to 15 seconds, press volume down and the C key on the keyboard. This should stop the dmesg program.

Grab the dmesg file off of your device, and attach it to a post. Note: You might have to do a media rescan thingamajig, the Trickster Mod app has a thing for it.

If for some reason the bug is severe enough that you cannot do anything on the device, you'll need adb set up on your computer, and then do it this way:

Open up a terminal window on your computer (with the phone plugged in already of course).

Run the following commands: "adb shell", "su", "dmesg > /sdcard/DMESG_NAME_HERE.txt".

After about 10 to 15 seconds, press Ctrl+C on your keyboard to stop the dmesg program.

Run "exit" until you are out of the adb shell, then type the following command: "adb pull /sdcard/DMESG_NAME_HERE.txt DMESG_NAME_HERE.txt

Attach the dmesg file to a post here.

omni-4.4.4-20140715-toro-FML.zip (159.05 MB)
[Samsung Galaxy Nexus] dbt816:
So far, so good here! :good:
[Samsung Galaxy Nexus] MWisBest:
New beta build, this adds back some of the bells and whistles (and even a couple security fixes...) to the kernel (as well as doing them in a more proper manner). Still not at 100% of course, but it'll get there.

This seems to be more stable than I had initially anticipated, so I'd look at it like this: If you aren't extremely dependant on your phone, and you can afford to maybe do a battery pull once in a while for a hard lock-up, it should be OK for you to use 24/7.

omni-4.4.4-20140716-toro-FML.zip (159.09 MB)
[Samsung Galaxy Nexus] MWisBest:
Based on the lack of replies I'm guessing there haven't been any issues with this build! :good:

Development update:

"OMAP Audio Control" is coming along OK. The equalizer stuff is way more complex than I had originally thought though! The equalizer probably won't be ready for a while, but I'm working on getting some other stuff in there as well anyway. I'm planning on adding a menu to DSP Manager for this, as well as eventually a standalone app that could be used on any ROM for those that e.x. stick with AOSP but use custom kernels (which I hope will pick up on OMAP Audio Control when it is further developed at least). I'm thinking that I'll have a new FML release within the next few days.

Other news:

I now have a weird obsession with the Nexus Q... it uses, guess what, an OMAP4460 SoC. How awesome would it be for me to have THREE OMAP4460 devices. :laugh: Hopefully someday I can pick one up for cheap on eBay or something.
[Samsung Galaxy Nexus] midnightdevil66:
No issues here running that build with SmittyV kernel. Thanks!
[Samsung Galaxy Nexus] dlabadie:
Working geeat with FML kernel.
[Samsung Galaxy Nexus] hawk687:
Really freaking excited for audio control... Just throwing that out there
[Samsung Galaxy Nexus] MWisBest:
Currently tinkering with compilers, hoping GCC 4.9 is maybe at a point where it produces a booting build finally...

Don't get your hopes up too much yet, this DSP stuff is a whole new galaxy (pun not intended) to me. If anything from it is even in the next FML build at all it probably won't be much.
[Samsung Galaxy Nexus] hawk687:
Hardware audio enhancement is very much worth the wait [good]... Thanks for all the hard work
[Samsung Galaxy Nexus] MWisBest:
BREAKING NEWS: Next build of FML will be built with Linaro GCC 4.9.
[Samsung Galaxy Nexus] mastertech007:
That is great. Can't wait.

Um, what is it? Googling now.. [emoji13]
[Samsung Galaxy Nexus] MWisBest:
Update regarding GCC 4.9...

I'm currently being hit by this bug: https://bugs.launchpad.net/gcc-linaro/+bug/1332989

While I'd certainly like to get that fixed, I think it might be out of my hands, so I'm not going to make just that one bug (so far...) stop me from switching to GCC 4.9.
[Samsung Galaxy Nexus] MWisBest:
I have a question for you guys:

Would you rather see more frequent FML builds but with less changes in each build, or continue with what I've been doing lately and release builds less frequently with a huge amount of changes in each build?

Part of what has caused me to slow down with releasing builds is that I'm just getting extremely ambitious with things. For example, here's a preview of the changes for the next build, in order of when they were um, started.

- Complete overhaul of the kernel, rebasing it on top of Ziyan's heavily updated kernel. He managed to pull in upwards of 1,000 commits from the omapzoom kernel (sort of the 'official' OMAP (the CPU the Galaxy Nexus uses) kernel, which while the Galaxy Nexus was based on this kernel, it got neglected and wasn't kept up to date). I've also used this as an opportunity to clean up many things with the previous kernel and do them 'properly' this time around.

- Laid down some initial code for "OMAP Audio Control". This isn't going to be much for a while, as I'm not really familiar with Digital Signal Processing (DSP), at least on such a low level! But like just about everything I do with FML, it's an opportunity for me to learn new things.

- Switched the compiler for the ROM to Linaro's GCC 4.9, and the compiler for the kernel to 'standard' GCC 4.9. This should result in an all-around improvement of speed, however it also could introduce some bugs. The kernel seems fine, but the ROM-side of things was pretty disastrous:

--- First, it wouldn't boot at all. After a while I was able to figure out what the problem was and implement a workaround for it.

--- Second, it resulted in a huge problem with my /data partition, after tracking down and fixing what was causing this I had to reformat /data.

--- Third, fourth, fifth, sixth, and seventh, there were just random inexplicable crashes, that I somehow managed to fix. Seriously!

--- Eighth: I haven't gotten to eighth yet actually but I'm sure I will eventually!

- Small change to the build.prop that will improve (reduce) memory usage.

- Updated libpng from 1.2.46 (released in 2011, however 1.2 as a whole was originally released in 2001) to 1.6.10 (released just a few months ago, with 1.6 as a whole being released in 2013), and also enabled NEON for it. This may or may not affect speed or stability... I'm not going to say that it will as there's not really a way for me to measure it and if I try to 'guess' based on how it 'feels' my mind will probably play tricks on me and just make it a placebo effect, but I certainly like higher version numbers!

- Switched from libjpeg to libjpeg-turbo. Like the libpng change, libjpeg-turbo has NEON support, and as a result is claimed to be 2 to 4 times faster than the regular libjpeg.

- Enabled LTO (Link-Time Optimization) for all the things it previously had to be manually disabled for: parts of bionic and parts of ART. This is partly due to fixes and improvements to LTO by GCC 4.9.

I hope the links were helpful! I know this stuff can be hard to understand sometimes.
[Samsung Galaxy Nexus] oman0123:
Holy poop on a stick.

Give me a minute to gather my brains that just exploded across the room from reading that.

I for one vote you keep what you have been doing. I like a few updates with a lot of change. Keeps things exciting for me lol

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] mastertech007:
Keep it the same. What you've been doing had been great this far, don't change it. If you spoil us, we will always expect it.
[Samsung Galaxy Nexus] midnightdevil66:
I'm good with how you're rolling now.
[Samsung Galaxy Nexus] thetakerfan:
While I have no issues with the infrequent builds as we've been getting (since the ROM is generally pretty stable, compared to most other KK ones I've tried), I would be a bit cautious with introducing too many big changes at once. Things like rebasing the kernel, switching compilers, etc are pretty major so it could introduce complexity with folks encountering issues once the ROM is out in the wild. The Galaxy Nexus seems notorious for "Well its working for everyone else except" type issues (So far I've been lucky and not been one of those, but I see it often enough)
[Samsung Galaxy Nexus] hawk687:
+1 for keep doing what you're doing. You're work has always been substantial... Not just for this rom but our lowly gnex all together.
[Samsung Galaxy Nexus] otter34:
I'd prefer a stable ROM without any issues and I'd rather see the bugs fixed before adding any bells and whistles.
[Samsung Galaxy Nexus] quickdraw86:
More stable with less frequent updates is what I like. I've never been a nightly flasher.
[Samsung Galaxy Nexus] cujo6801:
That's not what your neighbor says..... :D

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Rushead:
While I agree with what you're saying as a whole, [MENTION=341447]MW[/MENTION] knows what is best for his rom, and I welcome whatever changes he is willing to implement. His builds have never been really unstable, and he is always on top of any instabilities that may have arisen in the past.

I say fewer updates works since this rom is so super freakin stable. In fact, I think there's a hidden 12-step program somewhere in FML....I feel my crack addiction fading ever so gently away.......
[Samsung Galaxy Nexus] domenci:
I loved this ROM but had to switch since I had camera issues (MW acknowledged this but hasn't fixed it afaik) and random reboots. I'm on Shiny (basically AOSP) now, and with Xposed adding in the features I originally started using custom ROMs for, I don't think I'll be going back. I'm not seeing a difference in battery life or speed, and it's just as smooth for the calls, texting, browsing, and media that I do on the phone. The stability is the main reason I left, and I feel that constantly tweaking tons of things might have something to do with it. of course YMMV, and obviously a lot of people are fine with it as is.

I do want to say thanks for all your hard work, MW!
[Samsung Galaxy Nexus] quickdraw86:
Sharing is caring ;)