yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] creeve4:
Got it to work this way:

Installed and ran the app, then cleared the app data and ran again. It worked the second time. Must be a bug in the app.

Franco has not implemented discard in his kernel?
[Samsung Galaxy Nexus] The Gingerbread Man:
It is implemented I just like having a good clear out manually by clearing cache, run lag fix, reboot, run for ever gone, reboot, lag fix again. Probably pointless but makes me feel better everything is running as good as possible
[Samsung Galaxy Nexus] Blackcrx:
A BMW? Ouch. I'm sorry to hear that. Haha. Jk
[Samsung Galaxy Nexus] osm0sis:
That's how we've gotten this far! ;)

http://xdaforums.com/showpost.php?p=43506242&postcount=82
[Samsung Galaxy Nexus] creeve4:
Any idea where I can find it in the code?
[Samsung Galaxy Nexus] The Gingerbread Man:
Absolutely no idea as if never tried to decompile a kernel to look through it. Osmosis would know or use his android image kitchen use it to extract and look through
[Samsung Galaxy Nexus] uberberben:
Does 384 still has problems with wifi? Last time I tried it my phone had major problems with internet connection.

Wysyłane z mojego Galaxy Nexus za pomocą Tapatalk 2
[Samsung Galaxy Nexus] osm0sis:
What are you looking for? discard? It's in the ramdisk in /fstab.tuna - put it there myself. ;)

Also for userdata it's in init.tuna.rc to workaround bootloop issues from the tuna fstab with certain options.
[Samsung Galaxy Nexus] Khrushy:
So after a few days use I'm giving a thumbs up to the lmk settings. It just feels nice and. . . . consistent . . for want of a better word.
[Samsung Galaxy Nexus] karta1993:
Nice battery life today

Wish r384 osmod

Min 192 else is stock
[Samsung Galaxy Nexus] Prasad:
Can someone please post a link to the r384 osmod version?

PS. I searched.
[Samsung Galaxy Nexus] nitsua98:
http://d-h.st/mh8

It's a .img file so you need to fastboot flash the boot.img
[Samsung Galaxy Nexus] Bl4ck3urn:
http://d-h.st/users/osm0sis/?fld_id=20197#files
[Samsung Galaxy Nexus] UlbaWan-:
Well now I've tested the two ones and with the two, i've got the same experience... Impossible for me to tell who's the best, really. Generally, I had 10-20 minutes time screen on more with the osm0d, but maybe fortuity...

BUT ! With the two, after maybe a half day, I've a problem of delay between when I put my finger on the screen and when the phone make the action... And never had this with the older franco's kernel !

I'm on CM 10.1.1 :)

I don't have retested that on CM 10.1.2 because I wanted to test the CM kernel and this kernel give the the best experience between the 3...

I keep watching any update ;)
[Samsung Galaxy Nexus] osm0sis:
http://d-h.st/users/osm0sis/osmod or http://v.ht/osmod also work. :)

You guys see this today? http://theverge.com/2013/7/14/4522054/moto-x-always-listening-voice-commands-new-notifications

I wonder if those features are standard JB4.3 or if Google is still trying to keep Motorola somewhat separate from the Nexus line. Personally I'd still prefer a notification LED to having it silently turning the screen on and off all the time; if that thing's LTE it's already going to need all the battery it can get!
[Samsung Galaxy Nexus] misterk267:
Was wondering the same thing myself. I've been looking for a cheap but high quality upgrade from this gnex, and that Moto X is looking pretty good. That is, if the VZW model is boot loader unlockable.

~Nexus Powered~
[Samsung Galaxy Nexus] AutomaticFailure27:
Reminded me of this app: NoLED
[Samsung Galaxy Nexus] mixtapes08:
http://m.gsmarena.com/alleged_motorola_x_smartphone_specs_leak_packs_10mp_camera-news-6224.php

-3StarsAndaSun
[Samsung Galaxy Nexus] mrdevil_25:
pretty cool app. but it's a battery drainer for sure. just tried it and it kept my phone awake half the time
[Samsung Galaxy Nexus] AutomaticFailure27:
Yeah, I had a feeling that it would do something like that. There is another one, which I can't remember the name of, that does the same thing and should hopefully be a better battery saver.

