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

R370 with Os io script. Deadline schedule. Numbers varied alot and didn't nail any real reliable numbers but low end was 7mbs range and high end was the screen shot I gave. Either way it's alot faster now with the script. Thanks Os! Now we just need Franco to include it in r372 and possibly put the memory leak patch back in since it seems to be working fine.

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] Reechings:
Thanks so much for this! :) Was wondering if you could be more specific with the governor tunables as I am using the TricksterMod and don't know for sure which values are which for all of them. Cheers!
[Samsung Galaxy Nexus] osm0sis:
I think they still all match up except for maybe target_loads, which Franco just tacked on the end. Should be easy to figure out by the numbers at least. If not:

a_h_d / g_h_l / h_f / m_s_t / t_r / t_l :good:
[Samsung Galaxy Nexus] EDNYLaw:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

osm0sis (and whomever else contributed), just wanted to say that I flashed r371 and added the 950io to init.d and the play store lag is gone when updating apps and everything seems to be smooth and snappy.

Thanks for all the hard work and dedication to make this kernel even better. It's much appreciated by those of us who like to follow along but do not have the time to test. Keep up the great work, just wanted to say thanks for the effort!

Sent from my Galaxy Nexus using Xparent BlueTapatalk 2
[Samsung Galaxy Nexus] Gafanhotz:
Nice update, he merged the new upstream. But I'll wait for the next release, when "maybe" we can see an fix to the writing speed included on it.

