yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] my573r10us:
oh ya im so sorry, i didnt see the states before :o

oke then, thanks for your reply :)

anyway, just a question, can you or add more ram (maybe till ~770mb free)? i think i dont need a 1080p recording, i need much ram bcause when im running BBM app, it take ~140mb ram *scrollingeyes*

thanks so much :D
[Samsung Galaxy Nexus] osm0sis:
Haha, Francisco doesn't want to add any more than the ASRAM 50mb, but you can check out other SuperRAM kernels like DirtyV. :)

If you do some research I think you'll find free RAM technically doesn't matter in Linux/Android like it does in Windows. Free RAM is wasted RAM, and management is more important. Android manages it pretty well, and never actually reaches out-of-memory. ;)
[Samsung Galaxy Nexus] my573r10us:
ohh okay.. :(

with dirtyV, my camera always stop working after some use, i dont know why, need to restart to fix it, and then happen again after some use (any version of dirtyV).

but, my other app (such as whatsapp, line, and kakao talk, bbm) closed it self (notification pending till i open the app again) bcause of the little space free ram i think :'( (it always happen when i used some kernel that has ~700mb ram), after using mpokang ~751mb, it rarely happened)

wanna upgrade to nexus 5, but.. no money haha
[Samsung Galaxy Nexus] osm0sis:
Fair enough! :)

Maybe give DirtyV-SR another try. It's in constant development, so maybe your camera issue is resolved. I've never had any trouble with my camera on it, and I use the Google Camera in PA Stock GApps. I just make sure it's not set to 1080p before flashing the kernel and it's good. :good:

The one from the 27th is also at my osmod link in the post above. ;)
[Samsung Galaxy Nexus] metalspring:
you can always compile it yourself and change the amount of reclaimed ram ;)

https://github.com/bsmitty83/DirtyV_tuna/commit/bded16c4bb2075feb0f789d14b3a7e1af9a8e1fa
[Samsung Galaxy Nexus] my573r10us:
woah, okay will try.. thanks sir [MENTION=4544860]osm0sis[/MENTION] :laugh:

actually i dont understand how to compile it, but will see..

thanks sir.. :good::good:
[Samsung Galaxy Nexus] osm0sis:
So, back on topic.. ;)

We've got a few things to play with:

r396-test, and r395-toolchain + r395-optimized. :D

Comparisons? Benchmarks vs. r395 with the same settings?
[Samsung Galaxy Nexus] metalspring:
I can compare the r396 and r395 optimized, haven't had much time to compare to regular r395 yet though.

With r395-optimized, I got about 13200 but with r396 I only got about 12000 and a few games I tried stuttered a little bit on r396, but worked fine with r395-optimized
[Samsung Galaxy Nexus] osm0sis:
Thanks! Franco mentioned the ram scores in benchmarks were better with r396 than r395, can anyone verify that? :)
[Samsung Galaxy Nexus] metalspring:
I know when dirtyv tried some ram overclock like r396 has the ram speed scores went up very slightly but ram performance scores dropped from about 900 to a little over 700 so it wasn't really worth it
[Samsung Galaxy Nexus] Max94h:
I'm running r395 optimised and it works perfectly, it's really fast... I haven't tried any benchmark though, I really don't like them :)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] duffymm:
[MENTION=1143630]osmosis[/MENTION] : Are they both for 4.4.x roms ?

What's the difference between 396test and 395optimized ?

Thanks

PS : sorry I already found the answer in your links :D
[Samsung Galaxy Nexus] abalam:
Can we use this on 4.3
[Samsung Galaxy Nexus] ahmadairfan:
Just reporting, guys.

Lower overall scores on r396 test, even the rams benchmark is still the same. Even though I tested it with exact settings I have on r395-optimized :confused:

Running r395-optimized so far I am impressed, smoothy :)

Using neph's settings for DirtyV and 1536 max.
[Samsung Galaxy Nexus] Fatsodonkey:
The 395 optimized is awesome smooth. It would be my daily if it had vibration control and gpu control.
[Samsung Galaxy Nexus] creeve4:
395 optimized is definitely smoother than 396. No benchmarks, just based on feel.
[Samsung Galaxy Nexus] swedkg:
Are there 4.4 only? I flashed the r395-optimized and it's stuck on the Google logo
[Samsung Galaxy Nexus] osm0sis:
My AnyKernel r396 test build should be safe for any ROM, JB4.3 or KK4.4. metalspring's r395 experimental builds are bundled with a KK ramdisk however.