Have you tried turning it off and on again?
[Samsung Galaxy Nexus] mrdevil_25:
only briefly tried it then uninstalled it.
[Samsung Galaxy Nexus] bartolinio:
private video?

I can not watch :rolleyes:
[Samsung Galaxy Nexus] CADude:
I have a question that I am sure is on more than a few people's minds:

When Franco decides to end support for the Gnex, will the app be able to control other kernels that have continued to support the Gnex? Can I use this app with Trinity or Fancy Kernel?

I'm asking because if the Nexus 5 is another glass sandwich that doesn't appeal to me and I have to use the Gnex for another year, which is fine since it's powerful enough for my needs, I'd like to be able to use this app for another year with another kernel that has continued to support the Gnex. Or will Franco allow a volunteer to take over support for the Gnex by forking his kernel?

I'll eventually catch up with you guys when the Nexus line gets a phone that I really want to buy, but I'm curious about what Franco has in mind for those people who might want to continue using his app for an older device.
[Samsung Galaxy Nexus] Rimher:
I've used it with many other kernels, AK for example, and had no problems at all.
[Samsung Galaxy Nexus] swarm871:
Franco with the last update of fku (v10.1) introduced per app modes.

How we can set to have the best battery life/performance ??

Some use this feature??

I don't know if this is the right thread to post this question :confused:

Sent from my Nexus 7
[Samsung Galaxy Nexus] cap'nC:
Hi all, I see that the last versions of FKU ask for the new permission retrieve running apps. Am I correct to assume that it is used by the new integrated system monitor, or are there any other activities that need it?

I searched in the threads and in the changelogs, but couldn't find an answer by myself.

EDIT: ok, I am a bit slow tonight.. I guess that without it the app can't know when to switch between power modes :silly:
[Samsung Galaxy Nexus] sluflyer06:
Haha yea I dunno why we're getting such wildly varying results. I've been running #14 for 6 hours now and its just awesome for me. Super smooth, not 1 issue.
[Samsung Galaxy Nexus] samizad:
Flashing the latest mod is an addiction. At least it's a cheap addiction :) And I don't see the bug reports as complaints. It's a community of like-minded people trying to get the kernel perfected. Francisco is the owner but he's got thousands of testers; not just five.
[Samsung Galaxy Nexus] shawnn218:
So I'm on 13.1. If I flash the new one, do I need to wipe?
[Samsung Galaxy Nexus] yyz71:
Hey man I have zero problems with this kernel or any of his kernels I've used!!! Read before you make statements like that..

Sent from my pimped out galaxy nexus.
[Samsung Galaxy Nexus] samizad:
No. But I always do a Dalvik cache wipe for good measure.
[Samsung Galaxy Nexus] Vangelis13:
Really?

"many probably legit"? No, we thought we'd lie for a moment to spice up the thread.

"combinations of mods & roms". Yeah, we unfortunate ones on a custom / mod-filled 4.0.3 based rom. You must be on Google's unreleased, official 4.0.3 build, no..?

"faulty hardware". That's it, all our (how many, 20+ reports of reboot loop stuck phones) faulty hardware caused it. Or the above.

Seriously now: it wasn't a coordinated pseudo-attack on Francisco's kernel - it really happened!

Guten morgen

P. S. 14.1 is running flawlessly on a fresh aokp 20 install for the last 4 hours. Same setup as the 14 instantly boot-looped.
[Samsung Galaxy Nexus] dwang:
great job as usual and very fast at addressing the various issues that people brought up.

Even though I donated, I went ahead and bought your app.

Thanks for your hard work.
[Samsung Galaxy Nexus] 1Speed:
14.1 works fine for me after having boot trouble with 14. Thanks for the update and all of the hard work!

FYI not everyone that couldn't get 14 has a heavily modded phone. I have Buggless Beast 4.0.3 ROM installed, which is about as close as you can get to a stock AOSP build.