(It's not "ok" to flash an script aside the kernel every time you flash a new nightly of your rom. ;) )
[Samsung Galaxy Nexus] osm0sis:
malaroth, pkgnex, Khrushy, shreddintyres, joaquinf, The Gingerbread Man, yellowdie, myself, of course franciscofranco; and that's just the short list. ;) Thanks to everyone who has tested and provided feedback as we've been experimenting.

Obviously. But our settings are the tests that become the defaults. It's the reason it broke (nomerges 2 made deadline and row feel amazing, only later did we find out it also crippled write speeds), and it's the reason it'll be fixed. So for now there's no reason to refuse to upgrade when you can just flash the workaround init.d script zip as well and fix it. It's a stopgap until Franco incorporates our newer findings.

New version of the zip up with better status text (cosmetic only): http://d-h.st/users/osm0sis/
[Samsung Galaxy Nexus] Gafanhotz:
Well, I'll give it a shot and use it until next "full-o-things" nightly (in theory I only update weekly), if FK update comes first, then the work is done. ;)

Thank you for all efforts! (You and everyone that tested the settings. :good: )

Flashed, and my word, finally it is as it should be. :D
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Well its safe to say 371 with the winning governor control and latest io scheduler tweaks is the best my gnex has ever felt and getting 8.9mbs write speed for those who care about those with overall score 7579 both from antutu having just run the benchmark once.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] dracon6ai:
Re:[KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Just to note r370 with winning govs and io fix is amazing also. Haven't tested with r371 but I think the memory leak patch that was removed for r371 wasn't causing any issues.

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] J-Hop2o6:
[KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

This, but can't wait for the next release with the correct values. But I'm on 371 using cfq + iosettings script, getting around 8000 total & 13MB/s write (after a fTRIM--8MB/s before TRIM) in Antutu.
[Samsung Galaxy Nexus] wavedashdoc:
Sorry Osmosis about the post a few pages back. I was on vacation.

I have been testing these tunables for a day now, getting excellent battery life with maybe just a tad drop in performance. (3hr screen time though :D)

Max Frequency: 1228 MHz (Testing 1305)

Min Frequency: 192 MHz

Governor: Interactive

Governor Tunables: 30000 / 0 / 90 / 384 / 4500 / 30000 / 80 / 80000 / 100000

IO Scheduler: Deadline

IO Scheduler Tunables: 351 / 3500 / 4 / 1 / 2

Read Ahead Buffer: 512

TCP: Westwood

Screen Off Max Frequency: 384

CPU Voltage 192: 795

CPU Voltage 384: 825

Color Multipliers: 152 / 184 / 173

RGB Gamma: 2 / 4 / 9

Disable CAB: Check

Trinity Contrast: -5

OMAP Gamma: Disabled

Brightness: Auto Adjust or Max
[Samsung Galaxy Nexus] nuwan32:
Re: [KERNEL][GPL][GN] franco.Kernel r371

Hey os, for some reason I can't get your init.d settings to work. I tried copying the file manually and setting permissions then I flashed the zip file you have. Neither of them worked. I then reset my Franco kernel app and still nothing. I'm on pa and r371. Any idea how to fix this? Thanks

Edit: I also don't have a sysctl file and on a side note r371 has been then fastest/snappiest for me so far, loaded up instantly after boot and didn't have to wait for it to settle, just fast in general :D
[Samsung Galaxy Nexus] Mikes30000:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Same problem here. Running AOKP
[Samsung Galaxy Nexus] :
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Thank you for fixing the IO deadlock!!! I'd kiss you if it wouldn't be weird xD
[Samsung Galaxy Nexus] Empty Hand:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I ended up splitting the script in two. I use the general tweaks from the first part, and use a separate script for the scheduler. It was the only way I could get both to work.
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Bump this up to 537
[Samsung Galaxy Nexus] Gafanhotz:
Tested USB OTG, working very fine, to NTFS drives you can use something like the Paragon NTFS that's on Play Store.

Thank you Franco! :good:
[Samsung Galaxy Nexus] nuwan32:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

So having it split into two init.d scripts works? As long as one is general tweaks and the other is scheduler?
[Samsung Galaxy Nexus] Empty Hand:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

The scheduler definitely works. I'm not positive, but believe the general tweaks script works too (I just delete the scheduler portion). I'm really just fumbling along with the scripts and maybe getting some placebo effect.
[Samsung Galaxy Nexus] nuwan32:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I tried the method you mentioned before, it didn't work. I mean I checked fku and the scheduler settings were the stock ones
[Samsung Galaxy Nexus] reysonance:
Clear f.Ku cache+data, apply the tweaks, reboot.
[Samsung Galaxy Nexus] nuwan32:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

As I stated in my first post, I tried that. I even updated busy box. Still nothing
[Samsung Galaxy Nexus] reysonance:
Try running the script manually from the terminal, if it doesn't work then it's the script, if it does work, then something else is overwriting the script.

su
run-parts /etc/init.d
[Samsung Galaxy Nexus] franciscofranco:
I'm really sorry about the IO bug. I'm trying to find out the cause. Even with the settings that Osmosis posted here few pages back I'm still seeing big derp on write speeds from time to time. Trying to find the cause at this moment.
[Samsung Galaxy Nexus] thegtfusion:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I hope you find it! I tried r371, but it wass still there. Why did you remove sio ? The lag is less with sio on other kernels..

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
I'm getting 10,0 MB/s now from Antutu write test. Seems the new hashtable patch for Block subsystem + old IO tunables = big ****.
[Samsung Galaxy Nexus] franciscofranco:
But for some reason I still get the deadlock when downloading a big app from the Play Store. Wtf.
[Samsung Galaxy Nexus] thegtfusion:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Try it with sio I/O scheduler, the lag is less on it

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Ok it seems ok now!
[Samsung Galaxy Nexus] wavedashdoc:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I did some tests and with 366 and up I can run 384 screen off with no SOD, missed notifications or music stutter. Plus better battery life 8) give it a try!
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Sounds good, if your releasing something soon please can you add the -discard to mount so we don't need to keep running fstrim and consider the testing of the io schedulers tuning to be set as defaults? There was something else bit I forget the exact name for it but it has been mentioned before by Os and its purpose was to help prevent bricked devices by flashing the kernel for the wrong device.
[Samsung Galaxy Nexus] franciscofranco:
Ok try r372 please.
[Samsung Galaxy Nexus] franciscofranco:
Good idea about discard, re-uploading it.
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Its called race to idle, faster your phone completes the task the longer it spends in deep sleep state which will increase battery life.

---------- Post added at 01:11 AM ---------- Previous post was at 01:09 AM ----------

Thanks, it has been mentioned before it wasn't my idea though it was Osmosis' I beleive
[Samsung Galaxy Nexus] franciscofranco:
My device is bootlooping if I add discard to the fstab.

