yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] _chanstar_:
Built up to more than 10 posts just to give you some props Franco.

Kernel and App are working perfect. Installed SuperSU, BusyBox (Smart Installed Binaries), and everything is perfect. No issues as mentioned by others. Did what you did with r295 with Min Freq at 192MHz and UV'd to 750mV. Left the rest stock since you are the developer and that's how you released. If I'd want any tips on settings, I'd rather be configured the same way you have it configured.

Recommended this to all the peeps I know. Thanks broskie!
[Samsung Galaxy Nexus] MatthewYiu:
i have popping and clicking while listening using my bluetooth for audio (Sony MW600). Bluetooth seems to be more crackly and with mp3 listening which only happens like once an hour it feels like.

Getting excellent battery life with 295. got an hour 20 minutes of screen time, and i am at 55% now. pretty good in my book. :D

My settings are: Using CNA 3.8

max cpu: 1536

min cpu: 384

max screen off: 729

governor: interactive
[Samsung Galaxy Nexus] RevengeFNF:
After installing the last Franco Kernel App, i noticed Deadline was the default IO. Was not supposed to be BFQ?
[Samsung Galaxy Nexus] franciscofranco:
Wow... did you have any scripts running there?
[Samsung Galaxy Nexus] boki2911:
One more question, if r276 works fine on 4.1.2

whether 512 GPU consumes more battery gpu384
[Samsung Galaxy Nexus] gianton:
Yes, they are the scripts that come with CNA 3.8.0 ROM.

Here is the folder.
[Samsung Galaxy Nexus] BigBake88:
Franco made some changes to Deadline and made it default to get feedback I believe. This was only for the last nightly or two...

In theory, yes, a higher clock speed will always consume battery. That being said, I have ran both 384 and 512 and notice little to no increase in battery drain. Give them both a whirl and see which one you like best. :D
[Samsung Galaxy Nexus] franciscofranco:
Yes I dont control what roms pack, no wonder some people complain about my app not setting **** on boot... sigh.
[Samsung Galaxy Nexus] tibere86:
192mhz @ 750mv is giving me great idle drain.
[Samsung Galaxy Nexus] duduzinho15:
FRANCO I ASKED YOU A QUESTION AND YOU DIDN'T SEE :( I GOT SOME REBOOTS I UPLOAD MY LAST_KSMG, IF YOU CAN HELP ME :D http://www.4shared.com/file/A2-Qcl1i/last_kmsg_2.html
[Samsung Galaxy Nexus] osm0sis:
Holy ****.
[Samsung Galaxy Nexus] tgyberg:
Sorry, not loud enough! :p
[Samsung Galaxy Nexus] duduzinho15:
it's serious man, i need help, i got a 6 reboot per day :s
[Samsung Galaxy Nexus] ak:
The link require user/pass and account, can you use pastebin please?
[Samsung Galaxy Nexus] emd2009:
Lol someone help this kid please
[Samsung Galaxy Nexus] jltorrente:
Hey! Give him a cookie... that could help...
[Samsung Galaxy Nexus] duduzinho15:
i put the download for public
[Samsung Galaxy Nexus] ak:
.... link doesn't work for me .... :confused:
[Samsung Galaxy Nexus] Schneewitzchen:
Tss...why aren't you helping, instead of doing unnecessary post, which are flooding the thread.
[Samsung Galaxy Nexus] duduzinho15:
View attachment 1433487

and now man?
[Samsung Galaxy Nexus] emd2009:
I did help. I quoted his post so it wouldn't get buried.
[Samsung Galaxy Nexus] jltorrente:
I guess it was directed to me, it was just a silly joke (because of your avatar...) ... gosh, there are people that really must relax a little.
[Samsung Galaxy Nexus] franciscofranco:
I have no idea why you have reboots. It says it crapped out with PRM_RSTST=0x2 error. I can see this:

[ 3302.095916] LR is at hsi_mpu_handler+0x50/0x54