THANKS AGAIN!
[Samsung Galaxy Nexus] SomEngangVar:
Well I made that a lot harder on myself than I needed to. I didn't back up so I needed to push 14.1 and flash it but every time I pushed it I'd go back in to downloads for some reason instead of just /sdcard and I kept flashing 14 over and over and couldn't figure out why I couldn't get it to boot. Haha.
[Samsung Galaxy Nexus] simplistian:
Mount /data and push the file to somewhere in /data/media/ in CWM recovery.
[Samsung Galaxy Nexus] CakraMas:
Is it possible to have ADB over network with this version ?
[Samsung Galaxy Nexus] DJ "suMo*:
UV is definitely causing signal drop while screen off for me. If I restore stock voltages then reboot no issues, soon as I UV again signal drops while screen off. Didn't have this issue before 14 - I'm on Ir10 MCR, never did that stock.

Sent from my GN
[Samsung Galaxy Nexus] myxcon:
Flashed 14.1 and I keep getting reboots just 1 min after boot. It boots just fine, I can do whatever I Want for around 1 min then no matter if the phone is in use or not, it reboots. Reverted to stock voltages but does the same. *using aokp build 20*

Back to 13.1 for now.
[Samsung Galaxy Nexus] dwang:
Yep I'm seeing this behavior with 14.1 as well.

Once I undervolt, as soon as I turn off the screen, signal is dropped.

However if I reboot with the undervolted settings, things seem to be ok.

I'm undervolting by -50 across the board.

EDIT: -75 also works after a reboot

So try undervolting and then reboot and see if that fixes the signal drop.

With 14, i was getting the signal drop without any undervolting.
[Samsung Galaxy Nexus] sishgupta:
Franco 14.1 and AOKP 20...

Been running it for about an hour now and all of a sudden my screen wont turn on. I know the phone is working because i was able to pattern unlock the screen. I could feel the vibrate from hitting the pattern points and then it made the unlock sound. Also just took a screenshot.

My screen is black though.

EDIT: In pitch dark environment i can see that the backlight is turning on, although all the colour is black. The screenshot showed one of my desktops.
[Samsung Galaxy Nexus] nbeebe24:
Franco, I had zero issues with 14 fwiw
[Samsung Galaxy Nexus] BlackDino:
Crap I am bootlooping.. I have flashed 14, 14.1, 13, 13.1 and still am stuck.

Any advice to get past this?

I have also tried reflashing my rom

Although I do get past the Google logo, but I never get past the boot animation
[Samsung Galaxy Nexus] Bakedbread:
Flashed 14.1 and was running it for about 5 hours (on bixie rom) and I just started getting boot loops. Not sure what caused it as I was just watching some highlights with my browser.

Phone rebooted twice and changed my wallpaper for some reason too. Flashed back to #12 for now (had the best results)

Thanks for all your efforts Franco, just reporting what I encountered.

*edit

Btw, just wanted to also mention I haven't flashed any other mods and only use a calendar widget. Everything else is just stock bixie rom.
[Samsung Galaxy Nexus] apratomo:
maybe you could try to flash kernel reset? Can be found on faux kernel page on rootzwiki (I don't know if we're allowed to link to another forum page)
[Samsung Galaxy Nexus] BlackDino:
yea you can,

if you can get that link that would be awesome.

http://goo-inside.me/kernels/faux123/ICS-4.0.3-Reset-Kernel (1).zip

there is the link if anyone is wondering,

I will update if it fixes my problems

yea hasnt fixed anything.. lol this sucks, sad to say but I am not going to mess with my kernel any more

Last edit for the night,

It looks like a full wipe has fixed my problems.

Good night all, hopefully you guys dont have issues like this
[Samsung Galaxy Nexus] osm0sis:
Per app power modes are the reason for that permission.

Not a fan of the new icons myself, or the way System Monitor takes over the fly out menu. :/
[Samsung Galaxy Nexus] aR_ChRiS:
same, prefer the icons on the previous version.

Sent from my nexus prime (maguro)
[Samsung Galaxy Nexus] EnricoTFYKD:
What I really miss from the new per-app modes is the option to set a specific profile when the battery falls below a certain level of charge. I still have to use SetCPU for that.
[Samsung Galaxy Nexus] sci05:
+1
[Samsung Galaxy Nexus] kaluoshi:
Hey [MENTION=4544860]osm0sis[/MENTION], about the icons i hope Francisco will add a way to change them with presets, when he get extra time of course. About System Monitor i'm with you but i think Francisco choose that way to thank Christian with the redirect to the app itself :)

