yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] dbh369:
Depends on the apps and data you run. In many cases, this difference won't matter. For some, it does. DirtyV without SR is working great for many. And some want the ability to make HD video. Again, it is personal preference. Try them all and see which one you like, it only takes like 30 secs to change kernels (no wipes are needed).
[Samsung Galaxy Nexus] osm0sis:
Oh hell yeah! Looks like you nailed it. Testing it with fscheck now. What are the steps to the method you used in the end? We had like 4 guys working on it at one point and couldn't get a functional compile. :o :D

Edit: [MENTION=2765426]styr[/MENTION] Total 100% success, by the way! :highfive:

Semi-unrelated but Chainfire made a really cool Bootanimation for root devices that displays the live dmesg output of the boot-up, pretty fun for anyone in at least their late 20's feeling nostalgic for their old 80386. Or anyone just wanting to geek out. Or wanting to troubleshoot, I suppose. :p

https://play.google.com/store/apps/details?id=eu.chainfire.livedmesg.lite

They chose to go all-or-nothing with it, since there are some commits ROMs require to add proper f2fs support. All-or-nothing is also easier for me to try and provide a unified ramdisk solution, rather than support multiple configurations (system-ext4, data/cache-f2fs; system/data/cache-f2fs; system/cache-ext4, data-f2fs; ...), which would be a scripting nightmare. :good:
[Samsung Galaxy Nexus] büscher:
baaam... installed :D :good:

edit: year... lol can't read anything, too fast, too small :D :D
[Samsung Galaxy Nexus] osm0sis:
Hahah yeah, you can increase the size if you spring for the paid version. :rolleyes: :p
[Samsung Galaxy Nexus] büscher:
saw that, but nah :p

otherwise.... I reboot my device that often..

edit: [MENTION=4544860]osm0sis[/MENTION]: is it this commit you mentioned for trim?

Because that one now is in my rom
[Samsung Galaxy Nexus] infectedorganism:
Has blocking RILJ had any impact on making or receiving phone calls?
[Samsung Galaxy Nexus] büscher:
I'm blocking it since months and the only impact I see is an improved battery life... no negative effects...
[Samsung Galaxy Nexus] qu4nd:
Is there a way to stop my launcher from getting killed all the time?
[Samsung Galaxy Nexus] osm0sis:
Nah, it's the vold f2fs one: https://github.com/LiquidSmooth/android_system_vold/commit/24e69beef9fbfcfbaa2744d56b136c10a464ba4b :good:
[Samsung Galaxy Nexus] cujo6801:
4.4.4 is out...

From what I'm hearing it's just security fixes....

Sent from the "DOG" pound
[Samsung Galaxy Nexus] a3361035:
ART spamming your logcat has nothing to do with fstrim.

Speaking of security fixes, someone should backport all those to linux 3.0.
[Samsung Galaxy Nexus] cujo6801:
Or not... Lol

Sent from the "DOG" pound
[Samsung Galaxy Nexus] styr:
Well, i worked with the source i used for twrp, basically omni tree+cm busybox branch merged on top and started to build from a clean environment (basically a fresh shell).

cd /path/to/source/
LDFLAGS="--static" make CROSS_COMPILE=/path/to/the/toolchain/arm-whatever- ARCH=arm

