yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] pvkiniyan95:
yes rk's f2fs build booted and i only tried converting ur ls build, i m going to try vanir and let u know the results

update : [MENTION=3927368]poo706[/MENTION] just flashed vanir 28/6 nightly right away and my /system was reformatted to ext4 and so ended up at bootscreen (not stuck at google logo but further)

then converted it with ur script using latest dirtyV 28/6 ursr and u got it man, the script ****in works...

got vanir working so LS u compiled has an issue, i think u have to look into it....
[Samsung Galaxy Nexus] poo706:
Glad you got vanir going and that my script worked! Now let's see what we can figure out about my LS build. First off, maguro, toro, or toroplus? Second, how do you think system got reformatted back to ext4?

[poo]
[Samsung Galaxy Nexus] pvkiniyan95:
maguro..

vanir without converting reformats my system to ext4 which is due to their updater script right, but it atleast gets to boot animation

regarding the coverted LS system is in f2fs yet couldnt get past google logo

tell me what else can i do to assist

i think u should contact rkp coz afaik i havent seen anyone running the latest unofficial build in f2fs, if anyone successfully did pls post
[Samsung Galaxy Nexus] poo706:
I can't speculate as to what's happening here. This person was able to convert and install my 6/24 LS, and I have to assume they're on maguro since they're in spain: http://xdaforums.com/showpost.php?p=53759478&postcount=63 . Later they said that they had to install it twice before it cooperated: http://xdaforums.com/showpost.php?p=53791301&postcount=75 .

I'm inclined to just say to hell with it and recommend that you try the 6/30 that should be posted in a few hours.

[poo]
[Samsung Galaxy Nexus] pvkiniyan95:
i replied him too...lets confirm him if it works cause he was bragging about some permission error...

whatever, i'll test 30/6 however planning to stick with vanir for awhile, but always ready for testing:p:p
[Samsung Galaxy Nexus] sergialess:
In the tool thread I'm confirming that:

- My phone is Maguro.

- All partitions are F2FS (EXT4_to_F2FS_gnex_2014-06-25.zip)

- ROM is LS 6/24 compiled by Poo (LS-KK-v3.1-UNOFFICIAL-2014-06-24-maguro.zip)

- Gapps: PA Micro Modular.

- Kernel: Latest DirtyV.

The tool converted the rom ok. The first time I flashed it, I've got an error (can't remember what error, sorry). Before giving up things and starting over, I decided to give it a chance, and try flashing a second time the rom, which worked successfully. It's all I can say.

If you need more info please let me know. And yes, I'm from Spain ;)
[Samsung Galaxy Nexus] Edgarngg:
The last 30/6 changelog says f2fs support was added. Does it mean we don't need to convert it anymore?
[Samsung Galaxy Nexus] sergialess:
AFAIK, /system is being formatted and mounted as EXT4.
[Samsung Galaxy Nexus] poo706:
I'm not exactly sure what these f2fs commits are doing for us, but no, it's still an EXT4 build that needs to be converted in the usual way.

[poo]
[Samsung Galaxy Nexus] sergialess:
Dirty flashed 30/6, F2FS converted, over 24/6.

Working great so far. Thanks.
[Samsung Galaxy Nexus] poo706:
OP updated for 6/30, all 3 variants.

[poo]
[Samsung Galaxy Nexus] Edgarngg:
for me it didnt boot, stuck at google logo with no bootloop. Converted then dirty flashed it. i'm going to try again.

by the way i get a warning in the conversion tool that says it dint find some files, at the end it says is comlpeted but it doesnt say everything went ok like the last build. what could be wrong?

edit: yeah thats weird, i had to flash it a second time and flash no additional dirtyv kernel. now ill reboot and flash the latest and then it should be good.

2nd edit: nevermind. its stuck at the bootanimation. now i dont know what to do :P
[Samsung Galaxy Nexus] poo706:
Where is the folder located, any spaces in the path? Any other zips in the folder?
[Samsung Galaxy Nexus] Edgarngg:
allright, yeah there was a space in the path, sorry, i did read the first time, and i successfully converted the last build. its just that after that i moved the folder somewhere else. ill give it a try again. thanks man
[Samsung Galaxy Nexus] poo706:
You aren't the first, no biggie. I'm going to see about a rev 2 that works around the path issue.

