yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] poopooface:
The big question is, what program are you using to download torrents? Ttorrent is completely broken and causes reboots like nobody's business. For me it caused a reboot every time I downloaded at over 80k/second. I know it may be because I'm undervolting, but if there's a version that makes better use of power and allows you some tolerance for undervolting, then screw Ttorrent.

I switched to aTorrent, and everything is great now. Not a single reboot. Ever. Switch to aTorrent and see if that doesn't solve your problem.
[Samsung Galaxy Nexus] macellaio:
Good idea, but I think this should be automatically done in the background whenever the governor is changed. You know how us end users are. Why leave it to chance?
[Samsung Galaxy Nexus] homer2320776:
I have the same issue as you, I'm running a rooted 4.0.4 that is pretty much stock. I use adb to boot into CWM w/o flashing it to apply all the patches because I want to keep stock recovery as well.

It's almost as if everything in the init.d folder is being ignored, I don't know enough about Android to determine why either. All the code seems to be correct in the init.rc file that points to busybox and run-parts so I don't know what else to do.

My first issue was that the franco.Kernel updater wasn't creating the init.d folder in /system/etc , after I manually made it, the updater program was putting the files there but they still were being ignored on reboot and when I went back into the updater, the setting were being reverted back to factory as well.

I'll keep reading the forums to see if anyone else has insight.
[Samsung Galaxy Nexus] eiabea:
is it still recommended to open and close the camera app after installing the kernel? :o

case since 16.1 i noticed that the Android OS is now again on the top of my battery stats with 49%
[Samsung Galaxy Nexus] king23adrianc:
if ur using 4.0.3, android os is not fixed yet. its fixed in 4.0.4 +
[Samsung Galaxy Nexus] kin24173493:
Is it the default kernel setting is 700-1000 in francogazelle without any hotplug enabled? thx
[Samsung Galaxy Nexus] monkey hung:
I'm still having horrible lag and finding my experience switching between turtle and gazelle not as fluid. Idk what was causing all the lag though. How do I show you the log that you need to see?

What I'm looking for is one governor (like how you set it to interactive or whatever it was before) and just leave it at that. I don't want to keep switching back and forth between governors and clock speed. So is there a happy median governor you could possibly conjure up?
[Samsung Galaxy Nexus] gravis86:
Yeah it's called Ondemand and it's the stock Android governor...
[Samsung Galaxy Nexus] Baguett:
ok sorry for asking this, but is the nightly build the only free one?

Edit: btw i went down from 6900 in AnTuTu score to 4000 after i flashed 16.1 kernel, wtf? i have choosed 1350mhz as max freq nad 350 as min.
[Samsung Galaxy Nexus] rolear8:
Damn,... really your picture represents you...

---------- Post added at 11:28 AM ---------- Previous post was at 11:24 AM ----------

Franco Kernel is free, just download it and flash it if you have 4.0.3
[Samsung Galaxy Nexus] Baguett:
So the nightly version is the one people use? i thought it only was an early, unstable version that only testers used. Weird that i actually got bader score in benchmarking after flashing this kernel though.
[Samsung Galaxy Nexus] ArmanUV:
I had the same lag with turtle with or without dynamic hot plug even with no apps installed. I data wiped and flashed 16.1 and aokp b22 with gazalle 350-1200 and hot plug and its silky smooth now.

No offence to Franco but I think I'm gonna stay away from dynamic hot plug until #17 or so.
[Samsung Galaxy Nexus] ArmanUV:
It is called nightly but it's as stable as it gets. The really expermintal builds are not posted in OP. Just download and flash 16.1 and enjoy. If you liked it buy Franco's app from market to support him.
[Samsung Galaxy Nexus] xclusiv8:
For a newb that i still learning, what is this hot plug you guys talk about?
[Samsung Galaxy Nexus] jdk82:
hotplug is a mechanism to turn off one of the two cores in your cpu under certain circumstances. If you want to know what these circumstances are I would suggest reading the entire first post (a good idea anyway if you are considering flashing a kernel;)).
[Samsung Galaxy Nexus] nikulogical:
I had no issues with 16 but with 16.1 I'm not going into deep sleep. I'm staying at 700 majority of the time. How do I check for rogue apps?
[Samsung Galaxy Nexus] xclusiv8:
What do you use to check if your phone is going into deep sleep?
[Samsung Galaxy Nexus] spences10:
Successssss!!!