No vibe, but the GPU scales from 153-384-512, which is better than the variable OC which only goes 153-Max and Franco found less stable.
[Samsung Galaxy Nexus] Fatsodonkey:
Okay. The vibration is so high that i cant handle it. :D

Btw phone seemed to get really hot when using this kernel.

I was only web browsing and my hands were smoking.

E:clean installed on latest cm11 and not getting that hot anymore.
[Samsung Galaxy Nexus] swedkg:
My AnyKernel r396 :p is hot!!

Definetely feels snapier than Franco's r395 on 4.3, making the back of the device maybe a tad hotter.
[Samsung Galaxy Nexus] pkgnex:
-

Ok, here goes. Due to Os' request and all the comments, I've given each flavor another shot for 1/2 day...

I still prefer the mainline r395.

The toolchain and optimized versions don't benchmark as well as plain old r395 for me (antutu) and seem choppy/stuttery. They give me graphic stutters when swiping away or closing apps, or opening new ones.

The r396 benchmarks very slightly better than r395 for me (like 1 or 2 %), but it seems laggy in transitions and not as responsive to touch input. That said, I'd love to try r396 with a ramdisk, as kernels with osm0sis' ramdisk have always run better for me than the same kernel in anykernel format.

All evaluations were stock, except running 925vmsettings script and OC'd to 1305, which is my daily set up.
[Samsung Galaxy Nexus] osm0sis:
Thanks Paul. Great feedback, as always. :)

If you flash boot-r395.img and then the r396-AnyKernel on top it should be exactly the same as if I had made it by hand. :good:
[Samsung Galaxy Nexus] pkgnex:
No problem.

As for flashing r395 boot image then r396 anykenrel... understood, and thanks for the info!

I probably should have noted that before flashing the anykernel r396 version, I re-flashed the ShinyRom stock kernel. I have found this necessary in the past when a leftover ramdisk from a kernel interferes with a different kernel in the anykernel format, so I just got in the habit. Flashing the stock ROM kernel (or the entire ROM, doesn't seem to matter which, and just doing the kernel is faster) first, then immediately the anykernel gives a fresh, clean install without any potential leftover ramdisk interference - at least that's my understanding and it has seemed to work thus far!
[Samsung Galaxy Nexus] osm0sis:
Yup, that's generally what AnyKernel is for to make sure any ROM-dependent stuff is there. I've been pretty good about keeping f.K's ramdisk universal though, so I don't imagine there'll be any problems flashing over it. :)
[Samsung Galaxy Nexus] swedkg:
395 vs 396 on 4.3

I hope the Dropbox links work. 3 runs of Antutu. On 396 there was a forth one, but was extremely low, for whatever reason. Maybe it has to do with what pkgnex described as "choppy/stuttery".

Not much of a difference, however 395 seem more consistent.
[Samsung Galaxy Nexus] osm0sis:
Interesting. Yeah, your benchmarks are within the realm of the normal variance on things like AnTuTu, so really on your device they appear to perform exactly the same (according to benchmarks ;)). Thanks. :)

Do you still think subjectively r396 feels snappier?
[Samsung Galaxy Nexus] swedkg:
Yes, especially when the device is entering OS for the very first time, after you enter the PIN code, and everything has to be loaded at once. On 395 it stops rensponding for a moment, you can tell that the app drawer in not yet initialised. With 396 it just flies through this point.
[Samsung Galaxy Nexus] pkgnex:
[MENTION=4544860]osm0sis[/MENTION], I forgot to ask, is there a way to get a ram-disked r396 besides flashing r395 then r396-anykernel... such as extracting the boot.img from the r396-anykernel and dropping it in the r395 zip, or vice-versa? Or do you know if an official r396 (non-anykernel) release from Franco imminent since he built it? Thanks.
[Samsung Galaxy Nexus] osm0sis:
He built a KK-only one for me. But yes. Use my Android Image Kitchen, unpack the r395 boot.img of your choice, then put the zImage from the r396 AnyKernel zip in the split_img dir, renaming it and replacing the zImage file that's already there.

