yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] osm0sis:
franco.Kernel-tuna-nightly-r390-fixed (v2)

New version up that has SR disabled on boot. Should resolve most if not all problems we were seeing with the original r390 and my first fixed version.

http://d-h.st/users/osm0sis/jb4_3/

I can even UV with f.Ku again: Blanket +/-25mV works fine now; f.Ku still says it's going by 50mV at a time with the +/- on each specific voltage, but if you tap out you see it's only going up/down by 25mV, so it's just a display issue on f.Ku's side and will work fine if you keep that in mind and check after each step.

[MENTION=3292224]franciscofranco[/MENTION] SR being on was definitely responsible for the freezes+reboots there and hopefully someone can confirm with 192MHz as well.
[Samsung Galaxy Nexus] The Gingerbread Man:
Os can you remind me which one of the scripts contained the file for helping reduce launcher redraws please. Apex is getting annoying, almost every time I press home espically after sending an SMS it redraws and using the built in unkill-able mode creates one of those annoying on going notifications like noozy does when its active
[Samsung Galaxy Nexus] osm0sis:
LMK Whitelist is built into f.K so you shouldn't need an extra script... that said the whitelist is extremely finicky, so you could go ahead and try 975experimental to see if you can get it working, if it isn't now.
[Samsung Galaxy Nexus] TiagoRigueto:
=O

1800mhz??

is possible?? use daily?? not brick??
[Samsung Galaxy Nexus] misterk267:
Don't do it man. I fried a battery awhile back doing that. :P. Can't say for sure it was the clock speed, but I wouldn't take any chances. xD
[Samsung Galaxy Nexus] creeve4:
How can we tell if it is working?
[Samsung Galaxy Nexus] TiagoRigueto:
can i use min 192 and 1516 max??

you recommend?? or whats your recommend??
[Samsung Galaxy Nexus] The Gingerbread Man:
You can indeed if you wanted to, certainly nothing stopping you but you find your battery running out quicker when you over clock. As a little advice if your new then just see how you get on with leaving the default values. Honestly there isn't really much more to be done here, if anything at all. Look some pages back and you will find the 'osmod 390' which is the most up to date version with a whole host of optimisations built in already
[Samsung Galaxy Nexus] osm0sis:
ps -p | grep -E "PID|<launcher class name>"

cat /proc/`pgrep <launcher class name>`/oom_adj

Replace <launcher class name>. Currently these are supported by the script:

list="com.android.launcher org.adw.launcher org.adwfreak.launcher com.anddoes.launcher com.android.lmt com.chrislacy.actionlauncher.pro com.cyanogenmod.trebuchet com.gau.go.launcherex com.miui.mihome2 com.mobint.hololauncher com.mobint.hololauncher.hd com.qihoo360.launcher com.teslacoilsw.launcher com.tsf.shell org.zeam";

NICE should be -18 to make it smoother. oom_adj should be -17 to make it 'unkillable'.

P.S. r390-fixed isn't an osmod, it's just the tweaks Francisco already had in nightly r384 put back in, and a few bugs that were from ramdisk issues are fixed. :) I emailed [MENTION=3292224]franciscofranco[/MENTION] the fixed up ramdisk, so hopefully we'll see a r391 shortly. That was before I nailed down SR as the culprit for the other issues, so hopefully he'll throw that in as well and things will be pretty stable.
[Samsung Galaxy Nexus] TiagoRigueto:
osmod 390...???

this user or rom?? or app??
[Samsung Galaxy Nexus] AndyGnex:
Thats a special kernel version, slightly modified r390, done by [MENTION=4544860]osm0sis[/MENTION]

Sent from my bathroom throne.
[Samsung Galaxy Nexus] TiagoRigueto:
how to find this??

governor interative, too??
[Samsung Galaxy Nexus] AndyGnex:
page 4296, post #42959, im not gonna link it, you'll have to do a few extra clicks and scrolls to get to it :D
[Samsung Galaxy Nexus] TiagoRigueto:
thanks man... very thanks...

i am noob... english is not first idioma...

i'm learn... to read for me...is very very difficult and tired... :s

but this doesn't apply in my default language...

---