Thanks mike1986, I'll update my thread in the General section

w00t!

---------- Post added at 11:00 AM ---------- Previous post was at 10:54 AM ----------

Yes and yes

It just shows the Google logo

What I'm going to try now is manually flash rather than via ROM manager

I feel a bit more confident about doing it now I have my recovery back :D

---------- Post added at 11:10 AM ---------- Previous post was at 11:00 AM ----------

Ok went into recovery

cleared dalvik

cleared cache

flashed kernel

Still wont boot :'(

It's not like it's bootlooping though it just shows the Google logo constantly
[Samsung Galaxy Nexus] mskip:
You shouldnt need to clear the cache and definitely dont need to clear dalvik.

Download the attached image which is just the boot image without the cwm packing. Rename it to francoboot.img (its not been zipped up just added .zip on the end to be able to upload it here) and flash in the fastboot screen using:

If you just want to test it first to see if it works then you can use:

which will only keep the boot image on your phone until a reboot.

Mark.
[Samsung Galaxy Nexus] chriscole:
Not working for me either...

Hangs at the google logo - when flashed with either fastboot or CWM.

Can talk to the phone over adb but logcat fails with:

Unable to open log device '/dev/log/main': No such file or directory

/prov/kmsg contains the attached if it's any use...
[Samsung Galaxy Nexus] spences10:
Hi Mark, have tried fastboot now too and still the same result

I can get into shell via adb but can't use logcat get error 'unable to open log device'

But I can navigate the file system via adb shell
[Samsung Galaxy Nexus] franciscofranco:
I think I know what it is, I used a different boot.img that might not be compatible with stock users. I'll fix that in an hour, not home yet.
[Samsung Galaxy Nexus] knzo:
I know francisco's work and I can tell you all that you are very lucky. ;)
[Samsung Galaxy Nexus] franciscofranco:
Serious update is coming soon, just doing the final testing.
[Samsung Galaxy Nexus] Tung_meister:
Ooooo sounds interesting!
[Samsung Galaxy Nexus] franciscofranco:
Very interesting. Benchmark wise, linpack:

stock: single thread: 42, multi-thread: 69

my kernel: single thread: 45, multi-thread: 77

Thats just the tip of the iceberg and a little taste of whats coming, doing some final touches before its out.
[Samsung Galaxy Nexus] mohitrocks:
Thanks so much for your contributions! I hear you're quite renowned throughout the forums :) Welcome to the Galaxy Nexus section :D Are you planning on making a complete rom or are you just supplying the custom kernel?
[Samsung Galaxy Nexus] franciscofranco:
Only kernels :)

Update is up please test it, its based on stock boot.img only with my kernel, so it should work fine with stock rom users.
[Samsung Galaxy Nexus] mskip:
Thanks soo much for starting development on the Nexus kernel franco it has been a pleasure to work with you over the past few days and we are definitely seeing very good improvements over the stock kernel.

Linpack scores are looking great after such a short time and the kernel is testing very fast and stable.

Lots more to come in the future im sure ;)

Mark.
[Samsung Galaxy Nexus] dwang:
Thanks working well here.

Whats the purpose of deleting /system/lib/egl/libGlES_android.so?
[Samsung Galaxy Nexus] franciscofranco:
Delete it, benchmark Quadrant and see ;)
[Samsung Galaxy Nexus] stickjohnonaah:
Can this be used with the Android revolution hd rom ? Mike made an late version for me to test.
[Samsung Galaxy Nexus] kfjunky:
Currently running.

Smooth as butter.

