yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] osm0sis:
You make your phone wait until it reaches 95% load to only bump it up to 1036MHz? Try making the hispeed_load lower to use it how it was intended.
[Samsung Galaxy Nexus] SUTHRNFRIED:
I will admit I was slightly confused on this one. The only sense I could make from all I read was higher loads conserve batt, lower spends battery. But I will def give your suggestion a try. BTW, installed newest Franco update and there's a new setting, input boost freq, its set to 1036800 where my hispeed freq is set to 1036700. Any ideas on what input boost is and how this should be adjusted?
[Samsung Galaxy Nexus] osm0sis:
Your hispeed freq should also be 1036800, anything less will make it use the next step (729MHz). A higher load will save you battery at the expense of a device that doesn't react, so if you think about it, setting it too high will make things sluggish. Input boost is a similar idea, and is the speed it jumps to when a touch is registered. This is intended up keep the interface as fluid as possible.
[Samsung Galaxy Nexus] yellowdie:
I agree with osm0sis. And btw, if you are ever curious about what the exact numbers should be (1036800 vs 1036700, etc), you can use a root browser (like ES File Explorer) and browse to /sys/devices/system/cpu/cpu0/cpufreq and read the file called 'scaling_available_frequencies.' There are other ways to find the exact frequencies, but this is the guaranteed manual way to see all of the exact steps that your kernel has. So yes, like Os said, 'hispeed_freq' should be 1036800 (or higher) and 'go_highspeed_load' be 50 as well. I would recommend 'input_boost_freq' be 1036800 and 'hispeed_freq' be 1228000 or 1305600. So when you touch your screen it jumps to 1.0Ghz, and when your phone starts getting some more use, it will move up to 1.2 or 1.3Ghz.

:) :D :laugh: :good: :highfive:
[Samsung Galaxy Nexus] RevengeFNF:
What is the difference between hispeed_freq and input_boost_freq?
[Samsung Galaxy Nexus] franciscofranco:
input_boost_freq is the frequency that the device boosts to if it detects a touch input.

hispeed_freq is the frequency that the device ramps to before going to the max frequency if it detects an increased load.
[Samsung Galaxy Nexus] loonsy:
After multiple issues with XDA App loading, stuttering unable to resume after task switching, I swapped to tapatalk 2 and has been a much greater experience.

Also runs smooth without problems on Franco.

Only problem I have with franco kernel is whenever I flash a new nightly I ocassionaly get boot loops and the only way to fix it is to boot to recovery, wipe cache dalvik and did permissions.

Additional info - running AOKP Build 3 and using TWRP 2.2.2.0 recovery.
[Samsung Galaxy Nexus] Antob125:
So what is the consensus, Google Now, ON or OFF?

Sent from my Galaxy Nexus

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

For battery reasons.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bradm23:
What is stock high speed freq again? Changed it and want to change it back to stock
[Samsung Galaxy Nexus] osm0sis:
I personally don't use Latitude or any of that nonsense (very important for battery) so I also leave Google Now off. I can still use the new Voice search and bring up cards from the knowledge graph, and that's the only "Google Now" feature I care about.

729000
[Samsung Galaxy Nexus] creeve4:
Agreed, Tapatalk 2 is MUCH better than the CDA Premium app, mostly because they actually update it with bug fixes and improvements!

You would think a development forum would have a decent forum app...
[Samsung Galaxy Nexus] saintpanache:
Noob question :

Does the kernel takes a couple cycles to really show what his potential ?

I'm asking because I've noticed that the second battery cycle is always better than the first on a new kernel.

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] Savant:
Yes it is better on the second cycle and then you can see the difference.
[Samsung Galaxy Nexus] !crazy:
I am on 276 and Franco's app reports input_boost not supported in this kernel version...

I have tried deleting the app cache and reinstalling both that app and the kernel but the issue still persists.

