yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] a3361035:
There's no guarantee for that.
[Samsung Galaxy Nexus] klingklang76:
I'm currently running 0701. Assuming I want to clean install m8 when it's out, what would you suggest to restore app data and preferences: TB or restore nandroid /data only? Unfortunately I haven't tried either one myself yet... of course I would keep a complete nandroid in case of likely screw up [emoji6]
[Samsung Galaxy Nexus] mckennal:
I used My Backup Root last time and it worked quite well for apps + data (non-system apps that is).

Luke
[Samsung Galaxy Nexus] Kustaa:
Does anyone know why is that there's still present the annoying lag when going from notifications panel to quick settings and vice versa? Even the Moto G does it so smoothly. Why isn't that fixed already????
[Samsung Galaxy Nexus] xergio24:
The BBQLog Site has been down for several days now, someone knows why?

http://changelog.bbqdroid.org/#/maguro/next

(is the one that's on the #2 post)
[Samsung Galaxy Nexus] soder:
http://www.cmxlog.com/11/maguro/ is working.

/Söder
[Samsung Galaxy Nexus] a3361035:
Neither are clean installs anymore. Don't restore anything, so it's actually clean.

Restoring /data is exactly the same as a dirty flash.

TiBu restore of apps - even if not system apps - still contains the old Google ID which changes during a factory reset and apps don't expect random ID changes. Kind of the same problem as with clearing Google Services Framework data. [1]

[1] http://www.reddit.com/r/Android/com...or_google_service_framework/cdiymrp?context=3

Note that it's just parsing gerrit review [1] and not git. But CM devs sometimes merge directly without first going through gerrit.

You could directly look at gerrit review [1] and just ignore the other device trees.

And there's always /system/etc/CHANGES.txt for the last actual changes, if you don't need to look in the future.

[1] http://review.cyanogenmod.org/#/q/status:merged,n,z
[Samsung Galaxy Nexus] agritux:
[MENTION=5856785]a3361035[/MENTION] is the pro version of TB changes google id? it says changes?
[Samsung Galaxy Nexus] m.is.for.michael:
If the device id changes (eg after a factory reset) tb will detect it on first run and prompt you to change it back. You need to take this opportunity if you want to restore any data.

sent from my brain using telepathy
[Samsung Galaxy Nexus] cujo6801:
For myself I found it makes no difference

I hit ignore and go about my merry way restoring everything.

I restore apps and data with no problem...

Id may change but never found a problem with it...

Sent from the "DOG" pound
[Samsung Galaxy Nexus] m.is.for.michael:
I learned the hard way ... An error on reboot along the lines of "inconsistent device ids detected. Your device may be unstable (Ignore) (factory reset)" ... Followed by random reboots.

sent from my brain using telepathy
[Samsung Galaxy Nexus] cidefix:
I can't see any serious lags here.

"Even" the Moto G? You know that the Moto G is about 2-4 times as fast as our nearly three years old Galaxy Nexus, do you? :laugh:
[Samsung Galaxy Nexus] Kustaa:
Yeah I know but the GNex has been smoother than other phones with higher specs, and by lag I mean stuttering, low fps. And it's there...
[Samsung Galaxy Nexus] catalin.v:
I don't have a Gallery anymore in the latest nightly. How can I get it back?
[Samsung Galaxy Nexus] cujo6801:
If I'm not mistaken you can download from the Play Store

Sent from the "DOG" pound
[Samsung Galaxy Nexus] a3361035:
M8 is near. Prolly today (PT):

https://twitter.com/CyanogenMod/status/486231646060806145

Normal nightlies halted, prolly for M8:

http://jenkins.cyanogenmod.org/job/cm_daily_build_cycle/

Official notable changes (not final yet):

http://review.cyanogenmod.org/#/c/67613/

===

Edit:

M8 builds started. maguro is among them.:

http://jenkins.cyanogenmod.org/job/android/

Some full changelog from M7 to M8 for another device (amani). Ignore the device tree changes:

http://mirrors.reflected.net/pub/get.cm/jenkins/75178/CHANGES.txt
[Samsung Galaxy Nexus] Kustaa:
To make sure the safe jump from 07/01 nightly they should include searchable settings right?
[Samsung Galaxy Nexus] klingklang76:
Don't know about you, but to me 0701 is working so nicely that I'm having doubts whether or not switching to M8 actually makes any sense at all... :-\
[Samsung Galaxy Nexus] Darklife1337:
so today is the m8 day, think is time for a clean install with pa gapps (my last clean install was like on december lol)
[Samsung Galaxy Nexus] nischalnischal:
M8 here

M8 here M8 here... wow am excited :)
[Samsung Galaxy Nexus] yayakuya:
M8 yeaah... this is what im waiting for...