Sounds like CM added Multi-SIM support back into the latest nightlies so the ramdisk will need updates anyway. This is where AnyKernel shines. :)
[Samsung Galaxy Nexus] skizofrenic:
Is there any way to see GPU freq in real time???

Tnx
[Samsung Galaxy Nexus] The Gingerbread Man:
With system monitor you can on nexus 5 and n7, not sure about older devices though.
[Samsung Galaxy Nexus] skizofrenic:
Paid or lite version??? Cuz cannot find it...
[Samsung Galaxy Nexus] osm0sis:
In Terminal Emulator you can type:

while sleep 1; do cat /sys/devices/system/cpu/cpu0/cpufreq/gpu_cur_freq; done;

That'll print the live frequency until you Ctrl+C in Hacker's Keyboard to halt the command.
[Samsung Galaxy Nexus] skizofrenic:
Thanks.....

I go study !!!!
[Samsung Galaxy Nexus] pkgnex:
Got it. I may do that this evening.

I understand why anykernel is desirable for a dev who wants wide-spread ROM compatibility, but I don't care about CM :).

I swear that on the stock-ish ROMs I've always run, kernels with a good ramdisk always seem smoother and faster than the same kernel in the anykernel format. Can you convince me that it's all in my mind? Better yet, can you give a synopsis of what a ramdisk provides that anykernel versions do not, and what, if any, advantage is gained from having a ramdisk?

I really appreciate you taking the time to educate me a bit;)
[Samsung Galaxy Nexus] osm0sis:
Haha might be the tweaks most bundled ramdisks include, since most that would be AnyKernel were using koush's old AnyKernel zips which only have the kernel zImage. So if you take the franco.Kernel ramdisk as an example, with koush's AnyKernel over stock you'd be missing out on init.d support (potentially, if your ROM doesn't support it), all the /sbin/fkbootscript.sh tweaks (renicing, etc.), and a couple other tweaks (least-break-time, etc.) I have scattered around the ramdisk.

Good news is my AnyKernel 2.0 should properly remove the need for a ramdisk since all those tweaks can easily be bundled anyway with it. ;)

I need to get around to making a thread for it so maybe we can see some adoption.
[Samsung Galaxy Nexus] skizofrenic:
:crying:

System/bin/sh: cat /sys/devices/system/cpu/cpu0/cpufreq/gpu_cur_freq: not found
[Samsung Galaxy Nexus] osm0sis:
Type "su" first. ;)

Also, if you're not on f.K right now for some reason, on other kernels it might be /sys/devices/system/cpu/cpu0/cpufreq/gpu_clock but I made it match the CPU scaling_cur_freq awhile back in terms of naming and output for consistency.
[Samsung Galaxy Nexus] skizofrenic:
Hhehehe noob detected here!!!

Tnx man now i eat 10 mins then ... Retry!!!
[Samsung Galaxy Nexus] 47th_Ronin:
[MENTION=4544860]osm0sis[/MENTION]

Running cm remix (which uses lean kernel as base) I flashed r395 w/your ramdisk followed by the r396 any kernel test you'd posted a while back.

And I gotta say it's running fantastic, no lag or hang ups of any kind at all, even when playing The Room 2 and Oil Rush.

(I dont put much faith in benchmarks, due to how frivolous they usually are even when done consecutively.)

Running stock settings except for min at 182 and noop io as well as Illinois tcp.

Thanks for what you do man!
[Samsung Galaxy Nexus] skizofrenic:
Yhuhhuuu

Workin!!!! I feel so pr0 !!!

Btw i tried that r395 optimized... GPU has just 2steps.... Never displayed 384...
[Samsung Galaxy Nexus] SoftWord:
Where is link to download that optimized version please ?
[Samsung Galaxy Nexus] skizofrenic:
Here
[Samsung Galaxy Nexus] SoftWord:
thanks, that build have same mods of version r396 ?
[Samsung Galaxy Nexus] pkgnex:
Soooo....

Was the test-r396-anykernel built with your AK 2.0 format with all the fkbootscript tweaks included? If so, then it should be no different than with the r395 ramdisk. Which would suggest both that the laggyness I reported on the test-r396 was just in my head and that there's not much point in me compiling the r396 zimage into a boot.img with the r395 ramdisk tonight... right?
[Samsung Galaxy Nexus] osm0sis:
:laugh: Yeah they should be identical with regards to included tweaks. :D

