yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] PainFly23:
So to all you guys turning off fsync, is there a noticeable performance improvement outside of benchmarks? I've always just kept it on in fear of data loss (how does that work by the way, what kind of data loss are we talking about?) but I wouldn't mind turning it off if there's a noticeable difference.
[Samsung Galaxy Nexus] papatsonis:
Of course always on... Especially if you overclock.

Στάλθηκε από το Galaxy Nexus μου
[Samsung Galaxy Nexus] nikodr:
I tried to google it but did not find any answers,if somehow we managed to resize the system partition,by changing also the cache partition or data,would the kernels work ok?

I can understand that the fstab thing is compiled in the kernel?

Reason i am asking is that system partition on galaxy nexus is small nowdays,i guess on a 16 gigabyte model one could get 500 mbytes and give it to system,i thought i could find a way,but there is none for galaxy nexus but found way for some other devices.

I think the correct way would be to mount the partitions under linux and do it

the partitions needed to change are

size

System	mmcblk0p11	ext4	702464	System.img

Cache	mmcblk0p12	ext4	463872	Cache.img

userdata mmcblk0p13	ext4	15204352 Userdata.img

so wouldn't it be to our advantage to resize the small system partition?Has anyone ever done it ?

EDIT:here is link for galaxy s2 we need something like this to increase system partition

http://android.stackexchange.com/questions/79112/resize-system-partition-of-galaxy-s-2
[Samsung Galaxy Nexus] rambhanushali20:
Please tell me what settings you use... I got just 14880 with Zmod and r16.1
[Samsung Galaxy Nexus] sergialess:
I'm not a big fan of benchmarking apps, but it would be cool to know your settings (trickster or synapse). Thank you [MENTION=1124522]papatsonis[/MENTION].
[Samsung Galaxy Nexus] nikodr:
Just search for nephelim setting r6. I used it and got similar results
[Samsung Galaxy Nexus] Qwake:
Please can u check it? I am running on 16.1 and I got next random reboot. Thanks.
[Samsung Galaxy Nexus] bsmitty83:
Do you have zram enabled ?
[Samsung Galaxy Nexus] Qwake:
Yes, I use script .. I guess three pages back.

Edit : this http://xdaforums.com/showpost.php?p=60404323&postcount=1141
[Samsung Galaxy Nexus] bsmitty83:
That would be the cause then lol , zram causes random reboots , I haven't been able to pin down why , but I've always recommended it be disabled unless you can deal with the reboots . so if you turn zram off you should be OK .
[Samsung Galaxy Nexus] Qwake:
I noticed when u released first version of ur kernel R1. I used zram without reboots on firsts ziyan's cm12. But when I flashed for example R6 phone started to reboots on same rom and used same script for zram.
[Samsung Galaxy Nexus] trzesickipiotr:
I don't use ZRAM and with 16.1 I get reboots too.

Here's my last_kmsg log. A few lines at the end are:

EXT4-fs (mmcblk0p10): re-mounted. Opts: (null)
Emergency Remount complete
[MODEM_IF] xmm6260_off()
mgr_blank while GO is setDisabling non-boot CPUs ...
CPU1: shutdown
Restarting system with command ''.

View attachment last_kmsg.log

Maybe it's not related to the kernel, I don't know. I can PM you other logs from that time.

PT
[Samsung Galaxy Nexus] bsmitty83:
This looks like be a sys request from user space.

Application can write echo u > /proc/sysrq-trigger to trigger an

emergency remount. So it looks to me like it's ROM related , but thanks for the kmsg , i cant even guess whats wrong without it ;)
[Samsung Galaxy Nexus] Culex316:
Hey [MENTION=4608636]bsmitty83[/MENTION] I am using 14.1 with the latest Zmod ROM and my dmesg does not work. Whenever I enter "dmesg" in terminal emulator, I get a klogctl: function not implemented error. Could this be kernel header related?
[Samsung Galaxy Nexus] Scandy:
Well, there's no R3 in the downloads tab...