Ignore my signature, will update later.
[Samsung Galaxy Nexus] Hunteres:
+1

10char
[Samsung Galaxy Nexus] stickjohnonaah:
I'm using an LTE device. Are you?
[Samsung Galaxy Nexus] kfjunky:
As you can see in my signature, I'm using a GSM model, so can't guarantee anything for the LTE models.

Hope Franco can provide clarification for you though.

Cheers
[Samsung Galaxy Nexus] franciscofranco:
I have no idea to be honest. I don't know if the boot.img is different between GSM and LTE. Best thing to do is just backup your stuff and try this up. If it ****s up you can just restore.
[Samsung Galaxy Nexus] minooch:
You can still donate without having a paypal account.

you can use a credit card or bank account on the paypal website - there is that option :)
[Samsung Galaxy Nexus] ock:
Hi, just an update on the battery. I have been monitoring the idle drain for the 11 Dec build for the past 2.5 hours, unfortunately it still seems slightly heavier than stock. I'm using the non OC version, with no changes to governor etc.

From this graph attached, you can notice the slightly steeper slope towards the end. The almost horizontal lines were when I was using stock kernel.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
It takes a few charging cycles for the battery to be fine, it's a known fact ;)
[Samsung Galaxy Nexus] ock:
I do agree with that. :)

However, what's interesting is that the moment I flash back to stock rom, the drain dropped to 0.5-1%/hr, even without recalibrating the battery. To confirm this difference, I've done this alternating between stock and custom kernels for a couple of hours, and each time custom kernels use about 4%/hr with nothing syncing, and with screen off. I'll test other kernels to see if this is common to them too.
[Samsung Galaxy Nexus] beekay201:
grabbing latest now. flashed. all good.

btw, Francisco, have you thought about displaying date on kernel version, would make it easier to track history and incoming updates e.g. franco-3.0.13#YYYY/MM/DD?

my current UV. damn, this a nice phone. :D i wish all were like this, i really do. UV is a beatiful thing. can't go lower on 1200 though.

lol, you guys complaining about battery life? hahah look, that's from 100% to 51% in 5hrs. Who cares, almost everywhere I go daily there's a place to charge up if needed. Where do you people live/work anyway? Do you spend days without going home?

the last one it's what you wanted to see before, Francisco?

Sleeping. I'll check that other paypal **** tomorrow, too damn tired.

Edit: hmm.. just saw my first glitch/flickering, on screen unlock, and then another one inside xda app. Getting logcat now [multiupload]. Was messing with the phone all day long at work with franco#10122011, didn't see none.

Edit2: I did deactivate auto brightness when i got home, but checked a few things on the phone, phone was sleeping most of time (while watching anime ep of the week) flashed just a while ago..idk. really going to bed now.
[Samsung Galaxy Nexus] ock:
I'm not complaining, just highlighting the fact that it is possible for idle battery drain to be improved. (Just like the time when everyone was using Froyo bootloaders in i9000 CM7, and someone suggested a switch to GB BL)

I don't work long hours, and even if I do, I too have access to power sources ;)
[Samsung Galaxy Nexus] beekay201:
i remember that ;)
[Samsung Galaxy Nexus] darkstar2k77:
Thanks Francis,

My tests with 11 Dec OC kernel seems to get stuck at 1400mhz freq on boot up. Only starts freq scaling when I switch scheduler in setcpu..

Graphics glitch problem surfaced around 2hr after flashing. Had to force a reboot to resolve the screen issue..
[Samsung Galaxy Nexus] franciscofranco:
Thanks a lot for the logcat. As far as I can see there might have been to errors (I'm not a logcat expert):

First:

D/OpenGLRenderer( 442): GL error from OpenGLRenderer: 0x506

D/OpenGLRenderer( 442): GL error from OpenGLRenderer: 0x506

This one happened after a series of locking and unlocking, and like you said the first happened doing that, this might be the flicker problem:

Then I notice this:

D/libEGL ( 1643): loaded /system/lib/egl/libGLES_android.so

D/libEGL ( 1643): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_120.so

D/libEGL ( 1643): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so

D/libEGL ( 1643): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so

Do you have that file? If you don't then I suspect the flicker might be caused by the deletion of that file. This is all guesses, and don't worry everyone, there is a solution for everything :)
[Samsung Galaxy Nexus] kabauterman:
donation send! ;)