ready to jump from M7 F2FS to M8...

sure... it will be F2FS also... :D

thanks a tons CM TEAM
[Samsung Galaxy Nexus] michael_ch:
Is there any special kernel needed for F2FS or is support included in the CM11 M8 stock kernel?
[Samsung Galaxy Nexus] Darklife1337:
someone already flashed it? bugs/problems?
[Samsung Galaxy Nexus] Kustaa:
Flashed over 07/01 nightly, wiping cache, dalvik and system. Runing good, no problems so far
[Samsung Galaxy Nexus] onnaj:
Did a clean install. So factory reset, install 060614 gapps and M8 snapshot and got a bootloop the 1st time, but the 2nd time it is starting.

Yet have to install everything and try the new rom.
[Samsung Galaxy Nexus] xergio24:
Ok, here are 4 of the most frequently asked questions (taken from CM blog post about M8):

#1. When was M8 branched?

The M8 code was branched to stable on June 30th and is based on Android 4.4.4.

#2. What is the last ‘safe’ nightly I can upgrade from?

The last nightly you can upgrade from without chance of issues is June 29th.

#3. I didn’t see/know there were such considerations as #1 and #2, and now Settings is crashing – what can I do?

Clear the data for the Settings app – this can be accessed via the recents menu (long press the Settings multitask item).

#4. Why is #3 happening?

By being on a newer nightly than June 30th, your Settings database version is higher than that of the M release – and downgrades of database versions are not allowed in Android.
[Samsung Galaxy Nexus] Kustaa:
But in M8 there is searchable settings, and afaik june 30th nightly doesn't have this...
[Samsung Galaxy Nexus] xergio24:
I think that is because it was "cherrypicked".

If I'm not wrong that means they choose to take some things from newer code and add them to the M release.

BTW... I cannot tell if june 30 nightly has searchable settings because I am on june 29 now (about to update to M8) and it doesn't have it.
[Samsung Galaxy Nexus] Kustaa:
I'm almost sure it started on 07/01. Anyway...I dirty flashed and not a single issue :)
[Samsung Galaxy Nexus] a3361035:
Full changelog from M7 to M8 for maguro:

http://mirrors.reflected.net/pub/get.cm/jenkins/75222/CHANGES.txt

F2FS is neither supported nor does CM include the needed F2FS commits on the ROM side. [1] A custom kernel with F2FS does not change that, it needs to be in the ROM, too.

Those converted frankenbuilds are certainly not a good idea.

[1] http://xdaforums.com/galaxy-nexus/d...tyv-6-9-14-t2613655/post53598931#post53598931
[Samsung Galaxy Nexus] Darklife1337:
ty for the infos ;)
[Samsung Galaxy Nexus] yayakuya:
For F2FS users only

i will make it very simple as turn my phone off... :D

1] Download this M8 > open the rom.zip with winrar ( let it opened )

2] Download this package: https://www.dropbox.com/s/a6uvzpyk31j4i88/Kitkat-maguro_F2FS_Package.zip > also open it with winrar

3] Just DRAG N DROP the whole package into the rom w/o extract it

4] Flash n profit...

