[KERNEL][4.2.2] Kernel+ for d2spr | Linaro 4.7 | Bleeding Edge | (7/23/13) - Sprint Samsung Galaxy S III

Kernel+ for AOSP 4.2.2 ROMs​
This is a kernel that I have been compiling and using on my own device for a while, and I want to share this with the community. I enjoy the CM10.1 stock kernel, but I want to keep up to date with the newest Linux version and CodeAuroraForum source. I also want the most optimized experience possible, along with a few extra features. Kernel+ is always built with the latest Linux kernel and Qualcomm CAF sources to provide a fast, stable, and bleeding edge experience. The source can be found on my GitHub here Enjoy .
What is this?
This is a kernel based off of CyanogenMod's 'cm-10.1' branch of the Galaxy S III kernel.
Kernel+ is built with the goals in mind:
To always be up to date with the latest source from CodeAuroraForum and Kernel.org
To optimize as much as possible for the smoothest user experience
To base closely off of the CM10.1 kernel for optimal stability, not features
To provide a fast, stable, and bleeding edge experience for users
Features
Linux 3.4.54
always up to date with the latest source straight from Qualcomm's CodeAuroraForum
latest Linaro 4.7 toolchain compiled
CPU frequency from 384Mhz - 1.5Ghz
FauxSound App support
FRandom built-in
GPU overclocked to 480 Mhz default
custom voltage control
excellent battery life
optimized and stable
small kernel size
more coming soon...
Click to expand...
Click to collapse
Downloads
All downloads can be found here: CLICK ME
Click to expand...
Click to collapse
Instructions for Installing
1. Download the kernel.
2. Copy it to your phone.
3. Flash with TWRP or CWM.
Note: Kernel+ is packaged with invisiblek's AnyKernel, meaning that it will unpack your current ramdisk and repack it with this kernel during the flashing process. This means that it will be compatible with any AOSP 4.2.2 ROM, even if they have different ramdisks. Also, please make sure that you are currently running a stock AOSP kernel (CM10.1, AOKP, SlimBean, etc) before flashing Kernel+ so that your ramdisk will be compatible.
Click to expand...
Click to collapse
ChangeLog
7/23/13​
Linux 3.4.54
pulled in updates from CM
lots of updates from CAF
pulled in latest CodeAuroraForum and Kernel.org patches
7/5/13​
Linux 3.4.52
fixed voltage control (I compiled with the wrong defconfig before...my fault)
pulled in a few updates from CM
synced with latest CAF
pulled in latest CodeAuroraForum and Kernel.org patches
7/3/13​
fixed bug where init.d script permissions was not set correctly
7/2/13​
Linux 3.4.51
GPU 3D overclocked to 480 Mhz default
custom voltage control
lots of CAF updates...look at GitHub and see how many times I've merged CAF over week long period!
changed min CPU frequency to 384 MHz
synced with CyanogenMod source
pulled in latest CodeAuroraForum and Kernel.org patches
6/24/13​
Linux 3.4.50
lots of updates straight from CAF
many updates from CyanogenMod source; merged 'next' branch for support for media-caf
fixed frandom in build
added init.d script to enable frandom at boot - feel the speed increase!
pulled in latest CodeAuroraForum and Kernel.org patches
6/19/13​
fixed flickering (last time, I promise )
added frandom (Entropy Seeder - increases overall smoothness)
lots of updates from CodeAuroraForum
pulled in latest CodeAuroraForum and Kernel.org patches
6/16/13​
Linux 3.4.49
lowered MDP bandwidth values - flickering is gone now with the original values after the CAF merge
reverted Bluetooth "revert" code from CM - BT seems to be fixed from the latest CAF merge now
Updated FauxSound to v2.1 with PowerAmp Amplifier Controls
updated display code
sync'ed with CyanogenMod source
pulled in latest CodeAuroraForum and Kernel.org patches
Bleeding Edge!!
6/12/13​
adjusted MDP bandwidth values - no more flickering
fixed bluetooth
added support for FauxSound
added 189Mhz step with lowered voltage
sync'ed with CyanogenMod source
pulled in latest CodeAuroraForum and Kernel.org patches
6/8/13​
initial release
Linux 3.4.48
pulled in latest CodeAuroraForum and Kernel.org patches
compiled with the latest Linaro 4.7 toolchain
already 200+ commits ahead of the stock CM10.1 kernel
Click to expand...
Click to collapse
Thanks to:
CyanogenMod for their work and source for d2's
invisiblek for his AnyKernel package
Kernel.org
CodeAuroraForum
AndroidFileHost
...if I forgot you, please let me know!
Click to expand...
Click to collapse

FAQ
Frequently Asked Questions​
How do I disable GPU overclock?
By default, the GPU is allowed an extra 480 Mhz freq step, whereas stock only allowed up to 400 Mhz. If you feel that you do not need the extra GPU 3D power, then you can disable it by adding the line:
Code:
echo 1 > /sys/devices/platform/kgsl-3d0.0/kgsl/kgsl-3d0/max_pwrlevel
to the file /system/etc/init.d/98kernelplus. Then reboot.
How do I adjust the voltages?
You can control the CPU freq voltages by using an app such as Trickster, System Tuner, SetCPU, etc.
What is frandom? How do I enable it?
Frandom is basically a more efficient random generator. It can be used in place of /dev/urandom and is 10 - 50 times faster. Using frandom will use very little of the kernel's Entropy pool, which in turn will provide better performance and smoothness. Frandom is already built-in to the kernel and enabled via an init.d script. No need to manually enable it.

one more...

Nice! I've been wanting to flash some AOSP, will give this a try...
Sent from my SPH-L710 using xda premium

Hmmm....interesting I guess I will give this a 72hr run on vanilla RB nightly then report back vs stock kernel...which btw I'm running.
Sent from my so called "nexus experience GS3" Google, you are so late!

OK
You got my attention, im a try this out

Tried two downloads, failed the flash each time. It just says flash failed, right after "Updating Partitions...."

Are you guys phone FC'ing after this kernel? I'm trying to figure out if its this or the free next launcher 3d offer they was giving out yesterday that made my calls go bonkers.
Sent from my so called "nexus experience GS3" Google, you are so late!

CyberGmonster said:
Are you guys phone FC'ing after this kernel? I'm trying to figure out if its this or the free next launcher 3d offer they was giving out yesterday that made my calls go bonkers.
Sent from my so called "nexus experience GS3" Google, you are so late!
Click to expand...
Click to collapse
I may be wrong but I don't think a kernel will cause force closing issues. Also, Ive been running the next 3d launcher with slimbean6 and its very smooth. Try wiping dalvik/cache then reboot and if it's still occurring then clear data under Settings->Apps for whicher app is force closing.

Ascertion said:
Tried two downloads, failed the flash each time. It just says flash failed, right after "Updating Partitions...."
Click to expand...
Click to collapse
Anyone else have this problem? Try reflashing your ROM/kernel, boot up, and then boot into recovery and flash this kernel again.
Sent from my SGH-T999 using Tapatalk 4 Beta