You should do it anyway, it's a pretty useful thing to learn. :good: :p
[Samsung Galaxy Nexus] pkgnex:
Thanks for the info! Between me calling it laggier than r395 and a few others calling it snappier, I guess you got what you were looking for:p

I might try the extract and recompile thing tonight.

But probably not.

Then again, I might!
[Samsung Galaxy Nexus] osm0sis:
Haha it's hard to get a concensus. You always paid closer attention to the details, like choppy transistions, etc., so it's all valid feedback. :)
[Samsung Galaxy Nexus] osm0sis:
Another brief OT: my AnyKernel 2.0 thread is now live:

http://xdaforums.com/showthread.php?t=2670512

:highfive: :good:
[Samsung Galaxy Nexus] gtavo:
I don´t know if it is possible, but I´d love to have vibration strength control in this kernel :victory:
[Samsung Galaxy Nexus] tecno321:
Hello Francisco. Very nice work in this kernel! In the future you plan to put in this kernel a smart "wake your phone" like sweep2wake? It is very nice because improve duration of phisical button.

Greetings from Portugal
[Samsung Galaxy Nexus] AndyYan:
This kernel supports Touch Control (PGM) which does sweep2wake, sweep2sleep and even doubletap2wake.

Sent from Google Nexus 4 @ CM11
[Samsung Galaxy Nexus] tecno321:
How to activate this function? Thanks.
[Samsung Galaxy Nexus] AutomaticFailure27:
No. Not going to happen.

Touch Control. To activate, download the app, reboot, select the franco r384 module, enjoy.
[Samsung Galaxy Nexus] AndyYan:
Paid app. Download it and do what it says. Remember to choose r384 module instead of r391.

Sent from Google Nexus 4 @ CM11
[Samsung Galaxy Nexus] tecno321:
Thank you. It works nice.

Regards.
[Samsung Galaxy Nexus] SoftWord:
Which is best between:

franco r395 optimized

franco r396 test anykernel ?
[Samsung Galaxy Nexus] namtombout:
The former is better
[Samsung Galaxy Nexus] osm0sis:
We've got people saying each is better than the other. Both are good. I'd say still try both and see what you think. :)
[Samsung Galaxy Nexus] Piti8576:
I use TREX 4.4.2 Rom on my GNex that come with franco r395.

I have flash kernel emergency script, then r395 optimized and then r396 anykernel.

No Lags, very Smooth, all settings original that comes with kernel (no changes).

On my GNex is r396 better then all r395.
[Samsung Galaxy Nexus] lileoja:
hello thanks mates, which is (ex optimized R395) and (R396 anykernel)
[Samsung Galaxy Nexus] osm0sis:
Someone quoted the links again a couple pages back.
[Samsung Galaxy Nexus] sunscape:
Been using 395 optimized for a few days now. My phone has been almost lag free, and clearly better than plain 395. It might be related, or not, but I've noticed ridiculously longer battery life these past few days.
[Samsung Galaxy Nexus] lileoja:
where I can descagar 395 optimized
[Samsung Galaxy Nexus] pianistaPL:
Here http://www.mediafire.com/download/wkjj48y1nptc8vv/franco.Kernel-nightly-r395-Optimized.zip
[Samsung Galaxy Nexus] lileoja:
friend I have installed the 395 normal, I have to do is wipe cache ent in recovery dalvic cache and then flash the 395 if optimized?

