You rock, my friend. The amount of work that you put into this stuff, for free and because of enjoyment, is amazing.
RF
RF
[KERNEL] [GPL] [GN] franco.Kernel r398
- Thread starter franciscofranco
- Start date
Never had audio/google play music problems with r356 nor r357
Inviato dal mio Galaxy Nexus usando xda premium
Inviato dal mio Galaxy Nexus usando xda premium
The audio chip on this device is strange. I'll try to fix it, I think I know what is the problem in my code
never had the chance to thank you myself...awesome work! The frequency of updates is simply insane :silly: Thanks man :good:
The audio chip on this device is strange. I'll try to fix it, I think I know what is the problem in my code
Is there any chance this will make the over all volume louder when 60hz is boosted when playing from phone speaker? I know its too low to hear from the phone speaker but sounds better on head phones and the bass boost doesn't really work for really low notes
Sent from my Galaxy Nexus
On 357, when I plugged in the line out and played music it would rapidly switch between playing on the desk speaker and the phone speaker. Unplugging and plugging it back in changed nothing so I turned the volume down on the phone and it went away. This was last night. Earlier today though the music just stopped like it did on 356 if the volume was up all the way.
And on 348 all was fine too, I don't think the audio boost was in at that point
Sent from my Galaxy Nexus using xda premium
Also I would like to apologise to allgsmnetwork and everyone else here for making a **** of my self having a rant, my post got deleted and rightfully so by a moderator so sorry to who ever it was who had to deal with that, if I got reported I'm not surprised in all honesty. I was having something of a bad day, not that excuses help and more than anything else I feel perhaps maybe I might of lost some respect from you guys by showing off. So again I'll say sorry. Normally I'm I'll with helping less experienced guys and accumulated my this meter mostly like that.
Sent from my Galaxy Nexus
Sent from my Galaxy Nexus
osm0sis
Senior Recognized Developer / Contributor
Yup! That's it. It's 2 now.
sound: reduce one step on volume boost because previous value was making some users have their music stop randomly.
https://github.com/franciscofranco/Tuna_JB_pre1/commit/e2f047dece3e38f20fa3d46c2ebdd4b4e09d3f9c
Last edited:
Yes but if you continued to read, I mentioned that I was also having the same problem with franco's kernel, I fixed my problem though
Sent from my Galaxy Nexus using xda premium
Looks like 357 solved all issues i had with audio :good::highfive:
Thanks franco for all your hard work and continued support
Thanks franco for all your hard work and continued support
Battery works quite longer with 356/357 than earlier builds. Attached results I got from 357 on stock kernel settings (including Gov/IO, clock speed, UV) and on EDGE. Screen on time 4:15hr is by far the best by my any android phone till now. And oh I started off at 98% battery (Battery Life Extender set on 98%).
Franco, you are master of kernel tuning.
Franco, you are master of kernel tuning.
Attachments
Exactly I reason so 'always help the less experienced and do not take them for a ride like that screenshot of the monkey and to thank all went over the edge and I made the report to the moderator otherwise only those users with the brain half continued.I hope you understand me...
I think this one was the worst translation yet.
However, in all fairness, I'm sure my Italian would make allgsmnetwork laugh just as much if not more. I do like his point of helping the less experienced (like me).
Sent from my Galaxy Nexus using Tapatalk 2
Last edited:
Screen shot of the monkey? LOL are you talking about my confession bear?
Sent from my Paranoid Maguro
Same here. I have SODs quite often.
Stock GSM ROM (4.2.1)+ always the latest franco nightly.
Any ideas?
Sent from my Galaxy Nexus
I had a single SOD #357 maybe too much UV is stable now, videos of you tube feel at low volumes also stock kernel in telephoning speaker good :confused :
Been using r357 for 2 days now an not a single sod, so its a keeper this time.
Sent from my Galaxy Nexus using xda premium
Sent from my Galaxy Nexus using xda premium
been using r357 for one day and no problem so far, a bit smoother than r348. will keep using it
Edit: using stock 4.2.1 and just raised the CPU frequency a bit with other setting untouched
Edit: using stock 4.2.1 and just raised the CPU frequency a bit with other setting untouched
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! ]