Jon.StatiK said:
I may be wrong but I don't think a kernel will cause force closing issues. Also, Ive been running the next 3d launcher with slimbean6 and its very smooth. Try wiping dalvik/cache then reboot and if it's still occurring then clear data under Settings->Apps for whicher app is force closing.
Click to expand...
Click to collapse
That's why I was a little confused. Everything was fine on the latest vanilla RB until either this kernel or next 3d launcher. Thanks. I will get it sorted out!
Sent from my SPH-L710 using Tapatalk 4 Beta

I've just been compiling from your source, but so far so good

Rxpert said:
I've just been compiling from your source, but so far so good
Click to expand...
Click to collapse
Yeah that works too
This morning I pushed a few commits to bring it up to date with the latest cm10.1 kernel and adjusted the MDP bandwidth values...I have yet to test them though...
Sent from my SGH-T999 using Tapatalk 4 Beta

Flashed and running great.
Sent from my SPH-L710 using Tapatalk 2

Can't speak on the battery life yet since I switched ROM back to cm rc5 since the call fc issue I had with RB. However, I'm getting some flickering but it could be rc5 issue. Other than that this kernel seem so damn smooth battery life seem like its good too but a little early to judge. Nice new toy op!:beer:
Sent from my SPH-L710 using Tapatalk 2

CyberGmonster said:
Can't speak on the battery life yet since I switched ROM back to cm rc5 since the call fc issue I had with RB. However, I'm getting some flickering but it could be rc5 issue. Other than that this kernel seem so damn smooth battery life seem like its good too but a little early to judge. Nice new toy op!:beer:
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
I am currently testing the commits I pushed this morning, and so far I haven't experienced anymore flickering with the new MDP bandwidth values. :good:
I just need to add a few things and an update will be coming soon!
But for now, if the flickering really gets in the way, check disable hw overlays in developer settings. But just FYI if you check that option you are basically disabling project butter, and your experience will not be as smooth.
Sent from my SGH-T999 using Tapatalk 4 Beta

klin1344 said:
I am currently testing the commits I pushed this morning, and so far I haven't experienced anymore flickering with the new MDP bandwidth values. :good:
I just need to add a few things and an update will be coming soon!
But for now, if the flickering really gets in the way, check disable hw overlays in developer settings. But just FYI if you check that option you are basically disabling project butter, and your experience will not be as smooth.
Sent from my SGH-T999 using Tapatalk 4 Beta
Click to expand...
Click to collapse
If anyone else is not experiencing flickering than I'm guessing its RC5 (CM). I will look into it and do more testing to see what might be the culprit. Thanks!
Sent from my SPH-L710 using Tapatalk 2

I take that back...even with the new commits and bandwidth values, I still get flicker, although it seems to be less often. I still have to debug more and see where it is coming from.
Stay tuned...
Sent from my SGH-T999 using Tapatalk 4 Beta

I just finished tweaking the MDP bandwidth parameters, and I think I have found the sweet spot. There is no more flickering at all. Just a few more things I need to add and it will he ready for a new release, probably tomorrow.
Sent from my SGH-T999 using Tapatalk 2

klin1344 said:
I just finished tweaking the MDP bandwidth parameters, and I think I have found the sweet spot. There is no more flickering at all. Just a few more things I need to add and it will he ready for a new release, probably tomorrow.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the heads up! :good:

Related

[KERNEL] Speedy Kernel r39 || Everyone can commit changes to this kernel

Goals and their priorities
- Stability #1
- Battery life #2
- Speed #3
- Extra features #4
- Compatible with GLaDOS Control / Franco Updater App / Trinity Toolbox #4
Donations will soledly be used to buy the applications above mentioned or to share it with the developers I used their work from, so I can test compatability more often.
Everyone can make changes to this kernel. The only thing I will require from you is a SSH key as described in the help from github. This way everyone can contribute to this kernel. Extreme changes to the kernel must be approved by me or someone else I assigned to help me lead this project.
Are you interested to help? Sign up!
Developers list
- Jonas Hendrickx - djjonastybe
Features (what you see and experience) (also future features listed)
- Compiled with latest Linaro Toolchain
- 3.0.41
- CPU: enabled 1500MHz
- GPU: enabled 384MHz
- Fixed several bugs present in the stock kernel
- Custom Voltage
- C4 State (Cores can be turned off) + OSWR
- Customized compiler flags
- Color Control (Ezekeel)
- Vibration Control (Ezekeel)
- Sound Control (Ezekeel)
- Enhanced undervolting MPU/IVA/CORE
- No crappy workaround patches so we have a clean kernel.
Want more features? Want to see something removed? Want to see something changed? Please suggest. I don't eat you alive.
Coming soon
- Improved GPU Scaling 128/256/384MHz (Improved battery)
- Tweaked DRAM timings
- Requested: Trinity color palette source code
- Requested: Live OC (I don't like some aspects of Ezekeel's implementation. I believe some things can be done much shorter and much more efficient.)
This kernel focuses on changing bus speeds, removing useless code, and adding only useful things to the kernel.
Tweaking has been done carefully.
https://github.com/jonashendrickx/MAGURO-JB/tree/android-omap-tuna-3.0-jb-pre1
We do not want to exceed the limitations on our device. Don't ask for 2.0ghz overclocks or 512mhz GPU. It's still a phone and it will always be one. I will add it when I am ready.
Want to contribute to Speedy Kernel? Read the requirements.
Requirements:
- Knowledge of github
- Generate a SSH key and send me the public key: eg id_rsa.pub.
- Know that I can revert your code and accept this. It's still my kernel.
Depending on how much people want to work together on this kernel I might start a kernel which is open for anyone to edit. Only I will setup the repository.
First!
You here too!
Inviato dal mio Galaxy Nexus con Tapatalk 2
Yeah. I just received my Nexus. The Nexus S has become so slow I got tired of it. Have you made any releases here ?
djjonastybe said:
Yeah. I just received my Nexus. The Nexus S has become so slow I got tired of it. Have you made any releases here ?
Click to expand...
Click to collapse
Hahaha nice one!, i also sold my NS, and im getting my GN sunday , see ya ssoon
I am wondering how I can activate SLUB. I don't know what Android is using for stock. But apparently some devs use SLQB. I read SLUB is little faster when using Google Search.
I am going to make a first upload.
More features are coming ofcourse.
Uploaded. Please flash with fastboot. I am not going to make update.zip files. I find it faster and more efficient to do it this way. I might look into making update.zip files later
Released. Update.zip also.
Currently I have only enabled the green features. More is coming.
Do you at least know what is SLQB and SLUB ?
Sent from my Galaxy Nexus using xda premium
chadouming said:
Do you at least know what is SLQB and SLUB ?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Sure. I looked it up.
JB or ICS????
Jelly bean.
If you wait I will upload my second build in a minute
github
Do you have github repository? :fingers-crossed:
anarkia1976 said:
Do you have github repository? :fingers-crossed:
Click to expand...
Click to collapse
Not yet. I don't know how to upload to github. I have spent a few days on it before. I know my way working with the git I cloned. But uploading is still new to me.
Feel free to teach me. I have everything in this folder:
/Android/jb/maguro/omap
I know how to create a SSH key and upload it on my Github page. But then the uploading part doesn't work.
I may take a look into it later.
waiting for next one , interesting...
Uploaded!
PGM app support or not?
the begin
https://help.github.com/ :angel:
djjonastybe said:
Not yet. I don't know how to upload to github. I have spent a few days on it before. I know my way working with the git I cloned. But uploading is still new to me.
Feel free to teach me. I have everything in this folder:
/Android/jb/maguro/omap
I know how to create a SSH key and upload it on my Github page. But then the uploading part doesn't work.
I may take a look into it later.
Click to expand...
Click to collapse
Git remote add yourepo github.com
Git push -u yourepo yourbranch
Inviato dal mio Galaxy Nexus con Tapatalk 2
Is it possible to include option to turn FSync off?
Sent from my Galaxy Nexus using Tapatalk 2
Looks interesting, I'm installing it now.
Fast Charge would be a nice addition though.
Good to see a Belgian developer join the scene!
I don't know. I think you can turn off FSYNC with GLaDOS Application. I am not sure. I am still new to the Galaxy Nexus mods.
I will take a look into enabling PGM app support if I can disable it for those who don't use it.
Rcbrt thank you! I will try again github tomorrow night or maybe upload everything sunday.