So my question is, are you overclocking, undervolting, forcing cores to go up and down via some app?
[Samsung Galaxy Nexus] duduzinho15:
my config is max1228 and min192 or 384
[Samsung Galaxy Nexus] franciscofranco:
I need you to answer all my questions, are you undervolting or forcing cores go up/down with some app?
[Samsung Galaxy Nexus] Antob125:
I have the same exact settings but im trying out 5/5/9/3 for performance like Yellow said. Past 2 days have been great on battery and super fast response times. This phone Flys!

Now I'm trying to figure out if I should use Deadline or BFQ. I've read up on them from the link earlier in the thread but still can't decide. Yellow, Franco, Osmosis, thoughts?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] duduzinho15:
only with your app
[Samsung Galaxy Nexus] franciscofranco:
Can you answer my questions please?
[Samsung Galaxy Nexus] BigBake88:
Can someone attempt to explain something to me. I feel like scrolling in the browser while on WiFi is slow and laggy, and almost feels like the page is "heavy" and I have to drag the page across the screen. But on 3g I feel like scrolling is significantly improved and the page practically floats across the screen. Any one else? Running latest nightly.
[Samsung Galaxy Nexus] duduzinho15:
I disabled mpu, iva and core smartflex
[Samsung Galaxy Nexus] Blackcrx:
I prefer deadline personally. I was running 4/5/4/3 before, I am currently testing 2/5/2/2 for performance and I love it. Battery is to early to tell tho. Give it a try and let me know how your battery does

Might consider going back to 729-1228 as opposed to right now which is 192-1228
[Samsung Galaxy Nexus] duduzinho15:
Smartflex disabled have some problem?
[Samsung Galaxy Nexus] _chanstar_:
I suggest you re-enable them to see if that's causing the issue.
[Samsung Galaxy Nexus] galakanokis:
Are you under-volting? Only reason to disable SR is to undervolt.
[Samsung Galaxy Nexus] ciprianruse88:
hy guys,

i have a question.the read ahead buffer size is given by the rom or the kernel because i was on DarkPA and after flashing latest franco nightly it showed me 1024 buffer size and now i've flashed normal PA and franco and it showing me 2048 buffer size.and one more thing...which buffer size is optimal to use?
[Samsung Galaxy Nexus] duduzinho15:
No
[Samsung Galaxy Nexus] dracon6ai:
I have heard mixed suggestions for that one but Jrummy's Rom toolbox app now has a benchmark test for SD card boost if you want hard numbers. Here's what mine show.

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] duduzinho15:
I wiil renable them

After i renable to now no reboots
[Samsung Galaxy Nexus] sk8oldschool74:
What rom are you running
[Samsung Galaxy Nexus] glennv17:
I'm onto r295 now, with a min/max of 192/1036, screen off max 729 and the default interactive governor (settings included).

My usual habits were min/max of 729/1228, screen off max 729 and the default interactive governers and settings of the past, however I've undervolted just a bit (100mV or so) and I've usually gotten about 4 hours of screen on time, give or take 15 minutes with my extended battery. The thing is, I've always had data turned off when I'm not using it, and I've generally had location/GPS turned off all the time.

I want to start using my phone properly again, leaving data and location on, using Google Now and things like that. I don't play games or anything, so I'm ok with 192/1036. Hopefully r295 and the new settings help me retain as much battery life as I can while I leave things on more often. Better keep up with this mammoth thread a bit more often I think! Had to go back 50 pages just to find yellow's explanations!
[Samsung Galaxy Nexus] nuwan32:
Hmm... gotta say I was skeptical about trying 5/5/5/2 but the difference just blew me away. Specially in the app drawer no micro lags whatsoever. Gonna test this to see how it fairs on battery, but it looks amazing!
[Samsung Galaxy Nexus] marcocsh:
Do you have the same music popping/clicking problem as mine when you use my settings?
[Samsung Galaxy Nexus] Antob125:
Had it on headphones today and on auxiliary and sounded perfect

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] tgyberg:
I've got these settings running now and my audio is great too. Flac files, youtube etc.
[Samsung Galaxy Nexus] pnut22r:
Franco