Now it doesn't boot at all, nice.
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

As much as I'd love to help with that one my technical knowledge won't take me that far, Os or Malaroth might have some ideas perhaps when they get online
[Samsung Galaxy Nexus] franciscofranco:
Nah, its my installation that is ****ed. r372 works fine though.
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

So just to clarify does that mean given time it could work when you fix what ever is messed up or just not possible to implement?
[Samsung Galaxy Nexus] franciscofranco:
My device is ****ed up, thats all.
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

It might not be the -dismount that caused it as after flashing 372 I'm now in boot loop also. The changes I made before was to governor control, lower min CPU speed to 192 and running latest script for IO. I'll have to sort my gnex in the morning as running stock recovery and got to be up in 5 hours to take my gf to work....
[Samsung Galaxy Nexus] thegtfusion:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Use the omap_flash resurrector to revive it :D

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
I gotta re-upload r372 again, sorry folks.
[Samsung Galaxy Nexus] franciscofranco:
Its that discard yes, did a typo in the fstab, recompiling.
[Samsung Galaxy Nexus] thegtfusion:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

@franco:

Look

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

To revive it ;)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] The Gingerbread Man:
[KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Lucky he has a spare eh :D
[Samsung Galaxy Nexus] chickentuna:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Downloaded r372 at the first page, device doesn't boot. Stuck at bootscreen. Will wait for a fix

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

**** now I feel bad for asking you to add it. I hope your device survives and I'll fix mine in the AM

---------- Post added at 01:42 AM ---------- Previous post was at 01:40 AM ----------

Same here I posted this just before. Please everyone wait for the all clear by Franco before flashing 372 as there's a good chance you will

end up in boot loop!
[Samsung Galaxy Nexus] Gafanhotz:
After all that (yeah, I've read everything) the kernel is giving bootloops?
[Samsung Galaxy Nexus] thegtfusion:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

For now r372 yes, 371 not. Wait till franco reuploads it.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
There fixed.
[Samsung Galaxy Nexus] reysonance:
It booted up just fine here, and after a dozen of benchmark test it's clear the write speed is significantly better. Downloading a few large apps ATM to see if it still craps out, will report back.

EDIT: After a few downloading a few decently sized apps and games, no stutter have been encountered, it's all fine and dandy here :)
[Samsung Galaxy Nexus] osm0sis:
Hmm so discard or no discard?
[Samsung Galaxy Nexus] Fenvarien:
AW: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Same here, it's booting fine and a test installation from playstore worked fast and without any problems :good: :)
[Samsung Galaxy Nexus] franciscofranco:
No discard. I'm doing 10 things at the same time in the office, can't waste more time re-flashing my device if something goes wrong. Discard ****ed my rom twice.
[Samsung Galaxy Nexus] Khrushy:
3.72 Works. Noting a small but noticeable improvement in write speed. Good stuff ^^
[Samsung Galaxy Nexus] Gafanhotz:
About that init.d custom script, it will be removed automatically when I flash my next nightly of my rom, right? (Noobish question, but i'm serious.)
[Samsung Galaxy Nexus] reysonance:
Yes, the ROM.zip format /system, so it'll be gone with a simple dirty flash, ROMs like CM however, have userinit.d support, which is preferred, since the script is located under /data, it persist between dirty flashes.
[Samsung Galaxy Nexus] Khrushy:
Yes. /etc/init.d is wiped every dirty flash.

Unless you placed it in /data/etc/init.d (if your rom supports it) - that persists between dirty flashes.
[Samsung Galaxy Nexus] Gafanhotz:
I used the flashable zip by Osm0sis.
[Samsung Galaxy Nexus] reysonance:
Then yes, it will be wiped. You can move it manually though to prevent it from happening.
[Samsung Galaxy Nexus] Gafanhotz:
If needed I'll do that. Thanks.

------------

By the way, that's new. Antutu was giving me 8500 of score a while ago, with the r372 build it dropped to 7600. Is it with anyone else too?

(Maybe the init.d is conflicting with the newer kernel settings? I didn't noticed anything wrong in the scores.)
[Samsung Galaxy Nexus] osm0sis:
Damn that's really weird.. I had it set with init.d for awhile with no problems. :confused:

---------- Post added at 12:02 AM ---------- Previous post was at 12:01 AM ----------

The new settings are the init.d settings. :p
[Samsung Galaxy Nexus] Gafanhotz:
Oh well. Then I need to investigate the reason of the drop.
[Samsung Galaxy Nexus] reysonance:
Could be a lot of things, thermal throttling is the usual culprit, also try locking your min/max (or use the performance governor) to the max freq you want to test for a far more consistent results.
[Samsung Galaxy Nexus] thisguy23:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Am I missing something? R272 before and after script. Same results.
[Samsung Galaxy Nexus] Khrushy:
You're not missing anything. Franco put all the script values as the kernel defaults now.

Although, what's up with that terrible write speed? Something wrong there.
[Samsung Galaxy Nexus] thisguy23:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Right. The write speed should be much higher shouldn't it?
[Samsung Galaxy Nexus] Gafanhotz:
Changed governor to performance, the antutu hit 7900, locking the freq to min 1.2Ghz and max 1.3Ghz I got my 8500 back. Probably there's some instability on antutu calculations as well.

Writing speed here is 11.4MB/s! \o/

It should 10MB/s or more, can you trim (lagfix from play store) and run antutu again?
[Samsung Galaxy Nexus] Khrushy:
It *should* be in the 8-10mbps range, as long as your SD card isn't completely full.

Possible things to try:

1. Check you have at least 2GB free on your SDcard.

2. Run fstrim on your SD card if you haven't - https://play.google.com/store/apps/details?id=com.grilledmonkey.lagfix&hl=en

3. Disable the init.d script and reset your f.Ku settings (so basically resetting to the Kernel defaults) - maybe you've got a funky setting in there somewhere that needs to be cleared.

4. Try asking it nicely. Everyone needs a bit of encouragement now and then.
[Samsung Galaxy Nexus] mixtapes08:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Do we still need the iosetting script with the latest kernel?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] pkgnex:
cfq tunable trials

Anyone who wants to give feedback on some "bleeding edge" cfg tunables, feel free to give these a try:

quantum = 8

fifo_expire_sync = 62

fifo_expire_async = 125

back_seek_max = 12582912

back_seek_penalty = 1

slice_sync = 70

slice_async = 31

slice_async_rq = 2

slice_idle = 0

group_idle = 7

low_latency = 1

If you like them or hate them, please try to quantify why and post it!

Thx.:highfive:
[Samsung Galaxy Nexus] osm0sis:
Our general queue and row tweaks are f.K defaults now, if you want our improved deadline or cfq test values you still need the script.
[Samsung Galaxy Nexus] Khrushy:
If you use RoW, or Noop as your scheduler then you won't notice a large difference between using the script or not. If you use CFQ then the script has more recent settings.

Cheers
[Samsung Galaxy Nexus] mixtapes08:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

How about the sysctl.conf line? Do we still need it? Thanks in advance..

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Khrushy:
There was a post here, but it was banished to the pit for being filled with bad information.
[Samsung Galaxy Nexus] osm0sis:
Franco added that too. ;)

---------- Post added at 01:23 AM ---------- Previous post was at 01:21 AM ----------

Nah it'll interfere with the way Franco sets them too. Probably why we've always seen reports like "franco.Kernel and ROM x is soooo much better than ROM y."
[Samsung Galaxy Nexus] Khrushy:
I stand corrected. ^^
[Samsung Galaxy Nexus] mixtapes08:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Damn.. I love this thread :).. Thanksss.. :thumbup:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
su -c cat /sbin/fixtunapower.sh

;)
[Samsung Galaxy Nexus] J-Hop2o6:
?

