yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] boype:
Can you tell me why? I'm not 100% sure if this does not have any downsides... And why did TI in their OMAP repo and also Google with the gnex kernel set it if it is not needed?

Ah okay. Thanks
[Samsung Galaxy Nexus] pianistaPL:
[MENTION=4615478]boype[/MENTION]

What do you think about change toolchain to Linaro 4.7/4.8 or optimized Linaro 4.7 by [MENTION=4328678]metalspring[/MENTION]?
[Samsung Galaxy Nexus] osm0sis:
Keep the man from hunting around.. ;)

http://xdaforums.com/showpost.php?p=50326989&postcount=3271

Basically he compiled a toolchain specifically optimized for our device architecture; cortex a9, neon, etc, etc. :good:
[Samsung Galaxy Nexus] aosp:
omap: common: add kernel API to query RAM size · 0dfebc7 · KFire-Android/kernel_omap_bowser-common · GitHub - http://goo.gl/YQ9qiu
[Samsung Galaxy Nexus] siealex:
Does anyone use ZRAM in r49? Is it useful?
[Samsung Galaxy Nexus] Alkemix:
Mediafire Metalspring's compiler Link doesn't work ... Please Can You give me a working link ? I'm curious to try It ...
[Samsung Galaxy Nexus] boype:
My point of view: http://www.xda-developers.com/android/mythbusters-xda-edition-optimized-compiler-toolchains/

I have done builds with super-duper optimized linaro toolchains before. Benchmarks indicate no performance gain. Also, subjectively, the google 4.7 toolchain is the most fluid one.

This commit does not do anything except writing the total RAM size to a variable, which never gets called. What is this used for?
[Samsung Galaxy Nexus] erghetto:
pre 50 very very good!

thanks boype!
[Samsung Galaxy Nexus] TheGeekRedneck:
So far Pre-50 is working great on my GSM GNex w/ CM11 nightly... no more signs of that weird freezing and lagging I was getting with r49!
[Samsung Galaxy Nexus] oli20021978:
after several hours with pre 50 i was playing farm heroes saga. horrible lag and freeze on stock settings. have to pull the battery so no last kmsg

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] siealex:
Install Cool Tool (or any other monitoring app, I prefer Cool Tool) and set it to show free RAM with 1 or 2 sec. update. Look at the value when the phone starts lagging. If it is lower than 32 M, increase the last two values in OOM settings.
[Samsung Galaxy Nexus] klobkelosh:
Boype, just reporting in, running pre50 since you first posted it with no reboots. Ran fine until this evening when it slowed to a crawl and was out of memory. Rebooted fine. Imagine some oom tweaks still in order...
[Samsung Galaxy Nexus] revanmj:
Are you using newer CM11 nightlies (with new Theme Engine) or something that is based on them? Because that looks like crashes I've got (and not only me) after installing those nightlies without changing kernel, so the cause is more likely the new Theme Engine (which for now is far from stable), not Fancy.
[Samsung Galaxy Nexus] furb3t:
In my experience pre50 is worse than r49 using omnirom (updated to last nightly). Lag and freeze are increased but with pre50 homescreen is alway loaded while with r49, after a bit, homescreen was reloaded each time.

OT: #boype I always have my p970....do you have something for it of interesting? ;)
[Samsung Galaxy Nexus] MBQ_:
your problems sound like a sort of isolated issue. the majority of us have been thoroughly enjoying pre50
[Samsung Galaxy Nexus] poltor:
hello,

the latest version of the kernel is fantastic no problem. :good:

thanks for your work

as you know is out of the update KitKat google glass. glasses have the same hardware as the galaxy nexus, the version of the platform is almost identical 4430 downclock. we could revive our device with a kernel KitKat official?
[Samsung Galaxy Nexus] gautam_nexus:
rocking pre50..great work! [MENTION=4615478]boype[/MENTION]
[Samsung Galaxy Nexus] Teemoo:
Yes, I'll try to go back to m5 snapshot and report back.

