yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] AbhishekS:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I don't think the ROM I use (RasbeanJelly) supports init.d script.
[Samsung Galaxy Nexus] osm0sis:
franco.Kernel does, regardless of ROM.
[Samsung Galaxy Nexus] alexdemonumber3:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Well I'm running the full stock image for 4.2.2 and I flashed Franco with that, still unrooted, and wake lock issue seems to be gone. I got 9 hours with 1% drop overnight and not a single WiFi drop.
[Samsung Galaxy Nexus] matteventu:
Why is PegasusQ governor missing? :(
[Samsung Galaxy Nexus] sajty:
franco.Kernel never had pegasusq governor.
[Samsung Galaxy Nexus] lightingcloud:
I'm not sure I got how setting things via init.d work, so I'd like to ask for your help. If I push this file to the init.d folder, will it work correctly?
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

The file name might cause problems. Look in your init.d directory and see how the files are named... typically we use 900settings since that makes it run later than other ones. Also you have to remove the .txt extension before you push to your init.d folder and chmod -R 755

Franco r365

JBSourcery 4.5.5
[Samsung Galaxy Nexus] lightingcloud:
the init.d folder is empty, actually... I'll put 900 fjust to be safe, anyway. and remove the extension and all the other, thanks :)
[Samsung Galaxy Nexus] supernova_00:
Franco, does your kernel have ums (USB mass storage) support? I want to play music from my phone in my truck and I think have ums support is the key (plus an app) to letting me do that.

Does anyone know how I can check this with a command?
[Samsung Galaxy Nexus] Antob125:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Osm0sis is the sweet spot from 4.2.1 r364 still the same for 4.2.2 r365?

My numbers in fKu in order are as follows:

Max CPU: 1305

Min CPU: 384

Interactive

Max CPU Frequency for Screen off: 537

Gov Control:

above_hispeed_delay: 15000

boost: 0

go_hispeed_load: 95

hispeed_freq: 729

min_sample_time: 45000

timer_rate: 15000

target_loads: 85

timer_slack: 80000

boostpulse_duration: 80000

Deadline Scheduler

read_expire: 351

write_expire: 3500

writes_starved: 6

front_merges: 1

fifo_batch: 1

Anything out of place?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Looks good, only thing is the iosched tunables tend to not work via init.d unless you put in a sleep to make the script wait to perform the commands, so I'd put them at the end, with a sleep 35 before. Really though, those are the defaults in r365 so you don't need to set them via init.d at all.

So far we think so, yeah. malaroth and franco are still tweaking some things but they're pretty much the same. boostpulse_duration was 80000 in r364, and is 100000 in r365, but we always have boost set to 0 (off) so it doesn't matter.
[Samsung Galaxy Nexus] alexdemonumber3:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Anybody else getting the stutters with the notification bar on the home screen and lock screen after a few hours?
[Samsung Galaxy Nexus] ortrigger:
Franco and osm0sis,

I wanted to know if I could use your settings/tweaks for governors and schedulers to use in my kernel for the LG Spectrum. I didn't see anything that said no but I wanted to double check with you two and make sure.
[Samsung Galaxy Nexus] reysonance:
I'm not quite sure since it's an entirely different beast, the settings will work on the GN regardless of the kernel, but on a different device? I wouldn't hold my breath. Do try it out anyway for the sake of it though, would be interesting how different device react.
[Samsung Galaxy Nexus] ortrigger:
I'm just talking about the tunable values. I'm going to use them as a starting point and work from there as long as I have permission.
[Samsung Galaxy Nexus] reysonance:
Should work, but might not as nice as it was on the GN, I've been playing around with the GN Franco's default on my P-5100 and the difference is not as drastic as it was on the GN.
[Samsung Galaxy Nexus] osm0sis:
Free country/world, so no permission needed, I should think. I can't say for sure, since I have nothing to do with the kernel other than I helped test the values out along with joaquinf, The Gingerbread Man, and like 5-10 other people (for this round, and yellowdie of course for the original interactive tunables, and malaroth for the schedulers), so I won't speak for Franco, but I don't think there's a problem.

Either way, I'm with reysonance, it'll be interesting to hear how a different device handles them. When we tried them on the N7 we had to raise hispeed_freq and lower target_loads and go_hispeed_load to get the same smoothness and speed. The GN can handle them with hispeed_freq at 729MHz where the N7 can't. So there are definitely going to be some differences.

Make sure your kernel is using the latest interactive though, the one with target_loads, otherwise you might want to use our old "magic" tunables for the old interactive as your starting point. Let us know how it goes! :)
[Samsung Galaxy Nexus] Sik-1:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Cool idea, can't lie that I have been running these kernel settings on several other phones friends of mine have, an honestly they jus work, especially in the HTC sensation, but have to tweak the values slightly to get it right with the hot-plugging Qualcomm chips have versus ours
[Samsung Galaxy Nexus] ortrigger:
Awesome. I'll be starting work on that in the next day or two. I'll definitely post back and let you know how it goes.

