Related
Basic with a Twist SGS4G KJ6 Kernel
BML, don't flash if you have partitions converted to MTD.
Use at your own risk, I take no responsibility for anything that may happen to your phone because of this kernel.
This kernel is for those who don't want to be on the very cutting edge (CM7) but rather want stability without sacrificing too many recent features. It is based mostly on Bryan's 0.0.2d commit that supposedly never had problems with silent reboots. I made some changes to the config to bring it even more to the standard Samsung VibrantPlus in terms of hardware settings, but at the same time to optimize it for speed. I will add only tried and true features to this kernel, the ones that other kernel developers have used successfully.
Special thanks to bhundven (Bryan), FBis251, TeamAcid.
Features
initramfs from TeamAcid, including CWM5, SuperSU, forced ext4, etc.
Usual CIFS, TUN. I didn't include FUSE, if anybody needs it let me know.
BLN. Use BLN Control app from market to activate.
Voodoo Sound so paid app is not needed. Voodoo Sound app from market is required. Once installed, enable Smart Amplifier, it's the best thing you can do to improve music listening experience with our phone.
jhash3 for faster hash calculations. Used widely across the kernel, especially in networking.
OC/UV support with extended frequency table. Added 600Mhz, 900Mhz, 1.1Ghz, 1.2 Ghz, 1.3 Ghz, 1.4 Ghz. Use SetCPU or Xan's Voltage Control to enable and control frequency and voltages. Tegrak can be used only with no-OC/UV version.
ondemandX and smartassV2 governors. One of these should probably be preferred over stock ondemand. Change with SetCPU or similar.
TinyRCU. More lightweight version, it fits better our single CPU system.
Swap support, although I don't recommend using it.
SIO and BFQ I/O schedulers in addition to noop, deadline, and cfq that we already have.
Install
Flash with CWM or SGS Kernel Flasher. ODIN version is available only for OC/UV kernel.
Download
CWM:
v1.1.3
v1.1.3 (no OC/UV)
v1.1.2
v1.1.2 (no OC/UV)
ODIN:
v1.1.3
v1.1.2
Notes
* OC/UV version is very conservatively undervolted to -25mV. The preset voltages are still higher than on regular I9000, which has the same CPU. I'm running additional -50mV (total -75mV) for all frequencies without issues, but you may have them, every CPU is different!
* It is recommended to create a CWM recovery file before modifying voltages. This option is available in both SetCPU and VoltageControl.
* OC-ing to 1.4 Ghz is not recommended, especially for extended periods of time.
* Voodoo ext4 conversion, or "lagfix", is enabled and forced by default. There is not way and no need to go back to RFS.
Source
www.github.com/AntonX
Changelog
1.1.3
CWM 5.0.2.8 (blue) in initramfs
Disabled a little more of Samsung debugging
1.1.2
Minor changes to initramfs voodoo extension scripts
More neutral boot logo
1.1.0
Initramfs script will not force su update
Couple of small changes
1.1rc2
Few small changes
1.1rc1
Added BFQ and SIO I/O schedulers
Switched to TinyRCU
Added Swap support
Small change to Vibetonz
1.0b5
Some changes to OC/UV
Better BLN fix
Increased write timeout for bad SDHC cards
Added ondemandX and smartassV2 governors
Renamed the title, it's becoming less and less Basic...
1.0b4
Added native OC/UV support
1.0b3
Minor BLN changes
Replaced jhash.h with jhash3 code
Updated initramfs with SuperSU 0.88
1.0b2
Added BLN, first attempt
1.0b1
Original release
Let me be the first to push you....please consider BLN lol, that would be awesome!
Could you point me to the right repository/branch?
I'm curious to see your changes and I'm probably not looking in the right place on github.
Please add BLN
bhundven said:
Could you point me to the right repository/branch?
I'm curious to see your changes and I'm probably not looking in the right place on github.
Click to expand...
Click to collapse
Well, I didn't upload anything yet. If you tell me how to control the frigging repository from Windows I'll do it right away
But seriously I want to make absolutely sure that this kernel doesn't have this nuisance of silent reboots. Because it they still present there is no need to have this kernel.
No matter what happens, if Vooodoo sound works without problems, I'll give you the code if you want it.
AntonX said:
Well, I didn't upload anything yet. If you tell me how to control the frigging repository from Windows I'll do it right away
But seriously I want to make absolutely sure that this kernel doesn't have this nuisance of silent reboots. Because it they still present there is no need to have this kernel.
No matter what happens, if Vooodoo sound works without problems, I'll give you the code if you want it.
Click to expand...
Click to collapse
I'm about to post something to my cm7 thread, so heads up.
But stock kj6 kernel (if you download it from opensource.samsung.com and apply a few of my changes to fix tfsr and add initramfs) still has the same reboot issue.
I'm gonna start comparing some of the code from the froyo kernel to see wtf is going on. I fixed a problem with rild and random reboots are back.
I'm finding that the problem is related to suspend. The reboot happens when everything quiets down.
AntonX said:
If you tell me how to control the frigging repository from Windows I'll do it right away
Click to expand...
Click to collapse
Haha, I don't even know. Don't use Windows?!?
put BLN in!!!! (i would do it myself, REALLY, i would but i don't know how)
bhundven said:
But stock kj6 kernel (if you download it from opensource.samsung.com and apply a few of my changes to fix tfsr and add initramfs) still has the same reboot issue.
Click to expand...
Click to collapse
I'm operation on the assumption that 0.0.2d never had silent reboots. Nobody ever reported having them with this version. I have never ever experienced a reboot with it myself. That's why I took it as the base.
I haven't really looked what you did right after 0.0.2d. Seems like you switched to aries config instead from vibrantplus. Any particular reason? Anyway, I reverted it back and even slightly more back. Then you did some clean up and modified bunch of code. I don't care about cleaning somebody else's code like this. Unused functions and variables will be optimized out by the compiler anyway. To get rid of annoying warnings I just used -Wno-unused switch to gcc in the Makefile.
So - hard to tell what's happened between 0.0.2d and 0.1.0 (or 0.1.1?), but something must have happened. Too many people reported it to support this.
Great initiative Anton!
Flashing it on 2 devices. I will update in 3 days.
Sent from my SGH-T959V using XDA
Anton
Just flashed. I'm fully charging up right now. I'll run it for a day to check on battery life and do some restores to make sure all that is good to go. Including voodoo is a nice touch. A already have the paid app because the headphone amp is something I can't live without but really nice for those that haven't used it to check it out. I have never had a reboot on 2d so hopefully this will maintain that tradition. Nice work.
is voodoo sound fix better than the beats audio??
m0bstr said:
is voodoo sound fix better than the beats audio??
Click to expand...
Click to collapse
Voodoo is hardware. Beats audio sodtware
Sent from my SGH-T959V using xda premium
Voodoo Sound, awesome!
Thanks man.
Sent from my SGH-T959V using XDA
I've never used voodoo sound before, but wow I was missing out..... Separation seems slightly better, clarity, just everything is awesome... And being able to adjust output gain is nice too.
Also, so far, no reboots.
Sent from my SGH-T959V using XDA
Finally a kernel w/ Voodoo Sound! I've been using the paid app for awhile but the module doesn't load on boot sometimes plus I've always wondered if there might be a difference between the app loading the module vs. the module built in to the kernel. I've gotten really use to BLN though (hint-hint)... thank you!
Sent from my SGH-T959V using xda premium
Another request for BLN. Hope we have enough voters!
Figures, as soon as I jump ship voodoo sound comes out to play...
Sent from my Galaxy Nexus using XDA
tehgyb said:
Figures, as soon as I jump ship voodoo sound comes out to play...
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
gnexus lol
so far not a single problem, touch wood...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Oh, you'll love this.. So what actually is different in this kernel?
Core
Updated to 2.6.39.1
Brain F*ck Scheduler implemented for fast task switching, smooth scrolling and possible power saving
Code cleaned and optimized in the right places
Updated Android Binder, Ashmem and Timed GPIO drivers from 3.10-rc5 upstream sources
Compressed with the fastest compressor on the market: LZ4
Processor
Updated CPUFREQ drivers
Voltage Control (undervolted by default to a range of stable values)
Aggressive Overclock
PLL2 Overclock possible inside the app
Updated all the governors to their latest versions
Zen Governor written exclusively for our SoC
Zen
Borrows part of its scaling logic from SmartassV2
Adds Zen Dynamics
This feature makes the governor's parameters completely dynamic. The parameters change by themselves based on various system information (cpu load, suspended state etc.) This ensures that the governor will not bump to high frequencies when it is not needed, and that it will provide enough computational power in high workload cases.
Performance Bias parameter
This is a simple number between 0 and 15 and the only tunable parameter of the Zen governor. When this is changed every other parameter is recalculated through different formulas based on this value. A higher value will make your phone snappier, at the cost of some battery life and viceversa.
TouchPulse and SweepPulse interfaces
TouchPulse is the updated and much more accurate version of the older BoostPulse. This works by giving a slight boost on user input (key or touch).
SweepPulse shoots the CPU frequency to the maximum value when a Sweep function is activated to ensure best responsivity. Don't worry, this happens very fast, so no battery life is wasted in the process.
Suspend profile
When the screen is turned off, the governor keeps the power usage at minimum by re-tuning its parameters
Memory
LowMemoryKiller updated from 3.10-rc5 upstream sources
LMK Whitelist
This is a list of apps which will never be killed by the system, unless you do it intentionally.
I didn't have time to implement a better way for adding apps to this list, so I'll explain the primitive and only usable way right now.
In /system/etc/Badass you will find a file called whitelist. This file can only contain apps in java class path form, separated by commas. Like this:
com.touchtype.swiftkey, org.adw.launcher, com.whatever.app
All the apps that you add to this list, will be written to the LowMemoryKiller at every boot.
LMK Aggressivity: this parameter makes app-killing more or less aggressive. It can be controlled inside the app.
Latest ZRam driver with LZ4 compression (activated at boot so you won't have to bother)
Sweep functions
When the screen is off...
Sweep2Wake
This gesture wakes the phone by sliding your finger from left to right in the middle of the screen
Its sensitivity is controlled by a single parameter (factor) which can be modified inside the app
DoubleTap2[Wake/Play/Pause]
This gesture wakes the phone with a double tap on the screen if the lock timeout of 5 seconds hasn't passed yet. If the timeout has passed, double tapping the screen will Play/Pause the music.
The Media Control feature (Play/Pause) can be disabled, making DoubleTap2Wake work even after the lock timeout has passed.
Pocket Keyguard
This feature prevents accidental unlocks when the phone is inside your pocket.
When the screen is on...
Sweep2Lock
SweepKeys
All these functions work by swiping up from the first 3 pixels at the bottom of the screen(deadzone).
The Deadzone and the Sweep sensitivity are changeable in the app.
*Sweep4Menu is only available for Galaxy Mini
Internet
Westwood+ TCP Congestions Algorithm
Adaptive RED net scheduler backported from 3.4 upstream sources
Congestion window values tweaked
TCP Proportional Rate Reduction
Performance
Zen and ROW I/O schedulers
Triple Buffering
TinyRCU
Dynamic Filesync
Using the 20-50x faster frandom generator instead of the default random.
Never depleting entropy using Haveged and some new kernel code.
Dynamically changing kernel values based on suspend profiles (writeback ratios, cache pressure etc)
System cleaning every 3 days:
Zipalign every apk
Vacuum and Reindex every SQLite database
Clean the garbage data created by the system
Clean app caches
SpeedMod (disable kernel debugging)
Remove 98% of the active debugging code
USB Fast Charge
Native Multitask Enhancer
Replace services.jar Supercharging with a more native approach
Make Home app unkillable
Raise PreviousApp priority to make task switching faster
Handle CPU time allowed for the foreground app
Raise priority of the following processes
Kernel Threads
ALSA driver (audio playback)
Keyboard
SystemUI
Restrict resources used by the media scanner
Dev's last words (a.k.a. read this carefully before saying anything stupid)
This is a stable version and I call it final. I won't update it, unless there are some major bugs like setting phones on fire, giving them artificial intelligence or sh*t like that.
DON'T USE ANY OTHER TWEAK ON THIS KERNEL. These tweaks include, but are not limited to:
Performance Pack
Fly-On Mod
CrossBreeder
I/O Tweaks
V6 Supercharger
Whatever else with a cool name which has the words script, pack or mod in it
Don't get me wrong, these mods are good (most of them), but what's good is already included in the kernel itself
Use Greenify. It is an awesome app, and it does its job very well. I couldn't fully replicate its' features inside the kernel because I don't have access to Android APIs.
The first boot will be slow, due to the zipaligning and SQLite optimizing. Don't freakin' panic. This will happen only once in three days.
If you feel that the system is slow with the kernel, raise the Performance Bias, the LMK Aggressivity and maybe your max CPU frequency. The default values are optimized for ICS, not JB. Play with those values until you find that sweet spot.
Change your damn Superuser app. Use SuperSU or an insecure SU binary. The original SU binaries found on ROMs are freakin' slow nowadays.
Even better, use ICS. JellyBean is not for our low-end phones. But, your choice..
The key settings for the SweepKeys are ROM dependant. For example Recents SweepKey might not work on some JB ROMs. I can't do anything to fix this.
Don't be lazy. I'm here to help, but please show me that you've made some effort on the research for your questions.
And the thanks go to..
Androidarmv6 Team
Erikcas
psyke
A_U
Franco
Boype
Benee
AOKP Team
Paul Reioux (Faux)
Stratosk
zeppelinrox
Ezekeel
Downloads
Badass.v2(AOKB-JB).zip - 6.67 MB
Badass.v2(AOKP-ICS).zip - 6.67 MB
Badass.v2(AOSP-ICS).zip - 8.91 MB
Badass.v2(CM9.2).zip - 6.65 MB
Badass.v2(CM10.1).zip - 6.67 MB
Badass.v2(CM10).zip - 8.91 MB (UMS not working)
Installation
Boot into recovery
Wipe data
Re-flash your current ROM to avoid conflicts
Flash the appropriate kernel zip
Reboot and wait 5-10 minutes for the first boot to complete
Use the integrated app to control the kernel
Source:
Badass-BFS
Reserved
This is just for custom ROM?
ZmisiS said:
This is just for custom ROM?
Click to expand...
Click to collapse
um yes considering its for android 4.0 and above (not yet for android 4.3).
the ROM name for each kernel is labeled in the link(bottom of the first post).
Does it increase camera and gallery performance in cm10.1? Bcoz the camera and the wait time to the picture be loadeed in gallery was so laggy. Btw thanks, great job.
wow! thanks for your hard work o this project
i installed V2 on my miuiV4 and it's really smooth . multitasking is really better than previous version.
first i thought that sweep2things are buggy but after a day of working , i'm now comfortable with it.
- in word of performance it's perfect. thanks
- deep sleep works fine. :victory:
- i got some FC in controll app. first time that phone booted before i grant su permission i got so many FCs continuously!!
- sweep2wake sometimes doesn't work. after i puted and picked up my hand on proximity sensor , sweep2wake worked
- i'm not sure about this but it seems sometimes in sunlight prox sensor doesn't work at all (for sweep2wake function)
and thanks again !
ehsan-black said:
wow! thanks for your hard work o this project
i installed V2 on my miuiV4 and it's really smooth . multitasking is really better than previous version.
first i thought that sweep2things are buggy but after a day of working , i'm now comfortable with it.
- in word of performance it's perfect. thanks
- deep sleep works fine. :victory:
- i got some FC in controll app. first time that phone booted before i grant su permission i got so many FCs continuously!!
- sweep2wake sometimes doesn't work. after i puted and picked up my hand on proximity sensor , sweep2wake worked
- i'm not sure about this but it seems sometimes in sunlight prox sensor doesn't work at all (for sweep2wake function)
and thanks again !
Click to expand...
Click to collapse
Thanks for the review.
Yes, in bright sunlight the infrared sensor can be saturated and take wrong readings. I can't fix this unfortunately.
As I said in the Mini forums, I found a small flaw in the Sweep code and I will release a fix as soon as I get my laptop. This should make a better user experience with the Sweep functions.
First of all, thanks for your work
My review of Badassv2 in AOSP-ICS 4.0.4:
:good:
- The BadassControl app sometimes get FC but nothing to get relevance
- General performance are so good, i've never see my apps open so fast
:crying:
- After 30 minutes, when i open an app, it freezes and I'm obliged to remove the battery and turn on the device :/
-After the third reboot, the phone stays in bootloop and it never boot normally
So sad of this, because I love so much its performance... Anyway, thanks again
Well i tried on CM9 and CM10.1. Performance wise, its so good on CM9 but on CM10.1, it just lags many times (while opening any of apps and opening app drawer itself). I tried all the governors, OC and changed badass settings still lags appear. Previous version 1.9.2 is much better. So no matter how stable the kernel may be, we can't get much performce in CM10.1 right?
And for sweep functions, only doubletap2wake functions for the first time while booting and the screen lock disappears for first time. Even tried to cover proximity sensor but both s2w and dt2w wont work for me.
And sweep2lock also doesn't seem to work for me or am i doing it incorrectly?
If anyone observe CM10.1 to be more stable with no lags using this kernel, will u please share what governors and settings did u use?
swat4samp said:
Well i tried on CM9 and CM10.1. Performance wise, its so good on CM9 but on CM10.1, it just lags many times (while opening any of apps and opening app drawer itself). I tried all the governors, OC and changed badass settings still lags appear. Previous version 1.9.2 is much better. So no matter how stable the kernel may be, we can't get much performce in CM10.1 right?
And for sweep functions, only doubletap2wake functions for the first time while booting and the screen lock disappears for first time. Even tried to cover proximity sensor but both s2w and dt2w wont work for me.
And sweep2lock also doesn't seem to work for me or am i doing it incorrectly?
If anyone observe CM10.1 to be more stable with no lags using this kernel, will u please share what governors and settings did u use?
Click to expand...
Click to collapse
Well I tried on CM10.1, works smoothly for me, I used Zen as well as On Demand governors & zen I/O Scheduler..
Also sweep functions did not work fr me aswell (Tried alot of things bt couldn't get it to work)
Otherwise the kernel is amazing, snappier than the default kernel..
b_dev said:
Well I tried on CM10.1, works smoothly for me, I used Zen as well as On Demand governors & zen I/O Scheduler..
Also sweep functions did not work fr me aswell (Tried alot of things bt couldn't get it to work)
Otherwise the kernel is amazing, snappier than the default kernel..
Click to expand...
Click to collapse
Do u use default settings or tweaked a bit? Did u do a clean install?
swat4samp said:
Do u use default settings or tweaked a bit? Did u do a clean install?
Click to expand...
Click to collapse
I tested CM10.1 and I admit it is not smooth. But it's because I used ICS before and the difference is so much more noticeable. When Sweep functions don't work, it's because the app doesn't work as expected. If you delete the app, everything will work. I don't use Jelly Bean so I can't guarantee anything for it.
Sent from my GT-S5570 using XDA Premium 4 mobile app
alin.p said:
I tested CM10.1 and I admit it is not smooth. But it's because I used ICS before and the difference is so much more noticeable. When Sweep functions don't work, it's because the app doesn't work as expected. If you delete the app, everything will work. I don't use Jelly Bean so I can't guarantee anything for it.
Sent from my GT-S5570 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
True with CM10.1 but ur previous version 1.9.2 gives good results if we OC to 652mhz. Although CM9 kernel is stable and has best performance n multitasking along with battery life. Maybe i have to live with CM10.1 version. Will u make one for CM10.2 please? A basic version without sweep functions and less governors and shedulers maybe.
swat4samp said:
True with CM10.1 but ur previous version 1.9.2 gives good results if we OC to 652mhz. Although CM9 kernel is stable and has best performance n multitasking along with battery life. Maybe i have to live with CM10.1 version. Will u make one for CM10.2 please? A basic version without sweep functions and less governors and shedulers maybe.
Click to expand...
Click to collapse
Sorry but I can't revert all that stuff to make a basic version. It's not as easy as it sounds. I'll work on a CM10.2 kernel if there is any hope to get a fully working version of the ROM. Otherwise, I'll just make it bootable.
Sent from my GT-S5570 using XDA Premium 4 mobile app
alin.p said:
Sorry but I can't revert all that stuff to make a basic version. It's not as easy as it sounds. I'll work on a CM10.2 kernel if there is any hope to get a fully working version of the ROM. Otherwise, I'll just make it bootable.
Sent from my GT-S5570 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I know its too difficult to make one. But as CM10.2 development is going faster and its faster in performance compared to CM10.1. So maybe u can take a look once and decide for yourself .
alin.p said:
I tested CM10.1 and I admit it is not smooth. But it's because I used ICS before and the difference is so much more noticeable. When Sweep functions don't work, it's because the app doesn't work as expected. If you delete the app, everything will work. I don't use Jelly Bean so I can't guarantee anything for it.
Sent from my GT-S5570 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey alin, regarding my review.. do you suggest to delete your app?
galfit said:
Hey alin, regarding my review.. do you suggest to delete your app?
Click to expand...
Click to collapse
I suggest changing your su binary. If you don't want to do this then you can delete it.
Sent from my GT-S5570 using XDA Premium 4 mobile app
alin.p said:
I suggest changing your su binary. If you don't want to do this then you can delete it.
Sent from my GT-S5570 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm using SuperSU 1.65... Isn't it good?
galfit said:
I'm using SuperSU 1.65... Isn't it good?
Click to expand...
Click to collapse
It is good but you must set it to always grant permission, not ask for it.
Sent from my GT-S5570 using XDA Premium 4 mobile app
alin.p said:
It is good but you must set it to always grant permission, not ask for it.
Sent from my GT-S5570 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Done! And it works :victory: Thanks
Hi all,
Running Slimkat 4.4.1 beta 4, with Bank gapps running ART.
Everything is working pretty well, except for Trickster MOD keeping settings.
It will keep the scheduler and governor selection, but min and max freq and sound control doesn't stick.
Perhaps MPDecision is causing the issue or? Even tried switching to a custom kernel, same thing.
Any advice would be great, thanks everyone.
(I have already gone over most of the Trickster MOD website faq and general questions. And other threads on xda.)
Sick avatar bro!
Sent from my Nexus 5
THIS IS NOT COMPATIBLE WITH CM11 NIGHTLIES AS OF 5-8-2014 BUILD DATE.
I'll update it to be compatible as soon as I can.
Moretz - Final
"She's done, this is the end of the line."
Features:
- Linux 3.0.101
- Ultra KSM 0.1.2.2
- Dynamic Read Ahead
- FRandom
- Dynamic FS Sync (by faux123)
- Android Low Memory Killer
- SLUB (back ported from Linux 3.3 by faux123)
- Voltage Control (OV/UV)
- Tweaked min/max allowable voltages
- Tweaked CPU bus speed (added 400MHz)
- Clock Speeds: 192MHz - 1.78GHz
- 3D GPU Clocks Up to 320MHz
- 3D GPU Max Freq Control (Kernel Sysfs: /sys/kernel/gpu_control)
- 2D GPU Clocks Up to 266Mhz
- 2D & 3D Bandwidth Increase
- KGSL (GPU) Tweaks
- Added Scheduler: BFQ v6, SIO, V(R)
- Added Governors: Ondemand 2 Phase (modded), SmartassV2 (modded), Badass 3 Phase, Lionheart (tweaked)
- USB Fast Charge
- MSM MPDecision (Enables hotpluging across all governors) - modded for dual core CPU
- Smart Zipalign at Boot
- SQLite Optimize Databases at Boot
- Sync CPU governors (thanks elbermu)
- Sync CPU frequency policies (thanks elbermu)
- sweep2wake
- BLN support
- Mutex tweaks
- TCP network tweaks
- Other small tweaks / fixes / enhancements
Compatible ROMs:
CyanogenMod 11.0
(Guinea pigs feel free to test others and report back ...)
Thanks:
Team Chopsticks
Project Mayhem
Team ROOK
Cyanogen
InstagatorX
roger_n
The Muppets
ktoonsez
elbermu
toyes
mindmajick
franciscofranco
Your Mom
mtdew
Cl3Kener
faux123
Special Thanks:
To everyone in the SR forums, this is my last project release for you guys. You've been fun, you've been jerks and everything in between. It's been a really fun ride and I've enjoyed every minute.
Seriously, you guys are awesome. Thank you.
Sauce: https://bitbucket.org/carvsdriver/android_kernel_samsung_msm8660-common/
Code:
[CENTER][B]Installation Instructions:[/B]
Download
Nandroid
Flash
Reboot
Enjoy![/CENTER]
Download Moretz-Final Here
Link: http://d-h.st/CoU
MD5: 50055619ca662019ec0f5dffe32a07d8
Click to expand...
Click to collapse
One more for any break/fixes.
For the record, I only tested this for like 10/15 minutes ... please report any bugs with a last_kmsg and/or logcat. I will be around to fix critical problems. So it's tentatively a final version pending bug reports
CVD at it again. Kudos for keeping the skyrocket a beast.
Oh lord Jesus its a kernal ! thanks !! @car vs driver
AndroidGee209 said:
Oh lord Jesus its a kernal ! thanks !! @car vs driver
Click to expand...
Click to collapse
You're welcome sir.
Booted fine on latest carbon nightly. Thanks, man.
SGH-I727 Peace
This will work on any CM11 based ROM right?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
DSDONE said:
This will work on any CM11 based ROM right?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
as noted in the OP, only cm11 has been tested but only for 15 minutes. YMMV
test and see for yourself!
I can say for sure that carbon nightly boots fine
Sweet! If it boots on carbon ROM, I feel that it will boot on AOSB...
Sent from my SAMSUNG-SGH-I727 using Tapatalk
It'll boot on any of the CM based ROMs, they all use the same 3.0.y kernel. The only caveat is if any of the non-CM distributions have modded the kernel to include specific features for their ROM.
Flash it and find out. Worst case is that it doesn't boot or runs like dirt for some reason. You can always just revert back to whatever kernel your ROM has by reflashing it.
I don't use any of the other ROMs out there, so I cannot test or verify that all features work. So to be safe and have less of a headache, I don't officially support them (even if they do work perfectly well).
Confirm, boots fine on AOSB 4.4.2 ROM! I'll continue to run it... Seems stable... Good job devs! ?
?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Works great on Beanstalk as well! So glad there has been an update!
Another kernel for our skyrockets, i was waiting for this one since i had KitKat. Great job once again. :good:
2 questions,
Q1: Are you using source from CM?
Q2: Do you even plan something with Linux 3.4?
I tried your kernel with the lpa.decode fix from my post in the CM 11 thread and I noticed that audio will stutter for a split second every now and then. It works perfect with the CM kernel, but I am getting an error on a logcat of "AudioPlayer This indicates the event underrun case for LPA/Tunnel." I am not sure if the kernel is set to use lpa and since the fix disables it from build.prop if that is what is causing the error, but I was wondering if you could help? Thanks again for your support.
Care to elaborate on what the LPA fix is?
Sent from my Nexus 5 using XDA Premium 4 mobile app
They are changing one line in the build prop to disable lpa. Pretty sure its a workaround not a fix.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Oh... What exactly is that addressing?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Something about their audio issues I wouldn't know much more since Google play music has been flawless for me for some time now.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
car vs driver said:
Oh... What exactly is that addressing?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It is addressing the sudden pop when playing music through Apollo, DSP Manager effects not working correctly and certain Bluetooth streaming. If I change the "lpa.decode=true" in the /system build.prop to false, it fixes all the problems that I've had with CM 10.2 and CM 11. When I flash this kernel, it has a sudden stutter in music with that logcat message I posted earlier. Some users who have tried the fix said it fixed these issues with them too. I did email @roger_n about this possible permanent fix so it could be merged with the CM nightlies, but so far no response.
@TheCybertronian, I have tried Google Play Music in the past when this issue came up, but the sudden pop when skipping songs would still come up occasionally when a song would start to play. Granted this was awhile ago since I last tried Play Music with lpa enabled, but this was the only solution so far that worked with Apollo and DSP Manager.
Hello to everybody. Please use this thread to discuss, share and analyze prometheus kernel performance for your device. Let's keep the development thread clean.
I ll start by sharing my current synapse profile - I still use prom 1.4 - with you but DISCLAIMER - your mileage may vary depending on ASV...and other things. So do it at your own risk.
https://drive.google.com/file/d/0B3vI8d1OFCkwSkVlazVMdDAzNTA/view?usp=drivesdk
only for prom 1.4 !! I find it to be the most stable and has the best balance of battery and performance ever.
For those of you who don t know how to apply custom profiles in synapse, here s a link to a video tutorial i made.
https://drive.google.com/file/d/0B3vI8d1OFCkwbFRPMWpjcWQ3RkU/view
Why only for 1.4?
Any screenshots?
Inviato dal mio SM-G935F utilizzando Tapatalk
MScantamburlo said:
Why only for 1.4?
Any screenshots?
Inviato dal mio SM-G935F utilizzando Tapatalk
Click to expand...
Click to collapse
I use 1.4 because it s my personal favorite...feel free to use whichever version u like...
Also i m on APD1 baseband and TEKXNESIS URV 5.5 (very old) Rom.. but as long as it as this good a battery life...works for me!
Cheers all
aldoblaga said:
Hello to everybody. Please use this thread to discuss, share and analyze prometheus kernel performance for your device. Let's keep the development thread clean.
I ll start by sharing my current synapse profile - I still use prom 1.4 - with you but DISCLAIMER - your mileage may vary depending on ASV...and other things. So do it at your own risk.
Ciao
https://drive.google.com/file/d/0B3vI8d1OFCkwSkVlazVMdDAzNTA/view?usp=drivesdk
only for prom 1.4 !! I find it to be the most stable and has the best balance of battery and performance ever.
Click to expand...
Click to collapse
VERY NICE STATS!!!can you pls explain how to add in synapse your text file??
Z953RR said:
VERY NICE STATS!!!can you pls explain how to add in synapse your text file??
Click to expand...
Click to collapse
Here s a link to a video tutorial i made...hope it helps you.
Long story short - copy the file in the right directory..go to synapse...hit backup first...it gives an error, it s normal..then restart synapse and the config file will show ul. Proceed to restore as you would normally do it.
https://drive.google.com/file/d/0B3vI8d1OFCkwbFRPMWpjcWQ3RkU/view?usp=drivesdk
thank you!!!installing and monitoring!!!
Hi my name is aldoblaga, I tune my phone for performance 100% to make benchmarks and after that I tune my phone to low usage possible, plus low bright plus powersave Governor on a s7 phone to have 10h sot. I hope you enjoy my tips.
Enviado do meu SM-N930F através de Tapatalk
LiNe1771 said:
Hi my name is aldoblaga, I tune my phone for performance 100% to make benchmarks and after that I tune my phone to low usage possible, plus low bright plus powersave Governor on a s7 phone to have 10h sot. I hope you enjoy my tips.
Enviado do meu SM-N930F atrav�©s de Tapatalk
Click to expand...
Click to collapse
Word. Everybody can chose to use however they want their phone u can leave it at max performance or max battery life...or between. Your choice.
This will probably be the last battery screen that i post as it's getting repetitive.
Mostly indoor use as i was off work today, lots of web browsing, youtubing, HD movies (managed to finish Mad Men season 1 today ?), IMs e.t.c.
http://imgur.com/mIphVZr
http://imgur.com/2L4hNgf
http://imgur.com/wSANtJ5
http://imgur.com/X3uJz7K
Big Bread said:
This will probably be the last battery screen that i post as it's getting repetitive.
Mostly indoor use as i was off work today, lots of web browsing, youtubing, HD movies (managed to finish Mad Men season 1 today ?), IMs e.t.c.
http://imgur.com/mIphVZr
http://imgur.com/2L4hNgf
http://imgur.com/wSANtJ5
http://imgur.com/X3uJz7K
Click to expand...
Click to collapse
Good job. Important thing is you be happy about your phone! It s all that matters. If Prometheus kernel helped you achieve this, all the better!!!
Big Bread said:
This will probably be the last battery screen that i post as it's getting repetitive.
Mostly indoor use as i was off work today, lots of web browsing, youtubing, HD movies (managed to finish Mad Men season 1 today ?), IMs e.t.c.
http://imgur.com/mIphVZr
http://imgur.com/2L4hNgf
http://imgur.com/wSANtJ5
http://imgur.com/X3uJz7K
Click to expand...
Click to collapse
Can you tell as which rom you use and what you changed like UV or which apps you use. I would really like to reach this awesome battery life!
Maltonator said:
Can you tell as which rom you use and what you changed like UV or which apps you use. I would really like to reach this awesome battery life!
Click to expand...
Click to collapse
I use the stock touchwiz rom. My phone is currently off and charging so I can't really outline my undervolting (every phone is different), but you should use the profile which aldoblaga has provided in the first page (it should be the same undervoltage values which i'm currently using on the latest prometheus kernel and touchwiz firmware).
As for apps, i use disable services and ez package disabler to disable all those touchwiz and google bloat apps and services which are irrelevant to my daily usage. I could upload my ez package disabler and disable services app profiles, but if people use them and certain services - which i don't use, but they use - begins to malfunction (such as google cast/wear/tap and pay), then i might get a torrent of abuse from certain immature members on this forum e.t.c.
I turn on power saving (doesn't affect performance) and stick all apps into app powersaving (but i don't think it does much as all my IMs are still syncing in the background before i open them). I also use a black theme (search 'touchwiz black' in the theme store) for maximum sAMOLED efficiency (excellent black levels and power saving; win-win).
General prom kernel settings are smartmax_eps with stock cpu freqs (2.3 GHz mongoose/1.7 GHz apollo) and interactive with stock gpu freqs (650 MHz gpu). FIOPS for both internal and sd card I/O schedulers (but i'd prefer BFQ for sd card I/O, if lyapota adds it into the next update). The rest should be provided in aldoblaga's profile from the first page.
I'm still fighting some wakelocks in my device, so i still have a lot to learn
Big Bread said:
I use the stock touchwiz rom. My phone is currently off and charging so I can't really outline my undervolting (every phone is different), but you should use the profile which aldoblaga has provided in the first page (it should be the same undervoltage values which i'm currently using on the latest prometheus kernel and touchwiz firmware).
As for apps, i use disable services and ez package disabler to disable all those touchwiz and google bloat apps and services which are irrelevant to my daily usage. I could upload my ez package disabler and disable services app profiles, but if people use them and certain services - which i don't use, but they use - begins to malfunction (such as google cast/wear/tap and pay), then i might get a torrent of abuse from certain immature members on this forum e.t.c.
I turn on power saving (doesn't affect performance) and stick all apps into app powersaving (but i don't think it does much as all my IMs are still syncing in the background before i open them). I also use a black theme (search 'touchwiz black' in the theme store) for maximum sAMOLED efficiency (excellent black levels and power saving; win-win).
General prom kernel settings are smartmax_eps with stock cpu freqs (2.3 GHz mongoose/1.7 GHz apollo) and interactive with stock gpu freqs (650 MHz gpu). FIOPS for both internal and sd card I/O schedulers (but i'd prefer BFQ for sd card I/O, if lyapota adds it into the next update). The rest should be provided in aldoblaga's profile from the first page.
I'm still fighting some wakelocks in my device, so i still have a lot to learn
Click to expand...
Click to collapse
Bravo my man! A true and dedicated modder. U re using prom 1.7.1 or which version? It s a good thing that my synapse settings for 1.4 work on every other version released since! Kudos to @lyapota for keeping things easy to config going from version to version and backwards compatibility between profile versions is possible!
aldoblaga said:
Bravo my man! A true and dedicated modder. U re using prom 1.7.1 or which version? It s a good thing that my synapse settings for 1.4 work on every other version released since! Kudos to @lyapota for keeping things easy to config going from version to version and backwards compatibility between profile versions is possible!
Click to expand...
Click to collapse
Haha, thanks. Yes, i'm using 1.7.1 and indeed many thanks to lyapota for keeping the configs universal between kernel versions.
I just tried out aldo's perfection version 2 with renovate rom 1.1 r39 and it seems to be pretty fine.
I will try out the "battery" option for interactive governor with the next charge and then smartmax governor after this.
Maltonator said:
I just tried out aldo's perfection version 2 with renovate rom 1.1 r39 and it seems to be pretty fine.
I will try out the "battery" option for interactive governor with the next charge and then smartmax governor after this.
Click to expand...
Click to collapse
Keep us updated on your findings (by screenshots) from both governors with their respective settings, please. I have always been curious to see how smartmax_eps compares to interactive with battery settings enabled in synapse.
Thread cleaned yet again. If people want to have a screen on time contest that's upto them, if people want to OC or UV its upto them. But ALL members must be polite to each other, if someone's posts are annoying then add them to your ignore list
Big Bread said:
Keep us updated on your findings (by screenshots) from both governors with their respective settings, please.
Click to expand...
Click to collapse
I will report soon but it will need some days. Especially if the battery usage has to be similar to each "kernel-setting-test"
I'm now using Superman ROM with superstock kernel, and i want to try this kernel now with that rom, so my question is, if i change kernel now, should y root again and flash xposed again or just flashing kernel will be fine?<br />
<br />
Thanks in advance!
Enviado desde mi SM-G935F mediante Tapatalk
yamwt said:
I'm now using Superman ROM with superstock kernel, and i want to try this kernel now with that rom, so my question is, if i change kernel now, should y root again and flash xposed again or just flashing kernel will be fine?<br />
<br />
Thanks in advance!
Enviado desde mi SM-G935F mediante Tapatalk
Click to expand...
Click to collapse
If I'm right u have to flash supersu or magisk the one that u use also xposed if u use it, after flashing kernel