edit: rolled back to m5, pre50 looks better with m5 so far.
[Samsung Galaxy Nexus] furb3t:
Mine is just a report :) Anyway most users are using CM11 with pre50, maybe OmniRom is not good with this release. I'm curious to listen other experience from user who are using OmniRom.
[Samsung Galaxy Nexus] swedkg:
pre50 running phenomenally smooth and snappy on ShinyROM.

thank you boype, osm0sis, and everyone for coding this.
[Samsung Galaxy Nexus] RevengeFNF:
Pre50 is working fine so far.

No more services being rebooted and i can also see a lot of apps in cache without killing the performance.
[Samsung Galaxy Nexus] Piti8576:
pre50 works amazing.

Only facebook app restarts sometime all other are fine, in cache are 5-15 apps.

The only problem is that i have to make a init script for the minfree values, but i think is rom related.

My rom is trex 4.4.2 (carbon basis).
[Samsung Galaxy Nexus] siealex:
Can I dirty flash pre50 over r49?
[Samsung Galaxy Nexus] gautam_nexus:
No. First dirty flash your Rom and then flash r50

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] siealex:
OOM in pre50 is much less aggressive than in r49 and works pretty correctly on default settings.
[Samsung Galaxy Nexus] rjshrjndrn:
Perfect
[Samsung Galaxy Nexus] siealex:
In R49 only. These settings are too low for pre50.
[Samsung Galaxy Nexus] paarthdesai:
pre 50 running like butter....woott woooot :D

old fancy days back again for me :D :D: D:D:D
[Samsung Galaxy Nexus] boype:
r50 within the next few days

Hi all,

Since the reports concerning pre50 have been largely positive, I'll be pushing r50 within the next few days. I could already do that today, but I still want to find the issue [MENTION=4078274]infectedorganism[/MENTION] has with android 4.2.2.

I have a question for all of you about the anykernel install procedure: Is there anyone who had / has problems installing the kernel with this new method?

(I want r50 to be as solid, stable, smooth and non-problematic as possible)
[Samsung Galaxy Nexus] rjshrjndrn:
what's any kernel install procedure? :eek:
[Samsung Galaxy Nexus] motorazrv3:
First page!
[Samsung Galaxy Nexus] erghetto:
i've installed it on liquid 14 april, but on a full clean install (wipe data, cache, dalvik, system) no problems..
[Samsung Galaxy Nexus] mick.li:
I just flashed pre50 over r49 and wiped cache/dalvik afterwards. Don't seem to be having a problem. Running ShinyROM.

Mick
[Samsung Galaxy Nexus] klobkelosh:
Boype, will you consider fine tuning the minfree values on r50? The current stock values run very well for about a day, at least for me running omni on toro, and then the phone starts severely lagging. When this happens and I check the free memory I see that there is almost none left. Clearing all apps seems to help, but we shouldn't have to do that anymore (unless there's a memory leak). Right now, the stock values are (in trickster) 10 14 18 22 26 46. I think the first three and fifth values are right on and keep launchers in memory and allow decent multitasking. I think increasing the 6th (empty app) value might free up unused memory and prevent low memory after many hours. I'm trying values and will report back, but my daily test is too see if titanium backup runs on the middle of the night, so I won't really know until tomorrow.

Anyway, if no one else had this problem I guess it's not important, but if anyone does it would be worth the fine tuning.

Thanks for the amazing kernel boype!
[Samsung Galaxy Nexus] boype:
I've already fine-tuned them further. I noticed the exact same thing you did ;)
[Samsung Galaxy Nexus] mick.li:
How about sharing the new (trickster) values so we can try them on pre 50 :D.

Mick
[Samsung Galaxy Nexus] oli20021978:
+1 on this running carbon

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] osm0sis:
Increasing the Empty App was the single most important thing Paul [MENTION=4793042]pkgnex[/MENTION] found for LMK from all his testing. :)
[Samsung Galaxy Nexus] pkgnex:
Right on!

I will add that I have not done much new testing with the new LMK drivers that seem to be the flavor of the month, though (in either Fancy or Dirty-V, for example).