this kernel osmar is 'default' franco and some tweeks? better for battery or performance?

just flash on recovery??
[Samsung Galaxy Nexus] AndyGnex:
Yes, its default with tweaks, better performance, battery i think is same.

Sent from my bathroom throne.
[Samsung Galaxy Nexus] creeve4:
The built in script in 384-osmod is definitely not working. Using an init script works though.

Any idea why the built-in script doesn't work?
[Samsung Galaxy Nexus] bunnahabhain:
sorry wrong thread, delete! :laugh:
[Samsung Galaxy Nexus] AutomaticFailure27:
[MENTION=4544860]osm0sis[/MENTION]

About this BusyBox thing, since your Osmod kernel (Still on 4.2.2) includes BusyBox, would it be alright if I just uninstalled the BusyBox app (Stericon's or Jrummy's) so I don't run into any conflicts with the Ramdisk and the app loading?
[Samsung Galaxy Nexus] osm0sis:
The script is newer and has some fixes. Also you should check 60 seconds after a boot. Often it does work but there's no way to make it forever on some launchers. See my Odds and Ends thread for more info.

Shouldn't matter. It only works if called directly so the installed one should be dominant. It's called directly by fkbootscript so there should be no conflict unless that feature in stericson's Busybox Pro removes it. Pretty sure JRummy doesn't do this.
[Samsung Galaxy Nexus] AutomaticFailure27:
Ahh I see. I went ahead and uninstalled Stericson's version, rebooted and everything seems fine. I would run JRummy's but he hasn't updated it to the latest 1.21.1 version.

Have you tried turning it off and on again?
[Samsung Galaxy Nexus] TiagoRigueto:
you have thread? for changelog this kernel??
[Samsung Galaxy Nexus] osm0sis:
It's not a new kernel, it's just fixes to the ramdisk, as explained in my posts.
[Samsung Galaxy Nexus] TiagoRigueto:
sorry...

how to install??

just flash on recovery, wipe cache and dalvik??
[Samsung Galaxy Nexus] shawnaye:
wipe cache and dalvik first.

then just flash.

flash the zip version one please.
[Samsung Galaxy Nexus] TiagoRigueto:
installing the virus............ ¬¬"

you scare-me....
[Samsung Galaxy Nexus] osm0sis:
The only things we wipe around here are our asses. I think morfic said that. :) No wiping necessary for a kernel.

As for the virus thing, that's Franco's joke. :p
[Samsung Galaxy Nexus] wavedashdoc:
Osmosis, reboot issue still persists with your new fixed kernel :/ Mmuzzy 4.3
[Samsung Galaxy Nexus] DasGensu:
hey, i came from cyanogenmod 10.2 unofficial build with its "stock" kernel, then falshed r390

definitely got a big performance boost, but my battery seems to drain a lot quicker, any suggestions? Phone idle sits on 2nd place in battery consumption
[Samsung Galaxy Nexus] osm0sis:
Steps to reproduce?
[Samsung Galaxy Nexus] Prasad:
Can someone gimme the link for r390 osmosis version? And how is it different from stock r390 ?

Sent from the inner sanctum of my mind.
[Samsung Galaxy Nexus] metalspring:
search function is your friend, search by keyword r390, and by user osm0sis and voila

but i'll be nice and link you to the search results so you can see where it is and whats different

http://xdaforums.com/search.php?searchid=209957406
[Samsung Galaxy Nexus] wavedashdoc:
Every time I reboot or power on the phone, if I don't keep the screen on it will hard reboot. It's been doing this since 384. No undervolt.
[Samsung Galaxy Nexus] jackyhk02:
It sounds exactly like the CAB (content adaptive brightness) problem.

Try not to disable CAB by the franco updater app. If you want to disable CAB, use the init.d method instead.
[Samsung Galaxy Nexus] Pkt_Lnt:
The link is in his signature, go to his profile.
[Samsung Galaxy Nexus] osm0sis:
Bingo. :)

That, or it's really only a few pages back. People should take the time; this isn't a very fast moving thread anymore.
[Samsung Galaxy Nexus] god.fsl:
franco kernel r390 (-50 uv) with slimbeam alpha3.1

