yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Piti8576:
With r49 the only app that is in cache is Nova Launcher.

WhatsApp, Threema, Facebook and more restarts all time, in app overview "App Restart".

Is this normal? With r45 does nothing restart and the cache is full.

But when the apps always restart is there more battery drain?

Sorry, my english is not so very good :(
[Samsung Galaxy Nexus] boype:
How much RAM does Nova consume?

Try to disable the launcher whitelist: http://xdaforums.com/showpost.php?p=42537078&postcount=2341
[Samsung Galaxy Nexus] Piti8576:
They have 24 MB in Cache.
[Samsung Galaxy Nexus] boype:
What are your minfree values? Stock? Check them like this:

cat /sys/module/lowmemorykiller/parameters/minfree
[Samsung Galaxy Nexus] Piti8576:
12288, 15360, 18432, 21504, 24576, 30720
[Samsung Galaxy Nexus] infectedorganism:
After following the steps a few posts above and booting the system, I lost access to my internal storage. It appeared to be just a file, not a folder. I could access the internal storage via TWRP and I had a nandroid available so no issue there.

Next, I tried a clean flash with r49 but multiple apps would force close when trying to open them.

I'm thinking its an issue with the rom I am using: Slimbean 4.2.2 build 8.

I'll keep trying.
[Samsung Galaxy Nexus] boype:
That is _way_ too high. Do you apply any custom settings? If yes, remove them.
[Samsung Galaxy Nexus] Piti8576:
I have not change them and have no app to change them.

edit:

OK new test with your settings.

I have make a init script with the values 3072,4096,6144,7680,9216,14436 and test it.
[Samsung Galaxy Nexus] siealex:
What are these values in Trickster?
[Samsung Galaxy Nexus] tepar:
those value * 4 / 1024 ( 3072*4/1024=12)
[Samsung Galaxy Nexus] siealex:
What must I do if the custom ROM already has a CUSTOM kernel (maybe franco) built in?

---------- Post added at 04:40 PM ---------- Previous post was at 04:35 PM ----------

12? doesn't the device lock up with such low values? R43..R45 freezes with foreground<32 and empty<64.
[Samsung Galaxy Nexus] alfiemenace:
*pls delete
[Samsung Galaxy Nexus] SirOch:
Hi,

I tested the r49 and i have too many applications that restart.

I did a fresh install of carbon ROM and the kernel.

So I revert back to r45 and no problem.

May be the freemen parameters are not optimum for carbon.

Cheers

Envoyé de mon Galaxy Nexus en utilisant Tapatalk
[Samsung Galaxy Nexus] tepar:
it's the default value for r49 and it's working fine for me, flashed it 5 hours ago and not a single problem encountered...:) :good:
[Samsung Galaxy Nexus] infectedorganism:
r49 isn't working for me. I'm not sure what the issue is, but after flashing r49 on two different, clean installs of 4.2.2 roms, I completely lost access to my internal storage. I can access the files from within TWRP, but when using a file manager within the roms, its inaccessible.

I've also tried 'dirty' flashing the kernel, but the same issue arises.

For now, I just flashed the zimage from r49, and will continue to use the ramdisk from r36.
[Samsung Galaxy Nexus] Alkemix:
same thing as I have shown in the example .. with very clean installation you will never have problems by anykernel RAMdisks

Are You sure that You do not have root access problems? Do You use supersu or superuser ?
[Samsung Galaxy Nexus] JoSch68:
R49 with standard Minfree values and Vanir Rom does not work properly. Many applications are restarting so I revert back to R45...
[Samsung Galaxy Nexus] infectedorganism:
Superuser.

On a clean flash, file managers force close upon opening because it can't access the internal storage. Also, the Play Store force closes *shrugs*, not sure why.