For the "old' LMK driver, raising the last number was how you could affect the most change in device behavior. Raising it kept more free RAM (and sped up opening times for RAM hogs like Chrome and various games), but there was a limit (above 160 - 190 MB or so, depending on kernel) at which it just started killing off too much background stuff, leading to lags from everything closing and re-opening in the background whenever something new was opened. There was definitely a "sweet spot", and I imagine that will be the same with the new driver variants - albeit with different numbers.
[Samsung Galaxy Nexus] siealex:
Skype, e. g., declares itself "empty" immediately on minimizing even during a video call. When I open Browser or Email during a Skype call, the call ends in one or two seconds unless I set the minfree value for empty apps rather low.
[Samsung Galaxy Nexus] pkgnex:
That sucks if you depend on using Skype! Skype's crappy coding is essentially degrading your entire device user experience.
[Samsung Galaxy Nexus] swedkg:
got a 55 hours uptime, before i restarted my phone to install some Xposed modules updates. Buttery smooth, with absolutely no lag. End after a very long time, really wonderfull multitasking, without apps restarting when pressing the "Back" button.

Installed Shiny ROM some weeks ago, messed with Franco's kernel, then went with osm0sis's xperimental ones, back to rom's original kernel, and now on Fancy since r45. No rom dirty flashing or nothing, just cleaning caches before every new kernel flash. Pre50 brought the best experience I ever had on this device.
[Samsung Galaxy Nexus] enginmanap:
I had the exacly same situation with cm11 m5. After reading some recommendations on this topic, I start using cool tool to show the free memory, and lagging starts when the "Available RAM" drops below 100mb. I think it means free memory + cache, but I am not %100 sure.

All I can say is, the lag disappears after I clear the recent apps.
[Samsung Galaxy Nexus] spirit1002:
Use r50 pre about 2 days. I found that the available RAM of r50 is very low even when the phone just new booted.

Usually I have 370MB available RAM with r45 when the phone just new booted. But with r50 pre, I only have about 300MB available RAM.

After several hours use, with r45, there's usually 300+MB available. But with r50 pre, after I cleaned recent apps, there's only about 200MB available RAM.

I use the default LMK values and also try other values(25 30 35 39 47 67), the result is the same.
[Samsung Galaxy Nexus] erghetto:
maybe i'm wrong, i haven't knowledge about this argument, but i think that we shouldn't focus on "how much ram is available".

i mean.. if i have only 100 MB free, but my phone's behaviour is perfect, who cares of RAM? for me it's important that when i need to use phone in a faster way, it has to respond well.

this is my thinking
[Samsung Galaxy Nexus] pvkiniyan95:
u r late to the party, basically in linux more free ram means more waste of resources....be happy if ur phone doesnt lag when u got fewer free ram and feel good multitasking....whats the point of having a smartphone where ur apps get killed and restart everytime u open it, thats what having more free ram is all about.
[Samsung Galaxy Nexus] SirOch:
Hi,

After 2 days of usage of the pre_r50, there is plenty lags and the stock launcher very slow. Clear all recent APS solve the problem but for a short time only. The only cure is to reboot the phone.

I hope that the final version will rock as the the r45.

Cheers

Envoyé de mon Galaxy Nexus en utilisant Tapatalk
[Samsung Galaxy Nexus] klobkelosh:
Free RAM is wasted RAM. We need enough to open apps and multitask, but Linux is designed to kill off applications when mute RAM is needed. I've found (subjectively) that 150-200 mb is sufficient.

Not sure what boype has up his sleeve for final oom values on r50, but these values are performing very well on pre50: 10 14 18 36 32 64. No lags after many hours, background apps run, launcher stays in memory. Ymmv.
[Samsung Galaxy Nexus] spirit1002:
I think you misunderstand me. I know the knowledge that you say.

My English is too poor to describe it exactly...The RAM is really strange with r50.pre.