I love playing with Kernels :D

----

€dit: tested OC Kernel lately and Device was all the time on 1400 MHz no switching back to the lower profiles.

back to non OC and had no problem. maybe u need to check ;)
[Samsung Galaxy Nexus] 3c:
Same with 11 version: can't use 1400Mhz version, phone freezes all the time.

Got a weird glitch this morning (after a day or 2 using the kernel with stock ROM), pressed the power-button many times and it resovled. Though screen doesn't seem to switch off automatically anymore!? Set to 15 seconds, but stayed 1 hour on this morning (didn't rebooted after the glitch).

I do have that file, and still wondering why we have to delete it. So I used the phone without it for a day, then have put it back in, again for a day. Got a glitch this morning, so I imagined this was caused by that file? But you're saying it's the opposite?

EDIT: Forgot to mention I'm using this mod here (4x5 no search launcher) along with Paul's search MOD.
[Samsung Galaxy Nexus] franciscofranco:
I'm saying it might or it could, I'm not sure, I'm just guessing, but I can be totally wrong.
[Samsung Galaxy Nexus] Shetlander:
After using the kernel you posted last night over night I lost 21% battery overnight and when I woke this morning the graphical glitches where back.
[Samsung Galaxy Nexus] franciscofranco:
Can you get me Betterbatterystats stats please.
[Samsung Galaxy Nexus] schrickm5:
Uninstall Set CPU, then re-install. Worked for me. Check in Set CPUs - "Time in State" to see if % in 1400 comes down.
[Samsung Galaxy Nexus] Shetlander:
OK just bought it. Want do you want to know as I have never used it before.
[Samsung Galaxy Nexus] kabauterman:
Ok, worked, BUT

with the OC Kernel my GN is so damn laggy!

I've added even some extra voltage to the profiles but no change,

with 1200 MHz Kernel I get 75k in Linpack with 1400 MHz Kernel I get 29k in Linpack. Something is wrong there...
[Samsung Galaxy Nexus] minooch:
Good to see you can't read or search!
[Samsung Galaxy Nexus] kabauterman:
Sorry man, but of course your post makes less sense then my question...

I've seen in the other Kernel/Mod thread that the issues at 1.4G are "normal" but can't see a "overall"-fix for this. Maybe u better want to help and not to troll?
[Samsung Galaxy Nexus] Danny80y:
Guys, we all have better things to do than sitting here calling others stupid. The 1.4OC is not working on hardly any devices so if its not on yours you just need to use the no OC version. I'm sure eventually that will be sorted but at the moment there are other things that have a higher priority.
[Samsung Galaxy Nexus] nikulogical:
CPU spy.

I just force closed the camera app and it seems to be working now.
[Samsung Galaxy Nexus] sluflyer06:
How much have you guys (and Franco) looked into how easily the Nexus throttles with cpu temperature?

I've been messing around with sunspider for fun after installing Chrome and I noticed if I ran it back to back 3 times, it dropped measurably each run. (been using stock franco voltage @1.35ghz of 1.38v)

Just now playing with the 4.0.4 browser I got 1,711ms then lowered voltage to 1.25v and netted 1,643.
[Samsung Galaxy Nexus] nikulogical:
Err..nvm still not going as often as it used to.
[Samsung Galaxy Nexus] slide83:
Is there a place to download previous versions of this kernel?
[Samsung Galaxy Nexus] Shetlander:
Ive been messing around tonight (and screwed up my kernel) and noticed using 1.35Ghz and 1.2Ghz that when CPU temp gets to 72c it aggresively throttles the cpu.