Auto brightness

Perfect! :)

Sent from my ///\/ e X u s
[Samsung Galaxy Nexus] danvrez:
extended battery right? :rolleyes:
[Samsung Galaxy Nexus] shreddintyres:
This is the best I've gotten so far on slim bean beta 1 with the original battery. Before the phone powered itself off i hit 3 hours screen on.
[Samsung Galaxy Nexus] god.fsl:
no bro:D original battery:angel:
[Samsung Galaxy Nexus] sui785:
On the screenshot it shows that you barely even used WiFi or mobile data. It's normal for the battery to last that long without internet.
[Samsung Galaxy Nexus] itasoulas:
can someone drop me some light on this? Are franco releases for 4.3 based on JWR or JSS firmwares? Cause I think they share a completely different kernel...I maybe wrong at this. I just read somewhere that a JSS based kernel may cause a few issues on JWR. Any info would help me short this out in my head, thanks!
[Samsung Galaxy Nexus] -Jesco-:
i believe that doesnt matter on Gnex only affects N4 afaik
[Samsung Galaxy Nexus] smileyanz:
WiFi uses hardly anything what so ever!!!!!!
[Samsung Galaxy Nexus] zoomy942:
GPU is ondemand'd to 512 right?
[Samsung Galaxy Nexus] ChazzMatt:
Here's your answer, posted earlier in the thread:

http://xdaforums.com/showpost.php?p=44247212&postcount=42848

I was worried about that too, and tracked down the answer (even before Franco released the 4.3 kernel for our GNex).
[Samsung Galaxy Nexus] galaxy16:
I'm on cm10.1.2 and downloaded Franco.kernel-nightly-r384 is it the right kernel? Just wanna make sure before flashing. Is it stable too?
[Samsung Galaxy Nexus] ChazzMatt:
Yes.

___________

Sent from my Galaxy Nexus I9250
[Samsung Galaxy Nexus] Sik-1:
Yes and you should really check of the osmod version of 384, simply milestone
[Samsung Galaxy Nexus] galaxy16:
hmm.. what is the difference with the osmod version?
[Samsung Galaxy Nexus] osm0sis:
http://xdaforums.com/showthread.php?t=2239421&page=9 :)
[Samsung Galaxy Nexus] Wingzer:
Coming back to a GNex soon from a HTC One.

Whats franco kernal like these days on the GNex, only worries are the colour balance especially the whites, does franco kernal provide calibration for the screen similar to what it does on the Nexus 4 ?

Also whats battery life + general performance like compared to stock kernal ?
[Samsung Galaxy Nexus] :
you can use trikster mod for color cpu changes etc. yeah white will be white. battery & perf. will be better than stock

Galaxy Nexus - Rasbeanjelly - Tapatalk 4
[Samsung Galaxy Nexus] akash3656:
You can customize the screen colours but its not as vast as all the available options in the Nexus 4.

Battery life on the GNex sucks hard I'm afraid. Even when the phone was new, I never got enough battery usage. My mother's stock Nexus 4 simply lasts almost twice as long as my phone.

On the matter of kernel, I feel stock delivers quite decent battery life. Franco kernel stretches what you can obtain from kernel side but the screen hogs battery on this device a lot more than the SOC
[Samsung Galaxy Nexus] Wingzer:
Cheers guys, its just the white balance on a phone screen kills me if its not absolute white.

It's one of them things that when its been seen it can't be un-seen.

Hopefully I'll be able to get it somewhere near the HTC One, not really bothered if there is a slight drop in colour saturation.
[Samsung Galaxy Nexus] garuhhh:
I have been using franco kernel (r390) for a few days, and for those times I didn't restart my phone for around 2-3 days, it was running out of RAM (it went as low as 2MB). Apps kept on restarting, even the launcher.

Checking system monitor, there were these "Thread-xxxx" apps running consuming up to 90MB of RAM. Looking at the attached screenshot, the Thread-422, Thread-405, and Thread-179 were 50MB+ each! There is no way to "kill" the said apps. Anyone knows what are they for? Why can they not be killed? I tried searching but couldn't find anything useful.

