yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ciprianruse88:
If you are on stock then you don't have trebuchet launcher.trebuchet is in roms based on cm.f.w.y. i've tried cna,jellybro and now i am on Pa.it doesn't matter the rom or the kernel.
[Samsung Galaxy Nexus] nyamoV2:
Already did :D
[Samsung Galaxy Nexus] 15israellai:
Indeed. Vote!

Sent from Asia
[Samsung Galaxy Nexus] despard:
Yeah, treasure you've got the right to vote:D:D

BTW, does any of you have stutter while playing music? I have it screen off even when screen on, strange.
[Samsung Galaxy Nexus] osm0sis:
@despard: What music app, and what're your min/max and screen off max?
[Samsung Galaxy Nexus] despard:
I'm using PowerAMP at the moment. 1536/192 screen on, screen off 537. I tried raise the min to 384 it helps screen off stutter but screen on still happens.
[Samsung Galaxy Nexus] bhowanidin:
What's newer, the nightly or milestone?
[Samsung Galaxy Nexus] kingoanklebreakn:
Nightly.
[Samsung Galaxy Nexus] joaquinf:
Sh**t just got serious. Awesome work with your kernel Francisco, many thanks.

Setup as described in my signature
[Samsung Galaxy Nexus] osm0sis:
Yes, I'd suggest min 384 most definitely. What are your governor settings?
[Samsung Galaxy Nexus] amf100:
I just move nova to system and uninstall trebuchet. I then use some app or other that edits build.prop option to lock home in memory.
[Samsung Galaxy Nexus] osm0sis:
Franco has stock launcher excluded from lowmemorykiller with the following on boot:

sleep 60
pid=`pidof com.android.launcher`
echo "-17" > /proc/$pid/oom_adj
chmod 100 /proc/$pid/oom_adj

Not sure if that applies to m/any 3rd party launchers or not, would depend on their package class naming. My guess is not. If that's the case then you could add that to an init.d script with com.android.launcher replaced with the appropriate class name for your launcher of choice to see if it has the desired effect and could be used instead of those build.prop hacks, etc. :)
[Samsung Galaxy Nexus] gaich:
Look this
[Samsung Galaxy Nexus] Leegalaxy:
Right, I'm saying the difference is the ROM and the fact that it uses a launcher that is not party of the system. I used Cyanogen Mod for a long time. I know what trebuchet launcher is. It is a trade off. The kernel isn't the problem, it is the ROM (and the fact that you are using a 3rd party launcher).
[Samsung Galaxy Nexus] amf100:
Well I guess I'd wonder how cm10 codes it since stock is called Trebuchet instead of Launcher. Probably just my moving Nova to system with Titanium is good enough to keep it smooth.
[Samsung Galaxy Nexus] osm0sis:
Maybe. But stock Launcher is also in /system/app/ and Franco still felt the need to make sure LMK couldn't kill it, so it might be worth trying for 3rd party launchers as well. You could look for Trebuchet/Nova/Apex/(other 3rd party launcher)'s class name under /data/data/ since it should have a directory for its settings there.
[Samsung Galaxy Nexus] despard:
Was 60/70/45/15, I'm trying 60% for going high speed (729). Is IO scheduler going to affect anything? I changed it to deadline seems improve a little bit.
[Samsung Galaxy Nexus] osm0sis:
Franco default load is 65% so yeah, good thinking, maybe 70 was too high. Also I don't have any problems with bfq, but deadline is Franco's default right now and might be better in your case since he tweaked it to prioritize reads over writes, give all that a shot.
[Samsung Galaxy Nexus] Shadow-Nexus:
I need some help here

My battery doesn't seem to get any better

Here are my settings

Device: Galaxy Nexus

Kernel: 3.0.49-franco.Kernel-nightly-512GPU#298

Max Frequency: 1228 MHz

Min Frequency: 537 MHz

Governor: interactive

