Related
UNIVERSAL MSM8X60 KERNEL - LINUX 2.6.38.8
...now with better audio
Special Thanks to Ziggy471 for most of my installer scripts and ABOOTIMG
thanks to con247 for making this flashable on the rezound
please read post 3 - (known issues) before flashing
people with reboot issue = can you try on-demand
intelli controls gpu as well as cpu - but i never updated intellianthrax for the new gpu drivers i used in r14, and this may cause issues...
Click to expand...
Click to collapse
so far the only kernel for vigor released is GB SENSE. (not sense+ics)
if it works, i will release ICS and AOSP
in other words, dont flash on a non-sense rom such as cm7/cm9 or miui
Issue Reporting Form:
http://code.google.com/p/anthrax-msm8x60-kernels/issues/entry?template=Defect report from user
About rom compatability: My kernels do not replace your existing ramdisk (boot.img), I use Ziggy's script and abootimg that extract zImage from your boot.img file, i replace the zImage file, then re-package it into your boot.img (ramdisk). So custom ramdisk tweaks such as those used in synergy roms will remain intact, unchanged. Thanks goes to Ziggy for this method of installation.
This method of installation does require S-OFF. If your phone has S-ON, please consult your device specific threads on XDA or INFECTEDROM for directions on how to flash.
THE ONLY KERNEL TO PROVIDE 100% BEATS SUPPORT IN THE ACTUAL SOUND DRIVERS @ 96khz, 24 bit signal processing
FULL BEATS DRIVERS, CODECS, plus BEATS additions to the existing sound drivers.
*not just the headset notification code HTCDEV has in their source, im talking beats.c monster8x60.c monster.h beatsaudio.c beat8x60.c and beats_codec.c beatshelper.h
with FULL HTC REZOUND audio drivers ported over (qdsp6v3) with native HTC 2-way call record & Real-Time-Audio-Calibration
KERNEL Beats Support Defined:
Most ROMS now have beats in their framework, while sometimes this may improve sound, you will not get 100% of the beats experience unless your sound drivers (in the kernel)
have the BEATS CODECs,RTAC, and beats drivers activated in the kernel. My kernel has all of this, so you get the full 100% beats effects, just as if you had a HTC Rezound (IF: the rom supports beats correctly)
ALL post processing tasks are removed from the DAC (digital to analog converter) and done by the actual sound processor, this reduces CPU load to almost 0%, and improves quality, and removes any lag.
Also enabled the dedicated BEATS voltage regulator that assists power to the internal audio amplifier.
Due to the modifications to the sound drivers I use, sound in general should improve, no matter what rom you use, with or without BEATS.
DISCLAIMER: phones such as the Rezound has beats in stock form, while phones like the HTC EVO 3D do not, I took the REZOUND beats code, make some changes, and applied these changes to ALL devices. So, this may not be the only kernel for phones such as the REZOUND to include beats, but it is for devices such as the HTC EVO 3D. And since I use the same thread layout for all my posts, as i use the same source for all the devices i support, i thought i should throw this out there for all to read. IT PRETTY MUCH COMES DOWN TO THIS: THE REZOUND MAY HAVE SOME/ALL OF THESE FEATURES BY DEFAULT, WHILE OTHER DEVICES DO NOT. I DONT WANT TO BE ACCUSED OF CLAIMING TO PROVIDE NEW FEATURES THE STOCK KERNEL ALREADY HAS I DID IMPROVE ON THE REZOUND DRIVERS THOUGH (96KHZ/24BIT )
Click to expand...
Click to collapse
TERMS OF USE - the legal **** that protects developers (including XDA developers) who use my work, as well as myself, and infectedrom.com, and its hosting company and webmaster. HOW TO DOWNLOAD ALSO CONTAINED IN THE BOX BELOW!!
My kernels may contain closed source drivers, either written from scratch by me and copyrighted, or from source that was released to me under the terms of a NDA. therefore source code will never be released under the terms of GPL for these closed source drivers. If you do not agree with this, then dont use my kernel. Below is a disclaimer I copied and pasted directly from HTC's website regarding closed source drivers that they do not even post as part of their released source code.
This project is in a private test phase, where you are downloading a unfinished product for the sole purpose of testing. Once a final product is produced, GPL licensed source code will be available at googlecode.com, like my other finished products. The compiled binaries are not for public use or distribution.
--
SOURCE: http://htcdev.com/resources/faq
Why hasn’t HTC released the source code for some drivers?
HTC will release source code in accordance with any applicable open source license terms, i.e. GPL v2.0. Other source codes, which are not required to be disclosed by the open source license terms, unfortunately cannot be disclosed by HTC as they may be proprietary to HTC or its licensor.
--
yes, if HTC can hold back closed source portions of their kernel, so can I
I will supply source code for GPL 2.0 licensed parts of my kernel upon request (your best bet is to PM me here, or leave a public message for all to see - MODS/ADMINS can verify the existence of a PM), but parts of the kernel that include proprietary drivers, closed source drivers, and/or drivers written from scratch by me (such as intellianthax) will not be released. Code I developed from scratch that contains NO code from any GPL licensed source is entirly my code, and not licensed under GPL v2.0.
NOTICE FOR ROM DEVELOPERS:
If you agree to these terms, feel free to use my kernel in any roms you may develop, no permission is needed, though credit would be nice, it is not required.
To be compliant with XDA rules regarding GPL, as stated above, I will release gpl 2.0 licensed source code upon written request, but source for closed-source drivers as well as proprietary drivers, and copyrighted software will not be released. If the forum you post your rom on requires a link to source, feel free to link to this post, this will satisify the request for GPL compliance for forums such as XDA.
Click to expand...
Click to collapse
Closed Source software and drivers include, but is not limited to:
-source code released to me under a NDA agreement.
-software and/or drivers I have written from scratch, and have not used a GPL licnesed base to build from.
-software and/or drivers released to me under any non-GPL licensing agreement.
-software and/or drivers I was privileged to during my course of employment that was not considered proprietary my my employer(s).
-any modules, drivers, or coding not part of the linux source mainline, such as beats for example.
Additional source code that may never be released, even under GLP 2.0 include (but is not limited to) the following:
-Kernels that are un-released, experimental, and/or tests.
-Kernels considered private use (to be only used by myself, or anyone I send it to)
-Kernels protected from download by use of a password
By downloading my kernel, posting on this site, or posting on any thread, post, message, and/or article releating to my kernel (or any rom containing my kernel) on this or any other site (including, but not limted to xda-developers.com) you agree to these terms.
Download Link -> http://forums.infectedrom.com/forumdisplay.php/162-Anthrax-Kernel-Development
Click to expand...
Click to collapse
Comming Soon: (see change log in post 2 for more details, and items not listed here)
-full ZSL (2d is done, working on 3d)
-I/O scheduler tweaks
-CPU, RAM, Cache HOTPLUG notification tweaks
Click to expand...
Click to collapse
DISCLAIMERS:
1) overvolting/undervolting your phone may cause biit looping, or break it, brick it, cause it to melt, etc... do this at your own risk, and only if you know what you are doing. If YOU break your phone, please do not post on this thread about it.
2) If you OC'ed/OV'ed/UV'ed and now are in a boot loop or your phone is slow, or acting weird or just died - this means you changed something to a value your phone didnt like. I added the ability to OV/UV for those who know the risks and how to use it. Please do not post issues you may have after you OV/UV your phone, we may laugh at you.
3) overclocking your phone can break it, as you can see from reading this thread, this kernel has been 100% stable for quite a few, but some had issues. Overclock at your own risk.
4) not every phone can be over clocked, anything over 1.56 is considered unstable (on any of my kernels... well ok... most any ones kernel)
5) Please DO NOT use any task killers (or additional INITD scripts), they DO NOT improve performance nor battery life. They INTERFERE with your phone's stability (more crashes) and App compatibilities (Forced Close).
Click to expand...
Click to collapse
HOW TO INSTALL THIS KERNEL
PhantomApollyon said:
Ok so, if you're having wifi "Error" issues on BAMF Cubed, Inef, etc then please do the following as it was the only thing that fixed mine and got Anthrax R14 working.
1. boot into recovery and wipe data/cache
**2. reboot into fastboot(either by powering off and then holding volume down while powering on or by using adb) and flash the boot.img for whatever rom your're using(example: fastboot flash boot boot.img)
3. reboot device and verify that wifi works
4. reboot into recovery again and wipe data/cache again
5. flash con's repack from page 8
6. when it reboots to fastboot, select bootloader and then wait for it to check the file and then flash it
**notes: please understand that just because you have the stock kernel's zip file doesn't mean that you're flashing that, you are flashing "boot.img" that goes with your ROM
**regarding mainver errors: there are countless threads on how to fix this problem and you will most likely run into it, especially with BAMF Cubed because it's kernel is based off the old 1.xxxx mainver so PLEASE either search for that solution elsewhere or check out con's mainver tool to fix that
BAMF Cubed stock kernel <-- you can extract the boot.img from the PH86IMG.zip that is in that file so that you can flash it in fastboot
Click to expand...
Click to collapse
This kernel may (or may have in the past) contain work completed by the following people or companies (even if it was just one line of code).
If i discontinued using a developers work for more than 90 days, they will be moved to the list below.
Just because a name is listed here, does not mean I use their code in my current release, it means i used it within the last 90 days.
Companies: Qualcomm, HTC, Monster Audio, CreativeLabs, HP, IBM, Google, samsung, codeaurora.org, and kernel.org.
Private Developers:
...Chad Goodman (ME): about 85-90% of all the modifications, and tweaks
...Ziggy: CK3, scripts, installer scripts, autosched
...faux123: touch screen drivers for AOSP
...ToastCFH: usb drivers, some makefile files
Click to expand...
Click to collapse
Credit Disclaimer: if a major company has the same mod, code, change as a local developer who claims the mod was theirs (such as lithid, toast, ziggy, etc) - credit will go to the major company. If a mod consists of a change of a number for example (a common sense mod), credit will goto me for changing it. To reduce drama, I have given credit, even if I only used 1 line of code, and credit will remain, even if i stopped using their work/code/etc.
The following people (developers) have personally helped and/or assisted me with actual development (kernel or rom) in the past be it with this kernel, or work I did years ago:
Ziggy, Lithid, Virus, TrevE, QualComm, ToastCFH, JoelZ
Click to expand...
Click to collapse
Thanks to my beta testers, and non-developers who helped me out
Eternity-3D, kdunk (Special thanks for testing MegAnthraX), BigMase-3D, action-b, rudeboi3d (Special thanks for testing MegAnthraX), dondizzle, aaronpoweruser (Special Thanks for the 4.4.0 version of GCC Compiler that fixed WiFi and 4G), and easton
Click to expand...
Click to collapse
The last 90 days of releases DO NOT contain any code used by the following developer(s), but releases older than 90 days may have used code (even if just 1 line) from:
showp1984: some gpu code in the pre A-Series kernels from prior to OCT 2011.
TIAMAT: ICS Battery Reporting Drivers (battery, power, regulator, usb) - no released kernel contains code from TIAMAT's git.
Click to expand...
Click to collapse
In the future I may use code from the following developer(s), but as of now, I dont:
LeeDrOiD: cpu/voltage table
Click to expand...
Click to collapse
Features: (all verified working on the shooter and shooter_u devices as of 2-2012)
...basic features (some features may require additional support from the rom, such as USB HOST MODE for example)
Code:
-100% CIQ free, not 99.9, but truly 100% no CIQ (this may cause random lockups, freezes, reboots in roms that contain CIQ and make calls to CIQ memory space.)
-KGSL drivers, not SBA (HTC Sense based) - FULL OpenGL 2.0 hardware acceleration, full ICS / Sense 3.5 / MIUI hardware acceleration for 2D and 3D
-2-way call record support at the sound driver/kernel level
-beats audio support at the sound driver / kernel level
-quickcharge (not SBC, this will not over charge battery, but increases charging performance upto 50% depending on battery and voltage regulator temps
-GPU OC upto 320MHz
-Synchronous Multicore Threading
-FSB OC upto 460MHz
-CPU/l2 CACHE CLOCK Sync (share same clock, not 2 clocks set to same speed)
-SENSE and AOSP multitouch
-USB Host Mode (upto 4TB NTFS harddrives supported as well as usb keyboards) as of 2-11-2012, the only roms that support this are the titan hd series
-Bluetooth HID mode
-Bluetooth HBR mode, with support for 4 channel high definition sound.
-File System IO improvement hacks
-Hardware MEMCOPY support - improves code execution performance
-first with HTC 2-stage on-demand
-intellianthrax - focus on battery life AND performance while ignoring 'most' MPDECISON commands
-CPU @ 1.51GHz, both cores enabled during boot = faster boot times
-Clock and Voltage Settings set to Qualcomm spec by default
-Increased GPU Famebuffer size (memory)
-Undervolted WiFi, WiMAX
-WiFi Sensitivity adjusted - range extended by a LOT
-ZRAM, CLEANCACHE,
-Updated USB Drivers
-Updated WiFi Drivers - faster transfer rate, but may break "some" wifi hotspot hacks
-File System Support (Full Read/Write): CIFS, NTFS (4TB limit per partition), FAT16, FAT32, EXT2, EXT3, EXT4, and EFS
-FULL -o3 optimization during build
-UI tweaks at the kernel level (faster user interface)
-added steps to GPU clock
-added steps to OoM memory killer/task manager settings
-most basic tasks/house keeping limited to single thread processes
-CPU-supported unaligned access tweaks
-Vdd adjustable via SYSFS
-Camera ZSL framework in place for 2D
It provides support for
SmartShot™ - takes 5 photos and compiles the best parts to create one perfect shot.
BurstShot™ - capture 5 consecutive shots with just one click, so you never miss the action.
SweepShot™ panorama - take ultrawide shots then sweep in any direction.
ClearShot™ HDR - see crystal clear detail even when shooting in mixed or direct light.
as well as ZERO SHUTTER LAG
-Tweaks to Camera Flash/FlashLight drivers (added stobe mode, as well as adjusted low battery cut off points)
-Lots of Memory and Cache management tweaks
-custom RPC server
-Support for VPN and WiFi Calling (TUN and GAN)
-+mA mods to MHL Drivers
-120Hz, 3D support over HDMI/MHL @ 1080p
-CPU Governors: ziggy's lagfree, my intellianthrax, 2-stage on-demand, performance, smartass V2, interactive, userspace, powersave
-SD Card / MMC slot driver updates (faster IO performance for wimax and sd card r/w, using DMA access)
-100% ISO C99 Compliant coding, zero errors or warnings during -o3 compile
a friendly note
I personally own a 8x60 device, and developed this kernel for my personal use. Making this kernel work on 8x60 devices other than my own took a little time, but not much...and I am doing everyone a favor by doing this and sharing. You are not being force to use my kernel. I do not ask for donations, but I expect respect to me, my work, and other users. If people start drama for what ever reason, I will stop development for this device, just as I did other devices on XDA.
Click to expand...
Click to collapse
...additional features
Code:
-see the change logs in post 2 below for any changes to features.
linux 2.x change log
Code:
BUILD 15 19-FEB-2012 (IN PROCESS)
[COLOR="Red"]-DEFCONFIG edits for slide-to-unlock mod to work (included with vigor r14)
-some more camera changes (included with vigor r14)
-added OC ((included with vigor r14))
-backporting more linux 3 code (included with vigor r14)[/COLOR]
-some changes to support ICS android 4.0.3
-some ANTI-KANG mods (disabled some debugging and sysfs access)
-fixed AOSP performance issue
-louder audio (Voltage Regulator changes, no its not being over-volted like the Voodoo audio mod) (included with vigor r14)
-DEFCONFIG: verified good: shooter_aosp, shooter_sense, shooteru_aosp, shooteru_ sense, vigor_sense
-DEFCONFIG: working on: ruby_sense, pyramid_sense, tenderlion_aosp
-DEFCONFIG: need to finish: mecha_sense, supersonic_sense
[COLOR="#FF0000"]-ANTI-TAMPER, boot will check MD5 of zImage for tampering, cause bootloop if no-match -> thanks to IBM for this code
*bad downloads and/or a bad flash can cause a MD5 error and cause bootloops, please re-download if you have bootloops.
-beta/trial kernels will boot loop 15-days after build -> thanks to IBM for this code[/COLOR]
BUILD 14 18-FEB-2012 (RELEASED)
-custom cpu_hotplug drivers
-updated intellianthrax to work with more versions of mpdecision
-experimenting with camera drivers
-some GPU enhancements
-added SBA42 and 43 instruction set to the new KGSL drivers - should help w/ sense 3.0 issues
-better sound quality on 2-way record
-larger beats workspace (less lag)
-added 120hz 3D support via HDMI @ 1080p (experimental)
-improved HDMI image quality
-custom script to build ANTHRAX_CDMA_AOSP_DEFCONFIG, ANTHRAX_CDMA_SENSE_DEFCONFIG, ANTHRAX_GSM_AOSP_DEFCONFIG, AND ANTHRAX_GSM_SENSE_DEFCONFIG all at once.
.....also added defconfig files for other devices using the same source tree to build shooter
...still working on it - mainly the camera ****
-reworked audio drivers - best sound quaility yet, and a tad louder
-camera 2d and 3d now works with new OTA based roms, as well as previous roms (but only on HW001 - still working on hw002 issues)
-camera 2d and 3d work with new OTA based roms (all roms) but preview is broken on hw002
BUILD 13 20-JAN-2012
-fixed HDMI/MHL
-updated to latest KGSL drivers (KGSL 3.6)
-updated to latest BEATS device drivers
-updated to latest BEATS codecs
-updated sound drivers
BUILD 11 20-JAN-2012
-major RPC changes
-1st attempt at merging KGSL with SBA gpu drivers (100% merge)
BUILD 9 31-DEC-2011
-Fixed SysFS (enabled via defconfig, no code change)
-Fixed CPU Governors (enabled via defconfig, no code change)
-Reverted to KGSL 3.2, 3.3 was having some issues with some people (not all)
-Added CIQ Memory space emulation (redirected to NULL)
**Sitll using HTC's native CPU HOTPLUG code to manage cpu's
--zzzTESTzzzPLUSmA / EXPERIMENTAL (SAME as RLS9 plus the following:)
----->HDMI DRIVER UPDATE
----->CHARGE OVER HDMI (+mA)
*zzzTESTzzz is a test kernel, and the features added may or may not work.
It is a test because I have to way to test. please provide feedback to [email protected], NOT ON XDA.
BUILD 8 30-DEC-2011
-Fixed WiFi Issue with some roms
BUILD 7 30-DEC-2011
-Opened SYSFS FOR UV/OC
-ADDED 1.53GHZ
-410MHZ FSB ACTIVE (VS 360MHZ)
-300MHZ GPU CLOCK ACTIVE
-CPU and L2 Cache Clocks are Sync'ed (L2 and CPU run at same clock speed) up until 1.53.
---> 1.18Ghz (and only 1.18GHz) run all clocks @ HTC Spec (cpu, fsb, cache, gpu)
-ZSL FRAMEWORK (SO CAMERA MAY BE WEIRD, BROKEN OR ****ED UP)
BUILD 6a 29-DEC-2011
-ADD LINUX 3.X.X BRANCH TO MSM8X60_UNIVERSAL-ANTHRAX (NON-COMPILE)
BUILD 6 29-DEC-2011 UPLOAD FAILED - RC -2, RC 5, INV DIR
-ICS BATTERY FIX (I SERIOUSLY HOPE)
-FINIHED UNIFIED SOURCE (ALL 8X60 DEVICES, AOSP/SENSE/ICS - SAME TREE, **** - SAME BRANCH)
-> INCLUDES RUBY, VIGOR, SHOOTER, SHOOTER_U, DOUBLESHOT, PYRAMID, RIDER, HOLIDAY, AND GENERIC 8X60)
-> GUESS WHAT THIS MEANS :)
-CUSTOM RPC
--> INCLUDES CUSTOM L2 CACHE MANAGER
-KGSL 3.3 GPU DRIVERS WITH FULL SENSE 3.5, HONEYCOMB AND ICS HARDWARE ACCELERATION (2D AND 3D)
-KANGED USB DRIVERS FOR ICS (KANGED FROM TOAST)
-KANGED BLUETOOTH DRIVERS (FROM TOAST) - MODIFIED FOR HBR (BY ME)
-FRAMEWORK: CPU OV/UV +OC
--> INCLUDES FSB OC (UPTO 410MHz)
-FRAMEWORK: GPU OC
**FRAMEWORK MOD ARE NOT ACTIVE YET**
BUILD 5E 28-DEC-2011
-FIXED ICS BATTERY DRIVERS (AFFECTS ICS KERNEL ONLY)
--> ATTEMPT #2, STILL HOPING
BUILD 5D 28-DEC-2011
-FIXED ICS BATTERY DRIVERS (AFFECTS ICS KERNEL ONLY)
--> ATTEMPT #1, HOPE IT WORKS
BUILD 5C 28-DEC-2011
-FIXED ICS USB DRIVERS (AFFECTS ONLY THE ICS KERNEL)
-> ATTEMPTS IN 5A, AND 5B FAILED - BUT 5C IS GOOD
BUILD 5 27-DEC-2011
-ADDED ADDITIONAL CPU GOVERNORS
-ADDED CDMA_ICS_DEFCONFIG <---------- AOSP Verison
-FULL ICS 2D AND 3D HARDWARE ACCELERATION WITH KGSL 3.3 +TRIPLEBUFFERING
-ICS TOUCH SCREEN DRIVERS
-ICS USB AND BLUETOOTH
-ICS WIFI
BUILD 4 27-DEC-2011
-UPDATED USB DRIVERS TO LATEST VERSION (Still with HostMode/OTG support)
-FIXED BLUETOOTH HID DRIVERS
BUILD 3 24-DEC-2011
----> STABLE BETA, ALSO KNOWN AS "RELEASE-STOCK ANTHRAX" <----
-FIXED "PERFORMANCE" AS DEFAULT CPU GOVERNOR (ITS ONDEMAND NOW)
-FIXED BEATS HEADSET NOTIFICATION MODULE
-UPGRADED SOME BEATS MODULES TO 'REZOUND' VERSION
-UPDATED GPU DRIVERS - FULL HW ACCELERATION (2D AND 3D) (Sense 3.0/Sense 3.5/MIUI)
-ENHANCED AUDIO FOR AOSP (TESTED ON MIUI) - NOT BEATS QUALITY, BUT A LOT BETTER THAN THE STOCK KERNEL INCLUDED WITH MIUI
-NO OVERCLOCKING AS OF YET (CPU AND GPU) - EVERYTHING IS AT QUALCOMM SPEC FOR MSM8X60 CHIPSETS (NOT HTC SPEC)
BUILD 2 (BETA) 23-DEC-2011
-UPDATED AUDIO DRIVERS TO QDSP6V3 (SAME DRIVERS USED IN THE HTC REZOUND)
-ENHANCED AUDIO FOR SENSE - SHOULD IMPROVE ALL AUDIO, WITH OR WITHOUT BEATS
-QUALCOMM 2-PHASE ON-DEMAND GOVERNOR (SAME ONE USED IN THE REZOUND STOCK)
-EDITED DEFCONFIG TO ENABLE BEATS_AUDIO
-EDITED DEFCONFIG TO ENABLE BEATS_CODEC
-EDITED DEFCONFIG TO ENABLE BEATS_HDMI
-EDITED DEFCONFIG TO ENABLE RTAC
-EDITED DEFCONFIG TO ENABLE NTFS READ/WRITE
-EDITED DEFCONFIG TO ENABLE TUN/VPN
-EDITED DEFCONFIG TO ENABLE CIFS
-EDITED DEFCONFIG TO ENABLE GAN/WIFI CALLING
-EDITED DEFCONFIG TO ENABLE SENSE WIFI (QUALCOMM SOURCE IS 100% AOSP, NOT HTC SENSE BASED)
-EDITED DEFCONFIG TO ENABLE HIGH BITRATE BLUETOOTH
-EDITED DEFCONFIG TO ENABLE USB OTG (HOST MODE)
-EDITED DEFCONFIG TO ENABLE BLUETOOTH HID MODE
-CREATED 4 DEFCONFIG FILES (GSM SENSE, GSM AOSP, CDMA SENSE, CDMA AOSP) -- ALL BUILDS USE SAME SOURCE CODE
SENSE CDMA BUILD 1 (INITIAL COMMIT)
-100% STOCK QUALCOMM BASE, LINUX VERSION 2.6.38.6
-USED MSM8X60_DEFCONFIG FILE
-> THIS MEANS NO PLATFORM SPECIFIC FEATURES, SUCH AS WIMAX, OR WIFI - BUT ZIMAGE SHOULD WORK ON *ANY* MSM8X60 DEVICE
-COMPILED WITH -o3 OPTIMIZATION
IntelliAnthraX Features
Code:
[I]Proior to the rezound, on demand was either MINCLOCK or MAXCLOCK.
The rezound was the 1st phone to use a multi state on-demand govornor.
I made this available to all devices as my 2-phase on-demand governor.[/I]
IntelliAnthrax is 3 governors in one. Without going into too much detail,
It is a multistage on-demand govnornor for cpu0, cpu1, and gpu
(yes i said GPU). Some roms on the HTC EVO 3D had a custom
mpdecision file that caused issues with some of my kenrels,
IntelliAnthraX "attempts" to take priority over mpdecision as well.
[B]....this is just the basics[/B]
the good..
Code:
-it works
-my zip requires S-OFF
-con247 has a zip for those with S-ON
-sound is way better than stock, even over bluetooth
the bad... (Known Issues)
Code:
-my installer requires S-OFF - thanks to the rezound members for creating a new ZIP file that works w/ S-ON
-sometimes it needs to be flashed x2 times (dont ask why)
I WANT THIS ONE hehe
Chad.goodman for kernel dev of the year
Going through the changelogs, very impressive work man . The GPU doesn't have any issues @ 320mhz? Thanks!
JoelZ9614 said:
I WANT THIS ONE hehe
Chad.goodman for kernel dev of the year
Click to expand...
Click to collapse
14 downloads, no compliants - but i dont know if it will even boot
zetsumeikuro said:
Going through the changelogs, very impressive work man . The GPU doesn't have any issues @ 320mhz? Thanks!
Click to expand...
Click to collapse
i have been running this source on the htc evo 3d for months, as have many others..with no issues
the clock speeds are set to what qualcomm designed the 8x60 chipset to run at (as per their whitepapers and service manuals)
as far as the rezound - i dont know... its the same hardware...but i have no way to test.
chad.goodman said:
i have been running this source on the htc evo 3d for months, as have many others..with no issues
as far as the rezound - i dont know... its the same hardware...but i have no way to test.
Click to expand...
Click to collapse
I'm going to a Nand really fast and I'll flash.
Only flash on gb roms guys..Also read the whole OP im sure chad didnt write that whole thing up so you dont read it lol
JoelZ9614 said:
I WANT THIS ONE hehe
Chad.goodman for kernel dev of the year
Click to expand...
Click to collapse
joel...can you double check my installer script parition block numbers?
im off to bed - will check how things are going in the morning
thanks all
and a reminder:
THIS IS A SHOOTER/SHOOTER_U KERNEL MODIFIED TO WORK ON THE REZOUND - IT MAY OR MAY NOT WORK.
actually - its a shooter kernel that had been successfully modified to work on the shooter_u and ruby phones, hoping all goes well for vigor.
Click to expand...
Click to collapse
Almost positive flashing the zip did not work.... Unless you're S-Off I don't see how this will work. Is there anyway to see if it's installed?
Give me a sec and ill post a zip for you guys..
JoelZ9614 said:
Give me a sec and ill post a zip for you guys..
Click to expand...
Click to collapse
Thank you very much.
Yay you came over here too! Looking forward to ics sense version
Sent from my ADR6425LVW using xda premium
actually sorry i cant do it i dont have a gingerbread boot.img to pop this kernel into
Same as below, device boot animation is VERY laggy and does not boot.
Here goes...
Edit: Did NOT work for me. Couldn't get past the first, or second boot.
Flashed it on ICS Sense not realizing only for GB but I don't think anything happened to the rom, works fine.
Now here is a thread that's good to see. Nice having you and joelz over here. Let me know if there are any issues, I'll keep an eye on it too, but I can actually do something now.
Sent from my HTC Evo 3D using xda premium
This install script won't work. You need to use the script that I made that is a sticky at the top of this forum. It isn't updated for the newest mainver though so this afternoon I will rebuild the package for you.
Sent from my ADR6425LVW using XDA App
~~~~S6 UniKernel~~~~
For Galaxy S6 920 F / I / S / K / L / T / W8 For Galaxy S6 925 F / I / S / K / L / T / W8
For Lollipop 5.1.1 only!
UniKernel Features
- Supports F / I / S / K / L / T / W8 variants of 920 AND 925 devices
- Supports 920FS, ID and SD Dual SIM devices
- All edge screen special functions on Edge devices working
- Built from official Samsung Sources
- Full init.d scripting support
- SE Linux set to permissive (will prevent private mode from working)
- Stock Clocks
- Fully working Auto-Root for all 5.1.1 roms
- BusyBox injection if not detected in ROM
- DriveDroid support
- CIFS / FUSE
Kernel Configuration
The TWRP flashable kernel now comes with an Aroma installer, allowing you to choose a configuration you prefer. It also comes with 3 preset options - Stock, Performance, and Battery.
The Stock preset will make the kernel behave exactly as a stock kernel - no turbo mode, CFQ scheduler, stock interactive
If no pre-existing configuration file is found on the phone, (ie - New ROM flash) the ODIN flashable kernel will also have stock behaviour.
Every Aroma option is clearly labelled with an accurate description of what the setting will change. You are free to reflash to change configurations or manually edit the /system/unikernel.prop file that is generated by the installer (and then reboot). If you choose either the performance or custom options and enable Turbo mode, do not post in this thread about poor battery life. Turbo mode costs battery. deal with it
Download
UniKernel v8-0002 TWRP FLASHABLE >>> https://www.androidfilehost.com/?fid=24052804347808102
UniKernel v8-0002 ODIN FLASHABLE >>> https://www.androidfilehost.com/?fid=24052804347808101
If you get any FCs after flashing this kernel, wipe cache and dalvik cache in TWRP and reboot.
Changelog
UniKernel v8-0001
- Updated to COH9 Sources (New WiFi Driver and sensorhub firmware amongst other things)
- Fixed CIFS support
- Slight modification to ramdisk tweaks when a non-stock configuration is used
UniKernel v8-0001
- Updated to COH2 Sources
- Rewritten unification code
- Aroma Installer with preset and configurable options (Stock, Performance, Battery, Custom)
- ALL 5.1.1 ROMs are supported, even early versions, ie - BOFj / COF6
Sources
UniKernel >>> https://github.com/glewarne/S6-UniKernel
Credits
Source contributors
@ktoonsez - Major contributor to universal patch set
@edgarf28 - Relentless Testing testing testing, help and suggestions
@Xileforce - Help, encouragement and some code bits
@mikeyinid - Help, DHA tweaks
AndreiLux - Permissive mode patch and some other bits
Awesome Testers
@-Mr. X- for relentless and speedy testing
@sswagonman - Primary 925 feedback
Kyle - For not sucking any more
Robert - Primary 925 feedback
Steve - Primary 925 feedback
Other Credits
@Chainfire - For SuperSU included in the kernel
Disclaimer
You, the User, Accept full responsibilty for anything you choose to flash to your own device. I cannot be held responsible for any loss of data, income, revenue, software or hardware damage that may occur due to the use, or attempted use of this kernel.
reserved
Okay tried on the Canadian 920W8 and no call audio and Network Settings gets replaced with Sim Card Manager. LTE icon doesn't show anymore but data works!
Elisha said:
Okay tried on the Canadian 920W8 and no call audio and Network Settings gets replaced with Sim Card Manager. LTE icon doesn't show anymore but data works!
Click to expand...
Click to collapse
Yeah, to be expected. the defconfig in the kernel sources I used was specific to the international versions only. I will need to download the sources for the T variant (and maybe W8) and examine them for file differences and defconfig differences. gonna take some time. However, i I can build a working one its easy to build 2 simultanoeusly for upload in the future. only takes 5 mins per kernel.
thanks for testing though!
No problem.
If I flash back the stock kernel, will there be any leftovers from your kernel in the system?
So far no problem at all. Good work. I hope that some talented dev could port to our galaxy savoca color calibration... Thanks.
mcreego said:
So far no problem at all. Good work. I hope that some talented dev could port to our galaxy savoca color calibration... Thanks.
Click to expand...
Click to collapse
great to hear! thankyou
Hi , what about performance ? is it really more fluid than the stock one ?
thanks
Works like it should. Thank you for your work and time spent!
I don't see ktoonsez in your credits. Since you copied his voltage control.
jordan.elliott said:
I don't see ktoonsez in your credits. Since you copied his voltage control.
Click to expand...
Click to collapse
1) not released yet
2) originator is on the github commit
3) is actually made by Andrei lux
There is no need to credit every kernel contributor in existence especially if those commits are tagged
Um. ktoonsez spent hours trying to get the voltage control to actually apply. It was being overridden by touchjizz rom on every boot. I was one of his testers. It took about 4 hours. It wasnt just a copy paste.
jordan.elliott said:
Um. ktoonsez spent hours trying to get the voltage control to actually apply. It was being overridden by touchjizz rom on every boot. I was one of his testers. It took about 4 hours. It wasnt just a copy paste.
Click to expand...
Click to collapse
that may well be the case. however, as I said previously, the commits on my github from today are on code that has not been released yet. You can see the released kernel with the defconfig v01a commit and comment (last one pushed yesterday)
perhaps im using voltage control sysfs for some internal testing? maybe ill remove it before release? maybe i am going to release it in the future? maybe i would have given credit, as I have everyone else on the *curerntly released* code.
I will not enter into any further discussions with you on this matter. If you wish to report my thread please do go ahead. as it stands right now, i am 100% in compliance with both the stickies at the top of this very thread and XDAs very clear GPL rules.
The OP has not violated the GPL or xda rules by using kernel code from other developers. First because he hasn't released that code as a binary yet, and second he has not squashed the original authorship out of his sources. This satisfies the GPL and xda's rules on giving credit.
It is simply not possible to list all the kernel contributors in the OP...the list is way way way way too long.
If there are any more issues about the GPL, credit, sharing, etc. Please PM me about them.
Thanks!
OK everyone
After a bit of a delay due to computer issues, i have a new kernel ready for beta testing. Anyone interested?
Built in OC to 1.6GHz on .LITTLE and 2.3GHz on .big cores
lots of fixes and boosts
very very smooooooth
Bring it on. I would love to overclock 53 but tone down the 57 ones, it's possible with a tuner I belive?
Sent from a mobile gadget...
g.lewarne said:
OK everyone
After a bit of a delay due to computer issues, i have a new kernel ready for beta testing. Anyone interested?
Built in OC to 1.6GHz on .LITTLE and 2.3GHz on .big cores
lots of fixes and boosts
very very smooooooth
Click to expand...
Click to collapse
Can I test ? ?
sure ill have a beta up for you guys later tonight
ok, beta kernel time!
download here: https://www.androidfilehost.com/?fid=23991606952601582
some changelog:
BFQ scheduler default
increased bus frequency on apollo and atlas cores
enabled Mali 772Mhz GPU maximum
lots of kernel patches
framework for fixed overclock implementd (though not enabled in this build)
reduced readahead (is actually faster)
tweaked interactive and ondemand governors - interactive is now default again
please test for general stability and performance, I will released a overclocked version soon maybe
sources: https://github.com/glewarne/Galaxy_S6_920F_Kernel_v2
Hello!
This is a development thread for the project of upgrading of the Linux kernel for the U8500 platform.
Builds provided here (at the moment of writing this message) are not considered to be used as a daily driver, by any means, - these are rather a dev preview versions.
For now, there are a several LK builds (the highest currently supported kernel version is 3.10).
Because builds here are really not stable, I'll just leave a disclaimer here.
Code:
#include <std/disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modificiations, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
Working features
RIL
Camera (front & rear) - only works in <3.8
Video (playback & recording)
Audio (playback & recording)
Wifi
Bluetooth (broken in >=3.8, needs a workaround to manually startup)
USB, ADB
Tethering (not tested)
GPS (not tested)
Sensors
Known bugs
IRQs are mishandled by some device drivers (abb_btemp, abb_fg)
proximity sensor might not work (not tested, cause it's broken on my device)
deep sleep might not work at a times
MMC driver works unreliably in >=3.8 (contiguous usage might lead in a data corruption)
networking is not fully-functional (no mobile data)*
camera is broken in 3.8
*some other features of the android kernel might not present - it's because these kernels lacks android-specific patches.
Sources
LK 3.5
LK 3.6
LK 3.7
LK 3.8
LK 3.9
LK 3.10
Downloads
http://xda.mister-freeze.eu/XDA-files/ChronoMonochrome/misc/upgrading
Installation
install chrono kernel r5.2 or higher (this is needed to pick up the necessary scripts, incl. bootscripts, etc)
reboot to recovery
install build linked in "Downloads" section
Credits
Linux kernel development community
Google
ST-Ericcson
Samsung
Team Canjica
XDA:DevDB Information
U8500 Linux kernel upgrading project, Kernel for the Samsung Galaxy Ace II
Contributors
ChronoMonochrome
Kernel Special Features:
Version Information
Status: Alpha
Created 2017-05-09
Last Updated 2017-05-10
Reserved
Porting
The porting a higher kernel version tehnique I'll describe here is not intended to be a guide for dummies. I'll assume you've already built a kernel for your device, familiar with git versioning control usage and with some porting / coding tehniques.
Firstly, you need a cleaned source for your device. By "cleaned" I mean, there are no Linux incremental patches, android changes applied, manufacture-specific patches are avoided when possible and so on - you need sources as closest to a "pure" Linux kernel as possible. Otherwise you'll have later need to deal with conflicts resolution, you'll most likely be unable to resolve and the kernel won't boot.
So, without a further forewords, the tehnique is below:
1) As was previously mentioned, a clean kernel source is required, I'll assume we are starting from LK-3.4 ( https://github.com/ChronoMonochrome/Chrono_Kernel-1/commits/ea228ee0f5e9935841aff25c62fa163cd78dc01d ) and porting a higher kernel versions. A kernel base needs to be tested for any bugs just to distinguish, which bugs were intruduced during porting from those ones that already present in a kernel base.
2) The following steps will mostly use git bisect and git merge commands in order to merge all the changes from a higher kernel versions and help to find / resolve the bugs that were introduced. I suggest copying a git kernel repo that you use for building to a somewhere else, so you can use it , e.g. for grepping a different versions source, bisecting the revisions and so on, so don't need to bother messing up in your main repo that you use for build.
3) Firstly, lets just try to merge a higher kernel version, e.g. LK 3.5 by issuing a command git merge lk-3.5. You'll likely have a lot of merge conflicts, most of which you can resolve with resetting the paths to a some revision (either a kernel base - lk 3.4, or the version you do port, or just another suitable conflict resolution). So I suggest to write those paths to a text file, like so:
Code:
arch/arm/boot
arch/arm/mach-ux500
arch/arm/plat-nomadik
drivers/mmc
include/linux/mmc
drivers/usb
include/linux/usb
drivers/mfd
include/linux/mfd
...
Write all the paths you intend to reset to the kernel base, you most likely need to re-use them later. To actually perform a resetting source, you can issue
Code:
for path in $(cat file_with_a_paths.txt | xargs)
do
git checkout COMMIT $path
done
Be sure not to put to this file anything not the device-specific! Resetting to the kernel base should be avoided when possible (never ever try resetting archictecture-specific paths, e.g. arch/arm/kernel, arch/arm/mm and so on - unless you really know that kernel will boot thereafter, instead, you have to manually resolve such conflicts). Resolve any other conflicts by resetting paths to the porting source (e.g. LK 3.5).
Note. While resetting with a paths is probably not the most accurate tehnique, but people don't live that long to use more accurate approach, e.g. performing git cherry-pick for every upstream commit and then manually resolving all the conflicts, you'll just sooner or later get bothered and will abandon it.
4) When you're done with the previous steps you can try building kernel. You'll likely have a build errors - because some part of a source got not updated (e.g. the device-specific drivers), you need manually implement the necessary by a higher kernel version changes. Firstly check if an upstream kernel contains the necessary fixes (example: https://github.com/ChronoMonochrome/Chrono_Kernel-1/commit/9fae8c449b710f502662da1cbcf26ece5a098af9 , https://github.com/ChronoMonochrome/Chrono_Kernel-1/commit/fe027c25d6db0d100937deb5248e249ec5b24ee7 ). If the driver you are porting doesn't exist in the upstream, you can also try to find a similar change and mimic it: https://github.com/ChronoMonochrome/Chrono_Kernel-1/commit/5f2e7afbf2ac3284dc62b3d96a0627c7f99ed4e9 ( ported similarly to https://github.com/ChronoMonochrome/Chrono_Kernel-1/commit/526c597 ). In the worst case scenario you will need to examine the upstream changes and apply the changes so that the drivers complies to the upstream changes: https://github.com/ChronoMonochrome/Chrono_Kernel-1/commit/ea6432d167 .
5) If everything is done properly and you're lucky enough, the compiled kernel might already bootup. If not, you'll need to find a culprint that doesn't let the device to boot up. Switch to a copy of your kernel sources, reset the source to the base kernel version (e.g. LK 3.4), issue git bisect good, then issue git bisect bad lk-3.5, git will reset to a somewhere in a middle between of LK 3.4 and LK 3.5.
6) Save your changes in the kernel repo, by assigning a some branch to it, switch to the source base, merge all the fixes you've already introduced, then merge the revision you have got in the previous step by bisecting the tree. Repeat these steps until you'll find a first bad commit.
7) If you are already on this step, the most trickiest part starts here - testing (hopefully) working kernel for bugs (if any). While logs can be useful sometimes (so you can google the failing messages and find something useful), there are also many bugs you can find only performing git bisect tehnique decribed above.
The decribed algorithm only possible thanks to having a clean kernel source. The usage of this guide is not limited only to the kernel porting, it can be used on other projects as well, this is just what I've come across to, when I've ever started porting Linux kernel versions higher than LK3.4.
Reserved
I wonder if any of this expertise couldn't look pretty cool here too.
Wooooowwwewe
Oooh
Look whose good boys have been trying to win the STE mastermind prize as of lately
https://github.com/novathor-mainline/linux
https://git.kernel.org/pub/scm/linu...inux-nomadik.git/log/?h=ux500-skomer-v5.5-rc1
mirhl said:
Oooh
Look whose good boys have been trying to win the STE mastermind prize as of lately
https://github.com/novathor-mainline/linux
https://git.kernel.org/pub/scm/linu...inux-nomadik.git/log/?h=ux500-skomer-v5.5-rc1
Click to expand...
Click to collapse
Seriously!
mirhl said:
Oooh
Look whose good boys have been trying to win the STE mastermind prize as of lately
https://github.com/novathor-mainline/linux
https://git.kernel.org/pub/scm/linu...inux-nomadik.git/log/?h=ux500-skomer-v5.5-rc1
Click to expand...
Click to collapse
Wow, that's incredible
Exynos4412 already got some mainline support, it would be very nice to have this one supported too.
Aaaaand it's done, kinda.
ST-Ericsson NovaThor U8500 - postmarketOS
wiki.postmarketos.org
device/testing/linux-postmarketos-stericsson · master · postmarketOS / pmaports · GitLab
postmarketOS package build recipes
gitlab.com
Welcome to OreKazu-Kernel Project
My main objective for this kernel project is to somewhat keep it simple but include a few features that I find useful , it won't be bloated with all the features out there.
I decided to share this kernel (at first it was a personal project ) with the great S5 community. Im a noob at this so don't expect much (lol) , as far as I know this kernel was complied under KLTE but my variant is a KLTEVZW , so my guess any other variant that can run KLTE kernels this should work as well.
OreKazu-Kernel is still in beta stages but it still works very well.
* Features of this Kernel*
- 268mhz CPU
- Smartmax eps CPU Gov
- CPU Boost
- Input Boost
- CPU Voltage Control
- Mako Hotplug
- GPU Overclocked to 600mhz ( since LOS15.1 still has a power drain issue higher gpu freq will def drain even more , keep that in mind )
- GPU Overclocked to 657mhz
- GPU UnderClocked to 27mhz
- Adreno Idler
- Kcal
- USB Fast Charge
- Kernel Samepage Merging
- LMK (soon switching to @fbs 's version)
- Few TCP Congestion Algorithm
- and maybe other features to come..
Download : Rebasedv3 Latest Download ( !! This link will be updated with each release !!)
XDA:DevDB Information
OreKazu, Kernel for the Samsung Galaxy S5
Contributors
KazuDante, haggertk, sunilpaulmathew, LineageOS , @fbs , @ktoonsez , @hispasian, @CrazyGamerGR and @To all of you for trying my kernel......Thank You.
Source Code: https://github.com/KazuDante89/android_kernel_samsung_msm8974
Kernel Special Features: Listed in Original Post
Version Information
Status: Beta
Current Beta Version: v2.0
Current Rebasedv3 Version: v1.4
Beta Release Date: 2018-01-27
Created 2018-01-27
Last Updated 2018-03-16
Reserved
01/27/2018 - Initial Release (Beta).
01/29/2018 - Added MSM MPDecision Hotplug
- Sound Control
- Sound Control Gain Level increased by default ( thanks @sunilpaulmathew ).
Reserved
Nice to see your kernel @KazuDante
Good luck...
sunilpaulmathew said:
Nice to see your kernel @KazuDante
Good luck...
Click to expand...
Click to collapse
Its mostly thanks to you that this was possible. Thank you Mathew:highfive:
Great work...
OreKazu-Kernel v1.6 Released
check the OP for download link (updated as always)
Check reserved for changes made to the kernel.
Enjoy!!
Update
V2.0 is now out .
Kernel as been started back off from the ground ( :crying: ) up due to some issues i faced , heck it might start off from scratch again but that time it would be due a switch to a different ( new laptop) workstation.
-sound control was removed due to instabilities from initial Lin15-1 so adding sound control only made it worst ( in my experience)
-a few other stuff are not added back yet but a few thing were added.
- since this is not stable/official release i won't bore you with the details , as always same download link from OP is updated to current release.
OreKazu-Kernel-Rebased_v1.0
This is just a re-base launch ( yep started from scratch again lol ) but decided to switch it up a little .
Pretty much the same features with some new added ones that were not in the original Orekazu-Kernel.
Latest Lin15-1 kernel commits as of today.
Also added another gpu gov , and i dont remember if the other Orekazu-Kernel had the added cpu frequencies.
Download link in OP.
Enjoy!!
WireGuard
Hi, what about WireGuard support? Is included in this kernel? Or will be?
Thanks
ZS-Man said:
Hi, what about WireGuard support? Is included in this kernel? Or will be?
Thanks
Click to expand...
Click to collapse
I will look into it , ive never heard of wire guard b4 , but it is an interesting feature. Can't say for sure that it will work unless you know of another samsung kernel that already had the support in it ( that would be much helpful ) , but i will take a crack at it and see if it will work and not cause a loss in anyway.:highfive:
ZS-Man said:
Hi, what about WireGuard support? Is included in this kernel? Or will be?
Thanks
Click to expand...
Click to collapse
It will be difficult to include Wireguard support to any klte kernel atm as it is only available and intended to work on Linux Kernel versions 3.10.y and above.
KazuDante said:
I will look into it , ive never heard of wire guard b4 , but it is an interesting feature. Can't say for sure that it will work unless you know of another samsung kernel that already had the support in it ( that would be much helpful ) , but i will take a crack at it and see if it will work and not cause a loss in anyway.:highfive:
Click to expand...
Click to collapse
sunilpaulmathew said:
It will be difficult to include Wireguard support to any klte kernel atm as it is only available and intended to work on Linux Kernel versions 3.10.y and above.
Click to expand...
Click to collapse
3.10.x kernels and up? , then sadly it wont be able to be supported.
i guess the only option is if Lineage can support it unless it depends on the kernel aspect as well ,if so then thats a no-go for WireGuard.:crying:
Hi.. Awesome kernel.. Btw i manage to port it on hlte with lineage defconfig... I got many features but some are missing and may not work properly because u're using MSM8974PRO.. Can u support MSM8974 too?? Thanx.. Im new in this kind of things btw..
jprimero15 said:
Hi.. Awesome kernel.. Btw i manage to port it on hlte with lineage defconfig... I got many features but some are missing and may not work properly because u're using MSM8974PRO.. Can u support MSM8974 too?? Thanx.. Im new in this kind of things btw..
Click to expand...
Click to collapse
Not sure , since my setup is limited and manually applying the commit for hlte might be a a troublesome task , but none the less i'll give it a shot .
Can the CPU increase 3.0 oc
limalvin1203 said:
Can the CPU increase 3.0 oc
Click to expand...
Click to collapse
It will burn out your phone
Boot loop and how long does it take to boot
limalvin1203 said:
Can the CPU increase 3.0 oc
Click to expand...
Click to collapse
as @kenedielh stated , it will overtime burn(sort of speak)out your device, kill the cpu at one point , also to avoid even more battery drain as Lineage has not fully fix battery drain plus the gpu is at 657mhz compared to stock 578mhz max , also due to past experience testing 3.0ghz its very unstable so keeping max at 2.4ghz is the best course of action in this kernel's case. For example when i was testing Venom Kernel my max cpu freq was always set at 15xxmhz and nothing more and gpu at 657mhz max and between a 100-105 - undervolt ( silicon lottery , your mileage may vary ) .
Also since this is just beta thread im just compiling , testing and sharing builds here , Stable release when ready and very stable/smooth/and power efficient even for gamers like myself , it will be in the Unified section and this beta project will be deleted , think of this as a rough-draft for the main thing to come.( hopefully)
limalvin1203 said:
Boot loop and how long does it take to boot
Click to expand...
Click to collapse
You need to update your lineage to @haggertk's ( taking this opportunity to thank @haggertk ) latest build , i doubt my kernel will work on an old build of lineage since many changes have been made on both kernel and rom sides.
Yours: Kernel date : december 2017
Rom : december 2017
Heres the latest klte build : https://androidfilehost.com/?fid=673956719939820275 " download and flash it then flash OreKazu-Kernel-Rebased right after "
that what everyone else is using if running this kernel , both have to be up to date.
Linux Kernel 4.9 for Moto G5
As you guys already know, our Moto G5 has an ancient linux kernel (3.18.x) which is now EOL (end of life) from support from actual Linux Foundation. It's pretty much stuck there with no probable updates to it (can use the android 3.18 for updates, but I think that's pretty much soon to be deprecated).
I have been working on this kernel since the past one year and finally managed to boot it on our Cedric!
WARNING: THIS KERNEL IS STILL ALPHA AND MOST OF THE BUGS HAVE STILL NOT BEEN FIXED.
I just wanted to share this kernel with the community!
What works:
Boots
Display
Touch
Storage
Charger
Battery Indication
Bugs:
Pretty much every basic thing
RIL (Calls, mobile data, etc.)
Vibrations (Weird and too strong)
Camera
Flashlight
Only Oreo boots so far.
Want to try for yourself?
Click Here to download link LineageOS 15.1 with Linux Kernel 4.9
Huge Thanks to @wiktorek140 for helping me out with bugs and congratulations to him for booting 4.9 on Montana
Leave a thanks if you like my work!
Buy me a Cup of Coffee or Beer here
XDA:DevDB Information
Linux Kernel 4.9, Kernel for the Moto G5
Contributors
m_vaisakh, wiktorek140
Source Code: [url]https://github.com/mvaisakh/msm-4.9[/URL]
Kernel Special Features: Linux Kernel 4.9.x
Version Information
Status: Alpha
Created 2020-03-30
Last Updated 2020-03-30
Reserved
You can find screenshots here:
https://m.imgur.com/a/OWEhM3b
NOTE: The screenshots are from 2 different builds and hence the difference in kernel version.
Cheers!
Update:
I've been working to fix display and audio on for us.
You can check the progress in my kernel repository. I hope to fix it soon!
Nice! Simply nice. This will hopefully get more attention :good:
Update:
Indian variant finally boots now!!
Thanks to Neosight from Mido community for the fix!
It was because of the bootloader not accept the arm IOMMU of cedric (atleast in indian variant). Instead the kernel sent a full aarch64 (or arm64) iommu tz cb, which wasn't getting a secure pass from bootloader through qseecom interface, which apparently states that motorola still uses older (nougat) bootloader in XT1677 (or the Indian variant).
m_vaisakh said:
Update:
Indian variant finally boots now!!
Thanks to Neosight from Mido community for the fix!
It was because of the bootloader not accept the arm IOMMU of cedric (atleast in indian variant). Instead the kernel sent a full aarch64 (or arm64) iommu tz cb, which wasn't getting a secure pass from bootloader through qseecom interface, which apparently states that motorola still uses older (nougat) bootloader in XT1677 (or the Indian variant).
Click to expand...
Click to collapse
Ig edit the op then :angel:
nift4 said:
Ig edit the op then :angel:
Click to expand...
Click to collapse
Updated OP.
m_vaisakh said:
Updated OP.
Click to expand...
Click to collapse
bro how did u update from v3.18 to v4.9 ? Pls I wanna know where can I study about this?
devvikram said:
bro how did u update from v3.18 to v4.9 ? Pls I wanna know where can I study about this?
Click to expand...
Click to collapse
CAF had added support for msm8937 for 4.9 with Android Oreo, I just used their base and added moto g5 specific changes. It may sound easy, but it's not.
m_vaisakh said:
CAF had added support for msm8937 for 4.9 with Android Oreo, I just used their base and added moto g5 specific changes. It may sound easy, but it's not.
Click to expand...
Click to collapse
where to study on this??I want to do with my Snapdragon 625 . It's v3.18 which I have to upgrade to v 4.9
devvikram said:
where to study on this??I want to do with my Snapdragon 625 . It's v3.18 which I have to upgrade to v 4.9
Click to expand...
Click to collapse
There's no specific documentation for this. It was all trial and error. Have you read the OP? I've clearly stated it took me 1 year to get it to work.
To start, you should know your way around linux kernel and for reference you can use my source and well there are many other devices that were 3.18 and now run 4.9
m_vaisakh said:
There's no specific documentation for this. It was all trial and error. Have you read the OP? I've clearly stated it took me 1 year to get it to work.
To start, you should know your way around linux kernel and for reference you can use my source and well there are many other devices that were 3.18 and now run 4.9
Click to expand...
Click to collapse
thanks alot
I overtook the development and got a few quite nice results. Current bug list:
Boots -
Bt -
Wifi -
Camera -
Vibration -
Gps -
Audio -
Ril - (no call audio)
Fp -
Light Sensors -
Accelerometer -
Proximity -
Gyro -
Mic -
Usb Tethering -
MTP & ADB -
Headphones -
Offline Charging -
Flashlight -
SD Card -
FM Radio -
Issues:
Rebooting to recovery boots to system.
Random reboots.
(that is on Android 10)
my source is at https://github.com/n4experiments/
and thanks to wiktorek140 and his 4.9 montana port because without him I would never be able to get so far