Still loving this kernel, by the way. Honestly, I don't think I'll be changing any time soon...or forever for that matter.
[Samsung Galaxy Nexus] lightingcloud:
I'm on r364, waiting for Minco v7 (or v8, maybe).
[Samsung Galaxy Nexus] reysonance:
Try Mmuzzy's, a pretty good alternative for lean AOSP build like rascarlo's and minooch's, both which hasn't been updated to 4.2.2 AFAIK.
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

did you know Franco is involved in minco rom?
[Samsung Galaxy Nexus] reysonance:
I do know, I'm just suggesting an alternative from MiNCO?

Not to be taken as I'm driving people away from MiNCO...
[Samsung Galaxy Nexus] loudaccord:
I was fine on 13, went to 13.1 on the same rom and "modem_usb_gpio_wake" seems to be the only thing eating my battery... any idea what this is?
[Samsung Galaxy Nexus] Redflea:
13.1 is just the best yet for me...thanks, Franco, great performance and battery life, love it.

Wish you made kernels for the Touchpad too! :)

Sent from my HP Touchpad running ICS
[Samsung Galaxy Nexus] aron7awol:
Well, here's what I know:

The screen will use somewhere between 0.55 W and 1.44 W depending on brightness and what's on the screen. From 0.7-0.9 W is decent bet for average screen consumption on auto brightness or 50% brightness.

The CPU, on the other hand, uses about 0.05 W when idle and between 0.95-3.25 W when under 100% load. UV won't help reduce the idle consumption much. It is when the CPU is in use when it will make a significant difference. Because voltage is squared in the power consumption formula, I would expect reducing CPU voltage to 90% of original values to reduce CPU power consumption down to 81%. That is very significant at the high clock speeds especially, where the 100% CPU usage is going to be taking place a lot of the time. That's a theoretical reduction of power consumption at 1.35 GHz under full load from 3.256 W to 2.637 W.

I estimate that over the course of a day, my phone spends 15% of its time under a CPU load, mostly at the 1.2 and 1.35 frequencies. I also estimate that my phone spends about 50% of its screen on time under CPU load. Using those estimates as a guide, I would expect an UV to 90% to increase my screen on time by about 13%, say from 3 hours to 3.4 hours or 4 hours to 4.5 hours. I'm not really sure what my screen on time would be at stock voltages. In reality, I'm UV down to 80% of stock or lower, which should reduce loaded CPU consumption down to 64% of stock, increasing screen on time by 32%. Of course these are all hypothetical numbers, but they are based on ro_explorer's real measurements, so I didn't pull them out of my ass. As you can see, there is serious potential for UV to increase screen on time significantly. If stock screen time is 3 hours, we're talking about increasing that to almost 4 hours if you are UV to 80% of stock.
[Samsung Galaxy Nexus] Mondfahrer:
Hi guys,

I bought the 'franco.Kernel updater' and would like to know, if there are any recommendations for Undervolt and which Governor to select?
[Samsung Galaxy Nexus] jhericurls:
Well I don't know if its #13.1 or the UV (1125, 975, 875, 750), but I have achieved over 3 hours screen on time with 30% battery left. Which is a personal best for me.

---------- Post added at 09:02 PM ---------- Previous post was at 08:46 PM ----------

Did another simple test and my browsing time is now over 3 minutes before a percentage drop.

Also brightness is set to Auto, so a lot higher than previous test.

Nightly #13.1 with TeamKangs AOKP milestone 2.
[Samsung Galaxy Nexus] dpaine88:
Well I just spent the past few hours stress testing voltages and these are stable for me

1200mhz : 1125mV

920mhz : 975mV

700mhz: 875mV

