yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] thesebastian:
I'm a new Galaxy Nexus user.

I want to ask....can I get more RAM disabling 1080p or something like that?

I don't need to film 1080p videos but I use Chrome a lot and I have some issues with RAM. (At least with Stock Kernel or Franco r391. Just updated to r392 and I'll see what happens...)
[Samsung Galaxy Nexus] pkgnex:
Yeah, 1080p recording is fine on r392. I guess I should actually TRY the kernel before throwing stones:o. I should have known Franco wouldn't implement something that reduced a basic device functionality!
[Samsung Galaxy Nexus] alfiemenace:
After that 50mb more ram from yuv tiler, can we still get more by removing 1080p?
[Samsung Galaxy Nexus] thesebastian:
Yeah I want to know the same thing!

I would even kill 720p recording to get more ram!
[Samsung Galaxy Nexus] pkgnex:
[MENTION=4544860]osm0sis[/MENTION],

Mpokwsths has something cooking over on his kernel that nearly doubles the RAM speed on benchmarks (in his v10 beta). I'm not sure what he's doing - if it is safe / sensible, etc. - but when he commits it to his released version, you and Franco might want to take a look as the results people are getting are very impressive.
[Samsung Galaxy Nexus] Sik-1:
Very very impressive I must say
[Samsung Galaxy Nexus] franciscofranco:
I'll merge those newer values.

Its weird that the powerhal thingy was not being disabled, it worked on my device for some reason. Anyway I'll fix it.

I don't know about those FKU entries, but I'm working on the new generation FKU and I'm sure those annoying bugs will be fixed (I pushed an alpha yesterday). io_is_busy is not there because for some reason I didn't merge it from Google's gerrit. About the voltages that will be possibly happen on the new FKU and you'll be able to change to whatever value while still being able to -25mV/+25mV too.
[Samsung Galaxy Nexus] wavedashdoc:
Any chance we could we could get updated to 3.0.99 instead of 3.0.91?

Awesome work man! Nice to see Th big men implementation!
[Samsung Galaxy Nexus] aquatix:
Is it just me, or is the high performance sound toggle missing? Otherwise working great!
[Samsung Galaxy Nexus] osm0sis:
Yeah seems like it was working, but you had the cp if it didn't exist to make a backup then didn't do anything with the original file. I'll email you an updated version where it just deletes the powerhal after copying. :)

---------- Post added at 05:10 PM ---------- Previous post was at 05:05 PM ----------

Very rarely does anything important happen in those Linux kernel revisions. Francisco updates it more as a courtesy to everyone's ePeen than anything else. :laugh::p
[Samsung Galaxy Nexus] franciscofranco:
Indeed, 99,9% patches bring nothing to the table to this device, its mostly for x86.
[Samsung Galaxy Nexus] osm0sis:
Email sent [MENTION=3292224]franciscofranco[/MENTION]. Once that stuff's back in, you could easily go Milestone right after and call it a month. :):highfive:
[Samsung Galaxy Nexus] aeroxr1:
[MENTION=3292224]franciscofranco[/MENTION] you are a genius ! r392 is the best kernel ! Thanks ! What do you want to improve in the next version ? :)

Inviato dal mio Galaxy Nexus con Tapatalk 4
[Samsung Galaxy Nexus] carlinho77:
A question ! In the settings of Trickster Mod is the "increase volume of the sound in the headphones," but if I'm going to give a value (for ex 2), and save, when I go back in Trickster find him to 0. It only works if I set a value of 1. Ehm.....why ??
[Samsung Galaxy Nexus] erghetto:
I'd like to try this last version, but i don't know anything about this kernel because i've never tried it and followed this thread..

So before flashing it i want ask a pari of things.. Does it support PGM? And last version has more RAM without touching 1080p?

Edit: oh.. Other important thing.. Before flashing it, have i to flash ROM for having stock kernel? Or i can flash franco kernel normally?
[Samsung Galaxy Nexus] Schneewitzchen:
Franco recoded the sound control in #391 thats why only 1 works for now...see the changelog above
[Samsung Galaxy Nexus] carlinho77:
So the problem of low audio call was caused by the values ​​2 and 3 ?
[Samsung Galaxy Nexus] ha789di:
Pgm supported?