Just R1...
[Samsung Galaxy Nexus] rajputrajat:
it has been removed for now. until all the issues are resolved.
[Samsung Galaxy Nexus] CYoung234:
Can you do this from the File Manager in TWRP? When I looked, I could get to /system, but there was no lib directory, just bin. I looked at it before I installed the test kernel from Root Explorer, and it was there. There was a pvr module in the folder, so I removed it before I booted into recovery to install the kernel. The name on the pvr file was pvrsrvkm_sgx540_120.ko

But, the test kernel for CM12 still reboots at the google logo for me.

UPDATE: Sorry, brain cramp. I forgot that I had to mount /system.... At any rate, the were no pvr modules in /system/lib/modules.
[Samsung Galaxy Nexus] Heart1010:
Same here with R3* kernel... (FML) android starts but a few secs later it reboots.... so should we use R1 or your "old" beta3 kernel until this is fixed?
[Samsung Galaxy Nexus] alboz83:
With R3.1 and the last FML i have reboots very often, and everytime i see a strange glitch in gallery.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] JST99:
[MENTION=4608636]bsmitty83[/MENTION], Great work, works well with FML. I'm running the R1 stable version.

Would it be possible to add the larger RAM option as you did with Dirty V? IMHO diversity of options is always good, since every individual has different usage patterns.
[Samsung Galaxy Nexus] sodas43:
Right now kernel is not stable enough. After it become stable i think he can add that.
[Samsung Galaxy Nexus] Punkiderma:
Bought 3 fake batteries, tried to remove the antenna from the original one, nothing.

I just got used to the fact that I would never be able to use NFC again.

Thank you very much!
[Samsung Galaxy Nexus] osm0sis:
Like I said, switch scheduler to sioplus and it's stable. cfq is the reason for the reboots.
[Samsung Galaxy Nexus] Schneewitzchen:
+1 & it's faster then previous builds!
[Samsung Galaxy Nexus] Nephilim:
Dammit, guess I'll have to tweak sioplus tunables while waiting for row to get added back.
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4793042]pkgnex[/MENTION] already found statistically significantly improving tunables for sioplus. We had them on DirtyV and they were so good sioplus was made default. :)
[Samsung Galaxy Nexus] pkgnex:
Proven to be awesome... with statistical significance! There's actual math and science proving these settings are optimal... like what Osmosis, myself, and the rest of the Franco Dev Team did with the schedulers on that kernel. ;)

Not only are they the default on Dirty-V, but also Fancy and most every other kernel that has SioPlus.
[Samsung Galaxy Nexus] shadowam:
Hey mr. pkgnex, not sure if I understand correctly: The default values for sioplus on FA R3 are already the one you guys tweaked back in Dirty-V thread? If not, could you please post them? Thank you!
[Samsung Galaxy Nexus] cujo6801:
There the same...

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Nephilim:
Well then, guess I'll try the new kernel with my settings along with sioplus until row comes back. Got nothing going on when I get off work and don't have to get up anytime in particular tomorrow.
[Samsung Galaxy Nexus] jguerdat:
Fwiw, ROW is available for me. Why me and not others?
[Samsung Galaxy Nexus] cujo6801:
Its there just borked...

Sent from the "DOG" pound
[Samsung Galaxy Nexus] jguerdat:
Define "borked". It seems to be working but I frankly have no idea what any of these do.

Edit: While I'm at it, I'm just using Neph's settings because it appears I should. Wrong to do so?
[Samsung Galaxy Nexus] massoudsh:
TouchControl supported in this kernel?!
[Samsung Galaxy Nexus] bsmitty83:
no , I had printk disabled on that build , thats why dmesg does not work . I was working on something locally and forgot to re-enable it in my config file . not sure how many builds it slipped in , but the latest bulid has it enabled .
[Samsung Galaxy Nexus] Culex316:
Oh no wonder. Thanks for the heads up. I went ahead and flashed the latest build and now I have it again woot!
[Samsung Galaxy Nexus] bsmitty83:
Op updated with R17 in the downloads