This package has everything needed for ANY 4.4.x ext4 roms to use to f2fs partition nexus device

yes, you can convert ANY KK 4.4.x ext4 ROMs w/o any converter stuff

ps:

guess what, im running this M8 F2FS right now w/o any problems.... ;)

and idk idea if it make any sense or not, coz im ok with those converted Roms... i've Slimkat, P.A, Carbon, CM... all of these ext4 roms are running perfect with the package installed...
[Samsung Galaxy Nexus] saprer:
does this work with other roms also? and with roms from 4.3?
[Samsung Galaxy Nexus] AgentSmith:
Everyone, to use almost any ROM including CM11 with F2FS use [MENTION=3927368]poo706[/MENTION] 's amazing tool to convert it. This can be done in Windows, Linux and even in a terminal on your phone. Just make sure to use an F2FS enabled version of TWRP to be able to format /system, /cache and /data including /sdcard. Of course make a full backup of your device first as it will be completely empty. And READ THE INSTRUCTIONS.
[Samsung Galaxy Nexus] yayakuya:
post updated... ;)

only for KK ROMs...

================

if i see here on /system/bin

i saw this [ attached ss ] i think it's working f2fs
[Samsung Galaxy Nexus] a3361035:
CM is speaking for every device.

Nightlies aren't build all at once and searchable settings isn't prolly even the the last commit before branching - it wasn't cherrypicked[1]. Maybe the next nightly might be still safe for maguro, but i'm not going to hunt down the commits.

The actual Settings database version only changed later[2], but M8 branch was already different before.

[1] https://github.com/CyanogenMod/android_packages_apps_Settings/compare/stable/cm-11.0

[2] https://github.com/CyanogenMod/andr.../search/SettingsSearchDatabaseHelper.java#L33

Quoting my post about how stupid frankenbuilds are to post a frankenbuild doesn't make sense.

Read my post again.

You need to pick up those commits that CM is missing, actually build CM with those commits cherrypicked and then test it.

To be very clear:

F2FS is an experimental filesystem: not recommended

F2FS enabled custom kernels for maguro are still very much work in progress: not recommended

ROMs need further additions for F2FS: don't make frankenbuilds of random ROMs

If you really want to use F2FS at least use a ROM with an actual developer that supports F2FS like MWisBest's FML (Omni based ROM from Omni's maguro device maintainer):

http://xdaforums.com/galaxy-nexus/development/rom-fml-fork-life-06-05-2014-v2-t2764064

===

In other news:

ciwrl said on IRC that new Installer builds (based on M8) will be coming soon (~1 week)
[Samsung Galaxy Nexus] skyleth:
any problems with m8 so far?
[Samsung Galaxy Nexus] qtoo941:
still wondering the same... any lags? major bugs?

Btw one really important for me question - does CM11 still got incoming call delay bug?
[Samsung Galaxy Nexus] a3361035:
There's an official bugtracker for M-releases:

https://jira.cyanogenmod.org/issues/?jql=project = CYAN AND affectedVersion = "11.0m8"

That was fixed in Jan 20:

http://review.cyanogenmod.org/57224/
[Samsung Galaxy Nexus] qtoo941:
i am feeling d*mb right now .. so i gotta try this M-release. thank you :D
[Samsung Galaxy Nexus] stephendt0:
I came here for the same thing. I'd also like to know how performance is. This will probably be a build that I'll be running for a while. Installing it on my mums Nexus now - will update if there are serious issues.
[Samsung Galaxy Nexus] aniketkuber:
Running the m8 with default kernel .. Performance is very good ... Last I had tried m5 ..
[Samsung Galaxy Nexus] steffenbakke:
Running the snapshot m8, and tried an earlier m7 release too, in both I've had a problem when using any file explorer apps, even the built in cm one, when trying to move files from Download folder on the SD card (not external), it says "Permission denied", same thing happens when trying to give a file permissions, even with root mode on.