Sent From My Galaxy Nexus Using JELLYBEAN
[Samsung Galaxy Nexus] --__LoRiS__--:
Yes, it works for me on 392 osmod

Inviato dal mio Galaxy Nexus con Tapatalk 4
[Samsung Galaxy Nexus] erghetto:
what is osmod? XD
[Samsung Galaxy Nexus] Sik-1:
No way dude u can't b serious lol smh, I will share this with u tho , spend more time reading, u will learn an extraordinary amount of info
[Samsung Galaxy Nexus] erghetto:
i continue to not understand o.O
[Samsung Galaxy Nexus] abalam:
http://d-h.st/users/osm0sis/jb4_3/tuna/ One second, just noticed the powerhal wasn't actually getting disabled. Fixyfixing. Okay we're a go again. :D

There's weird stuff going on with the interactive tunables in f.Ku, like them populating with an old entered value when you go to edit (or nothing at all if you've never changed them before).

And it seems like interactive is missing io_is_busy now, though all the other schedulers seem to have it and you still have it in init.tuna.rc... [MENTION=3292224]franciscofranco[/MENTION] Is this intentional? Also please let us edit voltages to a specific value as well. The 990 +/- 25 for IVA is funky when I know that I can take mine down to 825mV safely.[/QUOTE]

---------- Post added at 07:51 PM --
[Samsung Galaxy Nexus] sd3993:
Is there a problem with auto brightness in the fixed version? it's set higher than in the original r392 even in a completely dark room.

I'm not sure if this is helpful but i'm also using your 900coloursettings init.d script.
[Samsung Galaxy Nexus] kevtrysmoddin:
Just switched from fancy kernel and I like the speed of v392 and 1080p recording works what a result great work Franco
[Samsung Galaxy Nexus] ssglackey:
Is there a reason that in FKU in Status is CPU temperature missing?

I am missing it for longer time, I thought it was due to 4.3, but on N7 2013 I have it.
[Samsung Galaxy Nexus] abalam:
Good point. In trickstermod you have that option, maybe an option to add this feature in FKU
[Samsung Galaxy Nexus] erghetto:
i can flash this kernel over another? or i have to flash rom to have original kernel before flashing franco-kernel?

edit:

and what's the difference? with franco i mean..
[Samsung Galaxy Nexus] ssglackey:
It was there in the past, but it was lost after big redesign if I remember good.
[Samsung Galaxy Nexus] Technical:
Do you know if Franco Kernel will be compatible with Touch Control Mod?

http://xdaforums.com/showpost.php?p=36763851&postcount=1

I've tested with r392 and a 4.3 Android Rom and it did not work.

Thanks.
[Samsung Galaxy Nexus] ChazzMatt:
osm0sis mod version of the Franco kernel fixes a couple of issues Franco hasn't had time to deal with.

Franco is busy with other current gen Nexus devices, so osm0sis has been keeper of the flame -- with Franco's blessing.

For the next Franco milestone, we hope it's basically going to be the current osmod version. :) Well, maybe with a couple more magic Franco touches thrown in.
[Samsung Galaxy Nexus] h1ghland3r:
Yes, it's. I'm with r392 and Touch Control. PGM was abandoned, I needed to buy Touch Control =(
[Samsung Galaxy Nexus] erghetto:
ooook thank you very much :)

and for my first question? could you tell me something?
[Samsung Galaxy Nexus] Technical:
I've tested Touch Control 1 hour ago with r392 and it cannot download any gesture to manage the kernel, saying the kernel is not compatible.

What did I do wrong?
[Samsung Galaxy Nexus] h1ghland3r:
I don't know. O.o!

Maybe because I'm with CM? But I think this is not related.
[Samsung Galaxy Nexus] osm0sis:
Module support has not been enabled again yet post JB4.3, ie. No PGM yet. I don't know how Touch Control operates though.

As for the color thing, Francisco added a patch to get rid of the purple on low brightness, but there's no difference in color between r392 and r392-fixed. My colorsettings init.d script does jack up the brightness a bit though so keep that in mind.
[Samsung Galaxy Nexus] ChazzMatt:
osm0sis actually has a "reset" kernel script you can flash in recovery that will remove all other kernel scripts. After you flash that, then you can flash the Franco kernel safely. Except I recommend the 392-fixed (osm0sis) version, of course. :good:

Franco Kernel 392-fixed (osm0sis)

http://d-h.st/users/osm0sis/jb4_3/tuna/

Find an osm0sis post and see the link to his kernel reset script there. Here ya go:

Kernel Emergency Settings Reset Zip

http://xdaforums.com/showpost.php?p=35648172#
[Samsung Galaxy Nexus] h1ghland3r:
Can I flash osm0sis r392 and continue to use Franco Kernel App to change colors?
[Samsung Galaxy Nexus] ChazzMatt:
Yes. The 392-fixed is still Franco kernel. Just a few modifications to make it "better".
[Samsung Galaxy Nexus] h1ghland3r:
Thanks! I'll flash right now.
[Samsung Galaxy Nexus] vitalero:
WOW no idea what u changed but after the app updated to 392 i felt like i have a brand new device in my hands that wasn't used for 2 years

everything faster and smoother, no idea why there even need for a "fix" it all works just fine since 390
[Samsung Galaxy Nexus] bhaji:
TC 1.8.3 works on r392 perfectly.

Have you seen the options in TC that ask you which kernel is similar to yours? there are 3 options: r391, r384, modified stock kernel. you should select r391 and TC will download modules.
[Samsung Galaxy Nexus] tomzefi:
I have been a Franco fan and supporter for a long while and probably have ran every kernel since android 4.1 and this is by far the baddest Franco kernel and kernel period. Thank you sir. 392 is plain awesome.
[Samsung Galaxy Nexus] osm0sis:
It doesn't "all work just fine", and I've explained perfectly well what I fixed, including root, so please read next time.
[Samsung Galaxy Nexus] nickcct:
Hi. My max frequency always back to 1200 even I switch to 1305. Flashed from stock kernel and using stock rom as well
[Samsung Galaxy Nexus] osm0sis:
That's the original Power Hal still being active, since you're a new f.K user as of r392. One of those fixes I made resolves this. :)

http://d-h.st/users/osm0sis/jb4_3/tuna/

Until Francisco can incorporate the fixes into an official build.
[Samsung Galaxy Nexus] puertorecon:
I wanted to find out if you have a flashable kernel zip file for PA 3.99 RC2? I am running AOSPAL SaberMod,...wanted to test out the kernel on this ROM.
[Samsung Galaxy Nexus] -Jesco-:
use the link in the post above your post :)
[Samsung Galaxy Nexus] fLipz:
OsMod R92 confirmed working with Touch Control.

thanks [MENTION=3292224]franciscofranco[/MENTION] for your great work and to [MENTION=4544860]osm0sis[/MENTION] for the fix
[Samsung Galaxy Nexus] puertorecon:
I have TWRP as a recovery,...I see that the file name has "CWM" on it. Can I still flash it?
[Samsung Galaxy Nexus] osm0sis:
Yes, "cwm" is just the shorthand I use to denote "flashable zip". :)
[Samsung Galaxy Nexus] Milleniumlance:
newb question, can this "fix" be used with the VZW galaxy nexus(TORO) since this file is under TUNA?
[Samsung Galaxy Nexus] puertorecon:
Thanks Jesco and Osmo!! You guys rock.
[Samsung Galaxy Nexus] osm0sis:
maguro, and toro are both Japanese names for different kinds of tuna. ;)

Mainline Franco is labeled that way as well. Kernels are generally for the board, which is tuna on the GN, and work on all variants.
[Samsung Galaxy Nexus] Milleniumlance:
wow that was quick thank you
[Samsung Galaxy Nexus] vitalero:
where is exactly the change log, sorry that i ask but how am i supposed to even know what you "explained" over 4000 pages?
[Samsung Galaxy Nexus] GamaX320:
The reset zip work on every kernel or only franco?
[Samsung Galaxy Nexus] sd3993:
yes...with a little bit of testing i did figure that out! :)
[Samsung Galaxy Nexus] demlv:
What is the last version of Franco kernel to work on Android 4.2.2?
[Samsung Galaxy Nexus] fLipz:
franco.Kernel-nightly-r384.zip for Android 4.2.2
[Samsung Galaxy Nexus] erghetto:
guys in trickster i've noticed that by default all smartreflex control are disabled, is it so for all or there is something wrong for me?