Paranoid ... wait for it ... Android
[Samsung Galaxy Nexus] myvijay:
Restoring kernels

After installing the new FK.U, it shows none of my previous kernel backups including stock. I read somewhere that kernel backups have a different format now. I prefer to keep a backup of the stock kernel at all times, could someone guide me on how to obtain one. I am on the nightly 384.
[Samsung Galaxy Nexus] kuyam:
Make a new folder called "franco.kernel_updater" in the root of your sd and move the kernel_backups folder into there.
[Samsung Galaxy Nexus] grumphy:
Or, make a new bkp first. Folder will be created. You can move the old ones after...:D

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] e753:
Hi guys!

Could you be so nice to share the voltage of your cpu?

Thanks
[Samsung Galaxy Nexus] namtombout:
These are the gingerbread man's

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

Mine are all raised by 25mV except for 384-I raised to 800mV and 537-i left at 850mV

U.O.E.N.O
[Samsung Galaxy Nexus] osm0sis:
There's no way to UV CORE or IVA in the new f.Ku.. :(

Had to set them via init.d. If you do the same be damn sure your voltages are stable.
[Samsung Galaxy Nexus] e753:
thx dude, mine are as you but 1200 at 1275mv and 1420 at 1275mv
[Samsung Galaxy Nexus] daxisalive:
My device has been getting hot recently with moderate use like YouTube... I have default kernel settings without any modification. Is it because of Franco setting which sets gpu to 512?

Sent from... what? SENT? ALEADY?
[Samsung Galaxy Nexus] thegtfusion:
Could be yes. Or because of his voltages.

Try another kernel and put it on 512 mhz. If it doesnt heat up its the voltages. If it does then its the 512mhz gpu ;)

Sent from my Nexus Prime
[Samsung Galaxy Nexus] Hungry Man:
Is there a way to roll back FKU? I really don't care much at all about UI, but the ability to change my IVA/GPU voltages is pretty important to me.
[Samsung Galaxy Nexus] osm0sis:
Write to Francisco on G+ and ask him to put it back. He probably just forgot.
[Samsung Galaxy Nexus] beyboo:
Flashed Franco nightly 384 on galaxy nexus with bigxie's 4.2.2 rooted deodexed ROM. Device hangs every few minutes , have to pull battery. Anyone else get this ?

Using default kernel settings, no tweaks and hangs using any app in first 5 minutes
[Samsung Galaxy Nexus] nickcct:
Im using stock rooted yakju 4.2.2 with franco 384. So far no problem and smooth. Uptime 100 hour.
[Samsung Galaxy Nexus] beyboo:
I am on stock rooted maguro 4.2.2 from bigxie. Moved to lean kernel now. Works alright. Again tried FKU.384 hangs
[Samsung Galaxy Nexus] Phazmos:
been running 384 since it hit with a few roms and no problems. beanstalk, liquid, slim, jellybeer, a couple others just for fun, all good. I have had trouble when loading Franco after other kernels though. some leave leftovers, like ak or askp, and those leftovers can be a problem. I had to start fresh after the last askp, wiping everything AND formatting system to get back to normal.
[Samsung Galaxy Nexus] AutomaticFailure27:
Osm0sis has a Emergency Reset Script which cleans out init,d and performance apps settings so nothing is left behind. Now, there is some [like AK] that leave a folder in the /data, these files are mainly harmless and are just there for pulling logs and such. AK also has a different wifi (3.4 I think), so it's also recommended to run the revert.wifi zip before flashing to another kernel.