On a 'dirty' flash, I can open the file manager, but I can see that the 'sdcard' appears to be a file, and not a folder.
[Samsung Galaxy Nexus] siealex:
I do not know the ramdisk of the builtin kernel, is it stock or not. Can this cause problems?
[Samsung Galaxy Nexus] Alkemix:
Try doing a "repair permissions" from recovery and if you do not solve do a full wipe (factory reset and wipe system) and re-install rom, google apps and kernel (be careful that the factory reset you lose all your data, then save it all before ... if you do not have a previous Nandroid)

Nope
[Samsung Galaxy Nexus] infectedorganism:
Thanks for the assistance.

I have done a full wipe and tried two different roms, both bringing about the same issues. I will now try to fix permissions to see if that helps.
[Samsung Galaxy Nexus] siealex:
Does the access restore if you dirty flash r43 (or r44..r45 for 4.4) without wiping?
[Samsung Galaxy Nexus] Alkemix:
Into TWRP recovery .. "Advanced" menu voice and after "Fix Permissions"
[Samsung Galaxy Nexus] Ashtrix:
r49 working great wtih Slim v4.0 with a dirty flash over Mpo (AnyKernel) , on 1420MHz max & 384Mhz min with Uv, and I can see only 56% of RAM full that's great boype...

Edit : Blazinn Faaast & Thanks !!
[Samsung Galaxy Nexus] mpokwsths:
Very nice and smooth kernel. One problem, the 192Mhz isn't used at all although it is set in Trickster. 384 is the lowest. OVERDRIVE Milestone 1 ROM and Fancy kernel rel 2.
[Samsung Galaxy Nexus] lippol94:
R: [KERNEL][4.2.x] Fancy Kernel (Rel. #2) (JAN-26-2013)

When my phone sleeps like a baby as it does with this kernel I don't give a sh*t if it doesn't use 192mhz.

Please remember that 192mhz step is used only when screen is off. But when screen is off phone goes immediately in deep sleep and this couldn't be more perfect then it is :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] dab_penyo:
Will try, downloading now.......

Btw this kernel PGM supported?
[Samsung Galaxy Nexus] Hawkw1nd:
Yes, PGM is supported.
[Samsung Galaxy Nexus] gwindlord:
BTW, the lowest frequency is a real minimum for both screen on and off, right?.. And the max one is different for on and off.

But the OP says

But the min screen on is just the min freq in Trickster, which is correct for both on and off. But the screen on minimum seems to be 384. Could someone please comment on that?..

Also I cannot find file, which is declared in the OP:

there are just gpu_clock and gpu_oc files.

I don't really give a darn, don't asking smth to be changed, that's all just out of curiosity :)
[Samsung Galaxy Nexus] boype:
In fact I cannot... The tweaks I find worth using are already implemented.

The lowest frequency (scaling_min_freq) is the lowest frequency that will be used be used both for screen off and on, given the case that screen_on_min_freq is equal to it. By default, however, I set screen_on_min_freq to 384 MHz. This results in the lowest used frequency with screen on is 384 MHz, while the lowest screen off frequency remains 192 MHz. I implemented this feature to improve responsiveness in UI interaction. If you don't want this, do 'echo 192000 > /sys/devices/system/cpu/cpu0/cpufreq/screen_on_min_freq'. You cannot do this in Trickster MOD.

Thanks for pointing this out, it's a mistake I made. Will correct the OP.
[Samsung Galaxy Nexus] gwindlord:
boype, it's a really interesting approach, thank you! You're the best ;)
[Samsung Galaxy Nexus] kpyhere:
Does anybody have problems with random freezes and reboots ?:silly:
[Samsung Galaxy Nexus] lippol94:
None here :)

Been running it for a few hours (without considering night time) and everything is going really well!

No reboots, no freezes, no SODs.

Left everything as it comes but BLX (set back to 100) and ROW as scheduler.