anyone got an idea what is wrong?
[Samsung Galaxy Nexus] a3361035:
That does sound like broken permissions.

Did you restore anything on sdcard without keeping Unix file permissions?

How about a logcat and 'adb shell ls -ll /sdcard/Download' and other affected directories.

osm0sis' sdcard Fix Permissions script might be the solution:

http://xdaforums.com/showthread.php?t=2239421
[Samsung Galaxy Nexus] AgentSmith:
CM nightlies are work in progress by default. People here are following this discussion because they want a relatively risky cutting edge android on their phones. F2fs is cutting edge and people like me are hungry for it. It works, it even behaves fast and nice. We want it simply because it's new and possible. I understand where you are coming from but you're preaching in the wrong church buddy. ;)
[Samsung Galaxy Nexus] steffenbakke:
On the restore part, I actually flashed the m8 on top of the old version but as there where crash on the settings (I know why now :P), I choosed to reflash the rom with a full wipe and so on. I didnt use any restoring tools.

I'll provide a logcat later, if the fix permission script doesn't work, otherwise I might aswell try to use an aroma file explorer instead to see if that gets it rightm I wouldnt need to move other files other than this one so

Edit:

Tried using the fix permission script, didnt change anything. Is the correct way to gain the log, to set log debug-information in the cm file manager?
[Samsung Galaxy Nexus] AgentSmith:
Luckily I read about the settings issue before dirty flashing M8. What I actually did was clear settings data, then reboot to recovery and flash M8. Android has been without issues since then.
[Samsung Galaxy Nexus] namtombout:
What he's saying is that f2fs is actually not working on most roms for gnex. Converting the updater script and changing kernels alone won't enable f2fs. It seems to me most people are following the discussion because they want stability (m8) not cutting edge nightly. You think f2fs works, behaves fast and nice because it's not doing much except offering less space in system partition. If f2fs is working on gnex I certainly can't tell
[Samsung Galaxy Nexus] nikodr:
Ι think that when the new 3.4 gnex kernel is ready,and when the new gfx drivers are made available for 3.4 (the amazing devs we have managed to port it to 3.0 kernel but it is not yet fixed 100%) ,then we shall have a cm 11 good for gnex.

The 3.0 kernel especially the gfx part i think is a lit slow for nexus nowdays,let's hope the devs bring the new kernel :)

all will be very fast then !
[Samsung Galaxy Nexus] AgentSmith:
So you are saying that the f2fs version of TWRP does not actually format the partitions in f2fs and mount command reporting f2fs for those same partitions is actually wrong? I am no expert but to me that sounds a bit farfetched. Android is still Linux based and I don't see why implementing a different filesystem would be impossible or even difficult.
[Samsung Galaxy Nexus] a3361035:
Please read everything of what was said and don't just stupidly repeat which was already disproved (F2FS/frankenbuilds working well).

All CM commits go through code review - even for nightlies. So not the same, but worse.

Yes, enable that in CMFilemanager and then provide a logcat:

http://wiki.cyanogenmod.org/w/Logcat

Or a logcat without adb and through an app:

https://play.google.com/store/apps/details?id=com.nolanlawson.logcat