[poo]
[Samsung Galaxy Nexus] HONG86:
Is the cm theme engine still old one:confused:
[Samsung Galaxy Nexus] poo706:
I believe so.

[poo]
[Samsung Galaxy Nexus] poo706:
See my edit.

[poo]
[Samsung Galaxy Nexus] madhavs:
yes will check in to that xposed module

Thank you

---------- Post added at 09:17 AM ---------- Previous post was at 08:49 AM ----------

neither working for me and its problem with skype latest version not with LS

I downloaded v4.9.0.45564 and its working great without need of any xposed module :D
[Samsung Galaxy Nexus] Culex316:
Just one question, how do I add or remove the tiles from the pull down menu? I've been looking through all the menus and can't find anything. Thanks in advance for the help m
[Samsung Galaxy Nexus] kansasboy001:
I though of a much simpler way to get the same effect. If you could remove the dependency that the nav bar toggle custom qs tile has for slim pie to be enabled so that the qs tile functions just as the toggle in settings, then both pa and slim pies would work flawlessly. Sense both pies will not enable from bottom if the nav bar is showing. This would give the user full flexibility to choose what ever pie they want and have the same effect.

I believe that this should be a simple as removing a few lines of code.
[Samsung Galaxy Nexus] flip360:
Thanks for the wonderful ROM, the tweaks you add really make a difference for the GNex!
[Samsung Galaxy Nexus] poo706:
Man, I don't know. I've been blindly looking through what I believe is the right section of the code, but I just can't find it. I think you're right that it's a simple matter of removing a few lines, but I have no idea where that one key file is. If we ever manage to find it, I'll be happy to do what you want, but until then I think it's a lost cause.

[poo]
[Samsung Galaxy Nexus] poo706:
Settings -> LiquidSmooth -> Notifications -> Notification Drawer -> Tiles and layout.

[poo]
[Samsung Galaxy Nexus] kansasboy001:
I found two sets of code that I think that might be behind what requires slim pie to be enabled to disable nav bar.

here are the two files that I could find that relate to navigation bar enable/ disable and pie.

https://github.com/LiquidSmooth/android_packages_apps_Settings/blob/66002f3df86342f5fed36f717c6177adccecc629/src/com/android/settings/liquid/PieControl.java

lines 88 to 92 and possibly lines 171 to 177

https://github.com/LiquidSmooth/android_packages_apps_Settings/blob/66002f3df86342f5fed36f717c6177adccecc629/src/com/android/settings/liquid/NavigationSettings.java

lines 174 to 179
[Samsung Galaxy Nexus] randommmm:
Do you mean you want the Quick Setting tile shortcut toggle navbar work without enable SLIM pie? well, I know where the code is. In fact, I build my own LQ with that tweak. Here is the code:

https://github.com/0rt/android_frameworks_base/commit/dcd189fc804e944805b54d2b4998532bf11472b1
[Samsung Galaxy Nexus] kansasboy001:
Yes that is exactly what I want! Thank you!

[MENTION=3927368]poo706[/MENTION] could you please take a look at this?
[Samsung Galaxy Nexus] randommmm:
*edit*

Ok, you read you original post, you want to toggle PA pie instead of SLIM PIE, right? Same file, line 155

else if (action.equals(ButtonsConstants.ACTION_PIE)) {
boolean pieState = isPieEnabled(context);
if (pieState && !isNavBarEnabled(context) && isNavBarDefault(context)) {
Toast.makeText(context,
com.android.internal.R.string.disable_pie_navigation_error,
Toast.LENGTH_LONG).show();
return;
}
Settings.System.putIntForUser(
context.getContentResolver(),
Settings.System.PIE_CONTROLS,
pieState ? 0 : 1, UserHandle.USER_CURRENT);
return;
}

This is the part should be modified. First part is boolean check of did you hide navbar when you want to disable PIE, it can be commented, should change "Settings.System.PIE_CONTROLS" to pa pie corresponded one, and I think it's Settings.System.PA_PIE_CONTROLS
[Samsung Galaxy Nexus] kansasboy001:
Is it possible to just completely remove the pie enable check, so that it would work with both pie versions?
[Samsung Galaxy Nexus] randommmm:
comment the check code block will skip PIE check, as I did in toggle navbar.

