Every time I unlock my phone from a deep sleep its @ 29c-30c either on 143 nightly or milestone 3.....aokp build 33
Sent from my Galaxy Nexus using XDA
Last edited:
[KERNEL] [GPL] [GN] franco.Kernel r398
- Thread starter franciscofranco
- Start date
Sent from my Galaxy Nexus using XDA
Ya im no dev just a guy with to many phones, I don't no about speed scores or hot plug this and UV that, I go by "feel " of actually day to day use and 121 ( using 384, 512 just as good but I don't feel necessary ...) is just perfect no lag no heat, games work flawless, speed is fantastic, battery is crazy good I think 2nd best battery life ever off 121, its also the one I personally keep coming back to, the one I compare all the others 2, I try give all builds at least 24-48 hours of trying out before judging them, that short amount of time don't give the battery life a fare judgment,but dose everything else, don't get me wrong everyone of the builds run great usually as far as I can remember I haven't had any real issues with any build besides heat in last builds .... my opinion; ) appreciate your time @Franco!!
i totally agree. that kernel release was almost perfect in terms of battery life and smoothness. that, together with r133.
I forgot about 133, ima retry it but ur right I remember not being able choose between the two 121-133
This was fun to read
All the users need to understand that if I've set Milestone GPU clocked to stock I must have a reason. And not releasing a simultaneous nightly build with overclocked GPU also has a reason.
The reason is simple, I want to understand if having a higher GPU OPP enabled ****s up battery life a lot more than it would if it was disabled. In this case we have OPP3 disabled for Milestone releases and enabled for nightly builds.
I did not noticed a big impact in battery's life with stock GPU, but on the other hand I appreciate a notorious impact on general performance.
I think that you are right on the idea of an OCed GPU in nightlies, but not as convinced to mantain the stock GPU in milestones..
I've been running 192mhz on your M3 and its been working pretty well. Even though I broke custom voltages in the process, I'm still seeing good battery life. From my observations the phone seems very good about hopping in and out of 192mhz to avoid lagging, even with lazy.
FYI to all the people about to say that 192mhz won't save battery... EVEN if 192 and 384 are running at the same voltage, 192 will consume half as much battery. Battery consumption can be estimated as (frequency)*(voltage)^2.
Anyone know where I can download past nightlies from? I'm specifically looking for 121
Sent from my Galaxy Nexus using XDA
Sent from my Galaxy Nexus using XDA
http://minooch.com/franciscofranco/Galaxy Nexus/nightlies/ 512 MHz GPU OC builds in Index, 384 MHz GPU OC in folder gpu_384mhz/
Last edited:
We should be as lucky. Franco is the type of developer that has his ear to the ground, and interacts with fans, flashers, etc. If it were up to me, I would have closed the thread, had all posts deleted except mine, and all you would hear from me was my changelog. Of course I would probably be lurking other individual's threads to see what people are saying; we should be thankful Franco is not that kind of developer.
Sit back, relax, and enjoy Milestone 3.
Sit back, relax, and enjoy Milestone 3.
+1
This can only be said of a handfull of devs. Francisco is one of them.
Thanks for that!
Loving r143 512. Very very smooth, great battery life (now @ 26%, 15h6m since last charge, 4h4m screen on)
Thumbs up!
for all guys that your GTA III is NOT WORKING
for all guys that your GTA III is NOT WORKING
Well got my nexus a few days before and at this phrase im testing out games.
justnow, installed GTA III -> game crashed -> WTF? well but i dont panic, cause i know im excellent at researching.
after messing with it for around an hour, please take some time to read the following:
(unless specified, im talking about version 1.3, which should the latest)
1) please make sure the application package of YOUR GTA is "com.rockstar.gta3" because upon my knowledge / researched results, rockstar has released "com.rockstar.gta3ger" as their version 1.3 which the "ger" literally means german version but apart from this, the version is also considered to be "censored" because blood has been reduced and violence such as kicking enemies on the floor, are REMOVED.
2) however, i dont know which restrictions / variety of "com.rockstar.gta3ger" and "com.rockstar.gta3" apply on different areas / countries / app stores, one thing is clear - in december something like that, which means around the r18 release of franco kernel, franco has made a fix about the inability of executing GTA III. As the time reveals, at that time GTA III was just on its versions 1.0-1.2 stage, and franco directs the fix towards the application package "com.rockstar.gta". Im not going to talk about the reasons why GTA was originally incompatible, go read the first bunch of pages of this thread in december.
3) now thats the tricky point - franco fixed "com.rockstar.gta3", but you installed "com.rockstar.gta3ger" (the official censored 1.3 version from rockstar), therefore your sd card data is not fixed.
4) if you get a 1.2 version of GTA III (i dont know where), you will definitely not crash because it is "com.rockstar.gta" which is successfully directed to the fix made by franco and his sd cracking mate.
5) some of you may ask then what the hell the fix is? well, upon my knowledge i cant really answer this question technologically. but, you will notice a folder called /sd_images in your sdcard partition and inside there you will see "com.rockstar.gta.img" (all these happen after you installed the correct package of it, i.e. "com.rockstar.gta", and downloaded the data from your phone)
6) therefore, to make it work you must confirm that the package name is NOT "com.rockstar.gta3ger" as franco's fix will NOT recognize this package and its sdcard data so your game will fail to run the sd card data!
if you want some REFERENCE, try searching "GTA 1.3 uncut" (which means, the uncensored), on google
thanks franco, but regarding the above information, you may be interested to include "com.rockstar.gta3ger" in your fix in next few releases in order to satisfy some of the users
still, i just want to say =___= to those who leave such a great (and best) kernel just because of a game but not to invest into the issue themselves...
cheers!!
for all guys that your GTA III is NOT WORKING
Well got my nexus a few days before and at this phrase im testing out games.
justnow, installed GTA III -> game crashed -> WTF? well but i dont panic, cause i know im excellent at researching.
after messing with it for around an hour, please take some time to read the following:
(unless specified, im talking about version 1.3, which should the latest)
1) please make sure the application package of YOUR GTA is "com.rockstar.gta3" because upon my knowledge / researched results, rockstar has released "com.rockstar.gta3ger" as their version 1.3 which the "ger" literally means german version but apart from this, the version is also considered to be "censored" because blood has been reduced and violence such as kicking enemies on the floor, are REMOVED.
2) however, i dont know which restrictions / variety of "com.rockstar.gta3ger" and "com.rockstar.gta3" apply on different areas / countries / app stores, one thing is clear - in december something like that, which means around the r18 release of franco kernel, franco has made a fix about the inability of executing GTA III. As the time reveals, at that time GTA III was just on its versions 1.0-1.2 stage, and franco directs the fix towards the application package "com.rockstar.gta". Im not going to talk about the reasons why GTA was originally incompatible, go read the first bunch of pages of this thread in december.
3) now thats the tricky point - franco fixed "com.rockstar.gta3", but you installed "com.rockstar.gta3ger" (the official censored 1.3 version from rockstar), therefore your sd card data is not fixed.
4) if you get a 1.2 version of GTA III (i dont know where), you will definitely not crash because it is "com.rockstar.gta" which is successfully directed to the fix made by franco and his sd cracking mate.
5) some of you may ask then what the hell the fix is? well, upon my knowledge i cant really answer this question technologically. but, you will notice a folder called /sd_images in your sdcard partition and inside there you will see "com.rockstar.gta.img" (all these happen after you installed the correct package of it, i.e. "com.rockstar.gta", and downloaded the data from your phone)
6) therefore, to make it work you must confirm that the package name is NOT "com.rockstar.gta3ger" as franco's fix will NOT recognize this package and its sdcard data so your game will fail to run the sd card data!
if you want some REFERENCE, try searching "GTA 1.3 uncut" (which means, the uncensored), on google
thanks franco, but regarding the above information, you may be interested to include "com.rockstar.gta3ger" in your fix in next few releases in order to satisfy some of the users
still, i just want to say =___= to those who leave such a great (and best) kernel just because of a game but not to invest into the issue themselves...
cheers!!
Last edited:
Ondemand, 729/1228, auto brightness, SR on.
On the 512 nightly branch I was getting up to 5h under the same conditions.
Now its time for m5 and m3 to meet...
Sent from my Galaxy Nexus
Last edited:
for all guys that your GTA III is NOT WORKING
Well got my nexus a few days before and at this phrase im testing out games.
justnow, installed GTA III -> game crashed -> WTF? well but i dont panic, cause i know im excellent at researching.
after messing with it for around an hour, please take some time to read the following:
(unless specified, im talking about version 1.3, which should the latest)
1) please make sure the application package of YOUR GTA is "com.rockstar.gta3" because upon my knowledge / researched results, rockstar has released "com.rockstar.gta3ger" as their version 1.3 which the "ger" literally means german version but apart from this, the version is also considered to be "censored" because blood has been reduced and violence such as kicking enemies on the floor, are REMOVED.
2) however, i dont know which restrictions / variety of "com.rockstar.gta3ger" and "com.rockstar.gta3" apply on different areas / countries / app stores, one thing is clear - in december something like that, which means around the r18 release of franco kernel, franco has made a fix about the inability of executing GTA III. As the time reveals, at that time GTA III was just on its versions 1.0-1.2 stage, and franco directs the fix towards the application package "com.rockstar.gta". Im not going to talk about the reasons why GTA was originally incompatible, go read the first bunch of pages of this thread in december.
3) now thats the tricky point - franco fixed "com.rockstar.gta3", but you installed "com.rockstar.gta3ger" (the official censored 1.3 version from rockstar), therefore your sd card data is not fixed.
4) if you get a 1.2 version of GTA III (i dont know where), you will definitely not crash because it is "com.rockstar.gta" which is successfully directed to the fix made by franco and his sd cracking mate.
5) some of you may ask then what the hell the fix is? well, upon my knowledge i cant really answer this question technologically. but, you will notice a folder called /sd_images in your sdcard partition and inside there you will see "com.rockstar.gta.img" (all these happen after you installed the correct package of it, i.e. "com.rockstar.gta", and downloaded the data from your phone)
6) therefore, to make it work you must confirm that the package name is NOT "com.rockstar.gta3ger" as franco's fix will NOT recognize this package and its sdcard data so your game will fail to run the sd card data!
if you want some REFERENCE, try searching "GTA 1.3 uncut" (which means, the uncensored), on google
thanks franco, but regarding the above information, you may be interested to include "com.rockstar.gta3ger" in your fix in next few releases in order to satisfy some of the users
still, i just want to say =___= to those who leave such a great (and best) kernel just because of a game but not to invest into the issue themselves...
cheers!!
Awesome, thanks man
What extended battery r u using?
Ondemand, 729/1228, auto brightness, SR on.
On the 512 nightly branch I was getting up to 5h under the same conditions.
Now its time for m5 and m3 to meet...
Sent from my Galaxy Nexus
I believe hotplug governor also turns off cpu1 when screen off today. I think that's what Franco and I talked about yesterday.
Sent from my Galaxy Nexus using Tapatalk 2
Hey francisco, I was wondering if you could tell me how your kernel app detects frequencies. I somehow managed to break it. Logcat shows an error with getmhz or something. I can't figure it out. Rom control sets frequencies fine.
Sent from my Galaxy Nexus using xda premium
Sent from my Galaxy Nexus using xda premium
It reads the frequencies from the file. I will take a look tomorrow, too tired today.
What have you been doing for 5h 43m, over the 9h period your device has been on?
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1562I hate big OPs.
Works on all roms. r390 and newer versions are ONLY for 4.3 or newer.
F.A.Q:
1. My device rebooted or crashed, how can I help?
A: Get me /proc/last_kmsg on pastie.org.
2. Battery sucks, my device is not entering deep sleep. FIX PLOX!
A: Fix it yourself, it's an app waking your device up not the kernel's problem
3. Signal is dropping since I flashed the kernel, amg u sucks!
A: The kernel has nothing to do with gsm/cmda signal. Make sure you have the latest radios
4. Do I need to wipe anything when flashing this kernel?
A: No.
5. Does this kernel has X or Y mod?
A: Learn to read, everything you need to know is in the features list, changelog or public repo.
Downloads:
4.3: http://192.241.177.15/GalaxyNexus/4.3/
4.4: http://192.241.177.15/GalaxyNexus/4.4/
Kernel changelog:
http://192.241.177.15/GalaxyNexus/4.3/appfiles/changelog.xml
Source:
https://github.com/franciscofranco/Tuna_JB_pre1/tree/nightlies-4.3
franco.Kernel updater Free apk: http://xdaforums.com/showthread.php?t=1867127
203[KERNEL][GPL][5 JUN - #Milestone 4][r200-ICS r210-JB] franco.Kernel | 4.0.3/4 |
Terminal commands for all the options in this kernel:
Color Multipliers:
echo r g b > /sys/class/misc/colorcontrol/multiplier
Replace r g and b for 2000000000 for stock color. If you want to change the colors just replace the first 3 numbers of each r/g/b with 0-400 of your choice.
Gamma Control:
echo r g b > /sys/class/misc/colorcontrol/v1_offset
Replace r/g/b by -255/200 of your choice.
Fsync:
echo 1 > /sys/module/sync/parameters/fsync_enabled - to enable
echo 0 > /sys/module/sync/parameters/fsync_enabled - to disable
Sound Control:
echo i > /sys/devices/virtual/misc/soundcontrol/volume_boost
Replace i with 0-3 of your choice.
Sound High Performance:
echo 1 > /sys/devices/virtual/misc/soundcontrol/highperf_enabled - to enable
echo 0 > /sys/devices/virtual/misc/soundcontrol/highperf_enabled - to disable
USB Fast Charge:
echo 1 > /sys/kernel/fast_charge/force_fast_charge - to enable
echo 0 > /sys/kernel/fast_charge/force_fast_charge - to disable
wifi_pm:
echo 1 > /sys/module/bcmdhd/parameters/wifi_pm - to enable
echo 0 > /sys/module/bcmdhd/parameters/wifi_pm - to disable
Trinity's Contrast:
echo i > /sys/module/panel_s6e8aa0/parameters/contrast
Replace i with -25/16 of your choice.
BLX:
echo i > /sys/class/misc/batterylifeextender/charging_limit
Replace i with 0-100 of your choice.
OMAP Gamma interface:
echo i > /sys/devices/platform/omapdss/manager0/gamma
Replace i with 5-10 of your choice.
Thermal Throttle:
echo 1 > /sys/module/omap_temp_sensor/parameters/throttle_enabled - to enable
echo 0 > /sys/module/omap_temp_sensor/parameters/throttle_enabled - to disable
TCP Congestion Algorithm interface
To check all the available options:
sysctl net.ipv4.tcp_available_congestion_control
To change to other option:
sysctl -w net.ipv4.tcp_congestion_control=NAME_OF_THE_ALGORITHM
Detailed test of all the algorithms:
167
haha. It's been a crazy two days. But it's been a blast.
Now, sleep is over, time to get back to work!
Yes and no. Here's what we're thinkin' so far.
THIS POST WILL BE A RECAP OF THE LAST FEW PAGES OF RESEARCH!
This was my original settings that I've been using for weeks:
So to make the short hand easier, we kept it in that order and just said: 20000/50/40000/20000 became 20k/50/40k/20k became 2/5/4/2. Make sense?
Here is a breakdown of what they each mean:
This is a good explanation that I wrote back on page 3038:
So Google's default is 10/5/6/2. Lower numbers are all better for performance except min_sample_time (there higher is faster). So our goal is to find a sweet spot.
The default 10 is for "Once speed is set to hispeed_freq, wait for this long before bumping speed higher in response to continued high load." So we think 10 is too high, but if you go too low, then you'll be using the higher freqs a lot more than you need and it will hurt the battery. So we are leaning towards 6 (60000) for above_hispeed_delay.
The default 5 is for "when the CPU hits X% amount of load, then jump to the hispeed_freq." Again if this one is too low then it will cause the higher freqs to be used more often then they need, so we actually turn go_hispeed_load up a little bit to 7 (70).
The default 6 is for "how long do I wait before lowering the clock speed from what it's currently at." So the lower we put this, the better battery will be. We're still trying to decide between 3 (30000) and 5 (50000). Osm0sis is getting more lag at lower levels, and finds the best performance mark at 5. So we turn min_sample_time down a little from stock to help with the battery.
The default 2 is for "wait this long before changing the clockspeeds from what it's at now." While technically 2 sounds better because it's changing more often, Franco believes that by setting the timer_rate to be the same thing as the CPU sample_rate (which is preset at 30000), then that will make the CPU more efficient at switching. So we increased it from 2 (20000) to 3 (30000).
So TO RECAP: Using the stuff from above, Google's defaults for these settings are 10/5/6/2 and we are changing them to 6/7/3/3 or 6/7/5/3 (again, still testing that third number for the min_sample_time).
Does that make sense for everyone interested in following along? Any questions? Feel free to try out these settings yourself (the easiest way is with Franco's app or something like Trickster). We want as much feedback as possible on this.
The next kernel release will have the totally tweaked settings for everyone to test without having to change their own stuff.
:laugh::good:111Kernel Emergency Settings Reset Zip
Alright so here's something that's been requested for awhile.
I wrote it up recently with Franco's stamp of approval, so I'm posting it here now. Please direct people back to this post from other threads.
This can/should be everyone's go-to when experiencing problems after updating to a new kernel build, you get stuck in a bootloop, or you think there's a conflict between ROM and kernel (or kernel tweaking app) you can't track down, since likely some leftover settings (voltages, etc.) are at fault. It's also useful if you just want to make sure you're running clean defaults. This should work on any device franco.Kernel and f.Ku support, as well as a variety of other devices, kernels and control apps: eXperience (Free/Pro), GLaDOS Control, TricksterMod, Trinity Kernel Toolbox, ROM Toolbox (Lite/Pro), SetCPU, Faux123 Kernel Enhancement Project, Performance Control and Synapse.
Flashing this via custom recovery of your choice will delete the kernel app settings file(s), disable init.d and userinit.d scripts by moving them to a subfolder (/system/etc/init.d/off/ and /data/local/userinit.d/off/ respectively) and wipe cache and dalvik-cache for good measure.
Hopefully it helps!
Note: If your ROM has a Performance/Tweaking App built-in you should also manually disable any Set On Boot options it has. For example, I couldn't include clearing CM's Advanced Settings since they're built into the main com.android.settings/Settings.apk along with a lot of other Android OS settings (APNs, Developer Options, etc.), so to run clean and without conflicts on CM you need to unset them yourself.
You should also avoid having more than one control app installed at a time. Conflicts have been reported even with everything "unset" in two apps.
I also chose not to disable anything your ROM may have in /data/cron or /system/addon.d since some rely on it heavily, so you can choose to review those directories' contents and whether you want to leave them enabled on your own. I also left out disabling sysctl.conf since that's done by f.K and the Franco's Dev Team scripts, and also seemed a bit heavy-handed for this zip script.
Download counts for the previous versions: 790; 2678.105Sure. Happy to post my franco.Kernel settings here for anyone who wants to try them. I'll keep these up-to-date if I change them.
These are my f.K settings, my DirtyV settings can be found here.
Fsync on just in case anything ever happens I want my data protected. That said I do disable it temporarily if I ever want a bit more performance in an app or game. SR is hardcoded disabled in the latest builds.
The other thing worth noting is I set my color settings on boot with an init.d script. Doing it that way you can end up with a completely different result from the same values. The contrast, blacks and colors are much more natural. Also it's seamless which is nice; they take effect during the Google logo. Attached is my init.d script for that. Alter it to your own color settings, remove the .txt extension, push to /system/etc/init.d/ and set the correct perms; rwxr-xr-x (chmod -R 755 /system/etc/init.d in Terminal Emulator).
900colorsettings can be found with my other init.d scripts (from Franco Dev Team), here: https://s.basketbuild.com/filedl/devs?dev=osm0sis&dl=osm0sis/scripts/900colorsettings
Note: On my new replacement screen, setting the color multiplier too early in the boot (any time before the boot animation) made everything look dark, oversaturated, uncontrasted and dusky; basically the opposite of the way it used to work on my old panel. Adding sleep 2; before that line in the init.d script fixed this, so experiment if your panel is more like my new one, and the init.d as-is after you put in your settings makes it look worse.
[ New init.d script with my new colors. I need the sleep 4 because of my problem in my "Note" above, so comment it out if you don't need it, it will make it look worse. Previous download counts were 1880, 646, and 307. Thanks everyone! ]
New posts
-
-
-
Question Sony Xperia 1 mark V china up rom SEA, Can use update OTA
- Latest: Laclevuinhon