- removed some unnecessary governors and io-schedulers

- added touchboost and cpuboost

- switched to xz kernel compression

- switched back to GPADC multi-function driver now that it is fixed

- added a no debugging version to cut down on kernel size and maybe a little better cpu performance

- enabled -Ofast math makefile flags

- hopefully fixed Zram , has been stable on my toro , but its not my primary device anymore so I havent tested zram under a normal use .

if I forgot anything , check my commit history on github for the whole run down

Sorry for not being around the site more , lifes been pretty busy for me . between my wife and 4 year old daughter and 1 year old son , plus that thing called work , I've been pretty tied up .

Enjoy and as always let me know how they work for you
[Samsung Galaxy Nexus] eternal70:
No debugging version works very good here with zmod. Is there still any possibilities for 3.4 interactive to be added ?
[Samsung Galaxy Nexus] PainFly23:
Updated from R14 to the nodebug version and my first impression is that performance is fantastic, the best it's been in a long time it seems. Now to see how long-term performance is...
[Samsung Galaxy Nexus] PainFly23:
Well shoot. I wonder if R17 could have broken Bluetooth audio, assuming that's even possible. Songs now play almost exactly 30 seconds (give or take a few) before they become a choppy mess and playback almost completely stops. It was working fine earlier today, and the phone speaker isn't affected by this issue. It's not a problem with my headphones because they seem to work with a different device. It also happens regardless of file format, bitrate, or music player.

I'll get a chance to test this more in depth and with more Bluetooth devices tomorrow, but I was just wondering if anybody knows anything about this or is able to recreate it.
[Samsung Galaxy Nexus] bsmitty83:
Interactive is synced to 3.4 plus a few more

https://github.com/bsmitty83/Kernel...c10a761#diff-1febeaefccfabc82e4dedda8958ef769
[Samsung Galaxy Nexus] rambhanushali20:
Tried no debug version with zmod latest and it gave me a Bootloop

---------- Post added at 12:10 PM ---------- Previous post was at 12:02 PM ----------

Edit:Flashed again and it worked...

I think something went wrong last time...
[Samsung Galaxy Nexus] akhi24nick:
R17 no debug version is magic :D with latest zMOD :D

Blazing Performance :)
[Samsung Galaxy Nexus] bamtan2:
Before I test the new version, I want to record my experience with the previous version: I added it to ZMOD and the increased performance from overclocking seems to just-about make up for the increased burden of lollipop on the ol' galaxy nexus. I imagine f2fs might help further.

I tested dyninteractive with 1650mhz and 80c temperature limit, and it seemed to benchmark (antutu, geekbench) well and perform well to the eye. I did not crash until I touched the zmod control :P in Kernel Adiutor.

I also used the interactive governor with manually tweaked options: I set the middle (high) speed to 1200mhz and top speed at 99% to 1650mhz. I also set the middle (high) speed back to default 920mhz and didn't notice it acting much slower, because under load it always kicked up to 1650mhz anyway. These are good governors. It seems from the frequency log that dyninteractive basically did what my manually tweaked interactive did.

The minimal free RAM is a problem for Galaxy Nexus. Every MB counts. Installing poorly designed software will hog too much. Startup applications and unused services will cause a person trouble. The low-memory-killer settings are interesting, but I'm not sure they can fix this problem. I wish I could disable every app and service I didn't need, but I'm not sure what they all do, so I leave them be. All that said, the memory situation seems as good as it can be, just because Android 5.1.1 seems to do a good job of managing it. I had no serious problems, and only a few rare app crashes which could have been caused by anything.