Though they may look alike, SLIM PIE and PA PIE are completely different feature in the view of code, The shortcut now is added for toggling SLIM pie, so it check and toogle SLIM PIE. The above code just hard code the switch from SLIM PIE to PA PIE.

It's better to add another shortcut for PA pie, 2 shortcuts for 2 features.
[Samsung Galaxy Nexus] poo706:
[MENTION=3447871]randommmm[/MENTION], [MENTION=5625510]kansasboy001[/MENTION]: Nice work guys! This is exactly the sort of assistance I need for feature requests. It looks like you two were suggesting a few different options. What did you ultimately want me to do, just comment out the lines like is shown here?

[poo]
[Samsung Galaxy Nexus] kansasboy001:
Yes I think that is what [MENTION=3447871]randommmm[/MENTION] suggested.
[Samsung Galaxy Nexus] poo706:
Easy peasy, look for a new build tomorrow.

[poo]
[Samsung Galaxy Nexus] kansasboy001:
I think that it would be a good decision to include dirty v 9-28 in your ROM. Dirty v 9-28 is more stable and offers better performance then fancy in my opinion.
[Samsung Galaxy Nexus] poo706:
If it proves to be free of problems like SODs and random reboots, I'll consider it. But it's been quite a while since dirtyv has been as trouble free as Fancy is. I'd rather lean towards stability.

[poo]
[Samsung Galaxy Nexus] poo706:
9/30 added to the OP.

- Fancy is back to r54

- The nav bar can now be disabled without having to enable PIE (special thanks to [MENTION=3447871]randommmm[/MENTION] and [MENTION=5625510]kansasboy001[/MENTION])

[poo]
[Samsung Galaxy Nexus] pianistaPL:
May I ask what's wrong with r57? :)
[Samsung Galaxy Nexus] poo706:
I had some people reporting that their phones were running hotter than normal on 57 and/or that the battery drain was higher. Personally I didn't have any heat issues, but I did notice the increased battery drain. I felt that that was enough reason to go back to 54.

[poo]
[Samsung Galaxy Nexus] fauner:
I don't know yet if it's a placebo effect but last version is the fastest version ever. Also for me r54 is the kernel for unofficial that runs better
[Samsung Galaxy Nexus] Nautilus74:
referring my experience with various kernel tested on your Liquid:

Fancy54: not perfectly stable: at least once every 48 hours I can find my GNEX freezed and I have to remove the battery.

Fancy57: perfectly stable and the fastest among those tested (on Interactive), but it drain more battery among all i've tested.

DirtyV-Ak2-Pre_Final: perfectly stable and fast (nearly) as fast as the Fancy , draining battery less quickly (on Hyper)
[Samsung Galaxy Nexus] poo706:
Interesting, thanks for the report. I've never once had these freezes you describe with r54. Since dirtyv is AK, what ramdisk did you pair it with?

[poo]
[Samsung Galaxy Nexus] Nautilus74:
it is the DirtyV (bigmem) that you find on the official page:

http://xdaforums.com/galaxy-nexus/development/kernel-dirtyv-6-9-14-t2613655

and it use AnyKernel2 ramdisk edited by Osm0sis:

http://xdaforums.com/showthread.php?t=2670512
[Samsung Galaxy Nexus] poo706:
I'm a bit confused. Walk me through the process of how you installed my ROM and DirtyV.

[poo]
[Samsung Galaxy Nexus] pianistaPL:
Official build by smitty is an AnyKernel format so it can't be integrated into ROM .zip but version by osm0sis has a ramdisk so it can be replaced in .zip file. Hovewer, both version can be installed in recovery :)
[Samsung Galaxy Nexus] Nautilus74:
I added the second link (AK2) only because you asked me what kind of ramdisk was inserted,

but i've only flashed the zip file taken in Dirty thread......

If you want , I've created the boot.img from DirtyV-Ak2-Pre_Final, so you can swap it on your rom!

I just tried, and a fresh install works perfectly... :)

---------- Post added at 09:36 PM ---------- Previous post was at 09:29 PM ----------

