Its been discussed already. Try to turn on the High Performance Sound in the Franco app
Sent from my Galaxy Nexus using Tapatalk
[KERNEL] [GPL] [GN] franco.Kernel r398
- Thread starter franciscofranco
- Start date
Its been discussed already. Try to turn on the High Performance Sound in the Franco app
Sent from my Galaxy Nexus using Tapatalk
Sorry didn't mention this info.
The headphones work when the phone is locked and stock.
The headphones worked when I rooted and flashed AOKP b27 w/ the Kernel included.
It also worked on Milestone 4 of AOKP. Now though after I flashed the Milestone1 Kernel and the subsequent nightlies it does not work.
If I completely wipe and go back to stock it works fine. It's just when I flash the Franco kernel I lose headphone support.
Yeah but then I waste more battery. I shouldn't have to enable that in order to fix a problem 
but I guess I have to
but I guess I have to
Yeah but then I waste more battery. I shouldn't have to enable that in order to fix a problem
Yeah it sucks.
Sent from my Galaxy Nexus using Tapatalk
@Francisco and anyone else, is there any reason you changes ondemand threshold to 80 instead of 98? I've been using it at 95 for the past few nightlies but I'm curious to know why the switch. Trying out 80 right now, but I'm just wondering
Sent from my Galaxy Nexus using XDA
Sent from my Galaxy Nexus using XDA
Because it moves up faster
Sent from my Galaxy Nexus using xda premium
Well obviously
but I was wondering if Franco had done any tests to show that this trade off between better battery (higher threshold would mean less switching and lower voltage at lower speed) vs performance from moving up faster Sent from my Galaxy Nexus using XDA
Man thats really weird, i'm on AOKP Milestone 4 + Franco Kernel Nightly r97, and i have the headphones working and device its fliying.
Headphones work just fine as well here.
About the threshold, it's true that with higher threshold should wield better battery in the long run, but I found out, at least for me, that it hurts interactivity too much, and I'm not willing to sacrifice the smoothness for an extra 30minutes of screen time (I just made up this number, dont use it to justify anything you want to claim as true, it's made up). And 80% is also pretty aggressive so why change it?
About the threshold, it's true that with higher threshold should wield better battery in the long run, but I found out, at least for me, that it hurts interactivity too much, and I'm not willing to sacrifice the smoothness for an extra 30minutes of screen time (I just made up this number, dont use it to justify anything you want to claim as true, it's made up). And 80% is also pretty aggressive so why change it?
That'll be your phone pooping so make sure you clean it up.
Yeah but then I waste more battery. I shouldn't have to enable that in order to fix a problem
Its called a work around guys. As has been said many times in the pages before this, the issue is with Ezekeel's sound mod so cannot be fixed by Franco.
Same here, listening to tunes as I type this.
Sent from my Galaxy Nexus
Is this kernel doing something with the brightness?
I'm probably just imagining it but I switched between this and other kernels a few times and I just always have the impression that (with the same brightness settings) the screen is slightly darker with this kernel.
Can't find any mention about that. Maybe because I'm just seeing things.
I'm probably just imagining it but I switched between this and other kernels a few times and I just always have the impression that (with the same brightness settings) the screen is slightly darker with this kernel.
Can't find any mention about that. Maybe because I'm just seeing things.
That top quote is from the OP, maybe you aren't reading?
You can control it via Franco's app.
Sent from my Galaxy Nexus
Thanks all for the replies, maybe it's just the kind of headphones i'm using.
They have those little switches on them. (edit: the ones that let you play, skip tracks, pause and such)
2 pair came with my G2, and the others came with my MyTouch phones so they're also old.
I'll pick up a pair of standard headphones and give those a try.
Thanks!
They have those little switches on them. (edit: the ones that let you play, skip tracks, pause and such)
2 pair came with my G2, and the others came with my MyTouch phones so they're also old.
I'll pick up a pair of standard headphones and give those a try.
Thanks!
Last edited:
Hi
Does anybody here use third party text to speech engines? i use inova and it stopped working. the default engine works fine here. I tried Pico TTS and it is not working too. I don't know if it is related to the kernel, but it was working fine before. i am on AOKP M4+ latest r97
Does anybody here use third party text to speech engines? i use inova and it stopped working. the default engine works fine here. I tried Pico TTS and it is not working too. I don't know if it is related to the kernel, but it was working fine before. i am on AOKP M4+ latest r97
Try wiping one more time and get the lateste nightly kernel first and see what happens. Maybe its also a weird app causing it?
Sent from my Galaxy Nexus using Tapatalk
Honestly im using r96 and im getting amazing better life and smoothness, im using ondemand and it gives me more juice and battery than when i had turtle! And uv works great too! Dont care much for r97 not worth the reboot lol but all in all thanks franco! Ur the best.
Sent from my Galaxy Nexus using Tapatalk
Sent from my Galaxy Nexus using Tapatalk
niksko - why dont you try using the gnex toolkit and completely reinstalling the stock yakju image packages from google? (i.e. bootloader, kernel, system, radio, data). if that doesnt get you back up again, im not sure what will.
you can then reflash your optus radio back if it works better for you. i know from my own testing that the telstra radio gives me about 1mbps more on average than the generic radio. any other roms shouldnt matter after you get that bit right.
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! ]