Screen on time with *very* minimal use was 4 hours with the original battery, which is quite impressive. I need to do more battery testing. So far I'm pleasantly surprised. Because Galaxy Nexus wifi and display BOTH seem to consume battery life more than the processor does, the key to making this device last is having wifi turned off as much as possible (when screen is off at least) and reducing the screen brightness to a minimum (including using dark themes). I wonder if the "adaptive brightness" feature makes a difference.

Overall my impression of ZMOD + overclocked full_auto kernel is positive. Galaxy nexus with ZMOD 5.1.1 seems to perform like a modern medium-low end phone like moto g. There are bugs and performance hiccups (and the OLED still looks like a mess ;)) but overall I think the developer community deserves a hearty congratulations!!! :D
[Samsung Galaxy Nexus] bamtan2:
I don't remember if your default settings changed, or if mine did ;) I noticed TCP: cubic -> westwood, and IO: zen -> sioplus. Anyone want to talk about the merits of these? :)
[Samsung Galaxy Nexus] Punkiderma:
After a day of usage, I can say that also on zmod r17 works great. Is blazing fast! However, enabling zram still causes reboots for me...
[Samsung Galaxy Nexus] bsmitty83:
How are you setting it ? I've found that if I set it from within trickstermod app , it works OK , but synapse will cause a reboot if you change the reserved space . again more than likely it (zram) is still messed up no matter what and because I don't use my nexus as a daily driver it doesn't reboot for me , but I've had uptimes of a few days with zram on , albeit the phone is just sitting there .

So I'd still disable it if you can't deal with random reboots , it won't provide that much of a difference in terms of usability anyways IMO .
[Samsung Galaxy Nexus] wavedashdoc:
Trickster Mod works for me. Be reboots, except for setting the max to 1652. Getting 1880's with antu. Nice work.
[Samsung Galaxy Nexus] bsmitty83:
I changed them , sioplus is a great scheduler , but I was using zen and decided to make it the default lol , i removed bfq and never build cfq as they are meant for spinning disk storage (HDD's) . noop is also a good choice for flash memory .

about ZEN

ZEN:

Based on the VR Scheduler. It's an FCFS (First come, first serve) based algorithm. It's not strictly FIFO. It does not do any sorting. It uses deadlines for fairness, and treats synchronous requests with priority over asynchronous ones. Other than that, pretty much the same as no-op.

Benefits:

- Well rounded IO Scheduler

- Very efficient IO Scheduler

- More stable than VR, more polished

- Quite battery friendly

- Great at light and medium multitasking workloads

TCP westwood is a good , balanced congestion control Algo. Most non-stock kernels set westwood and agree it performs the best , I really dont see a huge difference between tcp controllers , but I like to mess around and have been using westwood for some years now .

But by all means feel free to set what you want , I encourage it actually , I just set the defaults to what I use .

ps : heres a link to IO scheduler descriptions http://androidmodguide.blogspot.com/p/io-schedulers.html
[Samsung Galaxy Nexus] Punkiderma:
Using trickster, it was stable then I received a call and the phone rebooted
[Samsung Galaxy Nexus] Djalaal:
I have lag over time on f2fs. Will adding these mounting options help me? How can I do his? I'm using ZMod now btw.
[Samsung Galaxy Nexus] siealex:
Can't start this kernel on ZMOD. After flashing it tries to boot, then reboots and sticks at google logo. WTF?
[Samsung Galaxy Nexus] GilGameshn1:
Try to flash it again and boot to recovery once . My friends maguro seems ok . Thanks [MENTION=4608636]bsmitty83[/MENTION]
[Samsung Galaxy Nexus] siealex:
No, stuck at Google logo.

PS, LuckyK works, but it doesn't have custom MPU voltages, only IVA.
[Samsung Galaxy Nexus] cartman333:
Same thing happens with me. Flashing Zmod 5/16 and after i flash R17 it never gets past the google logo.

Edit: Can someone give me a link to R16 please? I would like to test it maybe it boots up with that :D
[Samsung Galaxy Nexus] bsmitty83:
Not sure what you guys are doing , but I'm runnng Zmod 5/16 , on a toro no less with R17 . Booted up on first flash . the kernel works
[Samsung Galaxy Nexus] massoudsh:
[MENTION=4608636]bsmitty83[/MENTION], i test both variant of r17 with clean flash, with debug it stay on google logo but no debug work fine for me.
[Samsung Galaxy Nexus] bsmitty83:
Here's R17 regular , again booted first time for me
[Samsung Galaxy Nexus] BfstMtn:
On maguro too. ZMod 5/16. Won't boot past Google logo.

Edit: nodebug boots fine.
[Samsung Galaxy Nexus] siealex:
Does it have in Trickster mod:

1) custom MPU voltages;