And hopefully Franco adds in the newer CFQ and other values & tweaks.
[Samsung Galaxy Nexus] wavedashdoc:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Got 2 dead locks in a row while downloading an app from Google play on 372
[Samsung Galaxy Nexus] Kurre:
I were fooling around with the ramdisk some time ago and made some fstab testing and had same problems as you with discard option. It made my phone to bootloop and logcat went crazy. I were able to solve this issue by changing 'data' option from 'writeback' to 'ordered'. Dunno why but discard option in fstab seems to like that one. If using init.d script, it works with writeback option too. It's little weird :p

But, how is the brick bug issue fixed in kernel level? Would it even be safe to enable discard for everyone?

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] osm0sis:
:confused:
[Samsung Galaxy Nexus] Khrushy:
fixtunapower.sh is the script that stops the franco kernel killing off 3rd party launchers for memory reasons. I forgot about it entirely.

The CFQ settings and other tweaks will come when they're done I'm certain.
[Samsung Galaxy Nexus] ReAlives:
Pgm nexus doesn't work with this kernel does it?
[Samsung Galaxy Nexus] osm0sis:
Actually that's not in there anymore, not sure why. That file's original purpose was to replace the power hal so that under/overclocking doesn't get reset when the screen turns off; now it contains a few different things, latest being a good chunk of our iosettings script. :D
[Samsung Galaxy Nexus] Khizar:
not using this kernel but seen pgm issue reported in many kernel threads so wait for the app to be updated.. its an issue with the app and not the kernel
[Samsung Galaxy Nexus] IINexusII:
been a whole day now running 1125, 1025, 925, 800 (1200-350mhz) no problems :) ill report back in a few days with battery life, going good so far
[Samsung Galaxy Nexus] 1Speed:
13.1 seems to be giving me slightly better battery life than 13.