I'm not sure if my issue is kernel related, but on stock kernel, I don't have this. In fact, I went back to stock kernel 2 days ago (and I miss the fluidity and battery life of francoKernel), and so far haven't seen those in the system monitor. Free RAM stayed at 100MB range.

I'm running all stock ROM, android 4.3, rooted. I'm running Greenify as well, by the way.

What can I do to help troubleshoot if these are kernel related?
[Samsung Galaxy Nexus] shreddintyres:
That is most definitely not Franco Kernel causing that, ive never seen those before but that looks like a rogue app gone wild, you may want to do a factory reset and start over, i havent rebooted my phone for nearly 4 days with over 200 MB free at any given time
[Samsung Galaxy Nexus] :
Hey guys! I have a question, I am using ASKP Kernel right now which has its own ram disk but I want to go back to r390. Am I right that I can do it if I flash stock kernel and after that I can flash r390? Or do I have to durty flash my rom again? Is this the stock kernel?

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

Thanks :)

Galaxy Nexus - Rasbeanjelly - Tapatalk 4
[Samsung Galaxy Nexus] garuhhh:
That's what I'm afraid of: rogue apps. But the funny thing is, I don't see them misbehaving on stock kernel :'(

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

From my very limited experience, no need to re-flash your ROM, just flash kernels straight away.
[Samsung Galaxy Nexus] :
yeah could go because Franco also has its own ram disk. So it would only be a problem if I flash a any kernel like trinity that uses default ram disk?

Galaxy Nexus - Rasbeanjelly - Tapatalk 4
[Samsung Galaxy Nexus] hdoraemonk:
Deleted...
[Samsung Galaxy Nexus] ilarrain:
[Suggested merge] TRIM support when using encryption.

Hi Francisco:

I suggest you merge this changes, in order to get TRIM support (allow_discards) on Android 4.3 when using encryption.

https://github.com/ilarrain/android_kernel_samsung_tuna/commits/cm-10.2 (all changes from Aug 14, 2013, the last one is just a merge).

http://review.cyanogenmod.org/#/q/o...t:CyanogenMod/android_kernel_samsung_tuna,n,z

Merge message:

I've been testing this cherry-picks (all changes are from Linux Kernel 3.1, and included in android-3.3 kernel) in my phone (using encryption): TRIM works (it didn't before), lag has been greatly reduced and I've seen no errors.
[Samsung Galaxy Nexus] franciscofranco:
Will check, thanks :)
[Samsung Galaxy Nexus] CADude:
Is there any reason the FKU app is always running with 2 or 3 different processes? I just want to update and change settings, not have the app running for things I don't need. Can I disable all the per-app settings processes if I dont need them?
[Samsung Galaxy Nexus] wavedashdoc:
Franco, can you please Fix the CAB bug? I hate to have my phone restart if I don't keep the screen on till its fully booted.

Thank you good sir. As always, appreciate your hard work to make our tech better.
[Samsung Galaxy Nexus] -Jesco-:
you can disable CAB yourself and it works for me
[Samsung Galaxy Nexus] metalspring:
try adding this to a script in init.d - sleep 45 means it will wait 45 seconds after booting to run, and 0 is disable CAB, 1 is enable CAB

sleep 45; echo 0 > /sys/class/backlight/s6e8aa0/acl_set
[Samsung Galaxy Nexus] dracon6ai:
There's the solution right there. I got the same CAB bug and I use a script like this to work around it. Only I did a sleep 10 (I'm impatient) but you can play around to see what's best for you. Sleep 10 seems to be borderline pass for me so I might up it to 15 one day, as for now I like living on the edge. :D
[Samsung Galaxy Nexus] stevensoaj:
Why not just have no sleep at all? That way it sets it during the boot logo. I've always done it this way without issue.
[Samsung Galaxy Nexus] osm0sis:
Did you look at the per-app settings? The option to disable it is pretty obvious. Then there's a battery service in system monitor and the update service under settings if you want f.Ku to be completely silent. None of those have any bearing on battery or wakelocks so really you'd just be doing it because you're anal.

This right here. CAB requires no sleep. :)
[Samsung Galaxy Nexus] metalspring:
So then I'm guessing the bug with it rebooting comes from having an app set it to on or off, since the app would only start running and apply the setting after the boot animation, rather than immediately upon boot?