I know I'm not the only one thinking this. Can you add the release date next to the kernel in your app. That would be super helpful.
[Samsung Galaxy Nexus] Culex316:
Hey Franco..did you do anything to the GPU performance on this latest nightly? (specifically for the 512Mhz slot)...before I never was able to run it without seeing pixelated **** all over the place but now it runs smoother and I even notice a small framerate advantage in 3D benchmarks and games.....:D
[Samsung Galaxy Nexus] nuwan32:
Lol so you think he plans on a date to release a kernel? This is worst than asking for an eta, more your making him do extra work just so you can see an eta
[Samsung Galaxy Nexus] Ranguvar:
He was asking for release dates for already released kernel versions.
[Samsung Galaxy Nexus] yellowdie:
I think it was back in the 270's-280's, Franco fixed the 512 line by disabling the GPU (CORE) SR and raising the voltages. Prior to that people (myself included) would get artifacts (junk on the screen) when running 512, but after he fixed that everyone should now be able to run his 512 versions without issues. :)

'About Phone' shows the creation date. But honestly, how important is the date? If there's a new version, the app tells you; if there's not a new version, it doesn't really matter when it came out. I don't think pnut22r was asking for an eta (btw, the next version is being worked on now. ;)), but I don't think there's really a need to see that "oh my goodness, it's been a whole two days since this kernel was released! wow this old junk is crazy." :eek: lol

---------- Post added at 12:18 AM ---------- Previous post was at 12:05 AM ----------

The first two (5/5) are fine, but the last two (5/2) would be better as multiples. Try 6/3 or 9/3. If you don't remember what the numbers are, you can always check here. Enjoy. And let us know what you think when you compare the options. :)
[Samsung Galaxy Nexus] Wh1t3Rose:
No matter how I set my settings I get this ignoring choppiness while scrolling in tapatalk. Using 5/5/6/3 atm

Edit: Forgot I set max frequency at 729 a few days ago. Bumped it up to 1036. Seems better
[Samsung Galaxy Nexus] marcocsh:
Guys,

I revert to M6 and the problem is gone. I'd rather wait for the next nightly, r296 maybe?:rolleyes:
[Samsung Galaxy Nexus] Schneewitzchen:
After installing app version 7.1.4 all settings stick for me after reboot.

Thanks man :good:
[Samsung Galaxy Nexus] Hans QC:
LightningTweaks?

Are the LightningTweeks still valid?

I tried to run the script but it fails on /sys/module/lowmemorykiller/parameters/adj (permissions are 001, so this seems logical).

I'm desperately trying to get rid of the lag/jitters when scrolling through long lists with images. Tweaking the parameters in Franco's app doesn't help.
[Samsung Galaxy Nexus] franciscofranco:
What rom are you using btw?
[Samsung Galaxy Nexus] franciscofranco:
Random question what IO scheduler and GPU version are you using?
[Samsung Galaxy Nexus] Hans QC:
512GPU and deadline. I tried 384GPU, same problem.

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] crimmylol:
Have this problem too with 295, rom CNA, will wait for fix from franco. Thanks.
[Samsung Galaxy Nexus] milesmarrero:
Out of curiosity, was the high quality audio tweak in the kernel removed? I don't have the option to put it anymore, and I didnt see it anywhere in the changelogs.
[Samsung Galaxy Nexus] tetrakinitis:
It' on by default, on r295.
[Samsung Galaxy Nexus] fredryk:
Pardon my ignorance, but what are these "5/5/9/3" numbers you all are talking about? I don't know what setting this refers to.
[Samsung Galaxy Nexus] jerrycycle:
Refer back to page 3096 or there about.
[Samsung Galaxy Nexus] tetrakinitis:
Check this post,

http://xdaforums.com/showthread.php?p=33161912

Sent from my SmoothCriminal
[Samsung Galaxy Nexus] thegtfusion:
Franco, does this kernel have linaro? ( or is it compiled with the linaro toolchain?)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] timbck2:
I have a confession to make. I just tried out the new Affinity Series Zen kernel. I like the ROM so much I thought the kernel would be awesome too. That was an hour ago, and I'm already back on Franco r295. The other one wasn't anywhere near as fast and smooth as Franco's. The difference is astonishing! I'll never stray again. :D
[Samsung Galaxy Nexus] morfic:
Look at the bottom string in cpuspy or:

cat /proc/version

To see which gcc was used to compile kernel
[Samsung Galaxy Nexus] Fenvarien:
With app version 7.1.4 I see every ~30 minutes the SuperSU popup message that Superuser rights are given to fKU.

Is there a new background service running? I wiped cache/data and uninstalled f.KU, but even after a fresh install from Playstore I get this behavior.

GNex with franco.Kernel / MiNCO ROM v5
[Samsung Galaxy Nexus] joaquinf:
Open SuperSU

Disable SuperSU notifications

Profit :p
[Samsung Galaxy Nexus] marcocsh:
The great Minco V5, boss:good:
[Samsung Galaxy Nexus] franciscofranco:
Yep, I just realised I forgot to stop the boot asyncTask. Thank you.
[Samsung Galaxy Nexus] osm0sis:
Actually, if I recall correctly, it was above_hispeed_delay and timer_rate that would be better as multiples. :good:

Edit: yup! :)
[Samsung Galaxy Nexus] Paragon_X:
Just thought I add, I had usb charging disabled, I took it off and no longer does the msg popup but I had similar issue.
[Samsung Galaxy Nexus] yellowdie:
Ah, you're right. So "high octane" should be 3/5/9/3. And normal is still 6/7/6/3. How are people feeling about those in real world experiences? Anyone comparing the two want to share?

Edit: I am still shocked that I am running 192MHz as my min. I was Mr. 729 min! Kinda weird, but I am totally cool with it. :)
[Samsung Galaxy Nexus] osm0sis:
I can't find any settings (including Google stock) that make the "speedbumps" in browser scrolling disappear. Not sure where that changed or if it's something that's always been there we're only noticing now since we're getting very scrutinous over little things. :p;)

Running your original "high octane" things did feel a little more snappy, but I noticed that the 384MHz slot pretty much never got used since it was jumping to the hispeed_freq of 729MHz too often. Maybe that was the idea though.

Last few days I've been experimenting with the "multiples" thing, like 5/6/5/2.5 and 4.5/6/5/2.25. The latency thing was never set in stone, especially since 30ms is only the maximum and actual transition latency could be closer to the default of 20ms or somewhere in between, so I thought I'd try somewhere in between too. :good:

Of course I've gotten sidetracked from that with our other testing, and 512GPU isn't the best to judge on, so I'm waiting for the next nightly to get back to that idea.
[Samsung Galaxy Nexus] BigBake88:
Yep 290 I didn't have the speedbumps. Interested to see the next nightly as well to see if scrolling is improved. Also, Franco are we ever going to get a change log for 295? Just curious...
[Samsung Galaxy Nexus] blipp:
I have the vzw GNex, and after I upgraded to the latest nightly, if I haven't plugged it in for a while and then go to charge it it reboots. Happens a lot. I'm also on the latest Bugless Beast.
[Samsung Galaxy Nexus] ChazzMatt:
if you like that, try 1228 MHz max or even 1305 MHz. :victory:

I have mine set for 384 - 1305. Used to have it at 729 - 1305, but minimum 384 is actually OK for me.

---------- Post added at 03:45 PM ---------- Previous post was at 03:36 PM ----------

Why? :confused:

So, you see rxx1 was released July 19, 2012 and rxx8 was released August 15. How does that help anyone? All those are pre-milestone 6, which was released in October 2012.

You are either going with the latest milestone or a recent nightly -- and it doesn't matter the exact date it was released. If you like a particular nightly, the paid app even allows you to save a kernel image so you can test another one, then revert. We've been on r295 nightly for a week or so now. Doesn't matter when it was released -- it's currently the best I've used. I even upgraded my wife's Nexus from Milestone 6 to r295.