Best thing I did to clean them, was to open the .zip file from the other kernels and check the init.d folder along with the /data and see if it installs any scripts. If I feel like I forgot something, dirty flash the rom again, then flash kernel of choice.
[Samsung Galaxy Nexus] Handled:
[MENTION=4544860]osm0sis[/MENTION], I am using your color settings. Well, one of your many recommendations, rather. My question is, I notice that I am able to keep the brightness on a much lower setting and gain, rather than just retain, readability. On other popular color profiles, I must crank my brightness up 75, sometimes 100% And even then it's not as legible and comfortable. Does my phone use less battery by changing my display properties and using this lower setting? Or is it technically the same amount? I hope that made sense.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Phazmos:
thanx man!! I saw that script before, but couldn't remember where! I knew I should have got it right then and there.
[Samsung Galaxy Nexus] osm0sis:
My color settings do bump it up just a bit in terms of brightness by raising all the multipliers. It's not as much as going up a whole brightness level so if you find it more readable on low brightness you could potentially save some juice. On the other hand, it's brighter one way or the other, so may consume a slight amount more battery than you'd see before at each brightness level. Depends on your usage and expectations. ;)
[Samsung Galaxy Nexus] Ladaga:
Sioplus?

Enviado desde mi Galaxy Nexus usando Tapatalk 4 Beta
[Samsung Galaxy Nexus] bunnahabhain:
Siominus?

Galaxy Nexus / Tapatalk
[Samsung Galaxy Nexus] thegtfusion:
not included.
[Samsung Galaxy Nexus] alfiemenace:
Hey guys, I was wondering why the Franco.kernel updater app is showing a toast notification that it has been granted superuser permission every now and then, is it normal? It causes my phone not to sleep :(
[Samsung Galaxy Nexus] osm0sis:
Probably the periodic update check. This has no effect on your device's sleep, however, so you'll have to look elsewhere for that. If you want it off then it's in the app settings, there's also a battery service in the System Monitor settings you can disable if you want f.Ku completely silenced. You should also go turn off toasts for superuser requests since they are known to slow things down.
[Samsung Galaxy Nexus] alfiemenace:
I didn't mean like deep sleep, it just keeps my screen on and overrides the timeout. Haha I had update thingy set to manual already, and the battery monitor disabled. Guess I'll just turn off the toast so I won't get bothered with it haha thanks man!
[Samsung Galaxy Nexus] Ladaga:
3.0.87 out xD

Enviado desde mi Galaxy Nexus usando Tapatalk 4 Beta
[Samsung Galaxy Nexus] kecinzer:
https://github.com/kecinzer/francoKernel_tuna/commits/sm
[Samsung Galaxy Nexus] SahilC:
But if you clean flash a ROM, then it should clean it up anyways, right?
[Samsung Galaxy Nexus] IRX120:
Does this kernel have sweep to wake? My power button is giving out, yet to find a kernel with s2w and s2s

Sent from my Gnex@1.2 GHz on Stock 4.2.2
[Samsung Galaxy Nexus] Seraz007:
nope

but PGM works with this kernel ;)
[Samsung Galaxy Nexus] Sik-1:
U can try a rom with the volume to wake buttons and set one of the quick tiles to screen off
[Samsung Galaxy Nexus] aryan79:
No more Milestone for GN??? :rolleyes:
[Samsung Galaxy Nexus] Edward Stanbury:
perfection takes time (:
[Samsung Galaxy Nexus] marcocsh:
For me it make no difference between a nightly and a milestone in Franco ;)
[Samsung Galaxy Nexus] aryan79:
Sure, but some time ago we had a lot of Milestone per GN, last is about one year ago! :)
[Samsung Galaxy Nexus] akash3656:
Doesn't matter to me, #384 is rock solid once I stopped fooling around with voltages (which I knew would wreck stability). Stable/Milestone is just a label. #384 practically can be called a milestone release already.

And even if there might be more to tweak our Galaxy Nexus, team Franco has already done a fantastic job fine tuning every single scheduler and the default interactive governor.

I flashed other kernels that have continuous updates (like weekly) and I still find Franco/Trinity are the best kernels. Trinity could do with some scheduler tweaks to reduce shuttering, but its also a very smooth kernel despite shuttering with heavy I/O. Franco is all around smoother than Trinity, so therefore I prefer Franco.

---------- Post added at 06:46 PM ---------- Previous post was at 06:43 PM ----------