(I've never personally had an issue with it so I'm just guessing)
[Samsung Galaxy Nexus] ThePanduuh:
So I'm a noob. Is r384 the latest stable version? I'm on a Verizon Galaxy Nexus running CyanogenMod 10.1.2 Android 4.2.2. Want to make sure before I flashed it. This is my daily driver and I don't need any bugs. I came from leankernel. Only thing I didn't like about FC is the over clocking of the CPU to a value higher than 350000. I like battery life. On stock battery. Any reply is helpful. :)
[Samsung Galaxy Nexus] bigknowz:
4.2.2

384 is for 4.2.2, should have no issues.
[Samsung Galaxy Nexus] cmstlist:
Lag question

Today at a certain point in the day I found my phone was getting mega-laggy... tap anything and it takes 2-3 seconds to respond to the input. I tried killing as many tasks as possible but still the lag persisted. I checked alogcat out of curiosity and found the following entry being spewed out rapidly, roughly once every second:

W/SurfaceFlinger( 126): Timed out waiting for hw vsync; faking it

I then initiated a full reboot, after which point the message was no longer appearing and the lag was gone. A few hours later, still no issues.

I don't know if this is franco related at all (4.3 stock OS, latest nightly franco r390) but is it possible that this message was related to the lag? Any thoughts?
[Samsung Galaxy Nexus] blackhand1001:
Anyone else getting random freezing on cm nightlies in r390.
[Samsung Galaxy Nexus] greyhd:
Yes and even some bootloops. So far on 817 no freezes or boot loops.
[Samsung Galaxy Nexus] blackhand1001:
I just got one. Seems to occur when media server is being accessed such as uploading a photo. One freeze happened when attaching a photo to an email and sending it and I just had another when trying to upload a photo to picasa. On build 8-17.

Also got a few before while trying to take a photo.

I think it may have something to do with this.

https://plus.google.com/app/basic/stream/z120w5bhivecd1xrw04cdlxbcwbycbeomhk
[Samsung Galaxy Nexus] kabauterman:
Maybe CIFS (common Internet file system) causes the signal problems?
[Samsung Galaxy Nexus] Rogoshin:
As far as i can tell you cant use it for 4.0.2, i read it further down in the first post.
[Samsung Galaxy Nexus] minipaolo:
back on 13.1 (AOKP b20).
[Samsung Galaxy Nexus] riddi:
Can you put a download link for version 13.1?

I have some issues.
[Samsung Galaxy Nexus] kabauterman:
http://dl.dropbox.com/u/16925401/franco.Kernel-nightly13.zip
[Samsung Galaxy Nexus] kva:
for me 14.1 = reboot in 1 minutes of using effects in drawer (in launcher).
[Samsung Galaxy Nexus] riddi:
Thank You.

Back to 13.1 version
[Samsung Galaxy Nexus] stesmi:
Not to mention the thread title.

It's like asking "Can I put Diesel into my gasoline-powered car". No, your gasoline powered car requires gasoline ..

// Stefan

---------- Post added at 11:17 AM ---------- Previous post was at 11:16 AM ----------

What makes you say that?

// Stefan
[Samsung Galaxy Nexus] danielvc:
Dit a few stability tests with 14.1 (700-1350mhz, conservative, no uv) and it did well. Thanks Franco for your work.
[Samsung Galaxy Nexus] kabauterman:
Internet problems caused by a internet TCP/IP Tweaking File System?

I deleted the Module by hand, until not no Signal loose if standby
[Samsung Galaxy Nexus] nbeebe24:
I was on 14 earlier with zero issues, and am now on 14.1 with no issues. The only time I had reboots with this kernel is when I screwed up the UV settings. Are any of you who are experiencing problems under volting lower than Franco's numbers?
[Samsung Galaxy Nexus] jhericurls:
Word of warning for those using 14.1, don't mess with the UV setting or you could be eating Bootloop sandwich.

I flashed 14.1 over 13.1, all was fine. I adjusted the values of the 1250MHz slot slightly and it all went dark.