That's it.
[Samsung Galaxy Nexus] gwindlord:
2.5 days with 1st and then 2nd version, no freezes/sods/reboots/slowdowns :) Everything left as it was (except adaptive brightness :D)
[Samsung Galaxy Nexus] ak:
Re: [KERNEL][4.2.x] Fancy Kernel (Rel. #2) (JAN-26-2013)

This is a cool features ... But when you listen mp3 with 192 min freq at screen off all work good?

Can you add my reference to Op if you cherry picking my work please?

Xda with AK Kernel inside ;)
[Samsung Galaxy Nexus] -Jesco-:
what is the default colour setting for this kernel ?
[Samsung Galaxy Nexus] boype:
Yes it works good, of course depending on the load the mp3 player is causing combined with the governor's scaling settings.

[EDIT] I may just have realized what you actually meant by your question. Screen-off is not locked to 192 MHz, but allows scaling from 192 - 537 MHz.

Sure thing, sorry I did not add you yet.

contrast -6

gamma 0

gam r -4

gam g 0

gam b 5

mult r 177

mult g 181

mult b 200
[Samsung Galaxy Nexus] jesssiii:
Re: [KERNEL][4.2.x] Fancy Kernel (Rel. #2) (JAN-26-2013)

This is upsetting to me, as I use Trickster and expected setting the min screen on to 192 was doing just that. Must have not read the op right :'( I'll give the initd script a go.

~JeSSie~
[Samsung Galaxy Nexus] albsat:
Re: [KERNEL][4.2.x] Fancy Kernel (Rel. #2) (JAN-26-2013)

Since setting the minimum frequency at 384, I haven't faced a block. The kernel is really smooth and I am very interested to find out its battery life with my usage.
[Samsung Galaxy Nexus] lost_:
Twice in 20h with #2. First time screen wouldn't turn on, with led blinking. Second time screen froze during browser scroll.

Not complaining, and just reporting. Going to clean up some newer apps I just installed to isolate external factors.
[Samsung Galaxy Nexus] boype:
I guess trying to set the lowest frequency to 384 would be a good idea in your case. Also, I believe you could profit from the next release, since you could try custom voltage to stabilize.

That said: New release coming tomorrow. As discussed earlier, there will be two different versions, one "standard" version and one "extended" version. Extended is exactly like standard, but with three additional features: Sound controls (HQ sound and volume boost), custom voltage and Fsync control. With tomorrow's release #3, everything I wanted is included in the standard version, and all additional requests from this thread will be included in the extended version. As of tomorrow, I will only release updates when kernel upstream patches or major breakthrough features are released.
[Samsung Galaxy Nexus] boype:
New release

Had everything ready for release, so here it is.

Changelog Rel. #2 >> Rel. #3:

introducing two different versions: 'Standard' and 'Extended'. Extended is almost exactly like Standard, with the following three additional features: custom voltage control, fsync control, and sound control (high performance sound and volume boost)

added custom voltage to Extendend version

removed sound control from Standard version

removed fsync control form Standard version

defaulted BLX to 100 again (users should decide whether they want use it or not)

announcement: The kernel is now where I wanted it. From now on, only kernel upstream patches and breakthrough developments will be considered for future releases. This will not be a kernel where no bit is left un-modded.

Best regards
[Samsung Galaxy Nexus] lost_:
I think you hit the sweet spot.
[Samsung Galaxy Nexus] joliv:
Re: [KERNEL][4.2.x] Fancy Kernel (Rel. #3) (JAN-27-2013)

OK...so many good sayings, I'll go for it
[Samsung Galaxy Nexus] Alkemix:
"Hyper" governor into next releases of Fancy kernel

Hi, Boype, Could You include in the next releases of fancy kernel "hyper" governor? I'd be curious to try it into fancy kernel :)
[Samsung Galaxy Nexus] gwindlord:
Noticed that on r14 PGM does not start automatically on boot, though tick is set and it worked on r13. Could anyone please confirm?..
[Samsung Galaxy Nexus] motorazrv3:
Can't confirm. Pgm working at boot with r14 exp.

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] iferlive:
I use PGM and works like a charm, I have had no issues with r14
[Samsung Galaxy Nexus] bolanrox:
What is PGM exactly? I tried to google it and did not get anything non technical. thanks!
[Samsung Galaxy Nexus] motorazrv3:
http://xdaforums.com/showthread.php?t=1721895

swyped with my galaxy nexus on purity rom with fancy kernel
[Samsung Galaxy Nexus] gwindlord:
Thank you all, it might be probably PGM issue on my env.
[Samsung Galaxy Nexus] kraleksandr:
How to enable zram? When I turn it ON in the trickstermod app, then apply settings, on next launch trickstermod app says that zram is OFF.

How to check if zram works?
[Samsung Galaxy Nexus] motorazrv3:
Are you using the extended kernel version? Only ext. Supports zram.

swyped with my galaxy nexus on purity rom with fancy kernel
[Samsung Galaxy Nexus] kraleksandr:
I use this now: fancy_kernel-tuna-4.2-r14-ext
[Samsung Galaxy Nexus] Riekr:
With cm10.1 it works ok by configuring it in performance settings but I have no experiences with zram and other ROMs. If you are using CyanogenMod or a derivative try enabling it in performance settings, I don't know if there could be conflicts with trickster.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] ak:
For check you can try to launch:

adb shell or terminal shell

and then wrote command:

free
[Samsung Galaxy Nexus] kraleksandr:
It means that zram is off, right?
[Samsung Galaxy Nexus] kraleksandr:
I use paranoid rom now (AOSP-based). Looks like I have to talk with the paranoid devs team...
[Samsung Galaxy Nexus] gwindlord:
Are there stock performance settings in PA?.. Zram is usually revealed there too, and the tick "Set on boot" is also present, maybe that approach would help.

Some kernels have command line tool zram (maybe lean or someone else), but not sure fancy does.
[Samsung Galaxy Nexus] Riekr:
How can I set Google stock display settings via a shell script? Which proc values have to be modified?

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] boype:
#!/system/bin/sh

echo "0" > /sys/devices/platform/omapdss/manager0/gamma
echo "0 0 0" > /sys/class/misc/colorcontrol/v1_offset
echo "2000000000 2000000000 2000000000" > /sys/class/misc/colorcontrol/multiplier
echo "0" > /sys/module/panel_s6e8aa0/parameters/contrast
echo "1" > /sys/class/backlight/s6e8aa0/acl_set
[Samsung Galaxy Nexus] Rufufu:
r15 incoming !
[Samsung Galaxy Nexus] boype:
r15 up

That's correct, sir ;)

Change log:

updated Linux to version 3.0.73

pulled in a few patches from TI's omapzoom repo (save a little battery; make the UI smoother)

Tweaked smartreflex for less voltage for lower CPU frequencies (will save a little battery)

various memory and scheduler optimizations

bcmdhd: Enable Ad-Hoc (IBSS) mode (from CM 10.1 upstream)

Best regards
[Samsung Galaxy Nexus] Delvien:
Does anyone else have troubles using bluetooth keyboards when using fancy kernel? It pairs, but it never connects to be able to use.
[Samsung Galaxy Nexus] boype:
Are you sure there are no custom minfree settings applied from anywhere?

You can test like this:

cat /sys/module/lowmemorykiller/parameters/minfree

If the result is not 3072,4096,6144,7680,9216,14436 , something overwrites your minfree.
[Samsung Galaxy Nexus] boype:
Since the update of the lowmemorykiller, the values you used to set earlier do not translate anymore! If think I might have to mention this somewhere in the OP so that this is clear to everyone
[Samsung Galaxy Nexus] Piti8576:
With the new values there are all ok.

I have make me a init.d script with:

#!/system/bin/sh

echo N > /sys/module/mmc_core/parameters/crc;

chmod 664 /sys/module/lowmemorykiller/parameters/minfree
echo "3072,4096,6144,7680,9216,14436" > /sys/module/lowmemorykiller/parameters/minfree
[Samsung Galaxy Nexus] ashclepdia:
I believe some ROMs(like vanir) throw some custom minfrees settings in the middle of some init(d?) scripts, which might be what happened(those values look familiar) and him adding a new initd with new values that runs later may have remedied it.
[Samsung Galaxy Nexus] infectedorganism:
Fixing permissions did not solve the issues of not being able to access the internal storage.

Yes. Flashing a previous version of the kernel fixed the issue; I regained access to the internal storage and everything worked as expected.
[Samsung Galaxy Nexus] swedkg:
So, for those of us who came from r48, r45 etc, and don't have any idea what ramdisk is, what it does, and where it belongs, is it safe to just flash r49 on top of the latest kernels or do we have to dirty flash before?

Can we revert the original kernel that came with our rom or their no point in doing that?
[Samsung Galaxy Nexus] zofox:
i'm also using vanir and lastest kernel version.

my minfree are exactly theese: 3072,4096,6144,7680,9216,14436

anyway i see lots of applications restart, and also launcher can't be kept in memory... so every time I open an app and then i press home it restarts ...
[Samsung Galaxy Nexus] tepar:
I did a dirty flash r49 over r48 and everything is working fine. I just wiped cache and dalvik cache before and after flashing r49.

I'm on latest Vania.
[Samsung Galaxy Nexus] Ashtrix:
Did u check the init.d folder for any scripts ?

[MENTION=4615478]boype[/MENTION] those two scripts u had in the zip, they do get executed at first boot and the LMK one gets executed at everybootup right ?? & i cant find those scripts inder sys/etc/init.d folder....

Thanks !!
[Samsung Galaxy Nexus] infectedorganism:
The fancyinit scripts should be in the /sbin folder.
[Samsung Galaxy Nexus] motorazrv3:
R49 working as aspected on crdroid 10.

I was on r48 before. I dirty flashed the rom again, flashed fancy r49 and wiped dalvik and cache.

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] zofox:
in my init.d there are:

0000kernelassimilat

00firsties

09cron

98sonic_shock

99vanir

what i've to check exactly? o.o

EDIT: under /sbin i'e found two scripts fancyinit1 and fancyinit2 . in the lastone i can see rhe minfree mentioned above :D
[Samsung Galaxy Nexus] boype:
Check all of them... Look out for minfree ;) and then delete those line(s)
[Samsung Galaxy Nexus] ashclepdia:
[MENTION=2769673]zofox[/MENTION] can u do me a favor?

I'm curios and lazy and don't want to download entire ROM zip for vanir just to see this lol,

Can u put all those files from init.d there in a zip and upload for me to grab? I wanna take a peak at em.

And also, if u have a file located in /sdcard called "vanir.cfg" if you could toss that in as well ;)

I'd just like to see what those are actually setting.

And [MENTION=3358582]Ashtrix[/MENTION] I believe the one script in the zip is only used once when you install and does something along the lines of extracting ramdisk from original boot.img and then packing it with the new kernel (zimage) but I believe this new anykernel2.0 thing does it in a different way than it used to be for better compatibility (I'm not sure on specifics as I haven't researched it yet, but I had assumed it was something like bringing over original modules and other such things that the previous type of anykernel did not do...don't quote me on that as fact though lol...I'm sure a quick search of [MENTION=1143630]osmosis[/MENTION]'s posts will turn up a very detailed explanation of what it does if you are interested... He usually explains everything VERY well even for 'nontechnical' users to understand at least somewhat)
[Samsung Galaxy Nexus] JoSch68:
so, i install my rom (Vanir nightly041014), gapps and now the R49 a second time with wipe system, cache and dalvik....

my minfree are exactly the values from R49: 3072,4096,6144,7680,9216,14436

In trickster: 12,16,24,30,36,56

By the way - anyway many of applications restart, also the launcher can't be keep in memory...

so every time I open an app and go back to home the launcher restarts ...
[Samsung Galaxy Nexus] zofox:
Nothing found ...i guess that everything is ok, right? :D

Here u are

https://app.box.com/s/qx16hllxmdmtce0wc7mf

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] ashclepdia:
Is everyone who is having app killing issues using greenify or something similar?