(but can't execute those adb shell commands then)

What's your understanding of a full wipe? Did you format the internal storage? How did you put things on /sdcard?

Are you using ART or F2FS?

This is not recommended at all. Having no FC is not the definition of working well.

Generally one should stay on the same branch.

Where are you GPU-bound? How big a performance gain would you need and why do you expect that from the new kernel/drivers?

To quote some actual dev:

Again:

Just having kernel space support of F2FS through the kernel but missing any user space tools support like in vold from the ROM is not really implementing it. For example you don't have fstrim anymore.
[Samsung Galaxy Nexus] AgentSmith:
I'll just ignore one word and say thanks for your response. Not everyone has knowledge about coding or even knows how to use github or other technical sites to look up all the information themselves. Thanks for your understanding.

Would you be so kind to share a bit more information about how exactly f2fs is disproved to be functional? I can't recall this being mentioned before on xda. How about the discard flag? Doesn't that make fstrim redundant? And I read that f2fs has been designed for trim on delete not to cause delays.

I just noticed that the new cursor soft keys swap places when the screen is rotated to landscape. I find this a bit confusing but it could be just me.
[Samsung Galaxy Nexus] skyleth:
So can we update from M7 to M8 without issues? I've never read about FC in settings after the update except here
[Samsung Galaxy Nexus] klingklang76:
My 2 cents: installed M8 after full wipe, with PA Gapps mini and PA google play services update package addon. Couldn't do anything because google keyboard FC repeatedly and wouldn't let me write. Reflashed (after full wipe) omitting play services addon, and this time everything went fine, apart for some play services complaints by a couple of apps, that were resolved after an update through play store. Now it runs pretty smoothly, although to my eye it's no better, nor less bugged, than my previous 0701 nightly
[Samsung Galaxy Nexus] musical_chairs:
Yes, upgrading M7 to M8 should be fine. Dirty-downgrading is not. For more on that, and the official word on settings FC'ing, see the blog:

http://www.cyanogenmod.org/blog/cyanogenmod-11-0-m8-released
[Samsung Galaxy Nexus] a3361035:
If F2FS would be stable it would be labelled as such in the mainline linux kernel and not be marked as experimental:

http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/fs/f2fs/Kconfig#n2

Just reading some changelog shows some issues:

https://lkml.org/lkml/2014/4/7/4

Not having a fsck that can repair consistency errors does exclude it from any serious consideration in productive setups:

http://elinux.org/images/b/b6/EMMC-SSD_File_System_Tuning_Methodology_v1.0.pdf (and yes it got corrupted)

Samsung never released a device with F2FS even tho it's their creation. (they had internal builds since the Galaxy S2[1])

Even if a OEM considers it usable, that doesn't say much. Remember the RFS fiasco:

http://xdaforums.com/showthread.php?t=799931

And Motorola just mounts /data as F2FS in the Moto X (same as Samsung did in their internal builds) and didn't use it anymore in the Moto E. Furthermore Google didn't allow F2FS in the Moto G GPE.

I didn't see any reliabiltiy/robustness tests for any of those F2FS backports. Afaik Android even lacks the LTP to do that. Linux wouldn't even allow an experimental FS to be upstreamed without passing the rudimentary ones:

https://lkml.org/lkml/2012/12/11/41

All in all it's an experimental implementation of an experimental filesystem.

P.S. Supposedly the discard mount option shows noticeably performance degradition. [2] Even if F2FS designed with trim on delete in mind, that operation won't cost zero. So not running it on every delete and just scheduling fstrim when free will be better.

Anyway fstrim will still run with discard, so not a clean solution.

[1] http://events.linuxfoundation.org/images/stories/pdf/klf2012_j_kim.pdf (beware those benches are old)

[2] http://xdaforums.com/galaxy-nexus/d...tyv-6-9-14-t2613655/post53078292#post53078292

Yes.

That issue only occurs if you switch from a newish nightly (somewhat after Jun 30) to M8.

This is more of an Gapps problem. So PA Gapps thread would be more suited.

It is a known issue that AOSP keyboard and Google Keyboard both in /system don't like each other.

So i would speculate that your full wipe wasn't a full wipe, i.e you did not format /system and some gapps addon.d backup script did restore Google Keyboard in /system while not deleting AOSP keyboard. Flashing PA Gapps the first time did replace that gapps backup script with a sane one, so it wasn't an issue the 2nd time.

It almost certainly is not related to the PA Play Services addon.

P.S. Technically Play Services updates itself and not through the Play Store, which is only for apps.
[Samsung Galaxy Nexus] klingklang76:
I did a factory reset the first time, manually wiped /system /data /cache the second. So I think you might be just right. Thanks, will keep that in mind for future upgrades :)
[Samsung Galaxy Nexus] emanuele1986:
I upgraded my galaxy nexus with m8 snapshot. Is IT better art or dalvick runtime?
[Samsung Galaxy Nexus] nikodr:
Ι think the lag that exists on certain roms,or delay when using the phone,i read some interesting stuff from that thread http://xdaforums.com/galaxy-nexus/devs-only/making-gpu-drivers-t2801072 this is taken from post 45 http://xdaforums.com/showpost.php?p=53965834&postcount=45