Anyone else noticed this?
[Samsung Galaxy Nexus] Blackcrx:
scroll further down and you will see "input_boost_freq"

---------- Post added at 04:16 PM ---------- Previous post was at 04:15 PM ----------

on the paid app, where do i find the option to change the i/o scheduler?
[Samsung Galaxy Nexus] chugger93:
anyone elses pandora not work at all? "Unfortuntely pandora has stopped" everytime the app is launched

I'm sure its not the kernel, I'm just trying to find other occurrences.
[Samsung Galaxy Nexus] Blackcrx:
try going to settings, apps, select pandora and clear data
[Samsung Galaxy Nexus] chugger93:
did that already...and tried going from 1.6 to 1.7 and vice versa from titanium backups i have

---------- Post added at 07:22 PM ---------- Previous post was at 07:21 PM ----------

I take that back. Sorry it worked! Thank you kind sir
[Samsung Galaxy Nexus] Blackcrx:
no prob... don't forget to hit the thanks button ;) haha
[Samsung Galaxy Nexus] !crazy:
Nowhere...
[Samsung Galaxy Nexus] Blackcrx:
any idea or reason why i/o scheduler isn't included?

I guess I still need NStools...
[Samsung Galaxy Nexus] osm0sis:
such complainers.. i wrote how to change the scheduler a few pages back. search the thread and rejoice in your new found knowledge.
[Samsung Galaxy Nexus] chugger93:
So check this out. clearing data works for pandora. However, if you sign out and exit the app, then go back into it...it force closes again.

Clearing data resolves it yet again, but if you listen to some music, exit and go back in...force close again. Its a friggin viscious cycle!!! ugh
[Samsung Galaxy Nexus] sotoskawasaki:
Just wanted to ask which governor is the default one. The standard interactive or dynamic interactive? And how do we change it? Thanks!
[Samsung Galaxy Nexus] BigBake88:
Standard dynamic is default and everything can be tweaked with Franco's app! Well worth the few bucks!
[Samsung Galaxy Nexus] k_nivesout:
Entirely OT but I have to say something: Your avatar is awesome :good:

Bringo!
[Samsung Galaxy Nexus] SUTHRNFRIED:
For your health you dingus!
[Samsung Galaxy Nexus] spartanhooah:
Bump.
[Samsung Galaxy Nexus] franciscofranco:
Because simply I didnt find the need to include it. I will add it when I feel I need to.
[Samsung Galaxy Nexus] Blackcrx:
Not complaining. Just asking. I know how to change it, I use nstools.
[Samsung Galaxy Nexus] Culex316:
I use the good old terminal emulator to change the i/o scheduler but don't know how to make it stick on boot.
[Samsung Galaxy Nexus] goTouch:
init.d script

Enviado do meu Galaxy Nexus
[Samsung Galaxy Nexus] ace-user:
isnt ondemand and deadline the default governor and schedule?
[Samsung Galaxy Nexus] goTouch:
Interactive and bfq.

Enviado do meu Galaxy Nexus
[Samsung Galaxy Nexus] Tarun95:
For some reason my phone is running great at m5 and I don't even feel like changing. BTW I changed input_boost to 1 and it reduced lag. Don't know if its because of that but this kernel gets more and more smooth the more I use it. :)
[Samsung Galaxy Nexus] koax88:
Battery after 2nd charge, Franco kernel latest beta

Stock interactive setting

as u can see, i rebooted my device once to flash tw launcher.
[Samsung Galaxy Nexus] tjackbjorn:
r276 should be a milestone. This is sick Franco, I've never experienced a kernel like this ! Suuuuper good work!

Sent from my super fast Prime filled with beans.
[Samsung Galaxy Nexus] Hessi93:
Am I the only one who get SOD with the latest nightlys? Even with #276.