Also, name your ROM being used please
[Samsung Galaxy Nexus] zofox:
This is exactly what is happening to me :D everything seems to work but apps can't stay in memory they get killed constantly :P

Yep using greenify :P and I'm currently using latest vanir nightly :D

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] infectedorganism:
Is there any relationship between the ramdisk and the minfree values?

I know I've beaten this to death (last post of these) and granted I'm on an older ram disk, but these settings are "perfect". Since using them, not a single app has been killed, apps remain in cache, multitasking is great, etc.

As an aside, I too am using Greenify.
[Samsung Galaxy Nexus] zofox:
[MENTION=4207125]ashclepdia[/MENTION] here u are vanir.cfg :D

https://app.box.com/s/nchrvlkyfpf7jhg8zud6

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] ashclepdia:
I looked at the scripts from vanir, no minfree being applied, I also looked at the scripts related to vanir(I delete most scripts like this... I use vanir but the commotio build by DHO... I've had a habit of deleting most all of init.d scripts along with vanir stuff from xbin lol..I don't find that they do any miracles for anything in my usage so I just get rid of them along with other things like cb runhaveged and other entropy stuffz...I just don't see a point to them except draining my battery or using resources for no reason that I don't need)

And I looked at the things in xbin for vanir(they were in my commotio zip) I didn't see anything related to minfree. The only thing I did find was in build.prop (check yours, it might have lines referring to minfree especially if you've previously used performance control app included within vanir which I also delete from system apps) and that was oom score adj for home app =1...I don't know if that could be affecting anything but you could try deleting that line from build.prop if u want and see if anything changes.