Screen Off Max Frequency: 537 Mhz
[Samsung Galaxy Nexus] TheHunterOfShadows:
On r295, (384) with jbsourcey 3.1. Having this issue where there is zero free ram, then the phone becomes almost completely unresponsive. Once I can finally open the recent apps and kill all, things speed back up. But this usually takes time. Didn't seem to have this issue on r268, but everyone i try after that I am having this issue. Thoughts?
[Samsung Galaxy Nexus] jacobydarkon:
The new keyboard swiping is better then Swype.
[Samsung Galaxy Nexus] osm0sis:
Your device is constantly running at 537 since its both your min and screen off max, try lowering your min to 384 or 192. Then of course check for wakelocks with BetterBatteryStats and all that good stuff. ;)
[Samsung Galaxy Nexus] Shadow-Nexus:
Okay I'll give that a try and just to be sure

How do I check the wake locks through the apps?
[Samsung Galaxy Nexus] osm0sis:
Well I highly suggest you buy BetterBatteryStats from the Play Store to support the awesome dev, but he also posts them in the xda thread as a courtesy. I encourage you to consider it a Demo and pay once you realize how awesome it is. What you'll want to do is charge your phone up full, make sure you don't have any apps running, then unplug and leave it alone for a few hours (2-3 is good, sometimes I push for 6). Then you want to check Other for your awake/ deep sleep, kernel wakelocks, partial wakelocks, alarms and sometimes network to see what's keeping your phone awake. It's also got a cpu freq % display like cpuspy and shows your battery usage %/h, so, pretty handy!
[Samsung Galaxy Nexus] Shadow-Nexus:
Well I have used better battery stats a few times and it seems that the maps app is causing most of my partial wakelocks
[Samsung Galaxy Nexus] yellowdie:
Try turning off all location services. That will shut Maps up. :)
[Samsung Galaxy Nexus] osm0sis:
I'm more middle of the road there. I have all location services on but GPS (which I turn on when I want it), but the trick is I don't use Latitude, so I turned off all the location reporting in Maps settings. Of course if you use Google Now (I don't, with it off the voice search cards from Knowledge Graph still work fine and bring up all the info I want and can do all the voice commands too), then you might need to leave Maps/Latitude location reporting on, but try it without and see how you get by.
[Samsung Galaxy Nexus] Shadow-Nexus:
If I do that will that disable geo location ?

Because I think that is used for CM lock screen weather
[Samsung Galaxy Nexus] Raijin:
Franco, maybe you can add support for most common launchers? I can help you by collecting the package class names to ease your work.
[Samsung Galaxy Nexus] Shadow-Nexus:
Apperently it didn't thanks for the help
[Samsung Galaxy Nexus] sk8oldschool74:
Just wanted to say my phone had a good day today on battery w/ milestone 6 check it out... :D:D:D Franco like it...

update my bad I just noticed I charged it a little forgot about that... Well i smiled for a minute lol... still get great battery life though...
[Samsung Galaxy Nexus] mixtapes08:
Man that's a good font can you share it?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] daveyglow:
Latest nightly does wonders to battery life on cm10! That's!
[Samsung Galaxy Nexus] marcocsh:
I check this thread every 2 hours to see if r300 and the recoded fku is out! can't wait!
[Samsung Galaxy Nexus] L-ViZ:
got the same issue, kinda short "knacks". using 295 min freq 384mhz. cm10kang.

argh, it didn't quote... it was in context to poweramp.
[Samsung Galaxy Nexus] mpokwsths:
On the NFS Most Wanted matter: Just tested r298 384GPU on an AOSP based ROM and it is the same as CM10. Slow Motion.

Then flashed another kernel and everything ok. So definitely not a ROM problem, not a combination kernel + rom. Only kernel problem.
[Samsung Galaxy Nexus] L-ViZ:
fku?

+1 bought and don't/can't play bacause want my customizations
[Samsung Galaxy Nexus] doomed151:
franco.Kernel Updater.
[Samsung Galaxy Nexus] black_sith:
Fku = Francos kernel updater, his app :)