It hit a few bumps on the road, 1st it complained about some missing headers on omni`s prebuilt toolchains so i used one of my old linaro 4.7.3, 2nd it had a problem with selinux missing some headers so i`ve disabled it in . config, the same if nfs mount (i figured we aren`t gonna use those on recovery so it`s not worth wasting time on fixing them), 3rd is was missing a config entry for the default modules dir, added that, and lastly it had some minor syntax problems on ash shell i`ve fixed. That`s about it, i`m guessing it can be build safely on CM source too.
[Samsung Galaxy Nexus] gohamstergo:
this-^
[Samsung Galaxy Nexus] Droiderat:
[MENTION=4544860]osm0sis[/MENTION]

Please see the attached screenshot. I'm getting a Synapse error, which I believe is for the Fstrim checkbox. Kernel is: cwm-DirtyV-RSR-5.3.14-2-Synapsed. ROM is: cm-11-20140617-NIGHTLY-maguro.

FWIW, when I could last see the checkbox, Fstrim was selected (so hopefully, it still is). Synapse has been updated since then, so perhaps there is an incompatibility between the new Synapse code and the Synapse hooks built into the kernel.

Comments? Solutions?
[Samsung Galaxy Nexus] osm0sis:
/data/trimhelper must have gotten deleted or something. Reboot and if you still see that, delete the file yourself and reboot again.

Synapse updating will never result in breakage; it's developed extremely intelligently (ie. lots of forethought) to avoid having to break things later. I'm sure AndreiLux would only do that as a last resort, if there was no other way to fix a showstopper or add some really important functionality. Hasn't happened yet, anyway. ;)
[Samsung Galaxy Nexus] büscher:
hmm... but that one is in my rom since the 17th may:

https://github.com/CM11MOD/android_system_vold/commit/afb3cdb174f4086a04a518674eaeb3392dc966e6
[Samsung Galaxy Nexus] osm0sis:
Hmm I see.. well that was my only guess as to why the internal vold fstrim wouldn't be working for f2fs. No ideas now. :p :confused:

Will have to ask some ROM guys. [MENTION=2765426]styr[/MENTION] [MENTION=2633294]DHO[/MENTION] [MENTION=2838735]aosp[/MENTION] [MENTION=4015637]rkpeterson[/MENTION] ?
[Samsung Galaxy Nexus] osm0sis:
[MENTION=5109059]7175[/MENTION] Awesome info. Thanks! :)

This doesn't work?:

busybox mount -o remount,rw -t auto /system

(-t auto is usually assumed for remount, but maybe it'll help if it's made explicit.)

Unified ramdisk was good fun; still a couple kinks to work out, like somehow moving in the fstab on-the-fly breaks encryption. I've pored through the ramdisk and haven't come up with any obvious reason for it, so I imagine it's just some quirk of the bootchain. I've got ideas for workarounds, but I need [MENTION=4834554]Oehr[/MENTION] to check his PMs, try my test.img and get back to me before I can commit anything to GitHub. :cyclops:

---------- Post added at 08:45 AM ---------- Previous post was at 08:29 AM ----------

Oh also, everyone, not to be cocky or anything, but this is pretty ****ing cool ;):

http://xdaforums.com/showthread.php?p=53543397#post53543397

:cool: :D
[Samsung Galaxy Nexus] DR3W5K1:
Does anyone know what RILJ does?

I hope it's not the NSA'S backstage pass.
[Samsung Galaxy Nexus] osm0sis:
Well, RIL = Radio Interface Layer. Basically it's the software driver that mediates between the OS and the radio.img baseband firmware you flash. The wakelock is generally just keepawake for transmit/receive on mobile. Poor reception or rogue apps are generally responsible for excessive counts/time. Check out my Baseband thread and the BetterBatteryStats Knowledgebase for more info. :good:

---------- Post added at 09:42 AM ---------- Previous post was at 09:18 AM ----------

[MENTION=4834554]Oehr[/MENTION] check PMs again please, buddy. ;)
[Samsung Galaxy Nexus] pianistaPL:
[MENTION=4608636]bsmitty83[/MENTION]

I see that ZZMove is regulary updated, could you add new version to your kernel? http://xdaforums.com/galaxy-s3/development/info-cpu-governor-zzmoove-t2326544
[Samsung Galaxy Nexus] osm0sis:
Dat.

Also dis:

But then I decided to break it 5 more times just to make things interesting.. ;)

So partial victory there. Thanks [MENTION=4834554]Oehr[/MENTION] for all the help!

That should be good enough for now. Does anyone even know if encryption works on f2fs at all?
[Samsung Galaxy Nexus] Oehr:
youre very welcome and I also thank you for fixing it! :)

P.S. i do plan on switching to F2FS at some point, though not anytime soon... too much stuff going on lately...
[Samsung Galaxy Nexus] DR3W5K1:
Check the nexus 7 forums?
[Samsung Galaxy Nexus] osm0sis:
Yeah I'll have to look into it. I also found this:

mkfs.f2fs

---------

The mkfs.f2fs is for the use of formatting a partition as the f2fs filesystem,

which builds a basic on-disk layout.

The options consist of:

-l [label] : Give a volume label, up to 512 unicode name.

-a [0 or 1] : Split start location of each area for heap-based allocation.

1 is set by default, which performs this.

-o [int] : Set overprovision ratio in percent over volume size.

5 is set by default.

-s [int] : Set the number of segments per section.

1 is set by default.

-z [int] : Set the number of sections per zone.

1 is set by default.

-e [str] : Set basic extension list. e.g. "mp3,gif,mov"

-t [0 or 1] : Disable discard command or not.

1 is set by default, which conducts discard.​

I wonder what the TWRP format command is issuing for -t (if anything), and it'd be interesting to see if trying it at 0 or 1 has any effect on "not a typewriter." Haven't been able to find it in the TWRP source yet.

Edit: I also wonder if we could reduce the space lost to conversion by tweaking the format commands.. Hmm.
[Samsung Galaxy Nexus] pattyboi:):
how [MENTION=4544860]osm0sis[/MENTION] celebrates when he figures something out thats been a pain in his arse -> https://www.youtube.com/watch?v=_cZJLA_z2OU
[Samsung Galaxy Nexus] AbhishekS:
Okay so a slightly OT question.

I'm going on a holiday with friends for about a week, and I want good battery life. No gaming at all. Just Camera, Calls, WhatsApp, Facebook, Instagram, Messaging, etc.

Which kernel settings shall I tweak for that? Undervolting/underclocking, etc.? Which governor, etc.?

Thanks. :)

All this because we will be outdoors most times and a power source won't be available that easily.
[Samsung Galaxy Nexus] osm0sis:
Haha I'm not exactly ballin' outta control with my recovering broken leg (guess I could turn my limp into a mean pimp walk..), but I did finish some bourbon and take a nap. :laugh:
[Samsung Galaxy Nexus] paarthdesai:
you need a power bank , not kernel setting :P
[Samsung Galaxy Nexus] osm0sis:
Airplane mode saves the most but if you need calls turn off Wi-Fi, global sync off for accounts, conservative governor, lowest brightness. Nothing else will really matter.
[Samsung Galaxy Nexus] AbhishekS:
Underclocking and all that similar stuff doesn't help?

And which governor is the most suitable for this situation? Or is 'conservative' the name of a governor? :P
[Samsung Galaxy Nexus] osm0sis:
Uh it's the name. ;)

Yeah underclocking as much as you can handle would help too. 700 or 920 at the least. Min cpu and min screen on to 190.
[Samsung Galaxy Nexus] cujo6801:
If you have time you should pick up a spare battery..

That would do wonders for easing your worries

Sent from the "DOG" pound
[Samsung Galaxy Nexus] osm0sis:
New Unified version zip with my latest fixes (see the Git) is up in the usual place. Snack and trying to sleep like a normal person now. :p
[Samsung Galaxy Nexus] Rushead:
^^^ what he said. Airplane mode makes a huge difference, but if you need connectivity, get an extra battery & a universal wall charger.

Sent from a flashead cracker.
[Samsung Galaxy Nexus] Edgarngg:
Oh Nice! This kernel is awesome, I would like to see the fixes you did to it , would you please point me to the usual place where I can download this kernel? I'm new to your modified versions of this kernel. Thanks
[Samsung Galaxy Nexus] osm0sis:
Ramdisk changes are (currently) at the top here:

https://github.com/bsmitty83/DirtyV_tuna/commits/DirtyV-f2fs

Also this one which was missing from 6.15.14: https://github.com/bsmitty83/DirtyV_tuna/commit/441b7c24a02630052eccc7296b0cf0da6a4c0592

Download:

http://v.ht/osmod -- http://d-h.st/users/osm0sis/osmod/
[Samsung Galaxy Nexus] DR3W5K1:
You forgot the most important battery saver of all time

Location OFF.

BTW Very nice thinking on looking into the format configurations!

I can feel it the force is strong with you.

I know you'll get this sorted out in no time buddy.
[Samsung Galaxy Nexus] Edgarngg:
Sorry for the big quote. Can I add this script just in the end of my init.d file, after the other settings? And also using scripts for governor and other settings plus trickster just for voltages could create problems?
[Samsung Galaxy Nexus] osm0sis:
My hunch about the partition size differences appears to be correct. It doesn't forget to clean though, it requires it to clean:

https://kernel.googlesource.com/pub/scm/linux/kernel/git/jaegeuk/f2fs-tools/+/v1.2.0/man/mkfs.f2fs.8

We could reduce the percentage/ratio when formatting to reclaim the space, but we might not want to:

http://www.spinics.net/lists/linux-fsdevel/msg60824.html

On the other hand, system is the only one where this "lost" space really matters, and shouldn't require much cleaning, so for system we could theoretically lower it substantially since it's just getting formatted with each flash, then see what it'll do about the reserved sections.

One could also argue that's a lot of ****ing hassle for a partition that doesn't see much traffic and we should just go back to ext4 for system (and the same could be said for the even smaller cache), but everyone would have to agree, because we shouldn't need to support multiple configs in the Unified ramdisk.

Anyway, now you can see why Motorola only used it for the large partition (/data) on the X.

[MENTION=2838735]aosp[/MENTION] [MENTION=4608636]bsmitty83[/MENTION] [MENTION=4328678]metalspring[/MENTION] [MENTION=2633294]DHO[/MENTION] [MENTION=4015637]rkpeterson[/MENTION]
[Samsung Galaxy Nexus] 7175:
Yeah you can insert the voltage settings script in any mksh/lksh/sh, ash, bash, zsh, hush, wy60 or other current script shell script. If you also tinker around using trickster and performance control or synapse, that's totally fine most of the time. Those apps usually run their init scripts after init.d when the phones booted, so their voltages would overwrite those scripted. You can add a line like "sleep 180" before your scripts so they run about 3 mins after power is turned on / init triggered. Just make sure the sleep seconds is greater than boot time (aka when the process com.android.systemui appears in the process list "ps"): "until [[ -n $(pgrep -fl systemui) ]]; do sleep 5; done && (voltage_script) &"
[Samsung Galaxy Nexus] AbhishekS:
Damn! Again an OT question and in desperate need for answers.

A magnet just came close to my phone and since then the proximity sensor is broken. Any app when tries to use the proximity sensor, the phone just reboots.

Any way by which I can completely disable the proximity sensor as if it doesn't exist on my phone? Or if that's not possible then just disable the proximity sensor during calls so that I can at least make and receive calls.
[Samsung Galaxy Nexus] AbhishekS:
Done! Extracted the 'sensors.tuna.so' file from system/lib/hw, edited it using a Hex Editor and removed Proximity from it.

Now my phone behaves as if there is no hardware of Proximity Sensor in it.
[Samsung Galaxy Nexus] creeve4:
After flashing and opening Synapse:
[Samsung Galaxy Nexus] osm0sis:
View attachment 2810189

Works fine here. You're holding it wrong? :p

Clear Synapse app data, close it and swipe it away from Recents to kill the activity then open it again.

That or you flashed the wrong zip. ;)
[Samsung Galaxy Nexus] iluvamk:
Running like a BOSS.
[Samsung Galaxy Nexus] DR3W5K1:
@ the entire Smitty gang Ty everyone This is the first time I've ever experienced this kind of BL.
[Samsung Galaxy Nexus] oman0123:
I can vouch for the zero lemon 5900mah battery. I can go 2 days with lite to moderate use. Heavy use I'll be down to 30% by the end of the night. That's with like 8 hours of screen on time. Makes the phone a heffer though. Which I don't mind personally.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] -Jesco-:
just saw this . once other device is settled , ill try and push a f2fs build for tunas .
[Samsung Galaxy Nexus] Ziyan:
If anyone's interested, I made some progress (yes, everything still works) on updating our kernel with the latest features from the last pandaboard 3.0 kernel, which is way more up-to-date than the tuna kernel. It seems like Google didn't really care about us, I think they integrated tuna support at about Nov 2011, then forgot updating it, although there are many optimizations, bug fixes, etc :confused:

There are some interesting commits, like removing pvr & omaplfb from the kernel, and graphics things like that, I think those are to support more up-to-date graphics drivers, there are some notes about it... maybe someone who has more experience with tuna should check it out (as it requires ROM side modifications)?

Seeing that we're so outdated, now I'm thinking on aborting my progress with DirtyV kernel and restarting it on stock Google kernel, to make things easier, but then again if I complete it, there would be so much work on updating other parts to make it dirty... :confused:
[Samsung Galaxy Nexus] osm0sis:
[MENTION=2633638]Ziyan[/MENTION]

You might want to check out the 3.4 WIP thread. This separating the pvr out stuff sounds a lot like what they were trying to backport from Glass. :good:
[Samsung Galaxy Nexus] dbh369:
Finally had a long uptime, about 36 with two recharges, on [MENTION=4015637]rkpeterson[/MENTION] LS with smitty, and here's what i got

Guessing that means I'm not trimming...
[Samsung Galaxy Nexus] bsmitty83:
To all those that have the reboot issue (bootloop after pressing reboot ) are you using dynamic fsync ?

Hack the Tuna
[Samsung Galaxy Nexus] osm0sis:
I think it was more prevalent when I was using dyn_fsync, but I've also had it after a clean flash with dyn_fsync disabled, so no time for any corruption. :confused:

Is there any sense to my other suggested causes?
[Samsung Galaxy Nexus] poo706:
I have the reboot issue and have dynamic fsync turned off.

[poo]
[Samsung Galaxy Nexus] demlv:
No dynamic fsync since last clean reinstall. Bootloops still seem to come and go.
[Samsung Galaxy Nexus] Schneewitzchen:
don't using dyn fsync. dunno if it 's worth to think about, first time it happened to me was with your twrp recovery installed. usually i have cwm installed and no problems.

on bootloop i switched to bootloader and flashed cwm through fastboot and bootloop is gone, rom starts with no problem.
[Samsung Galaxy Nexus] ILA:
Nope, and I'm experiencing it from time to time (not always tough...)
[Samsung Galaxy Nexus] bsmitty83:
possibly , its really all I can think of , I can try bumping voltages or others can try setting them higher in trickster/synapse , I've been working on this note2 kernel , freaking mess . its like starting all over ( Linux 3.0.31). hell cm's fork didn't even have all the .gitignores in it .

I'll see about getting some new versions out sometime soon

Hack the Tuna
[Samsung Galaxy Nexus] bsmitty83:
OK so everyone that has these bootloops on reboot , are you using twrp recovery or clockwork mod recovery ?

maybe it is twrp that's messing with a reboot .

Hack the Tuna
[Samsung Galaxy Nexus] osm0sis:
It's too early in boot for a tweaking app or even init.d, definitely something else or will need to be adjusted in the source.. Oh and I meant "more" not "not", stupid autocorrect. ;)

Has happened to me with both recoveries. Recovery doesn't touch the kernel bootchain though.
[Samsung Galaxy Nexus] bsmitty83:
I see ..

more what ? , not not what ? idk what you were referring to

Edit I got it , didt see your edit

I don't think its voltage related , if it was , booting into recovery wouldn't do anything , it would still bootloop , same with it booting at all .

Hack the Tuna
[Samsung Galaxy Nexus] ILA:
TWRP
[Samsung Galaxy Nexus] creeve4:
Yes, I am
[Samsung Galaxy Nexus] DHO:
The ROM is f2f rdy, but we currently do not make any regular build with it enabled

We have a varient of that commit here: https://github.com/VanirAOSP/system_vold/commit/9e04b8e56b6151ea1d148062019a2abf70371753

I know some tuna users have found ways to get it working, but not sure who is building it for them
[Samsung Galaxy Nexus] osm0sis:
It doesn't happen when you boot the recovery from the bootloader, just from booted android, so I think it's still possible it could be a voltage it's running at when booted causing an issue. Not even booting the kernel from the bootloader fixes it when it's bad, you need to boot recovery then reboot to system from there. It's like the recovery's kernel booting up resets whatever's gone wrong, like a breaker.

Problem we're seeing is on a different ROM, custom LS from [MENTION=4015637]rkpeterson[/MENTION] using that commit as well, and the vold fstrim isn't working. There must be something else we're missing to get it working. :confused:
[Samsung Galaxy Nexus] Schneewitzchen:
it's strange though...during bootloop i couldn't get to start recovery (twrp installed) from bootloader...even flashing twrp via fastboot didn't worked out. only flashing of cwm helped

just my thoughts...i don't get why recovery could interfere the boot process.
[Samsung Galaxy Nexus] osm0sis:
That's interesting. I've never encountered that myself, just that "Start" from the bootloader continues the loop, and instead selecting Recovery or Power Off would fix it for me.
[Samsung Galaxy Nexus] bsmitty83:
but if that was the case the kernel would not boot at all , even at first boot it would just bootloop , booting to recovery then out doesn't change the voltages , it must reset something that is causing the system to hang ,maybe its something not being flushed from the console or sonthing to that affect , but I really don't think the voltages are the problem .

Hack the Tuna
[Samsung Galaxy Nexus] Rushead:
You need to boot into bootloader (hold all buttons, don't pull battery (unless you absolutely want to)) then choose recovery. Like [MENTION=4544860]osm0sis[/MENTION] said, rebooting from bootloader doesn't work. You have to reboot system from recovery.

BTW, I've had this issue using stock kernels, too.

Sent from a flashead cracker.
[Samsung Galaxy Nexus] osm0sis:
Yeah, you're right, I'm just spitballing. Got the wheels turning though. :D
[Samsung Galaxy Nexus] dbh369:
Nope
[Samsung Galaxy Nexus] imam.krismanto:
Wow impressive battery comsumption, what your rom?
[Samsung Galaxy Nexus] Droiderat:
No

---------- Post added at 11:38 AM ---------- Previous post was at 11:36 AM ----------

TWRP
[Samsung Galaxy Nexus] DR3W5K1:
Liquid
[Samsung Galaxy Nexus] Punkiderma:
Twrp here, dynamic fsync off usually

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] aditya.jazzmaster:
I use TWRP official & Dynamic FSync On.

I got bootloop
[Samsung Galaxy Nexus] dbh369:
Ditto
[Samsung Galaxy Nexus] büscher:
Bootloops back, twrp, dfsync off (f2fs)

back in the ext4 days on philz with dfsync of (also bootlooped a lot)
[Samsung Galaxy Nexus] Atento:
It seems to be something related to twrp.
[Samsung Galaxy Nexus] bsmitty83:
its not twrp related , recoveries don't interfere with the boot cycle in any way

I use twrp and I never once get a bootloop simply rebooting the phone .

Hack the Tuna
[Samsung Galaxy Nexus] demlv:
Cwm here, with boot loops.
[Samsung Galaxy Nexus] blmvxer:
I'll get a boot loader loop sometimes on a random reboot on ext4 or f2fs.
[Samsung Galaxy Nexus] dezful:
How to reproduce bootloop?

Gratefully, since I switched to newest DirtyV SR ramdisk, LS 6/18, ART, F2FS, I've never experienced bootloop.
[Samsung Galaxy Nexus] rajputrajat:
Second that.

On vanir f2fs version... Never experienced any such problems.
[Samsung Galaxy Nexus] chongns:
No bootloop

use TWRP-2.7.1.1-F2FS/EXT4-MAGURO from OP

use SmittyV-UR-NoMeM { 6/15 } from OP

use Dalvik

use Omni FML 05 Jun self converted F2FS

no use Xposed
[Samsung Galaxy Nexus] DHO:
You need a couple commits:

http://vaniraosp.goo.im/#/q/owner:"Dan+Trifan"+status:merged,n,z

Search f2f there,.. pulls up 3
[Samsung Galaxy Nexus] osm0sis:
e2fs one might not be in, I don't know. Maybe [MENTION=4015637]rkpeterson[/MENTION] can tell us, since I think it's in his personal fork.

DHO, have you verified the 24h uptime trim actually occurs though?
[Samsung Galaxy Nexus] Culex316:
Hey guys, just a quick question.

This F2FS Recovery won't touch my /efs or /factory partitions when converting my phone to F2FS, correct? Is it OK if they remain EXT4 or would it cause problems? I do not want to lose my IMEI lol.
[Samsung Galaxy Nexus] bsmitty83:
correct , efs is untouched , it will remain ext4 and be fine [emoji106]

Hack the Tuna
[Samsung Galaxy Nexus] ak:
If you want not loose your imei I want to suggest you to make a backup.

ak@n4