And I'll hold judgement towards my thought of greenify being related until other users who report app restarts tell us whether they use it or similar.(I've never used apps like greenify. ... either my usage doesn't justify it or I see no point due to my usage... And add into that I seem to see more people who report issues with things tend to be using it. I've always had the mindset of "let the OS manage that stuff, and if an app misbehaves THAT badly that I need ANOTHER app just to stop it from doing something, I'll put in feedback/bug report to devs and just uninstall that app for now, it doesn't deserve to be on my device if it cannot behave itself lol)

Sorry I'm rambling..

(And damn, I need to change my signature...I use Tapatalk so much I don't see it often and it just makes my posts take up even MORE space then they already do due to long rambles like this hahaha sorry guys)

---------- Post added at 12:36 PM ---------- Previous post was at 12:33 PM ----------

Okay, I see nothing here either related to minfree.

Take a looksie in your build.prop(/system/build.prop) and see if anything related to OOM or minfree is in there(I think it usually gets placed at bottom of the build.prop)
[Samsung Galaxy Nexus] zofox:
Checked also on build.prop nothing interesting found .... I agree with u by saying that yes, there might be something stored in build prop because I remember that when I used to use supercharger script by zeppellinrox it also tweaked build. prop :D

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] siealex:
Are you using Trickster? Latest builds of Trickster apply minfree values every time on boot. Disable boot settings, reboot and enable them again.
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4615478]boype[/MENTION] question: what was the issue with my newer mkbootimg/unpackbootimg? They have more support for ramdisk address, and dtb, etc. which should make them more universal for device.

Great to see adoption though! Thanks! :)
[Samsung Galaxy Nexus] Alkemix:
I, for example with the new updates (mkbootimg/unpackbootimg) have issues.... instead if I use your original files no problems. Never had any problems with the "old" files... in fact I left my ramdisk built with your original files because the boot.img with the new was not created properly (for me) ...
[Samsung Galaxy Nexus] SoftWord:
Not good for me too the r49.... Lag and killing all with different kind of minfree values

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] siealex:
It kills everything... it works way better with much lower values :-O e. g. 2,4,6,8,12,16.