But to add on, the best kernel is a subjective thing. Not everyone would agree with me that Franco is the best. Another kernel may work great with but not for me with my usage/phone combination.
[Samsung Galaxy Nexus] osm0sis:
Would be silly to release a milestone that we may only be able to use for another day to a week. :p

My guess is we're waiting to see what 4.3 breaks, fixing anything it does, then milestone when it looks stable again.

Edit: Francisco's also on vacation. ;)
[Samsung Galaxy Nexus] dracon6ai:
I was just curious, with all the tweaking of interactive which made it the beast that it is today. And the specific roles Lazy, Performance and Wheatley play, where does Dyninteractive fall in the mix now?
[Samsung Galaxy Nexus] Sik-1:
DynI is simply put automagic lol, the os drives the CPU, ala project butter. all parameters that are tunable in interactive are managed from the os itself, its petty sweet actually, I use it all the time
[Samsung Galaxy Nexus] The Gingerbread Man:
Factory images out for 4.3 released fellow flash junkies https://developers.google.com/android/nexus/images#instructions
[Samsung Galaxy Nexus] nitsua98:
Toro :(
[Samsung Galaxy Nexus] whitedragonz83:
First thing I noticed... Google Play App Installs/Uninstalls is not freezing my system at all. Really impressive. /cheers!
[Samsung Galaxy Nexus] bigknowz:
Toro

See here.
[Samsung Galaxy Nexus] nitsua98:
I know but 4.3 is not actually out yet, except for gsm devices.
[Samsung Galaxy Nexus] osm0sis:
KNEW that was Google's derp. :cool:
[Samsung Galaxy Nexus] Culex316:
Can anyone confirm if Android 4.3 works with the current 4.2 kernel or will something break compatibility like it did when transitioning from 4.1.2 to 4.2?
[Samsung Galaxy Nexus] lightingcloud:
Isn't franco on holiday right now?

We're all doomed. :P
[Samsung Galaxy Nexus] bunnahabhain:
Indeed. No 4.3 kernel before 29 th of July.

Galaxy Nexus / Tapatalk
[Samsung Galaxy Nexus] osm0sis:
Yeah I can confirm it doesn't boot. I'll see if it's just ramdisk **** (ie. something I can fix for us in the meantime. ;))
[Samsung Galaxy Nexus] Sik-1:
Its prolly the drivers like b4 wen we first got 4.2 lol
[Samsung Galaxy Nexus] CADude:
Try fancy kernel. Its been working great for me with the Franco app and is getting regular stable updates. Franco has been merging stuff from boype (fancy kernel dev) so you can expect a similar level of quality.
[Samsung Galaxy Nexus] Sik-1:
Lol dude your statements about quality are hilarious.....jus saying
[Samsung Galaxy Nexus] nitsua98:
Please don't start a fight people...
[Samsung Galaxy Nexus] lightingcloud:
I can survive 5 days whithout franco kernel, I suppose :P and the ROM I use is still (ofc) 4.2.2 so I can wait. XD
[Samsung Galaxy Nexus] osm0sis:
Sometimes you get lucky and it's just ramdisk differences...
[Samsung Galaxy Nexus] osm0sis:
And case in point... "lol" yourself. :p

Recombining some stuff from franco's ramdisk now and we'll have a f.K-osmod for 4.3. :good:
[Samsung Galaxy Nexus] TheMysteriousOne:
Share the love! :P
[Samsung Galaxy Nexus] Prasad:
Oooh... *tickled*

Sent from the inner sanctum of my mind.
[Samsung Galaxy Nexus] doomed151:
I can't wait any longer, so I decided to do it on my own. :p

EDIT: Noticed that the default scheduler is cfq and readahead set to 128 kb on stock 4.3 kernel.
[Samsung Galaxy Nexus] Ladaga:
We want franco kernel for 4.3 hahaha true love

Enviado desde mi Galaxy Nexus usando Tapatalk 4 Beta
[Samsung Galaxy Nexus] supernova_00:
Maybe it will be a good thing to use the stock kernel for a few days so you all can notify Franco of any problems/slow downs/etc that didn't happen with the stock kernel.
[Samsung Galaxy Nexus] endymion2k5:
Well ive had one SOD on totally stock 4.3. While installing my google backlog apps.