i ask this beacuse in all other kernel i've tried smartreflex is always turned on by default.

other thing.. wich scheduler and governor do you suggest to use? i'm not a gamer, i play only something like hill climb racing, so i don't need much performance.. i use often browser at university so i need something good for battery..

sorry for all my question, but it's first time for me on franco-kernel ^^
[Samsung Galaxy Nexus] Bl4ck3urn:
SmartReflex has been disabled long time ago > http://xdaforums.com/showthread.php?p=44977529&highlight=smartreflex#post44977529

Plz use the seach button next time.
[Samsung Galaxy Nexus] carlinho77:
What's new in fix R392 compared to R392?
[Samsung Galaxy Nexus] ChazzMatt:
Go

back a few pages to see

. osm0sis fixed a couple of minor issues Franco has not had time to deal with. r392-FIXED is better.

osm0sis and the Franco Development Team live with this kernel every day, while Franco uses the Nexus 4 as his daily device.

Download the os0sis "r392-FIXED" here:

http://d-h.st/users/osm0sis/jb4_3/tuna/

---------- Post added at 08:24 AM ---------- Previous post was at 08:22 AM ----------

Every kernel. It's a nice "clean default" tool to have when installing new kernels even if you don't use Franco kernel.

You can read the post he made explaining it at the same link to download it.

Kernel Emergency Settings Reset Zip

http://xdaforums.com/showpost.php?p=35648172#
[Samsung Galaxy Nexus] carlinho77:
12424 with Antu Antu Benchmark !!!
[Samsung Galaxy Nexus] ChazzMatt:
osm0sis has a "fixed" version for r384 too. I recommend it instead.

It is the last Franco kernel that works with 4.2.2, while r392 is the newest for Android 4.3.

EDIT:

Here's the corrected download link:

http://d-h.st/users/osm0sis/osmod/

It's an IMG file, so you flash it in the Franco app not in recovery.
[Samsung Galaxy Nexus] osm0sis:
Nono.. Don't use the hybrid on 4.2.2.. It's for JB4.3 like the directory and filename suggests.

My last for 4.2.x was an osmod:

http://v.ht/osmod or http://d-h.st/users/osm0sis/osmod/
[Samsung Galaxy Nexus] ChazzMatt:
download link corrected in my post. Thanks.
[Samsung Galaxy Nexus] infectedorganism:
How much work would it be to backport a 4.3 kernel to work on 4.2.2? Does anyone know any good tutorials I should read?

Thanks in advance.
[Samsung Galaxy Nexus] Tennic:
r192 works with 4.3.1 rom? Or only with 4.3 rom? :confused:
[Samsung Galaxy Nexus] nickcct:
R u on ROM 4.3.1? I thought GNex latest is 4.3?
[Samsung Galaxy Nexus] Tennic:
CM 10.2 today nightly (cm-10.2-20131011-NIGHTLY-maguro), is on 4.3.1 ;)
[Samsung Galaxy Nexus] in1400:
And TREX V 41 is also 4.3.1 :)

Gesendet von meinem Galaxy Nexus mit Tapatalk 4
[Samsung Galaxy Nexus] kuyam:
4.3.1 brings nothing new for the tuna/mako. In fact, its only been released for the Deb, not even for Flo.
[Samsung Galaxy Nexus] hotrodwinston:
According to users of the aosp reference rom posted to the vzw dev section it fixes data drops on toro.
[Samsung Galaxy Nexus] Tennic:
So, the kernel r192 should work on 4.3.1 rom?
[Samsung Galaxy Nexus] blackhand1001:
Everything is working great so far. The color profiles clearly have changed in 392 though. The lowest shades of grey are now much closer to black so banding is better but I can't get rid of this horrible green tint to shades of grey especially on low brightness.
[Samsung Galaxy Nexus] abhishek93:
Guys my phone is usually hot when i run franco.. Any tips or ways to keep my phone cool.. Does undervolting really helps?
[Samsung Galaxy Nexus] metalspring:
Actually there is at least one ROM based on the open master branch of Google source that is technically 4.3.2.1.000.000 lol