(Edit. Doing a search shows r295 was first mentioned by Franco Oct 22, that he was TESTING it. I don't care when it was released. We have it now.)
[Samsung Galaxy Nexus] stick1300:
I'm getting the USB Charging Enabled notification multiple times since the latest update. I've seen it three times in the last hour. I also noticed a slight screen blink before it appeared once, almost like the app is crashing and restarting.
[Samsung Galaxy Nexus] ChazzMatt:
I was 729 min too, because of you. I've now racheted down to 384 MHz as minimum -- but I'm not following you down to 192MHz! :)
[Samsung Galaxy Nexus] osm0sis:
Just rolled back to r290 to see if I could confirm that, but unfortunately I can't :(

It's definitely still there, though it may be slightly less apparent. Here's what you can try though: Default Google tunables - 100k/50/729/60k/20k/1036; as well as bfq scheduler, and min freq 384.

The lowest min of 192MHz might be part of the issue (r290 was 230MHz, of course), bfq was smoother than deadline before the recent tweaks for paging through the apps drawer, so it might also help the browser out slightly, though I don't see any real difference between the two in-browser, even on r290 where deadline wasn't optimized yet.

If you are right about not experiencing it until after r290 that does narrow it down nicely in terms of commits: http://github.com/franciscofranco/Tuna_JB_pre1/commits/4.1

Only 11 since r290.
[Samsung Galaxy Nexus] franciscofranco:
Yes, I'm working on it already, patience please.

In the last 48h yes.
[Samsung Galaxy Nexus] ChongoDroid:
I got my best usage battery life so far. I've also changed a few things though like wifi scan time etc.

View attachment 851281

Edit: accidentally deleted the total times screen grab. Roughly 15 hours up time and about 20% was due to "Android OS"

Also my screen brightness was around 30%

Sent from my Google phone
[Samsung Galaxy Nexus] littleasian:
can i flash this kernel on a stock gsm galaxy nexus running 4.0.1? my phone is rooted/bootloader unlocked
[Samsung Galaxy Nexus] samizad:
No. Strictly for 4.0.3.
[Samsung Galaxy Nexus] ChongoDroid:
4.0.3 is in the thread title so i'd hold off until someone smarter then I mentions otherwise.

Edit: Samizad beat me to it :P

Sent from my Google phone
[Samsung Galaxy Nexus] rabhw:
Read the first post in the thread.
[Samsung Galaxy Nexus] dpaine88:
Not sure if this is kernel related or not,

I was using PowerAmp to play music today and everytime I got a text, it would pause the music as it should. But the SMS notification sound was very choppy and drawn out.

I noticed this with both hotplug off and on.

Running stock settings, 700-1200 conservative.
[Samsung Galaxy Nexus] esoomenona:
Try rebooting and see if the problem persists.
[Samsung Galaxy Nexus] yohinomura:
Running aokp build 15 and Franco kernel build 11, is it better to turn on power saver feature from aokp to have better battery life such as turn to 2g while screen off or we turn it off to avoid any conflict with the kernel?

Thanks for advise.
[Samsung Galaxy Nexus] franciscofranco:
New franco.Kernel updater patch 1.7 https://market.android.com/details?id=com.franco.kernel

Added interface where a user can choose where to save the kernel .zip. It may contain bugs, so if you find any strange behavior please email me with a bug report. Although if you do things with care it will be fine!
[Samsung Galaxy Nexus] s2d4:
have a look inside the actual settings, rather than just the the check to enable power saver..

maybe have a look at what a kernel actually means as well :)
[Samsung Galaxy Nexus] chakra:
Your link is not working to the updated app.
[Samsung Galaxy Nexus] Vangelis13:
No drain whatsoever??? Come on man, how's that possible?

Tried once with stock, no apps, airplane mode and still had 4% in 6 hrs I think..

By all means, I'm not saying you're lying! How do you achieve that though..?
[Samsung Galaxy Nexus] samizad:
I think he means his battery percentage remained at the same figure rounded to the nearest percent (i.e. battery drainage was less than 1% over 9 hours). Still pretty impressive.