Gesendet von meinem Galaxy Nexus
[Samsung Galaxy Nexus] L-ViZ:
stupid me :D
[Samsung Galaxy Nexus] The Gingerbread Man:
Franco does this file do what it looks like?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mrasquinho:
What the...? xD

Maybe a temporary bug, once I've restarted, it disappeared :)
[Samsung Galaxy Nexus] HyvelTjuven:
I just flashed this kernel yesterday and I'm really satisfied with it running on CM10 M2, it's really fast and smooth, however I do like to tweak my colour profile because I dislike the green-ish tint my screen has by default but when I try to lower the green RBG gamma through the franco.Kernel updater the screen goes all glitchy on automatic and low brightness levels; it pretty much goes extremely green.

Is this because I'm using Superuser instead of SuperSU? Or is this a known glitch.
[Samsung Galaxy Nexus] mariachi202:
It's a known issue, the green gamma slider is buggy when decreasing.

I personally like these settings:

gamma: -4, 0, 5

Multipliers: 180, 192, 200

Trinity contrast: 4

OMAP: 1.2

Try them out.
[Samsung Galaxy Nexus] HyvelTjuven:
Thanks, these settings look nice, however I put the multipliers to 180, 180, 200 instead because it looked better on my screen. Every eye and screen is different I suppose.
[Samsung Galaxy Nexus] L-ViZ:
using the pretty same

gamma: -4, 0, 5

Multipliers: 180, 192, 200

Trinity contrast: -16

OMAP: 1.0

nice contrast and great white :) blackest black :)
[Samsung Galaxy Nexus] Hatshipuh:
It happened again, this time device just froze.

And again, though battery was still at around 14%, after reboot all juice was drained.

Everything on default, no messing with SR, voltage or even scheduler.

View attachment 1463721

last_kmsg, don't know if it's the right one, device died during reboot due to no battery apparently,

http://dl.dropbox.com/u/26360797/last_kmsg
[Samsung Galaxy Nexus] osm0sis:
Your battery stats are likely just reporting the wrong number. Full charge, leave it on the charger for a few (~4) hours after it reaches 100%, then you should be good going forward.

Failing that, yeah a boot drains a fair amount, but not that much, so perhaps your battery is defective?
[Samsung Galaxy Nexus] Hans QC:
Support for launchers

Good idea! I am using Apex.
[Samsung Galaxy Nexus] skinnypupp:
Is there a fast USB charge widget out there that works with this rom? I like the feature, I would just prefer it if it was easier to enable. Thanks!
[Samsung Galaxy Nexus] osm0sis:
If you want to go ahead and collect the package class names then I'll at least provide an init.d script for everyone with all of them in it. Then we can hear if it actually helps anything.. ;)
[Samsung Galaxy Nexus] phishn:
I have experienced the same issue with 298 512 on sourcery 3.1. The problem I have had is that CPU 1 has been found to go offline and never come back on at some point. Not sure if this is cause and effect related. I flashed imoseyons kernel then reflashed 298 512. It's been 12 hours since and I haven't experienced the memory issue again or the CPU 1 going offline. I'll report back if the problem comes back. I usually can't go 24 hours without it reoccurring.
[Samsung Galaxy Nexus] Raijin:
Give me two days and will be made :)
[Samsung Galaxy Nexus] nuumuun:
to get you started:

ADWLauncher EX

org.adwfreak.launcher

Apex Launcher

com.anddoes.launcher

Holo Launcher HD

com.mobint.hololauncher.hd

Nova Launcher

com.teslacoilsw.launcher

Trebuchet

com.cyanogenmod.trebuchet

Zeam Launcher

org.zeam

i believe those are some of the most popular ones :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] joaquinf:
An app called "fast charge" has a widget and it works fine. Look for it on the play store. On a different note this is not a rom, wrong thread maybe?
[Samsung Galaxy Nexus] osm0sis:
Awesome! :D Any more either of you or anyone else want added to the list? If not I'll post it up later this afternoon on my coffee break.
[Samsung Galaxy Nexus] Hatshipuh:
Thanks for the suggestions!