Regret not learning English well.
[Samsung Galaxy Nexus] pvkiniyan95:
never mind....u r as good as ur mother toungue :D...english isnt a great language after all but a very recent one based on earth's timeline...
[Samsung Galaxy Nexus] cujo6801:
Lmfao....

Y u speak no like.... :D:p:eek:

Lol...

Sent from the "DOG" pound
[Samsung Galaxy Nexus] boype:
r50

Hi,

here's r50. Fixes for crazy app killing included, hopefully also the receipe for long smooth up times.

defconfig: reduce vmalloc to 496M (fixes apps being killed all the time)

added error codes / success message to anykernel2 installation process (good to see what's wrong when it doesn't work, right?)

min_free_kbyte tweak (10mb)

vfs_cache_pressure tweak (25)

dirty_bytes & dirty_background_bytes tweak (8 & 2 mb)

lowmemorykiller minfree tweaks 12,14,22,24,52 mb

renice systemui only to -10 (-18 is overkill)

renice block interface's flush daemon to 5

remove launcher whitelisting (if the lmk wants to kill the launcher, this has a reason (e.g. ram-hogging games))

P.S.: I'm sorry [MENTION=4078274]infectedorganism[/MENTION], I could not find the issue with slimbean 4.2 ROMs :/
[Samsung Galaxy Nexus] infectedorganism:
Thank you for taking the time out to try and find the issue; it's very appreciated!

I'll continue to test and see if I can find any new information.
[Samsung Galaxy Nexus] adamslast:
Is this version compatible with miui 4.2.2 roms?
[Samsung Galaxy Nexus] erghetto:
[MENTION=4615478]boype[/MENTION] can we flash r50 over pre50? or is however needed a flash over a clean rom?
[Samsung Galaxy Nexus] pianistaPL:
I think you can install over because ramdisk from pre50 is already installed. There is no many changes in r50 in compare to pre50.
[Samsung Galaxy Nexus] motorazrv3:
I just flashed r50 over pre r50and all went fine. No issues. Just do a backup for safety.

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] siealex:
And can I flash it over pre50 if pre50 was flashed over r49? R49 was clean flashed.
[Samsung Galaxy Nexus] pianistaPL:
I guess so, if pre50 was working fine.
[Samsung Galaxy Nexus] MBQ_:
Just going to pretend like this was your birthday present to me.

;p
[Samsung Galaxy Nexus] infectedorganism:
*shrugs* I would assume so. Just make a nandroid, follow the instructions in the OP and give it a try.

Has anyone on 4.2.2 flashed this build successfully and still had access to their internal storage after?
[Samsung Galaxy Nexus] klobkelosh:
Nasty freeze and lockup with stock settings on r50. I tried to get last kmsg, but couldn't get adb to connect to the frozen device.
[Samsung Galaxy Nexus] infectedorganism:
Could someone post a screenshot of the default minfree for r50? I checked the changelog, but I think it's missing a value.

Thanks in advance.
[Samsung Galaxy Nexus] cujo6801:
Sent from the "DOG" pound
[Samsung Galaxy Nexus] shag_on_e:
Do far I am loving 50! I flashed it over bsmitty's latest Dirty super ram build so it's ramdisk is in place. I kinda miss the boot.img kernel format because it was good for a solid kernel flash to overwrite funky stuff with other kernels, but I can go with the flow ;) thanks for the continued badassery boype!

~~~~There is no spoon~~~~
[Samsung Galaxy Nexus] garyngkt:
Tested r50 but Antutu shows only 9xxx
[Samsung Galaxy Nexus] pattyboi:):
antutu means nothing :P
[Samsung Galaxy Nexus] Charmacas:
[MENTION=4615478]boype[/MENTION] do you now personally use Interactive as your default governor?

Because it's set as default after flashing r50.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] Orilin:
Ondemandplus is still the default here. Maybe have you restored previous settings?

Sent from my Nexus
[Samsung Galaxy Nexus] Charmacas:
Could be. Thanks for the input!

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] revanmj:
Installed r50 and so far it works fine. No unneeded app killing and lockscreen doesn't get killed too. Thanks!
[Samsung Galaxy Nexus] adamslast:
I flashed it. Working but it seems that it has a wi-fi connection problem. I can not download swiss keyboard language pacques and themes. I did not try further and return to CM kernel. :confused:

Edit: Unfortunately i can not see internal memory.
[Samsung Galaxy Nexus] osm0sis:
Anyone who can't see internal storage, open Terminal Emulator and paste the output of this command:

su -c ls -al /

Also: su -c cat /fstab.tuna

It sounds like an fstab problem but could also be permissions on certain files. Hard to say why it would happen for some and not others.
[Samsung Galaxy Nexus] infectedorganism:
I'm hoping I typed the first one correctly, but it says: unknown option -- a. I tried typing it in terminal emulator, also copying/pasting in adb shell, but I get the same output: unknown option -- a.

As far as su -c cat fstab.tuna, the output is: unknown id: fstab.tuna

I tried fixing permissions in twrp, but that didn't solve anything.

In root explorer, it shows that my internal storage has full rwx permissions (rwxrwxrwx) and that root is the owner and group; trying to change permissions via root explorer causes it to force close. It also says that the md5 can't be calculated (access denied).

** It appears that my internal storage is accesible from /data/media/0, but not the legacy option where it was prior to flashing r50 (storage/emulated/0)

I am also using the latest version of twrp: 2.7.0.0. I'm not sure if that changed where my internal storage is located.

I hope that gave you some insight.
[Samsung Galaxy Nexus] krneki10:
Which version do you recommend? Can I flash it on top of OmniMetal + Dirty V?
[Samsung Galaxy Nexus] osm0sis:
Install busybox, that'll give you the a option. Also, sorry I forgot a slash, post edited. Please try again. :)

If it's a permissions issue, recovery fix_perms won't do anything because the root / ramdisk is extracted from the boot partition on every boot, and is inaccessible otherwise.

Also what boot.img did you flash the zip over? Was it just over your ROM, or another custom kernel?
[Samsung Galaxy Nexus] aliesz:
Everything works on its rule here ;) Rom slimkat stable build4 with r50 fancy
[Samsung Galaxy Nexus] infectedorganism:
I had busybox (1.18) installed prior to running the commands. I just updated to version 1.22.1 and the output of both commands are still the same.

From terminal emulator, running 'busybox --list' shows that 'a' isn't a defined function.

After adding the slash, nothing changed. 'unknown id: /fstab.tuna' was the output.

I flashed the zip over the boot.img packaged with the rom. I erased system, cache, and dalvik cache.. flashed the rom again, then flashed r50, rebooted the system and found that the internal storage was inaccessible. The same occurs with a "dirty" flash (wiping system, reflashing rom) and a clean install -- tested on Slimbean 4.2.2 build 8 and Carbon Rom 1.8 (4.2.2).

If I go back into recovery, flash a 4.2.2 kernel (r36 in this case), access to my internal storage is regained. Keeping the old ramdisk (r36 - 4.2.2) and flashing the zImage from r50 works too -- I can access the internal storage.

I'll be gone for the next few hours but will test any other suggestions you may have when I return. On the other hand, if this is proving to be not worth the trouble, that is okay too. I am just appreciative of the help you and boype have giving this issue thus far.
[Samsung Galaxy Nexus] osm0sis:
It's not busybox, it's ls. Try this:

busybox ls -al

Might just be a JB4.2.2 issue.
[Samsung Galaxy Nexus] infectedorganism:
busybox ls -al: http://pastebin.com/xckTTrgT

busybox cat /fstab.tuna: http://pastebin.com/b2WxuLab
[Samsung Galaxy Nexus] osm0sis:
Thanks! Hmm yeah, looks okay. Must just be some detail with 4.2.2 that causes the problem. :confused:
[Samsung Galaxy Nexus] zoomy942:
wait... makes the UI smoother?? Any details about that?
[Samsung Galaxy Nexus] boype:
Basically, there's two things responsible for that.