"From that 1000 commits, only a small portion are for the GPU drivers - the rest are OMAP updates. Kernels have two separate parts: the general kernel code, and the platform specific code (OMAP code in this case). Well, it was like the OMAP code was still on 2.6 for us.

We've got proximity fixed, and if everything goes right, camera will be working soon "

So even if gfx part is not the only deal the omap stuff will probably make kitkat roms so much faster for galaxy nexus,the guy added over 1000 commits from omap.It would never be the same.I am sure it will be way much faster when it is compiled for 3.4
[Samsung Galaxy Nexus] AgentSmith:
Different statements can be found about whether fstrim or discard is the better option. I don't have an opinion because of shear lack of knowledge. But are you implying that because in your opinion fstrim is better than discard f2fs will never be a valid option even when it becomes stable?
[Samsung Galaxy Nexus] Kustaa:
deleted.
[Samsung Galaxy Nexus] a3361035:
Only Dalvik is recommended.

That warning about it being experimental when you switch to ART is no joke:

http://review.cyanogenmod.org/#/c/55683/

First: that guy talks about backporting that stuff to the current 3.0 kernel.

Second: there are no statements about performance at all. Which of those commits do you think are related to performance?

Read my next sentence. Even if it were valid, you don't want both.

For discard vs fstrim you can further read the prev mentioned:

http://elinux.org/images/b/b6/EMMC-SSD_File_System_Tuning_Methodology_v1.0.pdf

Afaiu F2FS write operations are always sequential, so they can't take advantage of that.

Their result for f2fs was:

(that means w/o discard)
[Samsung Galaxy Nexus] AgentSmith:
Browsing through that PDF my impression is that it's all a bit inconclusive. E.g. they also conclude that discard works best with ext4 on media that doesn't support TRIM. That doesn't seem to make sense which they kind of admit. Now I fully agree that on productive systems f2fs is not at all an option now. However regular mortals like myself with phones that never ever need fsck as it is battery powered _could_ very well profit from this new file system.

I read somewhere that because of an IO queue f2fs is not really prone to delays with TRIM-on-delete but I can't find it anymore. But even if it does cause some delay again that doesn't really seem relevant for non productive systems with very few delete operations. But by all means, correct me again if I'm wrong. ;)
[Samsung Galaxy Nexus] a3361035:
More like a strange bug in the driver/controller.

I consider my phone a productive system and the fs should be proven to be reliable.

You should want at least a robust filesystem which doesn't easily get corrupted by a sudden-power-cut when you are on the bleeding-edge and battery pulls might be necessary. If you read that prev mentioned f2fs changelog again:

* recover xattr node blocks correctly after sudden-power-cut

That was a bug just fixed in April and SELinux does need xattr.

You are kind of right. But calling it TRIM on delete is wrong:

https://www.kernel.org/doc/Documentation/filesystems/f2fs.txt

So shouldn't be much diff.

Anyway this is getting way offtopic and should be prolly further discussed in some actual f2fs thread.

P.S. I'm still critical about those speed gain claims and they seem to have poorly implemented the clean-up routine, so you lose like ~15.5% space on /system:

http://xdaforums.com/galaxy-nexus/d...tyv-6-9-14-t2613655/post53527293#post53527293

P.P.S. That thread should be more suited for further discussion, tho has an obvious f2fs bias
[Samsung Galaxy Nexus] AgentSmith:
How does a battery increase the chance of a sudden power cut? Think UPS. My phone is never off despite the frequent power cuts where I live. You lost me here.