Thought that too at first, but last time the screen just froze without turning black.

Then I waited a while, expecting the battery to run dry and shutting down by itself.

But that didn't happen, so I thought it wasn't the case of an empty battery, but after booting, the battery happend to be empty again.

Maybe it's really a defective battery, but I'll try your suggestions first.
[Samsung Galaxy Nexus] yellowdie:
org.adwfreak.launcher is the paid version, org.adw.launcher is the free version. I would include both. :)
[Samsung Galaxy Nexus] osm0sis:
That sounds like a voltage issue. You running defaults or UVing?

Good thinking! Any other paid vs. free differences I need to add in for any of the others (Apex, Holo HD, Nova, Zeam)?

Edit: I'll post it in about 45 minutes so act fast! :laugh:

Edit 2: K. Added Go launcher, and most of the others seem to just have pro keys, so the actual launcher package class name would be the same. Finishing it up now
[Samsung Galaxy Nexus] Shadow-Nexus:
So I finally got maps to shut up thanks to yellowdie and I just need to adjust the syncing frequency of my services
[Samsung Galaxy Nexus] psycho2097:
since this was brought up, i wanna ask smthg... can sum1 tell me xactly which features of google now require what to be enabled? what depends on location history, what depends on auto update of location, n what depends on "report from this device"? My latitude is off anyways. I typically keep auto update location, do not report from this device(gives a lot of wakelocks), n no location history(not sure how much effect this has on battery). Basically i need a few google now features to work, like travel, fliights, places(maybe?), stocks, news update, photo spot nearby. Nothing else needed. What do i need to do to maximise battery life(w/o making my phone into a black screened dumbphone, that is)? will turning off any of these help my battery? Can sum1 pls take a little time n xplain?
[Samsung Galaxy Nexus] nuwan32:
Go launcher ex

com.gau.go.launcherex
[Samsung Galaxy Nexus] osm0sis:
Alright fellas, give this init.d script a spin and see if it makes any difference for your 3rd party launchers and related issues which could be caused by lowmemorykiller kicking them out of memory as discussed in the last few pages:

/system/etc/init.d/975lmkwhitelist:

#!/system/bin/sh
# chmod -R 755 /system/etc/init.d

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

while sleep 60; do
for class in $list; do
if [ `pgrep $class` ]; then
pid=`pgrep $class`;
echo -17 > /proc/$pid/oom_adj;
chmod 100 /proc/$pid/oom_adj;
fi;
done;
exit;
done&

Just create the above file in /system/etc/init.d/ and set permissions on it and the directory to rwxr-xr-x (chmod -R 755 /system/etc/init.d). Reboot and wait a few minutes for everything to run and settle down.

[113 downloads by the time I took the old one down though, that's awesome guys! Hopefully a few more of you will tell me if it helps. ;)]

Edit: Franco has said he'll be adding a custom LMK app exclusion option to be used with 3rd party launchers in the f.Ku bootservice in a future version. Hasn't happened yet but it's on the todo list. I'll take down the attachment but the script is still above if anyone wants to try this in the meantime. :good:

Edit 2: Updated launcher list (thanks boype/Fancy Kernel). Put it all in an independent while loop so it doesn't hold up the rest of the init.d script while it waits. The above is outdated now, the latest version is part of the Franco's Dev Team 975experimental init.d script on my Dev-Host: http://v.ht/osm0sis :)
[Samsung Galaxy Nexus] psycho2097:
awesome trying out now, thx.

---------- Post added at 03:55 PM ---------- Previous post was at 03:53 PM ----------

uh i m on trinity currently...trinity doesnt hav init.d now does it? any other way?
[Samsung Galaxy Nexus] osm0sis:
Franco's kernel is one of the few that has init.d, but the vast majority of ROMs have init.d support. What is your ROM? Also this is a test tweak for Franco's kernel. No idea what effect it will have with morfic's setup so I wouldn't recommend it.

Your other option would be to cut and paste that into Android Terminal Emulator after typing su and granting permissions.
[Samsung Galaxy Nexus] The Gingerbread Man:
Hmm I don't seem to have system/etc/init.d location, well at least not init.d folder.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Create the directory if it doesn't exist. ;)