1) A mechanism has been implemented that scales the IVA voltage according to the pixel clock. Higher pixel clock rates need a higher IVA voltage. If higher voltages are not granted, the UI may appear laggy.

Check out these commits: first commit, second commit, third commit, fourth commit, and fifth commit.

2) Another mechanism has been implemented that largely seperates the display subsystem composition from other kernel functions. Previously, a sharing of caches with those other kernel functions could cause FPS dips. See this commit.

I'm trying to be as simple as possible with my explanations... That's also why I don't write these rather technical things in the changelog, as I don't expect anyone following this thread to understand how everything works. Still: I'm always happy to explain things to the interested folks ;)

Is it working fine with other kernels?
[Samsung Galaxy Nexus] DrAk0H:
Hi! I have a random reboots with r15 on latest cm10((( Flashing r14 helps by now...

Отправлено с моего A701 через Tapatalk
[Samsung Galaxy Nexus] boype:
Thank you for your input. The random reboots are most likely caused by the lowered voltages that were introduced with r15. I will increase them again in r16 (but only a bit).
[Samsung Galaxy Nexus] momomok:
my phone will be lagging like crazy after an app has been installed or updated

it is like that on different ROM and kernel, except the stock one

is that I/O scheduler related? or hw related?
[Samsung Galaxy Nexus] sergini:
That's a known 4.2.2 problem. Happens everywhere.
[Samsung Galaxy Nexus] Rufufu:
Liking r15 a lot, no reboot for now! Using stock settings I only set the interactive governor.

Hope the battery is good too, will see it in a few days!

Thanks Boype!
[Samsung Galaxy Nexus] bolanrox:
No reboots as of yet. Left everything stock except for the color settings. Do notice a minor lag with swiftkey (only when trying to delete) generally bumping up the GPU fixes it, but I did not have to do that on 13 / 14. no huge deal, just something i noticed.

Edit: first crash just happened. Battery pull and am back in business
[Samsung Galaxy Nexus] boype:
Okay that calls for a fix release. Will get on it later today or early tomorrow.
[Samsung Galaxy Nexus] bolanrox:
Thanks! it crashed using Falcon Pro (clicking on the unread tweet icon) it that helps any?
[Samsung Galaxy Nexus] aeoveu:
Maybe its me - but I saw the phone was constantly active (Trickster's CPU usage module shows it) so I reverted back to r14. Changing the governors didn't help. Disabling SR didn't help either.

I'll try again later tonight, so fingers crossed.
[Samsung Galaxy Nexus] Riekr:
R15 seems to not boot with cm10.1 exp gerrit of today

Was working fine with the yesterday build

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Rufufu:
It is OK for me ( r15 with today's build)
[Samsung Galaxy Nexus] RevengeFNF:
Working fine here.
[Samsung Galaxy Nexus] phishn:
R15 working well here with the exception of bluetooth music with screen off. It occasionally cuts out. I suspect that this is voltage change related too. R14 worked fine.
[Samsung Galaxy Nexus] zoomy942:
Awesome explanation. The fps fix is exactly what I'm looking for
[Samsung Galaxy Nexus] n2rjt:
R15 feels laggy to me, and crashed twice. Not random reboot but frozen and unresponsive.

Thank you for your work. I really like these kernels. They make my phone feel faster and last longer. I use stock ROM.
[Samsung Galaxy Nexus] boype:
r16 up

Hey guys,

r16 is up. The main concern is the freezes some users reported. Let me know if this release fixes the issue.

Change log:

updated Linux to version 3.0.74

increased voltages for lower frequencies again since some users reported freezes

min_free_kbytes to 8192 since the UI could get choppy after one or two days

pulled in two more things from the TI omapzoom repo (DSS optimization; retention voltage spec update)

Best regards
[Samsung Galaxy Nexus] DrAk0H:
Installed r16... So far so good... UI is really smooth now))) Thanks!

Отправлено с моего Galaxy Nexus через Tapatalk
[Samsung Galaxy Nexus] agritux:
sometimes music plays laggy

is it kernel issue?

i have no more issue

it is best kernel for me

like p970 :)