thanks
[Samsung Galaxy Nexus] pianistaPL:
I guess this is not necessary but if you want to be 100% sure about right install, better would be to do cache and dalvik cache.
[Samsung Galaxy Nexus] lileoja:
thanks buddy, I got put with cm 11, is there any special configuration or must be left the way it is? :laugh:
[Samsung Galaxy Nexus] supernova_00:
r395 optimized runs great except when updating apps through the playstore. The phone basically becomes unusable while the updates are downloading and the phone doesn't become usable until all apps finish installing.
[Samsung Galaxy Nexus] osm0sis:
As far as I know that's pretty much a universal problem. You're saying you don't have that with r395 original recipe?
[Samsung Galaxy Nexus] peterlemonjello:
This has always been an issue with every kernel I've run. The only thing I've found to help it is to customize the io and governor tunables in the kernel. Check out this thread for some good settings http://xdaforums.com/galaxy-nexus/g...ngs-thread-t2401653/post44514476#post44514476
[Samsung Galaxy Nexus] SoftWord:
It's possible o have a mixed build based on "nightly r395OPTIMIZED + r396 of osm0sis" ?
[Samsung Galaxy Nexus] DroidOnRoids:
Per-app-mode is awesome! I just wish there was a way to disable the toast messages. I have almost every app in underclock mode so it gets kind of annoying when it pops up so often.
[Samsung Galaxy Nexus] goorek:
I'm on a ShinyRom, and after setting up Pattern security on my lockscreen, every time I turn on the phone and try to unlock, there's a bit of lag. Like I have to try my pattern three times to unlock it, diu to lag. Anybody experiencing this?
[Samsung Galaxy Nexus] osm0sis:
There's always a bit of settle time after boot-up. That's with pretty much any kernel that I've used.

If you wait half a minute before you try to unlock it'll be fine.
[Samsung Galaxy Nexus] sd3993:
Wrong thread mate :)

Btw there is an option for it under settings :)
[Samsung Galaxy Nexus] goorek:
But I meant every time I turn on the screen to unlock.
[Samsung Galaxy Nexus] Max94h:
Have you tried rising the min frequency?
[Samsung Galaxy Nexus] goorek:
Won't it make battery life worse?
[Samsung Galaxy Nexus] Max94h:
It depends, what's your current min frequency?
[Samsung Galaxy Nexus] goorek:
I'm on 384 right now.
[Samsung Galaxy Nexus] osm0sis:
Doesn't happen here on r395, r396 or any of the r395 mods from metalspring. And I'm using 192 MHz CPU min, otherwise basically defaults (see my sig post). I also use the DashClock lockscreen widget, have 3 widgets on my homescreen and run a variety of Xposed mods on AOKP so if it could ever lag, I would think it would be on my setup. I'm going to guess ROM/setup problem on your end.
[Samsung Galaxy Nexus] goorek:
Damn, I have to be more precise :) I meant 384Mhz as min frequency. Sorry, my bad, I'm after 8h of Android dev at work. ;) I will try to Greenify apps waking up on screen, see if it helps.

---------- Post added at 08:14 PM ---------- Previous post was at 08:10 PM ----------

EDIT

Tried it right now, and it works great. Seems like I have lags only while debugging via USB. Seems fair. ;)
[Samsung Galaxy Nexus] simplistian:
We may need to stop and think about where those numbers come from and how accurate they are. For battery consumption we should all buy a multimeter and measure the current flowing out of the battery instead of installing apps which we think we should trust :P
[Samsung Galaxy Nexus] franciscofranco:
Yes I've seen it. I googled a bit and couldn't find much info about it tbh...I'll drop 14.3 in a sec, better release more builds until I understand what the **** is going on.
[Samsung Galaxy Nexus] neoxz:
understood. Will wait for it.
[Samsung Galaxy Nexus] franciscofranco:
GG guys, just pulled an all-nighter to see this **** through. I hope #14.3 fixes whatever the latest ones ****ed up =)
[Samsung Galaxy Nexus] atsavlis:
Guys sorry if this has been answered before, been reading but can't find it. Anyone willing to tell me how to write a script to switch hotplug to on when the phone boots up?? I know how to do it manually each time the phone boots, but I would like to have a automatic scrips. Unfortunately I dont have credit cards to buy Francos app :(

Any help is appreciated.
[Samsung Galaxy Nexus] ro_explorer:
.... I don't see any new boot animation :)

And to be honest, I think kernels should remain kernels .. boot animation is another topic and it shouldn't be part of a kernel .. but this is MY opinion..
[Samsung Galaxy Nexus] nic85:
I am on 13.1 1200-700 1125-975-875 and is rock solid... Why i should upgrade to 14?

Are there huge improvements?
[Samsung Galaxy Nexus] nic85:
Double sorry..
[Samsung Galaxy Nexus] CitizenX:
Delete your current bootanimation from system/media/, Francos bootanimation is in data/local/ ...
[Samsung Galaxy Nexus] GR36:
I have done this and just get the default android one.