If the perms are right and you've got BusyBox installed to /system/xbin/ it should work. I'm on stock ROM and Franco's kernel even makes it work here.
[Samsung Galaxy Nexus] The Gingerbread Man:
I'll give system/xbin a whirl, cheers!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] danielvc:
This is what I call good battery life. Thanks Franco!

View attachment 1464659

View attachment 1464660
[Samsung Galaxy Nexus] yellowdie:
Nice script. :) For those of you that don't have init.d in your rom/kernel setup, you can also just add these two lines to your build.prop file (in /system):

# Keep launcher in memory to reduce redraws
ro.HOME_APP_ADJ=1

The first line isn't needed, but it helps you know what the next line is for.
[Samsung Galaxy Nexus] osm0sis:
Not sure if that's the exact same thing or not. Worth a try though! Good find. I believe build.prop hacks to be a little dirtier than init.d scripts though since you're modding system files, so I'd tend to avoid them at all costs. Even if your ROM does not already have a /system/etc/init.d/ directory, that doesn't mean it doesn't support init.d since, like I said, the vast majority do. So give init.d a try first.
[Samsung Galaxy Nexus] yellowdie:
True, I agree. Just another option (but not as good) :)
[Samsung Galaxy Nexus] Kurre:
Afaik, those adj related build.prop tweaks are deprecated since moving to android 4.x versions. Feel free to correct me if proven otherwise :D

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] Hessi93:
Share your settings :)

Skickat från min Galaxy Nexus via Tapatalk 2
[Samsung Galaxy Nexus] yellowdie:
Interesting. I have no idea either way about it, but do you have documentation showing that? That would be really good to know. :)
[Samsung Galaxy Nexus] nuumuun:
syntax error at

do;

you need to remove the semicolon. then it works nicely, thanks! :D:cool:
[Samsung Galaxy Nexus] osm0sis:
Ah must just be some **** with do vs other commands. thanks for catching that. Pretty sure we could just remove all the semicolons and have it work fine like any other shell script. I think I'll go back and do that now.

Edit: Done. Go back and get the file again if you got it before now.
[Samsung Galaxy Nexus] Hatshipuh:
Always been on defaults, never touched UV related stuff.
[Samsung Galaxy Nexus] Empty Hand:
Sorry for the noob question, but what is rwxr-xr-x? I am aware of r, w, e (read, write, execute) as options for permissions. Thanks!
[Samsung Galaxy Nexus] osm0sis:
r

ead,

w

rite, e

x

ecute. wiki chmod for the details. :)
[Samsung Galaxy Nexus] The Gingerbread Man:
Is this correct?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Nope. You've got -rwxrw-r-- there. ;)

-rwxr-xr-x = rwx, r-x, r-x = all 3 r's, the top w, all 3 x's.
[Samsung Galaxy Nexus] Empty Hand:
Checked the wiki. So, using noob speak for which boxes to select, 755 is -rwx-rx-rx, correct?

Edit: never mind, when I changed the permissions, I saw it was correct. Thank you!
[Samsung Galaxy Nexus] osm0sis:
Pretty much, but the gap is between r and x, since they're always in rwx ordering.