Guess thats another reason why these chips run at 1.2 and not the 1.5Ghz as they cant cool them.

PS - Anyone have Nightly 15 test 4 as mine seems to be screwed somehow. It shows up as Kernel 16 Test 4. Im having real problems with hotplug at the moment. CPU 1 will not turn on with Francoturtle set no matter whats on or off. 15 test 4 gave me only 2ma drain so I would prefer to stick to that.
[Samsung Galaxy Nexus] :
Hi,

Here: http://www.world-of-nexus.com/download-section/category/4-franco-kernel

:)
[Samsung Galaxy Nexus] poopooface:
I already posted it some pages back.
[Samsung Galaxy Nexus] loudaccord:
I like your sig :)
[Samsung Galaxy Nexus] Shetlander:
Yeah found it. Thanks.
[Samsung Galaxy Nexus] chamonix:
t

You could take that kind of qustions to the BBS thread if you want to.

The first reading shows an enormous amount to alarms (wakeups).

The second reading shows that most of the awake time was caused by rx wakeps (incoming wifi packets). There are different possible causes from router to another host causing traffic. The easiest ways to get rid of that wakeups:

- turn wifi off when unused

- change wifi sleep policy ot "off when screen off"

- use wireshark capture traffic, find the roout cause and remove it
[Samsung Galaxy Nexus] hasnol143:
I am using atorrent...I'll give it another go without hotplug and see what happens.
[Samsung Galaxy Nexus] franciscofranco:
Tonight I'll drop #16.2 that will contain:

* Custom Voltage mod from Ezekeel patched up to his latest changes - for more information check his github repo

* Dynamic hotplug removed - this is a good idea on paper but CPU spikes up every other time while trying to check if cpu1 was online or not, and that is not expected at all. I may return to this implementation in the future if I think of a better way to do it

* 350mhz bumped to 400mhz and set as minimum frequency as default - for testing purposes, we'll see that comes from this

* francoTurtle will be the default governor again
[Samsung Galaxy Nexus] hasnol143:
thanks a lot for the update! I'll test the 400 MHz and see if its stable
[Samsung Galaxy Nexus] Elganja:
will an update come as well? I assume so to remove dynamic hot plug option...

also, please bring back the ability to change the download directory
[Samsung Galaxy Nexus] franciscofranco:
Yes that will be removed from the settings panel. At the same time I added the option to turn on or off cpu1 completely manually via two buttons to give the users some flexibility.

That will be added in the next update, it requires some extra coding which I haven't had much time to write due to personal life errands that I've been doing.
[Samsung Galaxy Nexus] Elganja:
thanks for all the hard work!
[Samsung Galaxy Nexus] franciscofranco:
#16.2 is out.
[Samsung Galaxy Nexus] ArmanUV:
Thanks! I love how frequently you post updates!

One question: Does gazalle jump from min to max frequency without using the intermediate slots? I am running gazalle 350-1200 and cpu spy shows only the 1200, 300, and deep sleep being used ffter one day of moderate use. 700 and 920 are not used at all.
[Samsung Galaxy Nexus] franciscofranco:
Exactly. Gazelle doesn't use any intermediate frequencies, only min and max :)
[Samsung Galaxy Nexus] Elganja:
+1 to whomever said you can update the app from market.android.com... no more waiting when an update comes out for Franco's app!
[Samsung Galaxy Nexus] b33zu:
OK guys this kernel or the glados kernel?
[Samsung Galaxy Nexus] king23adrianc:
What about hot plug mod? Does that act up bad or its a stable good to go mod??
[Samsung Galaxy Nexus] nikulogical:
I flashes 16.2 and it booted with francoturtle 700/1000 not 400. I'm gonna keep it at 700 and see what the consensus is with 400 before I switch to it. I hate lag.
[Samsung Galaxy Nexus] franciscofranco:
Hotplug mod is as fine as it ever was, I use it all the time.