2) color settings;

3) Hotplug governor;

4) ZRAM;

5) temperature limit settings?

PS, what does it mean "no debug"? No ADB? No dmesg or logcat?
[Samsung Galaxy Nexus] BfstMtn:
There are two R17 kernels in downloads. One is "no-debug". No to all those questions. Also, TricksterMod doesn't apply any of those settings until it fully boots and the "grace period" expires (1 min, default). On my maguro, the regular kernel won't boot past Google logo. Tried to boot again into recovery -- someone recommended it in thread -- still won't boot. The no-debug kernel boots fine.
[Samsung Galaxy Nexus] bsmitty83:
1) yes

2) yes

3) no

4) yes

5) yes

no debugging version has some of the debugging options turned off , adb still works , logcat works as its ROM side now in Lollipop , no dmesg
[Samsung Galaxy Nexus] jcpowell:
Are you telling me it's plausible to flash and run maguros Zmod on my Toro? If so I'm game!
[Samsung Galaxy Nexus] bsmitty83:
Yes , if you remove the device check from the top of the updater script in the zip package , and you won't have cell service . my toro isn't activated anymore so it works fine for me
[Samsung Galaxy Nexus] zzpianoman:
I think GPS might not work either...
[Samsung Galaxy Nexus] bsmitty83:
R18 is up in the downloads section

- added "Zeneractive" cpu governor

an interactive-based governor

This governor provides full CPU hotplugging support

based on CPU load per CPU.

It also provides CPU hotplugging of CPU 1-X on

suspend/wake.

- added fstab replacement to anykernel installer , f2fs support , with my mount flags

( nobarrier , inline_data , discard ) for f2fs

this should allow you to run any rom f2fs on /data and /cache as long as you flash the kernel after you install a rom that does not have built in f2fs support

- enjoy , I tested on Zmod 5/16 , so hopefully they work for everyone
[Samsung Galaxy Nexus] bamtan2:
I've read the descriptions, but since I'm no expert, who better to trust than the kernel developer?!?! :) Since I haven't seen any substantive difference between the governors in my googling research, I assume there IS no difference. So only stability matters, and that means going with whatever is most popular and well-tested. I would like a miracle fix of course... but sometimes "it just works" IS a miracle ;) So I would need to hear a good argument to change from whatever YOU argue is the best default.

The no-debug version was working for me, but to test your bug I flashed the normal version. I got the same bug. Stuck at google logo with previous zmod version. I have since flashed non-debug back on to make things work again ;)
[Samsung Galaxy Nexus] musical_chairs:
Would you like a toro build of Zmod? I had one working a while ago (4G and everything, IIRC), I've thought about trying it again to see if CM is really worth it. If there's a reasonable amount of interest, I can push out a build. I can do toroplus too, if anybody cares.
[Samsung Galaxy Nexus] Merio90:
Bootloop

Anyone else experiencing a bootloop with nodebug r18? I flashed the latest Zmod 5/18, using F2FS /cache & /data and also using xposed. Hopefully xposed isn't the culprit, otherwise I would have to use the stock Zmod kernel which isn't bad although I could sure use OC frequencies to get the extra performance. Similar results anyone?
[Samsung Galaxy Nexus] trzesickipiotr:
Hi