On another note, is it true that a new kernel need to "settle"? After installing #11, I am seeing a gradual drop of battery usage from -313mA to -58mA over a one hour period. Hopefully it will keep dropping to the tiny numbers you guys are getting.
[Samsung Galaxy Nexus] thejosher:
Heya, thanks for your amazing work with this kernel — it seems to really like my phone.

I'm trying to donate by purchasing your app, but I'm getting an incompatibility message from the market. I'm running Codename Android ROM currently. Is this something I should report to you, or the ROM devs?
[Samsung Galaxy Nexus] Redflea:
It's under Kernel Settings... Thanks, Franco.
[Samsung Galaxy Nexus] franciscofranco:
Dunno, I'm just careful of what **** is running on my phone when I want it to idle. Yesterday in 16h without charging I lost 30% battery...It just can't go better than this, it's beastly.

It will settle, just make sure you don't have apps holding wakelocks or settings ****ing phone idle state.

Rom devs, something in the build.prop that is ****ed up ;)
[Samsung Galaxy Nexus] yohinomura:
Sorry bro, I'm just too stupid to understand. But if I interpret it correctly, there is no connection between the ROM power saver and kernel. Correct me if I'm wrong.
[Samsung Galaxy Nexus] thejosher:
Woops, looks like I was behind the times. There was an updated version of the rom with a fixed build.prop. Working now, and purchased!

Thanks for the quick reply, tho :)
[Samsung Galaxy Nexus] dpaine88:
So I havn't used Battery Monitor Widget before coming to this thread and there are a bunch of settings, are there any settings I should be aware of when running it?
[Samsung Galaxy Nexus] Schneewitzchen:
I think it's because of Franco doesn't stop the task mentioned above. Probably it's being fixed in the next app release.
[Samsung Galaxy Nexus] kmjo29:
I'm getting high android system percentage on my battery stats. Anyone know what maybe causing it?
[Samsung Galaxy Nexus] Shadow-Nexus:
I'm having weird behavior with 295

I have it set to 192 min and 1035 max with interactive and sometimes it will go all smooth without lag and some other times it will just lag like a motherf***er

Any tips?

Should I bump up the min to 384? Or the max to 12xx?
[Samsung Galaxy Nexus] CaspaTheGhost:
Don't speak to soon mate, I'm 729 crew but Yel and Os going on a testing bonanza got me to try stock 384.

I'm just about to give 192/1305 a whirl with the performance gov settings.

Finally succumb to the itch caused by Yel and Os!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] BigBake88:
Well mine is weird. Im on 3g now and the scrolling in the browser is butter. No lag no bumps. But as soon as I get on WiFi scrolling is significantly hindered. Speed bumps everywhere, micro lags, and the page feels heavy. Can't explain it. Is this what you have?
[Samsung Galaxy Nexus] osm0sis:
Try turning off the screen and turning it on again. Does it become smoother? Might be the Reduced Touch Sensitivity Bug. That's the only time things ever feel heavy for me.

For me, it scrolls fast just fine, but the slower speed scrolling is just barely perceptibly jittery, with "speedbumps" when it hits images. I'll check out the Mobile vs. Wifi thing. Do the settings I gave you to try help?

Edit: No difference on mobile data for the issue as I'm seeing it.
[Samsung Galaxy Nexus] BigBake88:
I'm trying the settings you gave me now. Thanks for checking that out Os. I'll report back...
[Samsung Galaxy Nexus] franciscofranco:
Dont use 192mhz or either change interactive settings to make it aggressive scaling.
[Samsung Galaxy Nexus] osm0sis:
I just did some more testing. Page 3100 of this thread really seems good for exhibiting the "speedbumps", especially around tetrakinitis' avatar pic. Tested a few settings and raising min freq to 384 seems to help the overall jittery feel, setting hispeed_freq to 1036 seems to help decrease the severity of the "speedbumps" at images, and changing scheduler to bfq seems to help the pages feel less "heavy".

Did these tests with Google default governor settings 100k/50/60k/20k.

I'm sorry to say but I think 192MHz might just be too low. 230MHz may have been the limit while keeping things running relatively smooth. :(