Couldn't boot up my device back up, flashed different Kernels, wipes, nothing. Had to do a restore.
[Samsung Galaxy Nexus] minipaolo:
Can you post any UV settings you are using?

I tried a bit, but as far as I go -100mV from stock it starts with loop boot.. :eek:

I am now on 700-1200 with 950-1050-1150 mV
[Samsung Galaxy Nexus] stesmi:
How do you mean Tweaking?

It's a tcp/ip filesystem yes. What exactly does it tweak? It makes it so you can mount it in the kernel.

Radio and filesystems don't have anything in common.

// Stefan
[Samsung Galaxy Nexus] rob151515:
Anyone managed to get cifs working with 14.1? I can get the cifs.ko module to load but I can't seem to mount any shares?
[Samsung Galaxy Nexus] Mrc527:
Really? You can load it? Try to do a "dmesg" and see, I receive an error when insmod it....:(
[Samsung Galaxy Nexus] nfin1te:
One question concerning the governor-tuning:

You said that it skips the steps between min-max: i like setting min to 350mhz because everything still works without lag. Does that mean it always jumps between 350 and 1200mhz without steps in between or does this only happen when min is set to 700mhz? I don't care about loosing the 9xxmhz step, but i don't want to loose every step between 350 and 1200.
[Samsung Galaxy Nexus] ro_explorer:
OK .. I finally did what I said I'll no longer do: I've wiped everything and started fresh. :( ...

Put Bigxie's rom (apex1.0) on a clean device and I've set-up everything. I've played around with stock apex to make sure everything is stable and all was fine (I even lost only 2% overnight with my usual settings).

This morning I've dome a full nandroid backup am I started testing again.

#13.1 went flawless on my device (stock values). Couple of hours os using it revealed nothing.

I then flashed #14.1 ... the phone booted fine and everything seemed stable ... I was wrong.

I was having 3g signal drop every time the screen went off.

I've tried playing with non-logical stuff thinking that maybe is something there:

- wifi sleep policy (it didn't solved anything).

- I've deleted the cifs module ... same **** ..

So .. I said ok ... #14.1 is a no-go for me ... let's just go back to #13.1 :) ... well, wrong again. Apparently #14.1 is one way only since flashing back #13.1 is resulting in an infinite boot animation looping. I'm now restoring the nandroid backup :|.

So, from my point of view, after making absolutely sure I've done everything "by the book", I can definitely say: #14 and#14.1 are a no-go for me.

I'll stick to #13.1 until further improvements.
[Samsung Galaxy Nexus] Nebucatnetzer:
If nothing helps try oem lock and unlock again. Did the trick for me earlier.
[Samsung Galaxy Nexus] meilstone:
Experiencing high idle consumption. 8% in 1 h
[Samsung Galaxy Nexus] The Gingerbread Man:
Those are rom ****, no problems on stock
[Samsung Galaxy Nexus] thegtfusion:
confirmed. running PERFECTLY fine on stock. best combo ever. i couldnt be happier :D :P
[Samsung Galaxy Nexus] gpzbc:
That problem supposedly doesn't affect the Galaxy Nexus. Mostly just the Nexus 4.
[Samsung Galaxy Nexus] blackhand1001:
Cm is usually rock solid. I have been running cm since January 2012.
[Samsung Galaxy Nexus] Edward Stanbury:
WOO iva and gpu voltage control is back and a SALE, anyone that doesn't have FK.u should get it now ;)
[Samsung Galaxy Nexus] jopherr:
i get this on 390 + cm nightly 8/17. i noticed under the system monitor, that the phone will randomly get stuck at like 197mhz regardless of phone activity. It occurs even if you designate the minimum frequency to be like 700mhz. i think there is a bug in the governer or something for maguro. The stock kernel seems to work fine for CM. Franco, is there a fix coming up?
[Samsung Galaxy Nexus] thegtfusion:
no problems with stock. absolutely fine. flash stock and see if the bug is still there.
[Samsung Galaxy Nexus] The Gingerbread Man:
The common factor with these 'bugs' is cyanogen lol
[Samsung Galaxy Nexus] Edward Stanbury:
Looks like it, everything is running perfectly on PSX ROM also :P