why?

as you can see above , I've "extract" the boot.img (not directly...)
[Samsung Galaxy Nexus] pianistaPL:
Hmm, i didn't know that in kernel without ramdisk (AnyKernel) exists .img file :P
[MENTION=3927368]poo706[/MENTION] What do You think about JustArchi Optimizations? http://xdaforums.com/showthread.php?t=2754997
[Samsung Galaxy Nexus] poo706:
Boom, that's what I was after, thanks for making the boot.img! I'll install it and run it for some time and see how it goes.

[poo]
[Samsung Galaxy Nexus] poo706:
Funny you should bring that up. LS just committed this yesterday: https://github.com/LiquidSmooth/android_build/commit/193804df155909a131387b6d19676206cf76aa83. I undid all of the optimizations from metalsping that I had done, resynced to pull in the commit, and made a new LS unofficial just for me today to test it out. Seems to be pretty good, I wouldn't say it's really any better or any worse than what I had done. But I really had no idea what I was doing when I implemented MS's optimizations, I'm really surprised that it worked at all. I'll be sticking with JustArchi's from now on since it's part of the official source code and I know it was implemented properly.

[poo]
[Samsung Galaxy Nexus] pianistaPL:
Haha, good time ;P

I'm waiting for new build then :) BTW which toolchain Liquid uses with this optimizations? SaberMod?
[Samsung Galaxy Nexus] poo706:
I used the same Linaro 4.8 toolchain that I got from metalspring that I've been using. I'm not really up on toolchains, do you have good reason to believe I should switch to SM?

[poo]
[Samsung Galaxy Nexus] pianistaPL:
Hmm, I don't know, I just have read on the JustArchi Optimizations thread that some people had some graphic glitches in Play Store with Linaro 4.8. SaberMod 4.8.4 works 100% perfectly (as I remember from that thread). And here You have a helpful link https://docs.google.com/document/d/1C-ehLWl6XcStOmB30QHDA_DOdceXiGIyzXT_0eIg5nQ/mobilebasic?pli=1 it's from this thread http://xdaforums.com/google-nexus-5/development/rom-optipurity-t2875143 Cl3Kener says SM is even better than Linaro.
[Samsung Galaxy Nexus] poo706:
Worth a shot!

[poo]
[Samsung Galaxy Nexus] thelegbra:
i wish this didn't have the theme manager. i just clean installed it and themes is running with a 50 mbs of ram in use :(
[Samsung Galaxy Nexus] madhavs:
After you install theme reboot the device then theme only uses about 2-3MB of RAM

Give a try!!
[Samsung Galaxy Nexus] sagara.sandaru:
And I saw somewhere on G+ that Lens Blur force close and Skype video call issue also related to linaro optimizations.
[Samsung Galaxy Nexus] pa.pn2:
That's true. Saw it in n5 forum too..
[Samsung Galaxy Nexus] poo706:
I'm not sure what lens blur even is. And is this issue specific to linaro, like switching to sm would fix it?

[poo]
[Samsung Galaxy Nexus] pianistaPL:
I believe lens blur is a feature in Google Camera (from playstore) but as I know (in Nexus 5) It doesn't work on SaberMod too but You have to check, maybe it'sonly Nexus 5 problem. If You can, compile ROM with SaberMod 4.8.4 and we will test it :) One is sure - SaberMod works very good with JustArchi optimizations.
[Samsung Galaxy Nexus] poo706:
Yeah I'm going to make a 4.8-sm build for myself this afternoon and see how it behaves.

[poo]
[Samsung Galaxy Nexus] pianistaPL:
Thanks to your latest build i don't think about downgrade to 4.3 anymore ? This ROM is definitely one of the fastest 4.4 ROMs so far :)
[Samsung Galaxy Nexus] pianistaPL:
[MENTION=3927368]poo706[/MENTION] And how SaberMod build is working? :)
[Samsung Galaxy Nexus] mono28aug:
Lol meant to comment here but did on tool thread . my bad anyways awesome ROM very fast and nice features but i have a question how do I disable the direction arrows that appear on nav bar when keyboard is active
[Samsung Galaxy Nexus] poo706:
Pretty good! If all goes well you'll be able to find out for yourself later today.