Might try out the 350 slot but I have just been using the kernel with the stock freq's and gov so far.
[Samsung Galaxy Nexus] KyesaRRi:
Any chance we will see cifs support. It's the last thing I'm missing from my nexus one.
[Samsung Galaxy Nexus] nikosrs4:
do you use usb tethering? according to the name of it, it could be..
[Samsung Galaxy Nexus] dpaine88:
Nvm...these stress tested for an hour using "Stability Test" app but now I applied the voltages again and it freezes upon applying voltages everytime
[Samsung Galaxy Nexus] MountainX:
Can anyone confirm that these features are all present in this kernel?

usbserial driver <-- very important

tun for openvpn

nfs client + server

init.d

zram

option to undervolt

underclock/overclock

USB drive / keyboard / mouse support

If usbserial kernel module is not included, does anyone know where to get a compatible binary and how to install it in Android? Thanks
[Samsung Galaxy Nexus] MarcLandis:
Did you even read the title of the thread?

franco.Kernel | 4.0.3 | OC | UV | INIT.D | COLORCONTROL

Marc
[Samsung Galaxy Nexus] loudaccord:
I don't use USB tethering... That's the funny thing, I haven't had my phone hooked up to my computer, I do almost everything right through my phone. Not sure why USB anything would even come up. I tried rebooting my phone but it's still eating the battery. It isn't awful, I just know I could be doing better if this weren't occurring.
[Samsung Galaxy Nexus] thegtfusion:
so franco, you said you were working on a kernel for nexus S(you wrote in a post that you'd start the development on 2th of jan), but the kernel never came :(:(:(. can I assume you have dropped the project? :(:confused:
[Samsung Galaxy Nexus] dpaine88:
Nexus S is soooo 2011 ;)
[Samsung Galaxy Nexus] nrgaway:
Wrong thread :)

This is the Galaxy Nexus GSM thread
[Samsung Galaxy Nexus] wayneb02:
His kernels aren't all that anyways, u don't want him :D

(Just in case...its sarcasm)
[Samsung Galaxy Nexus] taney:
Purchased Market App. Thank you!
[Samsung Galaxy Nexus] jetrii:
Wow... My cell standby has gone from 4-5% time without signal in my house to 0%. The changes have really boosted my reception
[Samsung Galaxy Nexus] onyxogen:
Thank you very much for the detailed reply!
[Samsung Galaxy Nexus] akellar:
There's basically zero chance the kernel improved your reception.
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I run stock rom on both my gnex and n7
[Samsung Galaxy Nexus] reysonance:
Since you're using a stock rom on your GN, do you have this bug where the stock browser URL bar basically become unresponsive, goes pitch black after you refresh a page, and then erratically disappears, because that's honestly the only thing that keeping me away from stock ROM, I've cleared data+cache, factory reset, hell even reinstall the stock image and oddly enough it's still there.
[Samsung Galaxy Nexus] osm0sis:
I use the Labs quick controls in stock browser. Best way to get around, should avoid your browser bar issue too.
[Samsung Galaxy Nexus] reysonance:
Actually the problem start appearing after I enabled the quick control, so basically I have a 60dp thick stausbar, can't enter any search terms too since everything displayed on it basically sort of freeze, so if I delete a word the word doesn't actually get deleted, if a write a new one it'll overlap the previous text.

I'll try flashing 4.2.1 and updating via OTA, maybe that'll change something.
[Samsung Galaxy Nexus] LordDeath:
Sometimes my device seems to be very slow and the whole system lags terribly.

According to some task managers the CPU has ~80% iowait and I don't know which app or which wrong kernel setting could cause this.

