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
Hey Fellow XDA Developers.....Sorry I've to start this thread due to a reason that I've toggled everywhere in existing guides & Threads but I'm fed up that none of them is comprehensive or Correct...
OK I want some of the answers to (I guess extremely silly) questions
Q.1:: So I want to Develop a Custom Kernel on Backbone of Aurora and stock Linux kernel. Any possible way how can i extract, mod ;
edit and add and recompile it.... any specific tools,links.(already visited android authority)
Q.2::Can anyone tell me where i can find additional "".KO"" files(Kernel object libraries/kernel expander)
Q.3::Since most apps have a <uses sdk> so it means somewhere in /root directory the sdk is save right so latest android like
lollipop has new revision of sdk. is his possible to copy kitkat and lollipop sdk files to system from Android studio(I know this
is the worst joke or some sort of question asked by a fool but still out of curiosity of my never ending thirst of development)
Q.4::Nowadays I'm in a Quest to develop a Custom ROM since my phone is "NOT EVEN UNOFFICIALLY PORTED".I tried finding
my phones stock ROM[Panasonic P81][Xda Forum of P81 is totally Crap](Some stupid guy modded and made it worst than
sh!t).I heard Rumour that my clone "Cool pad 7320" has CM 6 or 11 Successfully installed/flashed but referring to the website
I tried and Bricked it. (Ironically I'm now using that modded coolpad ROM by Xdafirmware.com)
Q.5::Can U Tell if I can flash Stock Marshmallow Nexus image on my phone!!!!!!!![greatest question] I'M Die Hard Fan Of
Marshmallow And can Brick my phone infinite times getting it..
Q.6::What happens if I Replace my Stock kernel with original Linux (the pc one) (that im having.) . Will it work,add functionality ,or
brick it.
=======System Specs=======
Device Name : Panasonic P81
Boot loader : Unknown.(Same for all Panasonic I guess)
Processor : Mediatek MT6592 @ 1.7 Ghz 8 cores 32 bit archetecture
Kernel version: 3.4.39 [email protected] #1
Custom Build : 1012
Android Version: 4.2.2 jellybean apl 17
RAM: 1 GB
MODEL/BUILD ID: EB-90S055P81V1012
Runtime: Dalvik(libdvm.so) version 1.6.0
Motherboard: yulong92_wet_jb9
Radio: MOLY.WR8.W1315.MD.WG.MP.V19.P2
SELinuxermissive by default (stock)
CPU ABI- Armeabi
Features: swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt
BOGO MIPS: 1685.91
Kernel Feature: Entropy & SMP PREEMPT
Toolchain: dcc version 4.6.x-google 20120106(pre release) (GCC)
**NEON SUPPORTED
==eMMC==
Name: K7XVMB
==sensors==
1: BOSCH BMA056 3-AXIS Accelerometer
2:ROHM RPR 410 PROXIMITY SENSOR
3:ROHM RPR 410 LIGHT SENSOR
==GRAPHICS==
VENDOR-ARM
GPU Renderer- MALI 450 MP
OPENGL: OpenGL ES @.0
ShaderpenGL ES GLSL ES 1.00
*****Eagerly Awaiting for answers . Please a positive cheer ups will be appreciated I'm noob here :angel::highfive: [Not that extreme I've enough xp regarding flash,boot loop,recovery,porting etc. ]*****
Most guides for this are found here,
http://forum.xda-developers.com/chef-central/android
If none there are helpful, then I'm at a loss for a suggestion. There's a lot of resources in that link. :good:
You are gonna run into a ton of issues. First off the chip that device uses never releases kernel source. So that will put a stop to your work real fast.
As for some of the other questions.
No you can't put a stock Linux kernel on the device. Kernels are made for each devices. They don't all work on every device.
zelendel said:
You are gonna run into a ton of issues. First off the chip that device uses never releases kernel source. So that will put a stop to your work real fast.
As for some of the other questions.
No you can't put a stock Linux kernel on the device. Kernels are made for each devices. They don't all work on every device.
Click to expand...
Click to collapse
Hey my kernel by default is stock aosp Linux version 2.4.39
Tanmoy Mitra said:
Hey my kernel by default is stock aosp Linux version 2.4.39
Click to expand...
Click to collapse
And the original revision of Linux I'm referring is the one created by Linus torlavads that is backbone of PC platform of Ubuntu, KDE and many other operating system. OK Aurora kernel is out of date and no support is available but I'm impressed by or rather moved by its spects and I feel that it is fantastic kernel to start with....... I just want to modify and continue from where he left a full stop to support. Many user still uses Aurora and there exist a hidden community about it.I WANT TO PROVIDE THE UPDATES AND SUPPORT OR WANTED TO DEVELOP A NEW KERNEL. OK on my 15 day research over kernel I found it is best kernel with a negligible cons and many features to opt within. Tell me which kernel can give me 16+ Governors and 9 scheduler and 6 TCP congestion algorithm to play with. With NEON and selinux support init.d and best battery backup among other kernel without even compromising a bit on graphics and rendering......Tell me
Tanmoy Mitra said:
And the original revision of Linux I'm referring is the one created by Linus torlavads that is backbone of PC platform of Ubuntu, KDE and many other operating system. OK Aurora kernel is out of date and no support is available but I'm impressed by or rather moved by its spects and I feel that it is fantastic kernel to start with....... I just want to modify and continue from where he left a full stop to support. Many user still uses Aurora and there exist a hidden community about it.I WANT TO PROVIDE THE UPDATES AND SUPPORT OR WANTED TO DEVELOP A NEW KERNEL. OK on my 15 day research over kernel I found it is best kernel with a negligible cons and many features to opt within. Tell me which kernel can give me 16+ Governors and 9 scheduler and 6 TCP congestion algorithm to play with. With NEON and selinux support init.d and best battery backup among other kernel without even compromising a bit on graphics and rendering......Tell me
Click to expand...
Click to collapse
I know what you are talking about and it won't work. Each device kernel is different from each other. Android is not the same as a desktop Linux set up. Also kernels differ from one pc to another.
As for those options you will have to add them yourself.
Again without the kernel source For that device being released you are out of luck.
zelendel said:
You are gonna run into a ton of issues. First off the chip that device uses never releases kernel source. So that will put a stop to your work real fast.
As for some of the other questions.
No you can't put a stock Linux kernel on the device. Kernels are made for each devices. They don't all work on every device.
Click to expand...
Click to collapse
Well I set to build it and yes I FOUND THE SOURCECODE FINALLY!!! although not for my board and device... While my device is Panasonic P81 and board is: yulong92_wet_jb9 the source was of Gionee Elife S5.5 same processor and features. But marked as board: vanzo92_wet_jb9
I don't think it will be issue, also found out that my device can support FDD LTE (VoLTE too) but needs a port from mt6595(helio x10)
[MT 6575 = LTE BASEBAND OF MT6590 + OCTA CORE architecture of MT6592 WHICH I USE]
So your help will be appreciated:good::laugh:
Sent from my Panasonic P81 using XDA Labs
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