It's -rwxr-xr-x , like I keep posting. :p If it's the first - that's throwing you off, that's just indicating it's a file; directories have a d there.
[Samsung Galaxy Nexus] danielvc:
R298, 192-1228, interactive, default settings, no uv, max freq screen off = 192 & that's it. sleeping like a baby.
[Samsung Galaxy Nexus] EDNYLaw:
Does anybody know if cold can affect the device? What I mean by that is, I've undervolted quite heavily and it's been rock stable for weeks, literally no changes to the phone whatsoever but now the weather is getting colder and when I leave the phone in the cold (phone maybe gets down to 50-60 F) it won't turn on and I have to pull the battery. If I have the phone on me, using it or in my pocket it doesn't freeze. I can just bump up the voltages, but I'm just curious if anyone has ever experienced that or knows the actual reason. I'd have thought that cold reduces resistance, so lower voltages would be tolerated better.

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] willl03:
I'm pattenting hotpad cases, should be ok with apple since they dont UV/OC, unless they want to warm their users hand cause their screen dosnt work using gloves
[Samsung Galaxy Nexus] EDNYLaw:
For those of us tech nerds that just have to undervolt but refuse to move somewhere warm :)

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] yellowdie:
Did y'all see this? http://www.theverge.com/2012/11/7/3614506/apple-patents-rectangle-with-rounded-corners
[Samsung Galaxy Nexus] willl03:
*facepalm*
[Samsung Galaxy Nexus] KJW979:
This is getting ridiculous, somebody needs to put a stop to these ridiculous patents. That's like Goodyear patenting a round tire and suing all other tire manufacturers for using their design.
[Samsung Galaxy Nexus] johno86:
Will this affect Franco Kernel?

I didn't think so.
[Samsung Galaxy Nexus] jkoljo:
The kernel is laggy in my device, too. Luckily I only fastboot booted it, so it was very easy to go back. So I also would like to see 1.2 GHz version :)
[Samsung Galaxy Nexus] dwang:
yep 1.4 lags for me as well. Plus I think it may be a little too undervolted as I'm getting reboots on this one because of not enough voltage.
[Samsung Galaxy Nexus] nism0o:
I heave undervolted it :

1200MHz-1100mV

920MHz-975mV

700MHz-875mV

350MHz-800mV

And it works great :)
[Samsung Galaxy Nexus] The Gingerbread Man:
Maybe when we have some solidly tested results someone could put a script for gscript for some voltage tables. Like stock v, mild UV, Med UV, high UV and extreme UV?

Good for swapping / changing in the go
[Samsung Galaxy Nexus] sluflyer06:
Either my device isn't loading the UV like it supposed to or I misinterpreted how its supposed to work. When I went into SetCPU I now see a voltage tab but the current/saved voltages don't match what I see in the changelog (they're higher).

is the UV stuff just supposed to allow us to undervolt or should the #'s posted already be in setcpu on boot?

Other than that today's Kernel seems to be working fine, I'll continue messing with it before I flash it I'm just booted on it for now.
[Samsung Galaxy Nexus] franciscofranco:
I think I did it correctly and the settings posted in the OP should be default yes. I'll recheck the code when I go home.
[Samsung Galaxy Nexus] GchildT:
No Lag for me.

Test Kernel from 120611 @ 1400Mhz No UV

AnTuTu 6950

Quandrant 2054

This Kernel @ 1400Mhz No UV

AnTuTu 6965

Quandrant 2518
[Samsung Galaxy Nexus] mskip:
Did you set the voltage manually via setcpu as francisco forgot to compile the undervolts so the latest flashable kernel in post#1 still has the default voltages unless you changed it. This has been fixed now and the next update will includ them :)

If you didnt set the undervolts then your reboots couldnt have been due to not enough voltage. If you did set them manually then what exactly was you running when the phone rebooted?

Mark.
[Samsung Galaxy Nexus] sluflyer06:
OK been messing with today's Kernel most of the day and not a single crash or force close, been doing extensive stress testing at different voltages to find lowest Voltage thats stable and doesn't cause a performance hit.

1.2ghz @ 1.175v

920mhz@ 1.125v

700mhz@ .950v

350mhz@ .850v

Quadrant Score @ 1.4ghz = 2,681

Antutu Score @ 1.4ghz = 6,955

@Franco it seems like SD card read/write scores have improved with this Kernel I was averaging 5.6W & 31.3 Read and now I'm hitting 7.3Write & 32.6Read