Going back to the default CM10.1 kernel also does not change this. :(

Could this be caused by some tweaks done by the france Kernel updater? Or is this issue totally unrelated to it?
[Samsung Galaxy Nexus] julian.kueh:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Running 4.2.2 with Franco 365 here. No problems so far. Smooth and fast.
[Samsung Galaxy Nexus] lightingcloud:
I don't get it. This is my 900setting

same settings in f.ku

when I reboot, the values in f.ku are all changed to default (except color). why? ?___?
[Samsung Galaxy Nexus] shreddintyres:
I intend to start testing your values shortly, i just wanted to add what ive thought up regarding each of the different tunables, (Ive yet to have sufficient free time to really start messing around with each individual tunable and testing the way i would like to as a result of school. but here is atleast some of my theory on how the tunables MIGHT work

Config options

+==============

+1. hp_read_quantum: dispatch quantum for the high priority READ queue

+ (default is 100 requests)

+2. rp_read_quantum: dispatch quantum for the regular priority READ

+ queue (default is 100 requests)

+3. hp_swrite_quantum: dispatch quantum for the high priority

+ Synchronous WRITE queue (default is 2 requests)

+4. rp_swrite_quantum: dispatch quantum for the regular priority

+ Synchronous WRITE queue (default is 1 requests)

+5. rp_write_quantum: dispatch quantum for the regular priority WRITE

+ queue (default is 1 requests)

+6. lp_read_quantum: dispatch quantum for the low priority READ queue

+ (default is 1 requests)

+7. lp_swrite_quantum: dispatch quantum for the low priority Synchronous

+ WRITE queue (default is 1 requests)

+8. read_idle: how long to idle on read queue in Msec (in case idling

+ is enabled on that queue). (default is 5 Msec)

+9. read_idle_freq: frequency of inserting READ requests that will

+ trigger idling. This is the time in Msec between inserting two READ

+ requests. (default is 8 Msec)

+

+Note: Dispatch quantum is number of requests that will be dispatched

+from a certain queue in a dispatch cycle.

my difficulty is understanding lines 1-7 specifically when it references quantum. I've read the note and understand that Dispatch quantum has to do with the number of requests that will be dispatched(discarded?) in a cycle. What i dont understand is quantum referring to something similar to "entropy" that we see mentioned in most kernel documentation?

my understanding that increasing 1-7 will generally lead to lag and greater overhead while dropping it will lead to higher consumption of battery but potentially less overhead increasing overall performance

increasing 8 would lead to lag cuz the cpu would hang in idle longer, definitely increase battery life as power consumption at idle is negligble

increasing 9 would lead to lag and probably worsen battery life to some extent because read actions would take longer to perform and would introduce lag, reducing would lead to generally faster processing of read requests, (presently this is set at 20ms by Default in Franco kernel)

@malaroth i'd appreciate it if you could give me any more insight into what these values mean.

- Cheers
[Samsung Galaxy Nexus] osm0sis:
Your sleeps are commented out. ;)
[Samsung Galaxy Nexus] LibertyMonger:
I strayed away from the Franco for the last week or so and had nothing but problems. I am back now on r365 and I notice a great difference just over night. Battery is much better, only lost 3% overnight and have already sent a few texts and my issue with screen freezing up is gone. I know other kernels are performing well for others, just not me and i haven't quite grasped the knowledge of controlling kernels yet. Haven't taken the time to study up on it and really never had to fool with any settings in the past. I usually am content with the performance right out of the box and that's how I like it! lol. Thanks a bunch Franco
[Samsung Galaxy Nexus] sajty:
My experience:

Ondemand+deadline,384 min,10xx max,5xx max screen off.Screen is off and i have incoming mail with sound notification enabled.Sound is very "laggy" for first few moments,then goes normal.New email and happened again.

So i tried change scheduler to noop and problem is gone.Something wrong with deadline?
[Samsung Galaxy Nexus] ChazzMatt:
Interesting. Thanks for the suggestion. Hadn't heard of that one. I was running Xylon, but decided to go stock for 4.2.2. Before Xylon I was running a lite AOSP ROM, and think I really prefer that. Will try it this weekend, when I get some free time.

[ROM] [AOSP] MMuzzyROM for Maguro - Jelly Bean 4.2.2 - JDQ39
[Samsung Galaxy Nexus] lightingcloud:
With or without the comment, it still don't work. None of the command in the file. Should I put them in separate files?

Also I experienced some play store related freezes, and I noticed they happen ONLY when some app is updating/downloading and the screen is about to turn off. If I keep using the device everything is fine.
[Samsung Galaxy Nexus] malaroth:
It differs as to which scheduler you're using but they all use algorithms to determine priority. That's where quantum is referenced. It's pretty tough unless you're a math whiz to nail down the perfect numbers but... what I did with my values was to determine if the current row values were too tough on writes or not tough enough on reads. We want our devices snappy and smooth. We don't want to see the device "processing", just know that it's happening in the background. So with that said I decided to lower the regular priority reads just a quarter to not clog the whole io with reads. The lag is coming from writes not getting finished so I increased the synchronous writes (ones that merge together) in the order of priority I felt would be most beneficial without totally eliminating the row function of read over write. In fact increasing read_idle increases io throughput since the idle function is to wait for higher priority data that hadn't been served when the process started but came in between. So instead of sticking it back in the queue it goes ahead and processes it. Increasing read_idle_freq allows more processes to be assigned into that queue. Now the document you got that from states that the default is 8ms... that's not for android. Each device is different. For the Gnex it's 7ms and increases in increments of 8ms. On the n7 default is 10ms with 10 ms increments. We've found that one step above default is the sweet spot. When I first brought these numbers to Franco he was very skeptical. Then he did some hardcore io testing and the numbers just showed better performance.

Edit* this is from Linux-mag on cfq but illustrates how quantum works

"quantum

This parameter controls the number of dispatched requests to the device queue, request-device (i.e. the number of requests that are executed or at least sent for execution). In a queue’s time slice, a request will not be dispatched if the number of requests in the device request-device exceeds this parameter.

Franco r365

JBSourcery 4.5.5
[Samsung Galaxy Nexus] creeve4:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

The latest 4.2.2 builds of AOKP will not boot with r365. The propriety binaries/drivers have been merged, but just in case I flashed those listed several pages back. Still won't boot past the Google boot logo.
[Samsung Galaxy Nexus] julian.kueh:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I'm running mmuzzy's aosp 4.2.2 on Franco 365. No probs.
[Samsung Galaxy Nexus] Empty Hand:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

r365 is working fine for me on zaphod's toro build from today (up on Androtransfer). It's the first aokp build that it's worked on for me.
[Samsung Galaxy Nexus] creeve4:
Bad kernel download. I re-downloaded from f.KU app and all is good :)
[Samsung Galaxy Nexus] osm0sis:
Did you create the file on PC and copy to phone? My only thought is you have the wrong end-of-line formatting.