Thanks!
[Samsung Galaxy Nexus] nic85:
Try 1125,975,875 ;)

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] vick1377:
Wake locks

I have the same exact issue though after I flashed jame bond kernel on my stock rooted galaxy nexus. My battery stats show the same as yours. I posted on few forums but no concrete answer yet from anyone. Let me know if you have resolved the issue. I'm trying to get to the bottom of these wake locks issues.
[Samsung Galaxy Nexus] nic85:
4 hours of display :)
[Samsung Galaxy Nexus] loudaccord:
very strange, I see you're on VZW also... I wonder if it's a TORO thing.

---------- Post added at 04:44 PM ---------- Previous post was at 04:43 PM ----------

looks like your battery jumped off a cliff! lol
[Samsung Galaxy Nexus] nic85:
Massive usage :D install/uninstall and some backup in cwm

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] Stretlow:
I'll do some testing and report back
[Samsung Galaxy Nexus] stesmi:
Hi!

I am using 13.1 together with the (bought) Market app - works great.

But something I've noticed.

I started playing around with undervolting, that's how I found this issue. NOTE: I have verified the issue is there without undervolting at all.

If I set Min and Max frequency to the same value (350/350, 700/700, 920/920, 1200/1200) then it works as it should, if I set it to 1350/1350 it doesn't.

I noticed that when I was running StabilityTest the bogomips line was sitting stable at the same number all through the tests if testing any frequency BUT 1350MHz.

If I run it at 1350MHz it's all over the place, as if it's changing frequencies.

I went into the kernel app and set 1350 min, 1350 max. Then I went into CPU Spy and chose "Reset Timers". Then started up Stability Test and let it run for 2 minutes.

Results:

1350 MHz 0:01:19 62%

1200MHz 0:00:15 11%

920 MHz 0:00:19 14%

700 MHz 0:00:14 11%

Unused CPU states

350 MHz, Deep Sleep

Then I redid it but 1200 min, 1200 max. (~2 minutes)

Results:

1200 MHz 0:02:04 100%

Unused CPU states

1350 MHz, 920 MHz, 700 MHz, 350 MHz, Deep Sleep

I have tried using both interactive and performance as guvernor - no difference whatsoever.

I have tried reboots, etc, etc - no difference.

Is this a kernel bug ? A phone bug ?

// Stefan
[Samsung Galaxy Nexus] AdrianE46:
Franco, could you add a setting in the app to oc the gpu, just like cpu? Maybe even up to ~500mhz like trinity kernel? Would be curious what that must be like.
[Samsung Galaxy Nexus] mohitrocks:
Yeah, I'm also a huge fan of this kernel and the GPU kernel would be an amazing feature to have