(Open master branch is basically the most updated source possible as far as I know)
[Samsung Galaxy Nexus] hotrodwinston:
392 not compatible with 4.3.1 - crashed refused to boot.
[Samsung Galaxy Nexus] aeroseek:
You are incorrect sir
[Samsung Galaxy Nexus] Robshr:
Great work

Love this kernel one thing I noticed when I flashed r392 my wifi goes all wacky I get faster upload speed than download so I reverted back to r391and all works fine again I was wondering if anyone else has the same problem or does the kernel have nothing to do with wifi also when using the updater the restore kernel doesn't seem to work it just reboots the phone but does not flash the kernel

Thanks Rob

Again awesome work no other kernel compares
[Samsung Galaxy Nexus] hotrodwinston:
Refused to boot on cm 10.2 for me - and even wiped out my /system partition.

Maybe I had a bad download - I'll try again.
[Samsung Galaxy Nexus] doomed151:
I used the fixed version by osm0sis.
[Samsung Galaxy Nexus] ASHURiCAN:
I see you have more memory than me, I have only 693! Same Nexus model, same nightly but different Kernel (CM native). Do you get this extra memory using Franco kernel ?

ASHURiCAN.
[Samsung Galaxy Nexus] metalspring:
Read the second point in the change log for 329...

r392:

* Fix SU problems. If your SU was broken before flashing r392 you gotta re-install it regardless

* Add the memory reclaim feature from mpokwsthsand boype (reclaims 50Mb from the YUV Tiler)

* Add a proper touch boost implementation 100% on the Kernel side. It boosts the CPU to 1GHz on touch for at least 250ms = 0.25s. The PowerHal is disabled since this implementation works only from the Kernel side. Interacting with the device should be smoother
[Samsung Galaxy Nexus] ASHURiCAN:
Thx, I think I missed a chapter! ^^

ASHURiCAN.
[Samsung Galaxy Nexus] SahilC:
Is this actually needed? I've never done it :eek:
[Samsung Galaxy Nexus] matteventu:
Flashed franco r392... coming from Fancy-pre44-3@1.4GHz... Franco is EXTREMELY more fast and smooth (with stock settings)!!

But battery drains a lot faster too... about 1% every 2-3 minutes.

Any tips? :)
[Samsung Galaxy Nexus] osm0sis:
Interactive tunables: hispeed_freq 729 should help. Default scheduler cfq has a bit of overhead too, maybe try deadline or row. Schedulers generally have negligible effect on battery though.
[Samsung Galaxy Nexus] matteventu:
OMG hispeed_freq is defaultly setted at 1.2GHz O.o

Setted to 729 now ;)

And what about input_boost_freq (1GHz currently) ?
[Samsung Galaxy Nexus] ChazzMatt:
Osmosis kernel reset script zip

Some kennels make a lot of changes to your system (AK is one). Previously the only way to undo that -- to flash a different kernel -- was to reflash ROM. This script simplifies the process of flashing different kernels, makes sure they're no conflicts.

No it's not always necessary. But if something is acting wonky, this is a great tool to have in your arsenal.

_________

Sent from my Galaxy Nexus i9250
[Samsung Galaxy Nexus] aeroxr1:
I'm going to flash 4.3.1 rom , crdroid v15 exactly . There are any incompatibilities with 4.3.1 rom ?
[Samsung Galaxy Nexus] hotrodwinston:
Redownloaded and everything works fine with 392 and 4.3.1
[Samsung Galaxy Nexus] SahilC:
I was surprised to find that the hispeedfreq was 1.2 ghz :eek: Edit: [MENTION=1578345]matteventu[/MENTION] Haha, right?

Lowered it to 700 mhz.

Edit: By the way, do you guys run hispeed at 1.2 Ghz? Doesn't it kill your battery?

Also, trying deadline. Would there be much of a difference?

Also, thanks for your reply [MENTION=3250376]ChazzMatt[/MENTION]!
[Samsung Galaxy Nexus] abalam:
I use row & interactive, fine combination for me
[Samsung Galaxy Nexus] ChazzMatt:
Well if your kernel CPU max is set for 1.2Ghz, makes sense hi_speed is also that value. :)

What you can adjust is how often and how long it hits that speed.

But when I want speed, I want SPEED. :)

_________