Just had to quote all that again to say, wow! Good read. Thanks for that brother! :D
[Samsung Galaxy Nexus] bigknowz:
Defaults changing

Are these tweaks being worked into ROW for r366?
[Samsung Galaxy Nexus] Khrushy:
Re: [KERNEL][GPL][GN] franco.Kernel

Great read Malaroth!
[Samsung Galaxy Nexus] bigknowz:
Deadline

Trying out Deadline Scheduler tweaks via script

read_expire: 351

write_expire: 3500

writes_starved: 6

front_merges: 1

fifo_batch: 1

Thanks for the suggestions. Are they purely for performance?
[Samsung Galaxy Nexus] reysonance:
@malaroth, I have been running your ROW tweaks for a full 24 hour now, initial impression is pretty good, there's noticeable improvement, although deadline is still a tad bit smoother, it doesn't struggle as much when writing apps to /data for example, I can still smoothly type on the keyboard (It still stutters though) while Play Store is updating a bunch of apps, as well as installing large games. Of course that's just some very basic testing without enough sample for a proper result, I'll try it for a few more days and see how it goes.
[Samsung Galaxy Nexus] ortrigger:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

So, I added some of the deadline tweaks into my Spectrum kernel and along with some tweaks to ondemand and it seems to be noticeably smoother.

Sent from my gnex running CarbonRom and Franco kernel
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Sorry Franco cut out my tongue and chopped off my fingers so I couldn't divulg info, typing with my nose. I don't know what is being implemented in any version so *shrugs* glad they're working good for y'all. I still like deadline better

Franco r365

JBSourcery 4.5.5

---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------

I'm not done with row yet... just gotta figure what's needed to work out the kinks. And you cfq fans....might be awhile it's being a pain in the osm0sis

Franco r365

JBSourcery 4.5.5
[Samsung Galaxy Nexus] aryan79:
I have a problem with the Franco Kernel. Time ago before applying an OTA I restored the original kernel and then I applied the update. But with Android 4.2.x even if I restore the original kernel saved before installing the Franco I always get an error when I apply the OTA? Any suggestions?

Thanks!
[Samsung Galaxy Nexus] AKA_noodle:
do u restore the stock recovery?
[Samsung Galaxy Nexus] aryan79:
Yes, I do a fresh install, I backup the original Kernel and then I flash the Franco Kernel. But when I restore the original kernel I can't apply the OTA

PS: the error is --> (Status 7)