[KERNEL] A.S.K.P | Build 20 | 3.0.93+ | 4.2.2 [B19] EOL | 4.3 [B20MR2] | 21-08-2013

THIS IS MAGURO SPECIFIC. Reference for toro/toroplus at respective forums.
DOWNLOADS HERE ARE COMPATIBLE WITH ALL VARIANTS.
I'm Very sorry. This is posted on 18th August. I need to start studying now. I'm left with 30 days. A major super milestone will come after 11 October Please await for my exams to end Cheers~
READ THIS BEFORE DOWNLOADING
THE ULTIMATE ASKP USER GUIDE
{
"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"
}
"The kernel for the ones who love everything in one."
Let's make it simple.
With the introduction of so many kernels in the forums, every user just wants his/her phone to enjoy the crisp experience of their device. With ASKP, you get to enjoy the brilliant works of all developers into one small kernel. ASKP, is a modified kernel that merges many tweaks together, just like P.A.C.
DISCLAIMER
We, the ASKP Team, are not responsible for any bricks that are caused by this kernel. When you flash this kernel, you agree that it's what you've done. Read the Thread THOUROUGHLY before posting any redundant questions or are trying to flame for bugs.
Click to expand...
Click to collapse
Features​
- Compiled with Codesourcery 4.7.3 May 2013 Toolchain
- Advanced Hotplugging System
- Optimized lib compression system
- Customized Memory Page Allocation from the Linux Community
- Optimized Generic Memory Hotplug Drivers
- SELinux Upstream Patches
- OSELinux System
- Joe's RCU
- MIUI Compatibility
- Google's Sources Merges
- Optimized OMAP 4 Tweaks
- zsmalloc support
- The new XZ Compressed Image
- LZ4 RAMDisk and lib compressor module from Linux Upstream
- dcache Support
- Overall Performance increase System-wide while reducing battery drain
- Frandom Optimizations
- word-at-a-time Interface by faux123
- -pipe Optimizations
- Optimized LPDDR RAM Timings
- sched per cpu variable which avoids locks
- ARM CPU Topology Support
- Content Adaptive Brightness (CAB)
- Battery Life eXtender (BLX)
- Tweaked Governors
+ Ondemand
+ hotplug
+ Interactive *Default*
+ hyper
+ Dynamic Interactive
+ performance
+ Powersave
+ InteractiveX
- TCP Algorithims
+ Westwood *Default*
+ reno
+ cubic
+ vegas
+ yeAH
- Read-Ahead Buffer
- Input/Output Schedulers
+ Noop
+ deadline
+ Sioplus *Default*
+ row
+ CFQ
+ BFQv6
- Dynamic File Sync
+ With commits upstream from Faux's source
- Gamma Control
- GPU Overclocking
+ 308MHz
+ 384MHZ
+ 512MHz
- USB Fast Charge
- Underclock and Overclock support
+ 198MHz Minimal
+ 1420MHz Maximum
- Init.d Support
- PGM Support
- BLN Support
+ Includes Battery LED
- Voltage Control
- Sound Control
- zRAM Support
- Linux Kernel Patch-ups
+ Latest Generic Hotplug Helper from 3.10
+ Interactive governor from 3.4.10
+ lpj from 3.4.10
- CGROUP_TIMER_SLACK Feature
- WLAN Modulus tweaks and fixes
- lib strings tweaks
- memhotplug upstream patches
- Hotplugging ARM Fixes from Linux 3.11 RC
Source: Github
4.3 Changelog - https://github.com/Amperific/kernel_tuna_4.3/commits
4.2 Changelog - https://github.com/Amperific/kernel_tuna_4.3/commits/milestone
Issues Log.
• NONE! XD
The ASKP Team.
*Head Developer* Amperific
*GFX & Admin* Idrito
*Head Test Pilot* Okanb3
*tuna Test Pilot* Khizar
WANT TO TREAT US TO A CUP O' BEER? Donate to us here!
​Credits:
Boy Petersen (Source Base)(Cherry picks)(Up to Build 20)
CyanogenMod (Source base)(Up to Build 20)(Cherry Picks)
AOSP (Source Base)(From Build 20 Onwards)
Imoseyon (Cherry picks)
idrito (Design)
Ezekeel (Voltage & Sound Control, BLX)
Anarkia (AK)(Cherry Picks)
Franco (FK)(Cherry Picks)
Edoko (AirKernel)(Cherry Picks)
Simone201 (N.E.A.K.)(Cherry Picks)
Faux123 (Cherry Picks)
Huexxx (Patches)
Texas Instruments (Generic OMAP Patches)(Source Base)
Linus Torvalds (Upfront kernel patches)
ARM Linux (Generic Patches)
Codesourcery (GCC)
Samsung (Cherry Picks)
Qualcomm (Patches)
_MBQ (FTP File Hosting)
Downloads​
How to's *READ BEFORE YOU DO ANYTHING EVEN IF UR DOWNLOADING STABLE*:
- These builds are currently at the super experimental stage. Whichever below are risky for being your daily driver, but I myself test it before release, so rest assured it will boot.
- By downloading the zip, just wipe cache and dalvik cache and flash the zip.
- Your first bootup may take up to 9 minutes, So yeah. Take note It's not a brick.
- Lastly, Always check up the issues log and make sure you accept that issue before flashing. I assure you that every single bug will be listed there.
- +Some Spoiler+ xD So everytime we release a Build, it means that the next build is ready and under testing Just to say xD
- Like our work? Click this! to support us
@lastforone's MEGA All-in-one ASKP Mirror~ Click below
Remember to thank him!
Open Alpha Releases - OBSELETE
ASKP-b1.zip - 5.69 MB
ASKP-b2.zip - 5.45 MB
Beta Releases
ASKP-b3.zip - 5.85 MB
ASKP-b4.zip - 5.82 MB
ASKP-B15MR2.zip - 2.93 MB
GOLDEN MASTER RELEASE NOTES
- Any release that falls under the Golden Master release is a pre-milestone release. With the G.M Builds, you'll get to enjoy 95% stability system-wide. This means that builds falling under G.M are considered daily drivers. But there's a saying, "Nothing is perfect". So yeah. Expect a few issues here and there. Even if there are, it wouldn't be bad. All the major bugs will be completely killed before the Beta phase ends.
- Boot up speeds won't take as long as Alpha and Beta releases, expect booting to be much shorter
Golden Master Releases *Pre-Milestone*
ASKP-b5.zip - 5.82 MB
ASKP-b5a.zip - 4.55 MB
Mirror: ASKP-b5a.zip
ASKP-b6.zip - 4.55 MB
Mirror: ASKP-b6.zip
ASKP-B16MR2.zip - 2.93 MB
ASKP-B17MR2.zip - 2.93 MB
ASKP-B18MR2.zip - 3.06 MB
STABLE RELEASE NOTES
- Yep. You see this. It means the kernel is good to go, you can take it, put it into your phone, and run it like you're putting a bacon on a bread Like spreading butter over a pan. That smooth. There should be virtually no issues here. Even minor ones most probably are ROM-related. Unlike the builds above, you won't get to enjoy super experimental features like higher frequency clock rates. Take note of that
STABLE RELEASE
ASKP-b7.zip - 4.56 MB
ASKP-b11.zip - 5.75 MB
ASKP-b12.zip - 4.57 MB
ASKP-B18.zip - 4.49 MB
ASKP-B19.zip - 4.49 MB
ASKP-B19MR2.zip - 3.06 MB
ASKP-B20MR2.zip - 3.06 MB
PRE-SUPER MILESTONE RELEASE NOTES
- This is the final few builds that can near the End Of Line product of the kernel. Whatever is here is extremely experimental, untested and unsupported. These builds are only a minor preview of the upcoming super milestone. Do not think that the main features of the super milestone will appear here. This is because we don't want other developers to strip our works off immediately even before we release the super milestone.
PSM RELEASE
ASKP-B13.zip - 4.45 MB
ASKP-B14.zip - 4.49 MB
ASKP-B15.zip - 4.49 MB
SUPER MILESTONE RELEASE
- I've got nothing else to say xD Bugless. Super Stable. End Of Line.
ASKP-B16SM.zip - 4.49 MB
​
Frequently Asked Questions (FAQs).
- Wait, is this another mainline kernel?
*No. It is not. ASKP has commits that would come from almost every part of the world. This gives it the feeling of unity, like a unified kernel. Apart from that, Patches from Various manufacturers of the many parts of the phone will be brought upfront into this kernel.
===================================
User-Based Tutorials
- These are basically either from the quotes of a member utilizing ASKP whom we believe may help you in achieving your optimum performance and battery life from this Kernel.
ASKP Team's
Amperific said:
Clock speed: 192-1228MHz
Governor: Interactive
Scheduler: deadline
Read ahead buffer size: 384
TCP Congestion: Westwood
CAB: On
USB FC: On
Multi Core Power Saving: 1
High Performance Sound: On / Boost: 2
Vibrator Strength: 75
Battery Life Extender: 100
Dynamic Fsync: On
GPU OC: 384MHz
zRAM: Off
Smartreflex: All Switched On
RGB: morfic
Click to expand...
Click to collapse
User-Specific
gamerman123x said:
ASKP B14 is really smooth with the ROM LiquidSmooth 2.9 and here are my settings for trickster mod
General:
R.A.B - 512
Schedular - BFQ
CPU Frequency;
Min - 192mhz
Max - 1344mhz
Max Screen Off - 537mhz
Min screen On - 384mhz
Governor - Hyper
Specific:
WiFi High Performance - Off
C.A.B - Off
Force Fast Charge - Off
Multi core Power Saving - 0
High Performance Sound - On
Headphone Volume Boost - 3
Vibrator Strength - 60
Battery Life Extender - 100
Dynamic FSYNC - On
Temperature Limit - 64
GPU OC - 384mhz
ZRAM - Off
Then all voltages are stock
Screen:
Contrast . -21
GAMMA - 6
GAMMA Offset;
Red - 2
Green - 4
Blue - 6
Color Multiplier;
Red - 165
Green - 185
Red - 205
And those are my trickster settings and my phone is buttery smooth no lag..!!
Enjoy!!
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
================================
=================================== ==
Joining the ASKP Team.
- Yep, you see this. I just feel that being a soloist isn't helping this kernel. I want to bring an up to date kernel to my users as soon as I can, and in fact, I prefer giving them nightly builds. But it is the fact that I can't work on it daily, so I need more help, that's why I am forming a team, a team to help in this kernel. So here are the few people I need
+ Kernel Developer (You know it
+ App Developer (Something like A trickster mod?) xD
+ Official Tester - We've got two already So Yeah, no need anymore
PM me please or email me @ [email protected]
here comes a kernel!
Another yay :good: !
Is • WLAN module is broken means cant use wifi?
okanb3 said:
Is • WLAN module is broken means cant use wifi?
Click to expand...
Click to collapse
Yep. :/ I'm gonna release a flashable modules package. Am testing it right now.
Sent from my Galaxy Nexus using Tapatalk 2
Amperific said:
Yep. :/ I'm gonna release a flashable modules package. Am testing it right now.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
IMHO, is stupid release thing when 's unusable, i suggest do some test alone,without write new post here, and when u have first beta usable without any big problem release beta for find every little bug and problems
Never understand this haste of release thing.
I never seen HALO alpha that don't work but only floating visible
I never seen franco kernel that don't boot
i never seen AOKP official released with no audio working
d0ge01 said:
IMHO, is stupid release thing when 's unusable, i suggest do some test alone,without write new post here, and when u have first beta usable without any big problem release beta for find every little bug and problems
Never understand this haste of release thing.
I never seen HALO alpha that don't work but only floating visible
I never seen franco kernel that don't boot
i never seen AOKP official released with no audio working
Click to expand...
Click to collapse
Come on bro. Chill~ There are always bugs. If you've flash B1, the build isn't today. And besides, it boots, just that WLAN is broken.
Sent from my Galaxy Nexus using Tapatalk 2
d0ge01 said:
IMHO, is stupid release thing when 's unusable, i suggest do some test alone,without write new post here, and when u have first beta usable without any big problem release beta for find every little bug and problems
Never understand this haste of release thing.
I never seen HALO alpha that don't work but only floating visible
I never seen franco kernel that don't boot
i never seen AOKP official released with no audio working
Click to expand...
Click to collapse
Let's piece together this puzzle, shall we?
We're a community, right? Right.
This is a developer thread, correct? Correct.
Although it may not work, let's not put him on blast, lets kindly and patiently try and help him solve the problem.
Sent from my Nexus 7 using xda premium
d0ge01 said:
IMHO, is stupid release thing when 's unusable, i suggest do some test alone,without write new post here, and when u have first beta usable without any big problem release beta for find every little bug and problems
Never understand this haste of release thing.
I never seen HALO alpha that don't work but only floating visible
I never seen franco kernel that don't boot
i never seen AOKP official released with no audio working
Click to expand...
Click to collapse
relax, the dev clearly mentioned in the title thats this is an "alpha".. if you want something bug free dont flash alphas and try showing some respect the guy is doing this for free and in his spare time, dont act like you pay the devs to build rom/kernels/mods/etc
Okay guys. I found the issue. I'm gonna fix it asap. It's within the RAMDisk, really glad to hear this cause it will be fixed easily.
Sent from my Galaxy Nexus using Tapatalk 2
Amperific said:
Okay guys. I found the issue. I'm gonna fix it asap. It's within the RAMDisk, really glad to hear this cause it will be fixed easily.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Excellent! Let me know if I can be of any help.
Sent from my Galaxy Nexus using xda premium
MBQ_ said:
Excellent! Let me know if I can be of any help.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Okay I really need your help now. I switched the RAMDisk to Franco's. Still doesn't work. Dang.
And here's the latest build. I even attempted a switch to codesourcery.
I can't figure out. The same errors appeared in the logs i've sent you.
Sent from my Galaxy Nexus using Tapatalk 2
Amperific said:
Come on bro. Chill~ There are always bugs. If you've flash B1, the build isn't today. And besides, it boots, just that WLAN is broken.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
MBQ_ said:
Let's piece together this puzzle, shall we?
We're a community, right? Right.
This is a developer thread, correct? Correct.
Although it may not work, let's not put him on blast, lets kindly and patiently try and help him solve the problem.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Broken wireless is strange and surely is merge error or compilation error,
Khizar said:
relax, the dev clearly mentioned in the title thats this is an "alpha".. if you want something bug free dont flash alphas and try showing some respect the guy is doing this for free and in his spare time, dont act like you pay the devs to build rom/kernels/mods/etc
Click to expand...
Click to collapse
Mine is not criticism or an offense, just an observation, you're right! there are always bugs but imho broken wireless is strange,
i suggest anyway to confront https://github.com/Amperific/kernel_tuna_4.2/blob/nightly/arch/arm/configs/amperific_tuna_defconfig with stock one or see compilation error while compiling wireless module
Amperific said:
Okay I really need your help now. I switched the RAMDisk to Franco's. Still doesn't work. Dang.
And here's the latest build. I even attempted a switch to codesourcery.
View attachment 2061320
I can't figure out. The same errors appeared in the logs i've sent you.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I want to suggest you to post here the errors if you want help from others developers.
AK
anarkia1976 said:
I want to suggest you to post here the errors if you want help from others developers.
AK
Click to expand...
Click to collapse
http://www.4shared.com/office/jjGUO-rZ/dmesg.html
http://www.4shared.com/office/Euy0Kyts/logcat.html
Here's the logcat and dmesg. I think the RAMDisk is having issues.
Sent from my Galaxy Nexus using Tapatalk 2
If I know AK like I think I do he should definitely be able to help you out bud. Same goes for mbq. Some of my favorite and highest respected devs not just on xda but overall!
Sent from my Galaxy Nexus
anarkia1976 said:
I want to suggest you to post here the errors if you want help from others developers.
AK
Click to expand...
Click to collapse
Anarkia, Can you help? Would be very grateful if you do so. I've tried again thrice today. Am tired. Can't find any issue. Darn it. I'm heading to sleep. I hope you can lecture me in fixing this issue. Faced it before but didn't know how to fix it.
Thanks a million in forward
Sent from my Galaxy Nexus using Tapatalk 2
As I can't find the RAMdisk anywhere, I cannot tell you for sure what is wrong (I haven't read the logs that were posted because 4shared need registration). Nevertheless, I think I know what's going on:
Your defconfig is set-up to build the WiFi driver as a module. After compiling your kernel, the module is located at /drivers/net/wireless/bcmdhd/bcmdhd.ko. You need to insert this (and exactly this) module on boot in order to get WiFi working. If you upload your RAMdisk, I can tell you in detail what has to be done.
You can save yourself from trouble by not building wireless as a module. In your defconfig, simply set CONFIG_BCMDHD=y.
In Fancy Kernel, I'm also building it as a module, because there's a workaround for suspend WiFi drops that relies on ejecting / reinserting the module.
[EDIT] Turns out I had an account. And my assumption was right:
Code:
[ 253.240570] bcmdhd: version magic '3.0.82-4.2-fancy_kernel-r31-ext SMP preempt mod_unload ARMv7 ' should be '3.0.82-ASPK SMP preempt mod_unload ARMv7 '
So judging from that message, I see you have automatic module inserting already (it's most likely my RAMdisk?!). All you have to do is to replace bcmdhd.ko in /sbin after every compilation. That is if you want to keep CONFIG_BCMDHD=m of course.

[ROM][4.4.2] OmniMetal [05-24-2014] (Linaro Omni rom)

Presenting OmniMetal rom for the Verizon Galaxy nexus where speed is king
This will be a semi nightly build and a work in progress
OmniMetal
Standard disclaimer-
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Credits and thanks to-
@Mwisbest for all his source with various fixes and optimizations
@bsmitty83 for his great kernel source
MBQ_ for help with github
Linaro for thier optimizated toolchains and code
Omni Rom for the awesome base
Vanir Aosp for all their code fixes and enhancements
Anyone else that contributed to source
Google and Linux for open source goodness
And of course anyone that uses my roms
Current Modifications by me
fix for mobile network settings for toro
-O3 optimizations
Switch to linaro 4.8 toolchain
Added a little more gcc optimizations
Change animation scale in developer settings to .5 (helps with graphics some and gives an overall snappier feel)
Various tweaks and modifications for performance
Switch to Dirty_V
To-do List
Suggestions?
Downloads
OmniMetal-toro
PA gapps
Installation
Use only the latest cwm (6.0.4.3) or latest TWRP (2.6.3.1)
Backup current rom in recovery
Wipe cache and data (I suggest wiping system as well but its optional)
Flash rom
Flash Gapps
Reboot
Enjoy some OMNI goodness
Known Issues
None?
Like my rom or work?
Donate to me​
XDA:DevDB Information
OmniMetal, ROM for the Samsung Galaxy Nexus
Contributors
metalspring
ROM OS Version: 4.4.x KitKat
Based On: Omni Rom
Version Information
Status: Beta
Created 2013-11-18
Last Updated 2014-06-01
User Input and Issues or Bug Reports
User Input-
Although my coding knowledge is limited I am still open to try to add in any feature suggested here
However, please try to limit it to features found in other kitkat roms since it's most likely beyond my ability to forward port things lol
If you have any other feature requests please post them in the thread or at this link
Issues/ Bug reports-
If you have any issues with this rom, please provide details so I can troubleshoot them
details should include-
version of the rom you are using
kernel you are using (if not stock kernel)
any modifications you are using (ART, supersu, etc)
what the issue was and what were you doing when it happened
And also logcats/dmesg/last_kmesg logs are appreciated (even with known issues)
I will do my best to fix any issues that might arise to the best of my ability
Suggested Apps, Settings and Various Other Goodies
My personal settings for maximum performance
DirtyV kernel (included in rom)
TCP Congestion Control: Cubic
Read Ahead Buffer Size: 1024
I/O Scheduler: FIOPS
Frequencies-
230000 Min
1500000 Max
700000 Max Screen Off
350000 Min Screen on
Governor: Ondemand
Dynamic Fsync: On (Please turn this off while adjusting settings to avoid issues if these settings dont work with your phone)
Temperature Limit: 80
GPU OC: 512 MHz
ZRam: Off
SmartReflex: Core, IVA MPU All On
Optimal Display Settings-
Content Adaptive Brightness- Off
Contrast: -14
Gamma Adjustment: 6
Gamma Offsets-
Red: - 6
Green: 0
Blue: 8
Color Multipliers-
Red: 200
Green: 200
Blue: 265
Other Settings for Performance-
Force GPU Rendering: On
ART Runtime
Window Animation Scale: .5
Transition Animation Scale: .5
Animator Duration Scale: .5
NEPHILIMS CUSTOM KERNEL SETTINGS (For balance of performance and battery life)
Useful Apps/Addons
Xposed Framework (Not compatible with ART runtime)
For Music Lovers- VIPER4Android (Please follow instructions in thread op and use SuperSu)
Google Dialer with nearby places and search
Photosphere Addon
Anything you think should be here? Just tell me and it will be added
Yeehaw!!!!
Thanks metal, dl imminent!
Ok dl'd gapps but dont see the rom link?
Damn...
I got ninja'd...
Got it now thanks again!
Sent from my Galaxy Nexus using Tapatalk 2
47th_Ronin said:
Yeehaw!!!!
Thanks metal, dl imminent!
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Link is up in op
(xda is taking forever to upload to the dev db link lol)
Ok, quick question, I've always used nexus louder mod because of low volume on my phone due to the headphone jack being a p.o.s. any one know of a way to fix volume on 4.4?
I've tried the usual, i.e. build prop edits and such but haven't been able to make anything work too well.
Sent from my Galaxy Nexus using Tapatalk 2
47th_Ronin said:
Ok, quick question, I've always used nexus louder mod because of low volume on my phone due to the headphone jack being a p.o.s. any one know of a way to fix volume on 4.4?
I've tried the usual, i.e. build prop edits and such but haven't been able to make anything work too well.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Well, you could use the viper4android app
Its more of a super feature rich dsp manager, but it also has the capability of increasing the volume of headphone audio, speaker audio and bluetooth audio
link to app thread- http://forum.xda-developers.com/showthread.php?t=2191223
Hey, just a suggestion, I would try cherry picking from Fitsnugly CM11, they have Quick Toggle Settings setup.
Thanks for this. 3G/4G handoff has been seamless. :good:
Ooooo! I love new ROMs to try! Thanks for this
t1.8matt said:
Hey, just a suggestion, I would try cherry picking from Fitsnugly CM11, they have Quick Toggle Settings setup.
Click to expand...
Click to collapse
looks like he just cherry picked them from the cm gerrit so I should be able to add that in (unless he also made local changes)
right now I'm trying to get a build with linaro 4.8 toolchain in to see if linaro or 4.8 gcc breaks anything right now
so far only had a couple of errors stopping the build but they were easily fixed (hopefully no more pointless Werror clfags hidden around lol)
Btw, any ideas on kernels?
metalspring said:
looks like he just cherry picked them from the cm gerrit so I should be able to add that in (unless he also made local changes)
right now I'm trying to get a build with linaro 4.8 toolchain in to see if linaro or 4.8 gcc breaks anything right now
so far only had a couple of errors stopping the build but they were easily fixed (hopefully no more pointless Werror clfags hidden around lol)
Btw, any ideas on kernels?
Click to expand...
Click to collapse
From what I've read, the CM kernel has stopped the random reboots. Would building with another kernel bring them back?
oh, one other thing that would be great, i don't know if it's doable, is a clear button for recents.
modernbummer said:
From what I've read, the CM kernel has stopped the random reboots. Would building with another kernel bring them back?
Click to expand...
Click to collapse
Not sure how fixing the reboots, but dhackers version of the cm kernel is supposed to at least help
I could switch to it and then see if I can add different patches to bring in more available kernel settings and overclock
t1.8matt said:
oh, one other thing that would be great, i don't know if it's doable, is a clear button for recents.
Click to expand...
Click to collapse
It may be possible, I'm sure either AOSPA, slim roms or vanir have that brought up to kitkat in their source
if not then i can at least try to port it from the 4.3.1 sources
metalspring said:
It may be possible, I'm sure either AOSPA, slim roms or vanir have that brought up to kitkat in their source
if not then i can at least try to port it from the 4.3.1 sources
Click to expand...
Click to collapse
I haven't seen it yet in any 4.4 rom, but it'd be sweet if you could do it.
So far it's the best CM11 ROM I've tried thus far! This will get me through until January when I'm going to the Nexus 5. Thanks for the hard work! Looking forward to this one getting better & better!
metalspring said:
Not sure how fixing the reboots, but dhackers version of the cm kernel is supposed to at least help
I could switch to it and then see if I can add different patches to bring in more available kernel settings and overclock
Click to expand...
Click to collapse
You should definitely switch to the dhacker kernel. I'm on his 11/18 build, I've been trying to get a screen freeze or reboot...... Its not happening.
Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
justen7723 said:
You should definitely switch to the dhacker kernel. I'm on his 11/18 build, I've been trying to get a screen freeze or reboot...... Its not happening.
Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
speaking of which, i found some an interesting post that might help even more
http://forum.xda-developers.com/showpost.php?p=47036814&postcount=170
This ROM is smooth. I'm having one issue though. I can't seem to log into my Google account in the calendar app. It just keeps saying it can't access the Google servers.
EDIT: calendar just started syncing.
Possible to add hold back to kill app???
Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2

[KERNEL][I9295][AOSP/CM11/CM12][TW-4.4]KT-SGS4 port for Active Intl

Credits go to @ktoonsez for his kernel sources and KT apps (KTweaker and KTmonitor) :good:
Disclaimer: me no responsible if you use this!
So what is this? KT-SGS4 AOSP-4.4 S4 kernel ported to S4 Active (Intl). What has changed is of course jactive related stuff:
jactive board definitions and kernel config
camera sources and handler functions
some display settings
assorted stuff, can't really remember all the imporant bits
pre 1.0.0 AOSP4.4
Also, i tried to make a unified kernel, i.e. all differences between original and jactive are controlled with code ifdefs. But this haven't been tested as i don't have S4
So what works? So far i have found only one bug, when making or receiving calls i can't hear what the other side is saying and vice versa, i.e. no audio. Call sounds fixed.
Also overclocking the CPU seems to be broken, at least KTmonitor shows CPU to go only up to 1890 even though the clock is set over that value. So that's one thing to work on. I'll try to debug someday next week.
Compiled with linaro-4.7-12.10 toolchain.
This should work on CM11 and AOSP based roms. Personally i have it running on SlimKat (dualboot) and CM11. Just flash the CWM zip. It contains KTweaker and KTmonitor apps, courtesy of ktoonsez. Thanks mate.
Latest version 04.14.2014
Personal experiences:
benchmarks are slower than with CM11 kernel, dunno if it matters...
still it's smooth in everyday use
KTweaker has lots of stuff to tweak, only if i had time...
AOSP4.4/CM11
This one works with CM11 and AOSP v 1.0.0 and later. Don't use with earlier AOSP since this needs newer blobs.
KT-SGS4-KK4.4-AOSP-eur-02.11.2015
Built with Linaro 4.9 2014.09
Beta release
AOSP5.0/CM12
As there is no AOSP5.0 for jactive yet, just use CM12 .
KT-SGS4-LP5.0-AOSP-eur-02.15.2015:
fixed bootloop for now at least
supports ext4/f2fs partitions
KT-SGS4-LP5.0-AOSP-eur-02.11.2015
Built with Linaro 4.9 2014.09
Beta release
TouchWiz
This one works with KK TW roms (well i have tried only WizCyan...). Seems stable with default clocks and even with some OC. But every phone is different in regards OC, so YMMV. KTweaker and KTmonitor included. Do note that Display settings might not work as we don't have Amoled.
Changes ver 01.12.2015
Fixed unresponsive screen bug
Compiled with Linaro 4.9-2014.09
Changes ver 01.03.2015
overclocking works better now
increased touchscreen min limit freq, hopefully removes problem with unresponsiveness
built with Linaro 4.7.12.10
Changes ver 12.15.2014 (BETA)
first version of KT TW kernel for jactive
added KEXEC_HARDBOOT support, works with MultiROM
General notes
Do keep in mind that if you don't set oc settings in boot, you need to use KTweaker app and reset the cpu min and max sliders for the settings to take effect. Even though the app asks if you want to apply the settings, it doesn't update the actual min and max values.
Download here: https://drive.google.com/folderview?id=0BzJzDM42pkRvd1ZtMDZOR1M1OFE&usp=sharing
Github here: https://github.com/spegelius/KT-SGS4
god !!!!!! .... spegelius did it again you beast ... keep up the good work :good::good:
mythi said:
god !!!!!! .... spegelius did it again you beast ... keep up the good work :good::good:
Click to expand...
Click to collapse
Heh, thanks. Sadly there seems to be a bug with call audio, so for test use only at this point. I went through the kernel code and all i can think of to do is to try audio stuff from CM11 kernel, to see if that's the problem. Still, audio works perfectly everywhere else so really hard to say what's wrong...
spegelius said:
Heh, thanks. Sadly there seems to be a bug with call audio, so for test use only at this point. I went through the kernel code and all i can think of to do is to try audio stuff from CM11 kernel, to see if that's the problem. Still, audio works perfectly everywhere else so really hard to say what's wrong...
Click to expand...
Click to collapse
Whats even harder is taking a logcat and ksmg while in a call
mythi said:
Whats even harder is taking a logcat and ksmg while in a call
Click to expand...
Click to collapse
True, but luckily i have two phones and sims (other one is my work phone) so it's easier to debug.
Some progress: it turns out that for some reason es325 codec can't connect to slimbus sink and thus no audio. slimbus has some kt additions, need to debug more. Also i think it would be good to try to build the kernel with some other toolchain than linaro...
spegelius said:
True, but luckily i have two phones and sims (other one is my work phone) so it's easier to debug.
Some progress: it turns out that for some reason es325 codec can't connect to slimbus sink and thus no audio. slimbus has some kt additions, need to debug more. Also i think it would be good to try to build the kernel with some other toolchain than linaro...
Click to expand...
Click to collapse
Hmmm... does it build modules with kernel ?? Ya changing the compiler to maybe the google ndk gcc may fix up some issues but I think u will have alot of pain in debugging files since not all elements that linaro supports are supported by other .... I maybe wrong but ...xxxx
Good job man :good: :highfive:
mythi said:
Hmmm... does it build modules with kernel ?? Ya changing the compiler to maybe the google ndk gcc may fix up some issues but I think u will have alot of pain in debugging files since not all elements that linaro supports are supported by other .... I maybe wrong but ...xxxx
Click to expand...
Click to collapse
Yes, modules are compiled and part of the cwm package. I haven't checked that all required modules are present, but i don't think that's the problem. Gonna be setting up a proper kernel dev env, found a good howto for Eclipse here: http://simonkagstrom.livejournal.com/33093.html. Regular editors just aren't cutting it anymore
ktoonsez said:
Good job man :good: :highfive:
Click to expand...
Click to collapse
Thanks . Luckily i had some experience with LeJay's cm10.2 kernel and cm11 kernel so i knew roughly what parts differ between jf an jactive. Just a matter of diffing those parts (meld is my tool of choice for that kind of work).
This kernel s awesome. It's speeded up my phone. I want to use this regularly has anyone found a way for the phone call sound??
Sent from my GT-I9295 using xda app-developers app
lijoc said:
This kernel s awesome. It's speeded up my phone. I want to use this regularly has anyone found a way for the phone call sound??
Sent from my GT-I9295 using xda app-developers app
Click to expand...
Click to collapse
Not yet. Been debugging and the problem is somewhere in kernel's slimbus communication, it seems es325 codec cannot get audience firmware loaded properly or something...
spegelius said:
Not yet. Been debugging and the problem is somewhere in kernel's slimbus communication, it seems es325 codec cannot get audience firmware loaded properly or something...
Click to expand...
Click to collapse
Ah, found he bug; && should be || when checking if CONFIG_JACTIVE_ATT or CONFIG_JACTIVE_EUR... es325 wasn't configured properly. Now call sounds work. I'll upload a new build after i do some testing first.
Waiting for the upload
Sent from my GT-I9295 using xda app-developers app
Uploading, KT-SGS4-KK4.4-AOSP-jactive_eur-04.19.2014.zip should be online soon.
It's working now. The volume is too low is there a way to increase it?
Sent from my GT-I9295 using xda app-developers app
lijoc said:
It's working now. The volume is too low is there a way to increase it?
Sent from my GT-I9295 using xda app-developers app
Click to expand...
Click to collapse
Hmm doesn't the volume button work? Also what rom are you running?
Volume button works and is on maximum. I am using carbon rom
Sent from my GT-I9295 using xda app-developers app
I am running your AOSP 4.3.1 ROM http://forum.xda-developers.com/showthread.php?t=2621883
I flashed this kernel in recovery, wiped cache and dalvik, but it will not boot. I get the "Samsung Galaxy S4 Active I-9295" splash screen, then it hangs, and hangs, and hangs.
I had to restore back to the version 8 nandroid of that thread. ADB would give me nothing so early in the boot sequence.
Pkt_Lnt said:
I am running your AOSP 4.3.1 ROM http://forum.xda-developers.com/showthread.php?t=2621883
I flashed this kernel in recovery, wiped cache and dalvik, but it will not boot. I get the "Samsung Galaxy S4 Active I-9295" splash screen, then it hangs, and hangs, and hangs.
I had to restore back to the version 8 nandroid of that thread. ADB would give me nothing so early in the boot sequence.
Click to expand...
Click to collapse
Did you read the topic? this kernel is for 4.4
Indeed, it's for AOSP 4.4.x. You propable need to reflash the whole rom to get back original boot.img and kernel modules.
As for the phone sound being too low, dunno. If it was working ok with the original Carbon kernel, that points the problem being in the new kernel. But to my limited understanding, the volumes come from settings outside the kernel... personally i'm running CM11 with this kernel and volumes are ok.
The volume in carbon rom also is the same. I tried the sound mods but it changes all the volumes of system other than the incall volume.
Sent from my GT-I9295 using xda app-developers app

[KERNEL] [Nougat] [Voltage Control] Kawori Kernel for Oneplus 2 (r7, 2017/08/16)

Some of you know me from the OOS3 kernel I built, and now I am moving to Nougat and starting working on it.
It mainly majors in keeping a balance between features and stabilities, so I did not add too many features (And I think features like adding 10+ governors is a bad practice), but the features I added is of great use. Some of the features are unique in existing OP2 kernels.
I am sick of those kernels which say it is the smoother than butter or is more powersaving than Nokia 1100, and I do not think that could happen. What I provide is an average kernel with some little tweaks. If you are looking for some specific features, this is not the place for you.
The features list:
Features:
- Catch up with latest Linux upstream 3.10.107
- Catch up with latest CAF source
- Catch up with latest sdcardfs, f2fs, exfat, xpad source
- Add flash and electron governor (both based on interactive, credits to The Flash and frap129)
- Tweaked interactive governor based on CAF MSM8996 branch
- CPU voltage control (The first for MSM8994?)
- Replace H-cube with core_ctl from CAF MSM8996 branch
- Remove powersave, conservative governor
- Add maple, sio, fiops, zen I/O scheduler
- Partly Faux sound control
- Partly thermal control
- KCAL
- Dynamic Sync control
- Wakeblock toggle
- Fingerprint boost tweaks
- Sultanxda's I/O switcher
- TheCrazyLex's memory automatic compaction mechanism
- Various improvements from AOSPA (thanks to TheCrazyLex)
- Various improvements from Sultanxda and myfluxi (The people I really admire)
- Various improvements from CAF
- Fix some ROM's ramdisk bug (why should I fix these?)
- ...
Usages:
Note that LineageOS based roms and other roms use different sysfs nodes for gestures. So I provide 3 versions, just use the one that your rom is based on, otherwise gestures may be broken. For non los based Roms, use other version, if it does not work (such as Pure Nexus), use pn version.
Use kernel adiutor to tweak it.
Source:
https://github.com/aviraxp/ONEPLUS_MSM8994_KAWORI
Credits:
Fist of all, thanks to Linux upstream and CAF. Without them, doing this work is impossible.
Of course, thanks to Lord Boeffla for a good picking source.
Then I want to thank to Sultanxda and myfluxi for the 30+ commits I picked and the guidance he provided. You are the real MVP!
I also want to say thanks to dorimanx, Joe Maples and Franco for the good features they provided.
Support:
Just like many other so-called "developers" for OP2, I do not major in computer science and know little about C. All my codes are written by guessing. Feel free to provide feedbacks, though I may not know how to fix it.
reserved
Nice to see new kernels popping up for the device. Good work @aviraxp
MZO said:
Nice to see new kernels popping up for the device. Good work @aviraxp
Click to expand...
Click to collapse
I am using your Purenexus
aviraxp said:
I am using your Purenexus
Click to expand...
Click to collapse
That's awesome ?
thanks for kernel. have you tested undervolting? is it safe? whats basic rules to use voltage control without killing phone? never used this feature
chxei said:
thanks for kernel. have you tested undervolting? is it safe? whats basic rules to use voltage control without killing phone? never used this feature
Click to expand...
Click to collapse
Phone should technically reboot and discard changes before any damage occurs
Sorry if I missed it.. Is this kernel compatible with official lineage weekly?
Sent from my ONEPLUS A3003 using Tapatalk
chxei said:
thanks for kernel. have you tested undervolting? is it safe? whats basic rules to use voltage control without killing phone? never used this feature
Click to expand...
Click to collapse
I have tested, and think undercoating about 80mV is fine. Lower voltage will make it reboot.
infatality said:
Sorry if I missed it.. Is this kernel compatible with official lineage weekly?
Click to expand...
Click to collapse
Of course
r2 will be soon uploaded , thanks to @MZO for pointing out a different implementation of gestures that I missed.
First of all: nice to see a new kernel of OP2, and I love new features! Good work!
Second: Unfortunatly, flashing this kernel for me kills WiFi on latest Unofficial RR. Had to flash stock boot.img to make it work again. Other than that it seems to work fine.
Defineatly gonna give it a try as my daily driver after WiFi issue is gone.
chxei said:
thanks for kernel. have you tested undervolting? is it safe? whats basic rules to use voltage control without killing phone? never used this feature
Click to expand...
Click to collapse
No problems for the hardware with undervolting but the system may become a bit unstable
almlex said:
First of all: nice to see a new kernel of OP2, and I love new features! Good work!
Second: Unfortunatly, flashing this kernel for me kills WiFi on latest Unofficial RR. Had to flash stock boot.img to make it work again. Other than that it seems to work fine.
Defineatly gonna give it a try as my daily driver after WiFi issue is gone.
Click to expand...
Click to collapse
I have tested my kernel on omni, du, aex and pn, no issues so far. Some lineage guys also flashed and encounter no issues. But I will try to look at it.
Using this kernel for Almost 12hrs, so far everthing working here with decent battery life.
Cpu cores implementation is the same as in Franco kernel (all cores always online) or different from it?
almlex said:
First of all: nice to see a new kernel of OP2, and I love new features! Good work!
Second: Unfortunatly, flashing this kernel for me kills WiFi on latest Unofficial RR. Had to flash stock boot.img to make it work again. Other than that it seems to work fine.
Defineatly gonna give it a try as my daily driver after WiFi issue is gone.
Click to expand...
Click to collapse
Could you please flash boeffla kernel and report if it works? I suspect it is a toolchain issue.
parasthakur37 said:
Cpu cores implementation is the same as in Franco kernel (all cores always online) or different from it?
Click to expand...
Click to collapse
Different. It is actually same as stock, just built in kernel to keep stability.
aviraxp said:
Different. It is actually same as stock, just built in kernel to keep stability.
Click to expand...
Click to collapse
And I suppose there's no way we can use franco's implementation if we wanted to?
parasthakur37 said:
And I suppose there's no way we can use franco's implementation if we wanted to?
Click to expand...
Click to collapse
I don't know what Franco's implementation is. I don't care either. If you want to keep all cores on, use kernel adiutor and change the min cpus to 4.

Categories

Resources