Both regular and nodebug R18 versions don't boot on CM12.1 for me. It's getting stuck at CM bootanimation.

PT
[Samsung Galaxy Nexus] rambhanushali20:
Both R18 dont work with Zmod...
[Samsung Galaxy Nexus] sergialess:
Both r18 work flawlessly here with ZMod. Zeneractive is great!

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] Schneewitzchen:
[MENTION=4608636]bsmitty83[/MENTION]

got a lot of this in logcat. I'm on ZMoD (05/18) with R18_nodebug.

05-18 13:48:29.317: E/Tuna PowerHAL(678): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
05-18 13:48:29.327: E/Tuna PowerHAL(678): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
05-18 13:48:29.327: E/Tuna PowerHAL(678): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
05-18 13:48:29.337: E/Tuna PowerHAL(678): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
05-18 13:48:29.337: E/Tuna PowerHAL(678): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
05-18 13:48:29.346: E/Tuna PowerHAL(678): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
05-18 13:48:29.346: E/Tuna PowerHAL(678): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
05-18 13:48:29.364: E/Tuna PowerHAL(678): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
05-18 13:48:29.364: E/Tuna PowerHAL(678): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
[Samsung Galaxy Nexus] akhi24nick:
R18 no debug with zMOD latest is blazing.

Zeneractive is way too good :D
[Samsung Galaxy Nexus] bsmitty83:
I wonder if its the VLYOOM chip bug that is affecting some people . I'll add the patch that's supposed to fix it but I've never had a problem with it until now .
[Samsung Galaxy Nexus] eternal70:
Well after some test, here's my review about the new 'zeneractive' governor.

Provide smooth UI, but with some little stutter (and i tolerate it for 4 years old device). Good game performance, good at battery too. Overall this is a great balance for performance and battery.

But some cons, is lagging when turning on the screen. I think its because hotplugging.

Here's my screenshot, nearly half of the time is playing dream league soccer, and the rest is light-to-medium usage with line, path, tapatalk, etc.
[Samsung Galaxy Nexus] eternal70:
Maybe OT, but, really zeneractive is already a governor for tuna in the past ?-_-(In JB 4.1.x era) Im not up-to-date tho. Yeah, 'old but gold'

Btw, [MENTION=4608636]bsmitty83[/MENTION] Maybe you could explain why you choose zeneractive than ZenX (new version of zeneractive) ?
[Samsung Galaxy Nexus] bsmitty83:
It was just a governor I found and tried out , I did see zenX and some others , I'll probably test them out at some point .

I'm not sure if zeneractive was ever used on tuna , the source I pulled it from was a quad core , so I had to remove 2 of the core hotplugging options .

If your experiencing slow wake ups , try raising the max screen off freq . I usually run it at 1200mhz
[Samsung Galaxy Nexus] eternal70:
Thanks. I'll try it. Btw these are source for ZenKernel for tuna. There's also a thread in xda for that.

https://github.com/AndroidDeveloperAlliance/ZenKernel_TUNA

http://xdaforums.com/galaxy-nexus/development/kernel-ada-4-1-4-2-v3-0-58-zenseries-t2072787
[Samsung Galaxy Nexus] akhi24nick:
Enabling CAB, and rebooting the phone seems to make the phone unstable on boot, that it immediately reboots.

So after initial boot and one more reboot, it settles down.

Using zMOD with R18 no debug. [MENTION=4608636]bsmitty83[/MENTION]
[Samsung Galaxy Nexus] siealex:
Switching CAB on or off with screen off causes an immediate reboot. It's a known ? since Android 4.3.
[Samsung Galaxy Nexus] venni:
R18-NoDebug gets stuck on the ZMod 5/16 boot animation. R18 with debug gets stuck on the Google logo. My maguro has the VLYOOM chip. Flashed back to the ZMod stock kernel and everything is fine again.