Sent from my Galaxy Nexus i9250
[Samsung Galaxy Nexus] SahilC:
Well said!
[Samsung Galaxy Nexus] devarajan_p:
Installation succeeds, but the old kernel stays

I've CM 10.2 nightly with the odak kernel. I installed Franco 189 on top it, and the installation went through alright. But the phone boots with the old kernel and not Franco. I've an LG P880 (Optimus 4x HD)
[Samsung Galaxy Nexus] osm0sis:
It's at 1.2 by mistake since the rebase. Should be fixed in the next build if Franco's following my email.
[Samsung Galaxy Nexus] Sik-1:
Wrong thread and def wrong kernel
[Samsung Galaxy Nexus] blackhand1001:
You guys definitely should look at this commit. It has to do with the wifi scanning dropping out. I think some other kernels have merged it but I don't think it has been on here.

https://github.com/anarkia1976/AK-tuna/commit/2d72cbe3d687c05039e1d5f1ef546721a0ad42f4

Referenced post: http://xdaforums.com/showpost.php?p=46402184&postcount=1050
[Samsung Galaxy Nexus] ChazzMatt:
What should it be at, as determined by the tunables testing you and the Franco Development Team did?
[Samsung Galaxy Nexus] buggerthis:
Osm0sis, your fixed version is running very well. Is there a reason you have hispd freq set to 1228 instead of 729.6
[Samsung Galaxy Nexus] hotrodwinston:
You better be glad it failed - you can't use kernels from other devices - they are not generic - they are device specific. Do some more research on kernels for your device before flashing.
[Samsung Galaxy Nexus] osm0sis:
729, and I don't, Franco does by mistake since the JB4.3 rebase, but it's something that needs to be fixed kernel side. My fixed "release" only covers the ramdisk stuff.
[Samsung Galaxy Nexus] SahilC:
Are the other interactive values fine?
[Samsung Galaxy Nexus] nickcct:
Love Franco default color. It's good for my eye :good:
[Samsung Galaxy Nexus] osm0sis:
Yep. They're all the ones like 12 of us in here worked out. :)
[Samsung Galaxy Nexus] SahilC:
Alright, so all I did was change the hispeed, and change back to my colors, and i have to say in all seriousness, my phone has never been this fast. I know everyone probably says that lol, but it's true.

I feel like buttons are almost getting pressed right before I press them haha.

I can't report on battery life yet though, obviously.

Thanks, everybody!
[Samsung Galaxy Nexus] hotrodwinston:
I'm getting a little over 2 hours screen on in spotty signal with Wi-Fi on constant - stock battery toro. Really good considering stock wouldn't make 1.5 hours screen on in the same house.
[Samsung Galaxy Nexus] Edward Stanbury:
Man I can't wait to update I'm on a rock climbing expedition atm back on Tuesday hope all is good ! :D
[Samsung Galaxy Nexus] erghetto:
which scheduler do you use guys? i'm interested in battery, more than performance
[Samsung Galaxy Nexus] thegtfusion:
deadline, i get around 3.5h screen on with a full charge. stock battery, maguro. rom: latest purity.
[Samsung Galaxy Nexus] osm0sis:
Scheduler doesn't really matter for battery. Just go with what feels best to you. Mentioned this like a page ago, please read. :)
[Samsung Galaxy Nexus] DoesntPostAThing:
Used to feel this wayk, can't say the same after I've used a G2 (at the store). I think I'll be picking up a N5 when it comes out, but for now my GNex is holding up fine.
[Samsung Galaxy Nexus] The Gingerbread Man:
Well the g2 is 2 years newer than our gnex and out specs in just about every way, natural progression through technology. I'd be more worried if you came here saying the gnex was smashing the g2 lol I think there will be a few of us migrating to n5 when it is released.

---------- Post added at 12:57 AM ---------- Previous post was at 12:50 AM ----------

Yup I would agree with that on the most part, battery life could be mildly effected through scheduler but not majorly. Deadline did prove to be fastest I believe and I guess the boost of io might tax battery through long intensive tasks over extended periods, but then there could be the argument that row for example with lower write speeds could take longer to complete said task. Personally for now I'm using cfq which is default and Google default for our lovely low ram devices

Perhaps as a parting gift Franco https://plus.google.com/109995262342451767357/posts/FqqPZcmdkeg ? As we about to expire 2 years