Skickat från min Galaxy Nexus via Tapatalk 2
[Samsung Galaxy Nexus] arhung:
Sorry, a noob question, which one save more battery or have a better battery life? interactive or dyninteractive
[Samsung Galaxy Nexus] !crazy:
Too much OC?
[Samsung Galaxy Nexus] mrm43:
What is your rom and settings? So we can avoid it
[Samsung Galaxy Nexus] a5pe4:
LOL
[Samsung Galaxy Nexus] phishn:
I can't get Rayman Jungle Run to launch on CNA 3.6 or Sourcery 2.3 with latest nightly. Is the sdcard fix listed in the OP for GTA III, etc, for jelly bean too?
[Samsung Galaxy Nexus] gaich:
I don`t know what`s wrong, but something is wrong with wifi in 276. When I use it in my home net, everything is OK. But today went to a cafe, where I could not connect to the wifi. The indication was that the wifi is connected, it showed good sygnal, but the sign was grey and the browser cold not open any page, the weather widget either worked and showed no internet connection. I had similar trouble in another wifi network earlier, it was some version after 249, I do not remember well, I thought it was wifi spot bug. But this time I tried to fix it.

First I flashed r246, I had a zip on my phone - the same. Then I downloaded Milestone 5 via GPRS, installed it and everything went well- the internet connection appeared and worked fine...

P.S. I hardly managed to eat something in this cafe - I was too busy with my phone and internet connection!!!:D
[Samsung Galaxy Nexus] franciscofranco:
Grey bars is google services connection problem, not directly related to wifi drivers or the connection itself.
[Samsung Galaxy Nexus] gaich:
I know, but i tried to connect to different sites, not only google related.
[Samsung Galaxy Nexus] franciscofranco:
Probably faulty connection on the cafe that got fixed when you rebooted to flash M5.
[Samsung Galaxy Nexus] tjackbjorn:
I love the speed of r276. But I'm having a very bad battery drain... It sucks battery like no other kernel....

Sent from my super fast Prime filled with beans.
[Samsung Galaxy Nexus] yellowdie:
I would try flashing r276 again. Mine feels like it's not even using the battery at time. :) Last night I had ZERO wake locks in a 10 hour period of sleeping (I love weekends!) Dropped about 5% in 10 hours. This kernel is GREAT! :laugh:

And before everyone asks what my settings are;

http://xdaforums.com/showpost.php?p=31952301&postcount=27671

http://xdaforums.com/showpost.php?p=31957726&postcount=27686
[Samsung Galaxy Nexus] a1exus:
I've been playing w/ settings and I was wondering if it's possible to just do "reset" bring all settings to default?
[Samsung Galaxy Nexus] The Gingerbread Man:
This thread now causes xda app to force close hahabababab :D
[Samsung Galaxy Nexus] chrisgtl:
@franco

Is there any way of auto loading my colour settings when I reboot? My colours never stick so I currently go into your app and re-load my colour profile.
[Samsung Galaxy Nexus] J-Hop2o6:
Same here. It's that one certain post from earlier. It won't do it in landscape.
[Samsung Galaxy Nexus] franciscofranco:
Clear my apps data, should do it.

Change to SuperSu and colors will stick.
[Samsung Galaxy Nexus] numb_:
I have the same problem.. Colors don't stick at boot, I'm running minco v4 and SuperSu is updated..
[Samsung Galaxy Nexus] meanwhile:
With #276 in 48hrs haven't got a single data drop, that's kinda amazing for me

Sent from microwave
[Samsung Galaxy Nexus] chrisgtl:
I'm already using SuperSu. Using rascarlo latest ROM.
[Samsung Galaxy Nexus] tjackbjorn:
Thanks! Just reflashed r276, I'll see if that solves the problem! :) Gonna try it with your mhz settings! It's worth giving a shot :D