and there is no boot animation in data/local at all??

weird
[Samsung Galaxy Nexus] ro_explorer:
Yep .. same here.

More than that .. I just saw that I have no gsm signal at all once the screen is going off. I'm increasing the min freq to 700 (currently at 350)
[Samsung Galaxy Nexus] blackdub370:
kernel decompresses and copies the data/local bootanimation.zip - /system/media
[Samsung Galaxy Nexus] grinch247:
I see it :) nice bootanimation....franco.kernel.....looks pretty damn cool!
[Samsung Galaxy Nexus] Cutting-TM:
How much mA does your GN consume during deep sleep? I have 25-30 mA. Is this OK? With 14.1 I got 2mA and nothing has changed.
[Samsung Galaxy Nexus] rascarlo:
this is the boot animation

[YOUTUBE]q7_473twX4E[/YOUTUBE]
[Samsung Galaxy Nexus] mzet:
and what about turn off boot logo (google logo after turned on) in first phase and show standard kernel output? :)
[Samsung Galaxy Nexus] Mrc527:
The screen off bug, with signal lost is back. :-)

Btw, the cifs module won't mount my share. The best still the 13.1 release.

Inviato dal mio Galaxy Nexus usando Tapatalk
[Samsung Galaxy Nexus] ro_explorer:
By setting minimum freq at 700 MHz there is no gsm signal loss.

However, this shouldn't be happening.
[Samsung Galaxy Nexus] jhericurls:
Anyone else getting mystery voicemail alert on 14.3?
[Samsung Galaxy Nexus] minipaolo:
franco repeated many times that it's better to set min freq to 700mhz.

I am not having any issue with 14.3, but I'm not actually seeing any improvement from 13.1 (which seems to be more battery efficient).
[Samsung Galaxy Nexus] Shoaib1247:
Well I am on liquid smooth ROM, and the using DirtyV kernel, I am facing the same problem..
[Samsung Galaxy Nexus] namtombout:
r-395 optimized crDroid build 6
[Samsung Galaxy Nexus] movelbit:
I have 395 optimized but I cannot find r396 anykernel. Can anyone point me to it? What's the most recent unnoficial version? Thanks

Enviado do meu Galaxy Nexus através de Tapatalk
[Samsung Galaxy Nexus] osm0sis:
http://v.ht/osmod

All my test goodies live on my Dev-Host. ;)
[Samsung Galaxy Nexus] mangusZen:
Hi [MENTION=1143630]osmosis[/MENTION], Im late to the party...what are the differences between 395 and 396 in short? Cheers
[Samsung Galaxy Nexus] osm0sis:
The original posts for each say it all:

:)
[Samsung Galaxy Nexus] andreskafe:
What version for slimkat 3.6?

[Galaxy Nexus]
[Samsung Galaxy Nexus] victor2868:
I get com.phone fc again on the cm latest nightly version and franco r395 optimized version ...:(
[Samsung Galaxy Nexus] supernova_00:
It comes and goes with kernel releases so I'm thinking it might just be your builds that I see the issue with. I really don't have spare time to flash back and forth to confirm this but I didn't have the issue using Franco's last released kernel and did after using your latest optimized. I'm kind of sure the same happened for the builds prior as well.
[Samsung Galaxy Nexus] osm0sis:
Sorry, but it is universal, like I said and was corroborated for you already:

Please don't blame silly sh*t like Google's derped update code on something insignificant like a repacked ramdisk. If you don't believe, go back to ICS and watch how crazy fast and smooth the old Android Market updated.

I didn't even touch the optimized ones, those were metalspring's. And the exact same ramdisk, my ramdisk, is in all of them, including the official r395. You're imagining things, I'm afraid. ;)
[Samsung Galaxy Nexus] Syfer_Fever:
hey os, why there is no zram option in r395 and r396?
[Samsung Galaxy Nexus] osm0sis:
Is that new? Francisco's never been a fan.
[Samsung Galaxy Nexus] Syfer_Fever:
sorry i don't know if franco didn't like zram, but if i'm not mistake previous release has zram?
[Samsung Galaxy Nexus] luckana:
on the optimized r395 i don't have GPU OC control, is that how it should be ?