[poo]
[Samsung Galaxy Nexus] pianistaPL:
Cool! I'm charging my phone then :)
[Samsung Galaxy Nexus] poo706:
Saw that, I assumed it was meant for here. As far as the direction arrows, Settings - Language & input - Advanced options - Volume key cursor control - change from disabled to one of the other options.

[poo]
[Samsung Galaxy Nexus] mono28aug:
Ahh that did it thanks :)
[Samsung Galaxy Nexus] wkr.mky:
Can't wait. I love this ROM! Just converted to full F2FS and I'm simply amazed. So glad I got a GNex, every month I find something else that brings new life to this phone. Many thanks to poo and other devs involed! :victory:

Quick question because I see it on bsmitty83's DirtyV and MWisBest's FML. Why not gcc/linaro 4.9? I know MWisBest had the same issue with corrupted Play Store images, but I don't know what fixed it. I don't want to add more work, just curious because I'm waiting on a few linux distros to release updates before I get my hands dirty and start breaking roms. :p
[Samsung Galaxy Nexus] poo706:
I just haven't experimented much with alternate toolchains is all. Early on, someone (can't remember who) convinced me to test out some crazily-tweaked toolchain and the ROM built, but it caused the camera to FC. When I started using metalspring's optimizations, I figured it was best to use the same toolchain he did, which was linaro 4.8. Now that I'm using JustArchi's optimizations, which are now part of the official LS source, I'm using 4.8 sabermod, which is what the official LS source uses. I might try making a linaro 4.9 build next week for myself to see how it behaves, just for S's and G's. The toolchain used on the kernel is irrelevant since I include 3rd party kernels with my unofficial gnex ROMs.

[poo]
[Samsung Galaxy Nexus] pianistaPL:
Hmm... [MENTION=3927368]poo706[/MENTION] If I have all partitions formated with f2fs, do I have to convert this ROM with Your tool? Of course I know that unofficial build is unified but is it ready for /system f2fs?
[Samsung Galaxy Nexus] büscher:
No conversion needed, you are good to go
[Samsung Galaxy Nexus] poo706:
10/4 added to the OP.

- Switched optimizations from metalspring to optimizations from JustArchi

- Switched toolchain from 4.8 Linaro to 4.8 Sabermod

- Switched kernel from Fancy r54 to DirtyV Pre-Final

A few notes regarding the 9/30 -> 10/4 DeltaJen:

- It's about 31 MB because of the toolchain switch

- It will NOT touch the kernel. For some reason the DeltaJen creation failed due to the switch to DirtyV, so I had to exclude the kernel from this DeltaJen. If you're on 9/30 with Fancy r54 and want to go to 10/4 with DirtyV, either install the full ROM or use the DeltaJen and follow that up with the attached DirtyV flashable ZIP.

Special thanks to [MENTION=4758810]Nautilus74[/MENTION] for creating the boot.img to allow me to include DirtyV with my ROM: http://xdaforums.com/showpost.php?p=55799653&postcount=608

[poo]
[Samsung Galaxy Nexus] Punkiderma:
Is normal that using deltajen the ROM version inside setting remains the one of the full flash? I still have 9-16 written in there,but I have updated with every deltjen that came out,up to today's 10-4

Thanks!
[Samsung Galaxy Nexus] poo706:
When installing the deltajen, do you happen to notice any files being skipped because they are "missing or modified", particularly Settings.apk or build.prop?

[poo]
[Samsung Galaxy Nexus] GorfDroid:
Is it possible to get high performance sound with dirty?

Fancy kernel doesn't seem to be playing nice with this update.
[Samsung Galaxy Nexus] pianistaPL:
High performance is buggy, better use Viper4Android ;)
[Samsung Galaxy Nexus] GorfDroid:
Thanks

Does that viper app work with all audio or certain apps only?

I use rockbox for android
[Samsung Galaxy Nexus] pianistaPL:
It should work but I can't tell you in 100%.
[Samsung Galaxy Nexus] mono28aug:
Can I flash 30mb deltajen over the normal version to update to the latest one ? Or do I need to flash the latest ROM than deltajen zip and then dirty v..a bit confused here [MENTION=3927368]poo706[/MENTION]