Sent from my super fast Prime filled with beans.
[Samsung Galaxy Nexus] The Gingerbread Man:
Ah here we go not force closing now we are on a new page

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Astug:
Same here, I got 65 hours standby, with data enabled 100% of the time, before I had to recharge.
[Samsung Galaxy Nexus] gaich:
Don't think so. Everyone around me was using their pads and phones, I hardly suppose they did it with GPRS. By the way, my mobile sygnal bars were grey too until I disconnected WiFi to download milestone. And I rebooted twice before doing this, nothing helped.
[Samsung Galaxy Nexus] The Gingerbread Man:
I guess the WiFi driver used in the nightly didn't agree with the host WiFi network and since the drivers have been changed quite a lot recently the drivers are different than m5 driver. As a suggestion you could download the .IMG of m5 and put it in your SD/kernel_backups and then switch when you wish to use that particular host if you use it frequently.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] gaich:
It's a good idea, but I certainly prefer the kernel to be universal for every WiFi spot I use, without switching backup images in every new place...:eek:
[Samsung Galaxy Nexus] franciscofranco:
Yep thats true, data drops are gone since I removed calibration on the lowest Core entry.
[Samsung Galaxy Nexus] The Gingerbread Man:
I see your point its perhaps not the most convenient thing is to reboot your phone in the cafe / pub but at least its only a reboot. Your phone won't take ages to boot like it does when you flash .zips. There is possible argument that it could be convenient because you could at least connect to the host, or switch when you know your going there and not tell your mates you need to swap kernel. That's all I can think of for now on that one

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] slvrarrow:
Is there a way to keep continuous data when the signal switches from 3g/h to 2g e.g. When driving and streaming radio? Or is that just how it works?
[Samsung Galaxy Nexus] gaich:
I see, I`ve just made a backup! To save some time to the food...:silly:
[Samsung Galaxy Nexus] The Gingerbread Man:
That's just one of those things you have to live with I'm afraid, only thing that could decrease the time disconnected is the quality and strength of signal local to you

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] slvrarrow:
Is there a way to force the phone to retain 3g/h for longer before it switches to 2g due to weak signal? Thanks again
[Samsung Galaxy Nexus] franciscofranco:
That's nothing related to the kernel. And I have no idea about that.
[Samsung Galaxy Nexus] friedCELLS:
Hey, just bought my nexus. Been flashing for years but for the last year, I had a low budget phone that had 3 developers & only 1 kernel. A little overwhelmed with the amount of choices here. I just read the OP & first ten pages & last 20 pages but can't figure out the difference between the 512Gpu & 384Gpu? Obviously, one makes the Gpu faster but is one recommended over another? One more stable? Thanks
[Samsung Galaxy Nexus] franciscofranco:
Think r276 is awesome? Think again. I'm not yet 100% satisfied so I'll bring some surprises for r277 hoping to close the gap into Milestone 6. More news soon after I do some testing, this is just a little something before I'm finished.
[Samsung Galaxy Nexus] mike216:
268 has been my favorite so far!

Appreciate you spending your Saturday night with us Champ :D

Sent from my OGparanoid CM D2tmo
[Samsung Galaxy Nexus] franciscofranco:
Hey welcome to the Nexus paradise island. Its easy: stock GPU is 307Mhz. My kernel comes in two flavors, one is 384Mhz (using the same voltage as 307Mhz), and another one at 512Mhz. If your device can run the higher clock with no issues then flash it. If you have artifacts with the high clock GPU just use the 384Mhz version. Easy as taking a piss ;)
[Samsung Galaxy Nexus] The Gingerbread Man:
Well here you well and truely spoiled for choice! The preference in gpu is really wether or not your phone can handle the extra speed, the 384 is stablest but youl find the 512 will perform better (smoother) but also uses a bit more battery. Try both and see what you think, weird stuff on your screen or random reboots or other strange stuff going on probably means your gpu cant handle 512 so use 384 if you find problems.

Ooh surprises, can't wait for this one already :D:thumbup:

You do make me laugh with the comments you make like that

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nuwan32:
just try both. if your phone cant handle 512, just flash 384. the 384 is more stable because its closer to stock clock and not all chips can handle 512 since its really dependant on the quality which may vary between chips.
[Samsung Galaxy Nexus] creeve4:
Running r276. I rarely use WiFi, but I had it on today and was connected to my in-laws WiFi. I turned the screen off for about 30 minutes and after waking the phone, it will not reconnect. When I open the WiFi settings it just shows: Searching for WiFi networks. When I tap the refresh button I get a popup which says: WPS failed, please try again in a few minutes. After 15 minutes still nothing...
[Samsung Galaxy Nexus] franciscofranco:
Ok I'll try to give you a hint, and I don't want you to think I'm being arrogant or a bastard, just a friendly tip: for the last 5-10 pages you've been one of the users with constant problems, either its Wi-Fi, or reboots, or something else. Don't you think the problem might be on your Rom or your apps? Seems just strange that for the last nightlies every one of them gave you problems while others don't have the same problems as you. Think about it :)
[Samsung Galaxy Nexus] mike216:
Good point. If I didn't see any other users reporting the same problems I definitely would kick that rom to the curb and fully wipe on the next one. This means format system, wipe data/factory reset and both caches!

No TB restore neither :D

Some users should take into consideration that if your willing to flash stuff on a 400-500$ phone its probably a good idea to read, read and read some more

Sent from my OGparanoid CM D2tmo
[Samsung Galaxy Nexus] creeve4:
Re: [KERNEL][GPL][20 AUG - Milestone 5][r196-ICS r276-JB] franco.Kernel | 4.0/4.1 |

Just trying to report problems I'm having. I've been running stock JRO03C for the last week, don't think its a ROM problem. Could be an app, although I only have a few utilities installed (Root explorer, To backup, quick pic, tapatalk app, your app, CPU spy, and nenamark2).

I tried turning off WiFi, but when I do the toggle immediately switches back on.

I have had multiple problems with the last few nightlies, but they have all been different.
[Samsung Galaxy Nexus] RoscoeDpG:
i keep thinking the same thing when i hear all the probs some are having i have not seen any of those *knocks on wood* but now bring on the next one! lol
[Samsung Galaxy Nexus] franciscofranco:
There you go, your Rom is old. I bet you're also not running the latest radio/bootloader. Although Google released that Nexus image we're already on JRO03R on AOSP so I suggest you double check your radio/bootloader and flash a different and updated rom like MiNCO or Rasbean.
[Samsung Galaxy Nexus] johno168:
maybe creeve4 has a really bad phone....
[Samsung Galaxy Nexus] The Gingerbread Man:
Try sticking to the safe bet milestones then as nightlies are experimental by nature. Or see if unchecking 'avoid poor connections' in wifi options helps. As the main man says m6 isn't far off now

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] creeve4:
Seriously? My ROM is old? UGLH1 radio and baseband. I do appreciate your work on this kernel, but you don't have to treat me like an idiot (granted I do not know nearly as much as you about doing development, I am learning).
[Samsung Galaxy Nexus] friedCELLS:
Holy crap! 3 responses in under ten minutes including from the dev himself! I am in paradise!
[Samsung Galaxy Nexus] johno168:
JR0O3R?
[Samsung Galaxy Nexus] The Gingerbread Man:
Dude chill the first thing Franco said to you was:

and why not try a different rom, the two mentioned by Franco are probably the best closest to stock and stablest out there Rasbean (not tryed but ICS version was excellent) and Minco where Franco actually is in partnership helping develop it with Minooch.

Sent from my Galaxy Nexus

---------- Post added at 03:12 AM ---------- Previous post was at 03:11 AM ----------

No monkey waiters with funny little red hats with silver trays of cigars though here though I'm afraid

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
I was trying to help the best way I could, but ok, suit yourself!
[Samsung Galaxy Nexus] creeve4:
I do appreciate franco's advice, but despite the preface, his words are a bit condescending.

I don't mean to be a pest, I just want to share my experience with the kernel. Maybe the issues are not always kernel related, but I'm not always sure so I share.

---------- Post added at 08:24 PM ---------- Previous post was at 08:21 PM ----------

I just find it a bit absurd that you suggest that the stock Google ROM is the problem. Maybe I am just an idiot, if so please forgive my ignorance.
[Samsung Galaxy Nexus] franciscofranco:
No one is calling you a pest or anything, I think you're misunderstanding my and the other users words, we're actually trying to help and believe me that these days I don't answer as much as I did a year ago. I appreciate your sharings, trust me a I really do, thats why I'm trying to help and I did gave you a good advice. Kernel developers/tinkerers whatever you want to call, usually go by patterns. For example in 100 users if 1 has random reboots, 1 has high battery drain and 1 has the famous "XX app FC'ed wtf!?" all of those are random ****s caused by other random factors other than a Kernel. If in 100 users 10/20 report high battery drain and the pattern is similar then its surely a Kernel ****. Your case fits in the first example because none of your problems don't fit in a pattern shared by other users thats why I alerted you to the fact that probably you have something wrong of malfunctioning in the userspace (rom universe). Beyond this theres few, if nothing, that I can do ;)
[Samsung Galaxy Nexus] creeve4:
Thank you, I will try to be more informed. I can understand your explanation.
[Samsung Galaxy Nexus] BigBake88:
Looking forward to 277, but at the same time 275/6 is so good I'm afraid to flash anything else!:cyclops: Franco, 276 really is a great kernel. Appreciate the hard work!
[Samsung Galaxy Nexus] franciscofranco:
r277:

* Remove Smartreflex calibration of all Core entries for stability: By default the voltages are 950mV, 1050mV and 1150mV.

* Compiled every TCP Congestion Algorithm into the kernel so now every user will be able to choose which one to use. Best to read this: http://en.wikipedia.org/wiki/TCP_congestion_avoidance_algorithm to know more about this Kernel feature. By default we use Cubic since thats what Linux Kernel uses by default. To check all algorithms run this command on the Terminal/ADB Shell: sysctl net.ipv4.tcp_available_congestion_control

To change the algorithm: sysctl -w net.ipv4.tcp_congestion_control=NAME_OF_THE_ALGORITHM

All of this will be available on the app in the future. Check the second post for a detailed speed test with all the algorithms - although they do much more than handling download/upload speeds. I don't know every single detail of every algorithm so you have to test for yourself and do some research to find your best option.
[Samsung Galaxy Nexus] Hungry Man:
I'll read up and wait for it in the app - thanks.

This core calibration thing, that's screwing with the voltages. I'll flash and see.
[Samsung Galaxy Nexus] J-Hop2o6:
+1. Might have to do some experimenting with this one. Hopefully this one won't give me artifacts from using the 512GPU that the previous 27X kernels were giving me. 26X-512GPU is running fine on my phone without artifacts.
[Samsung Galaxy Nexus] obsanity:
It always amazes me how much more new options and tweaks Franco can put into this kernel.

Thank you for all you do man.
[Samsung Galaxy Nexus] osm0sis:
net.ipv4.tcp_available_congestion_control = cubic reno bic westwood highspeed hybla htcp vegas veno scalable lp yeah illinois

Wow! Nice suprirse Franco! I've always heard good things about vegas.. DD-WRT uses it, for example. :good:

And yet it's one of the lowest performers on the throughput from your tests.. weird.
[Samsung Galaxy Nexus] Culex316:
First of all, thanks for continuing to push the boundaries as to what is possible with this kernel.

I tried entering that command "sysctl net.ipv4.tcp_available_congestion_control" in Terminal emulator but it didn't work for me (it says sysctl not found)..
[Samsung Galaxy Nexus] bigeyes0x0:
The answer to nearly every command not found on Android is either missing busybox and/or borked PATH env var.