It booted with 400min for me, you should have a script/app doing that.
[Samsung Galaxy Nexus] sakuhei:
I flash 16.2 downloaded from the link in op but after restart 16.1 is still shown up and the default is not francoturtle...
[Samsung Galaxy Nexus] johno168:
Not sure if this is just me but im only getting around 2 and a 1/2 hrs of screen with #16 and up. Going back to stability release 15.2 too see if theres any difference.
[Samsung Galaxy Nexus] samizad:
If you are using AOKP, make sure the Min CPU is correctly set to 400MHz in the "Performance" section of ROM Control.

Looking forward to testing #16.2. I did not get amazing battery performance with #16.1 :(
[Samsung Galaxy Nexus] Optimusg2x:
I keep getting random reboots with 16.2. Can someone upload 16.1?
[Samsung Galaxy Nexus] johno168:
Its just 2 pages back, and you could've searched the topic first but http://www.world-of-nexus.com/download-section/category/4-franco-kernel
[Samsung Galaxy Nexus] drawde40599:
16.2

16.2 is very laggy for me with default settings and other gov/ freq settings back to 16.1 so smooth
[Samsung Galaxy Nexus] Tubes6al4v:
On 16.2 now. To get things back to normal, uncheck set at boot, or change to 400/1000 francoTurtle in the app, as well as disable DHP, enable Hot Plug.

So far 400 has presented no issues. Screen on is quick, ramping up is good. But I am not an intensive user (no games, videos... er except for Ted Talks :p )
[Samsung Galaxy Nexus] drawde40599:
Wow Seriously??
[Samsung Galaxy Nexus] johno168:
View attachment 895359View attachment 895360

16.1, this is why ima go back to 15.2 stable
[Samsung Galaxy Nexus] nikulogical:
Yeah I know.. I just thought it would change as it was the default. I decided to change it to 400 anyways to test out and so far its just as smooth. I even did some gaming.
[Samsung Galaxy Nexus] yyz71:
Rocking this kernel with 4.0.4 and running super fast and smooth. Thank you Franco :-)

sent from pimped out galaxy nexus 4.0.4 :)
[Samsung Galaxy Nexus] nikulogical:
question - on francoturtle if set at 400/1000, will the cpu only move between 400 and 1000, or will it run at 700 if needed? Reason I'm asking is because I'm thinkin of upping the max to 1200 or 1350, but only if itll run at 1000 most of the time and go higher when it needs to. I don't want the cpu to be either running 400 or 1200/1350, don't think that'll be good for battery.
[Samsung Galaxy Nexus] opensourcefan:
My CPU spy shows it running at 700 for a little bit.

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

400 was just too low for me, was noticing some increased lag. I don't wanna sacrifice that much performance so save battery. 700/1000 Turtle is just on the fine line where it all works well for me. When I want a treat I go to Gazelle.
[Samsung Galaxy Nexus] johno168:
Hows the battery life with those settings for you? Screen time wise?
[Samsung Galaxy Nexus] tornado6:
Anyone getting random lock screen freeze? Running 16.2 and now reverted back to 16.1
[Samsung Galaxy Nexus] THE_KINGDOM:
does anybody else find that 15.2 just seemed to be the fastest and best battery life of them all so far?
[Samsung Galaxy Nexus] opensourcefan:
Haven't been running 16.2 long enough but on Gazelle with 14.2, 15.2 and 16.1 I got about 16hrs up time with no less than 3 hours screen time and with Turtle about 20hrs up and 3.5+ screen on. I do charge every night though so that is usually with 15-20% remaining. And there's usually 1hr of my up time playing some game that cranks on the cpu, heats the top back of the phone up quite good.

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

Ya, kinda. Was going to give 16.2 a couple days and see but 15.2 worked quite well for me.

---------- Post added at 10:11 PM ---------- Previous post was at 10:09 PM ----------

Not yet, been running it since it was released and have unlocked quite a bit. Which lockscreen you using. Slide, Face, Pin... I'm also back up to 700 instead of 400.