---------- Post added at 02:36 PM ---------- Previous post was at 02:35 PM ----------

Use viper and then turn on high performance sound with tickstr mod and see the magic
[Samsung Galaxy Nexus] Punkiderma:
Now that you say this, build.prop get skipped because Nexuslouder, which I use,modify it by adding some lines.

Do you think I should flash the entire ROM,or it doesn't matter?
[Samsung Galaxy Nexus] GorfDroid:
There is no high performance sound with the dirtyv kernel
[Samsung Galaxy Nexus] josera06:
Any problem if i install fancy kernel with the last build? I think its more battery friendly than dirty...

Enviado desde mi Galaxy Nexus
[Samsung Galaxy Nexus] poo706:
When you say "normal version", are you referring to the official LS? If so, no, you cannot use deltajens to go between official and unofficial.

[poo]
[Samsung Galaxy Nexus] poo706:
It probably doesn't matter, but to be on the safe side, I would stick with the full ROM zip. Either that, or back up your build.prop prior to modifying it so that you can restore it before installing the deltajen. Either way, you'll need to reinstall nexuslouder after the upgrade of course.

[poo]
[Samsung Galaxy Nexus] poo706:
Go for it!

[poo]
[Samsung Galaxy Nexus] mono28aug:
No not official I am using your unofficial release from 9th. And to update to latest 10th do I need to download the 10th unofficial ROM or the deltajan zip and flash it
[Samsung Galaxy Nexus] poo706:
Your questions are difficult to understand. If you're on the unofficial 9/30 build and want to update to the unofficial 10/4 build, you can use either the full ROM zip or the deltajen. If you use the full ROM zip, you'll have the included dirtyv kernel. If you use the deltajen, you'll still have whatever kernel you're currently using on 9/30.

In general, you can only use a deltajen under the right conditions, but you can always use the full rom zip.

[poo]
[Samsung Galaxy Nexus] mono28aug:
Lol I am sorry bro :P I will try to make myself more clear from next time :) and thanks I have my answer I will just flash deltajan now .
[Samsung Galaxy Nexus] mono28aug:
So this is what happened, I flashed deltajan over 9/30 build and my back button stopped working :/ anyway I dirty flashed the 9/30 build again hoping that it would fix the problem but it still dint fix it, so I wiped completely and freshly installed 9/30 build with pa gapps modular and its working fine now .
[Samsung Galaxy Nexus] poo706:
That's a new one to me. I really don't think it has anything to do with the 10/4 build, but I can't explain it.

[poo]
[Samsung Galaxy Nexus] mono28aug:
Well I am downloading the full ROM now will flash it and see how it goes .
[Samsung Galaxy Nexus] GorfDroid:
My wallpaper keeps resetting upon reboot. Does anyone know how to fix this?
[Samsung Galaxy Nexus] x3m.zone:
I have the same problem. Also, sometimes after applying wallpaper, lockscreen background not changing.
[Samsung Galaxy Nexus] GorfDroid:
My lock screen is working fine but sometimes the image gets distorted.
[Samsung Galaxy Nexus] ahmadairfan:
Anyone tried latest version? I wonder how's SM compared to Linaro... Cheers!

(still on latest Omnimetal lol)
[Samsung Galaxy Nexus] marcomesa:
Love your ROM, cmopared with the official one it seems has better battery duration. I'm testing anyway. I've a question, cyanogen in the last build add a new reverse look up server called "pagine bianche", useful for italian user (since now they can't use this feature), I wonder if it will be added to this rom too...
[Samsung Galaxy Nexus] TheMan0790:
Latest version is fast and working very well.
[Samsung Galaxy Nexus] poo706:
I've noticed this too, for a while now. It doesn't concern me because I use Wallpaper Changer to randomize my wallpaper every 30 minutes and at boot, so the default LS wallpaper gets replaced as soon as Wallpaper Changer starts. I have no idea what's causing this, or even whether it's LS in general or something I've done with my unofficial builds.

[poo]
[Samsung Galaxy Nexus] poo706:
Couldn't you just install this: https://play.google.com/store/apps/details?id=it.seatpg.paginebianche&hl=en ?

[poo]