Database Info

[KERNEL][3.10 PORTING][DEVS ONLY][S4][VILLE]

FOR DEVS ONLY
THIS IS A DEVELOPMENT THREAD FOR PORTING THE LINUX 3.10 KERNEL TO THE HTC ONE S (VILLE) S4 EDITION
MODERATORS PLEASE DELETE ANY POSTS THAT ARE NOT RELATED TO THE DEVELOPMENT OF THE KERNEL (OTHER THAN THESE FIRST POSTS USED TO CREATE SOME DOCUMENTATION)
XDA:DevDB Information
3.10 Kernel for the HTC One S, Kernel for the HTC One S
Contributors
javelinanddart
Kernel Special Features:
Version Information
Status: Testing
Created 2015-01-15
Last Updated 2015-01-15

This thread is a development thread for porting the Linux 3.10 Kernel to the HTC One S
All Devs are welcome to step forward
https://github.com/javelinanddart/android_kernel_3.10_ville
This will be done from the CM 12 Source Code
This IS NOT an easy task, it will take a lot of time and lot of things will need to be changed
CyanogenMod might have to be rebuilt from source to have this work properly
Look at the mergeconflicts.txt to look for things to fix, look at the fixedconflicts.txt for things that are fixed

Advantages:
-Officially Supported (3.10 is what the Nexus 6 & 9 and Android Wear Devices are Using)
-Future Android Compatibility (Android Framework and Kernel are Decoupled but Still Matters)
-Better Performance (Somewhat)
-Bragging Rights (xD this is a joke)
-Better and Newer Drivers
-More Features
-More Optimized
-Longer Support Date (Most Likely)
-Most Future Devices will Run 3.10 Kernel (Keeps our Device Current)
-Lower RAM Usage
-Support for F2FS (a faster file system for nand flash storage devices)

Contributor List
@intervigil (Ethan Chen)
@AKToronto
@mikronac.ns (Mikronac)

FAQ
Why?
Because I can (lol)
Check the Advantages list

Changelog
Initial Upload of Source
Merge tag v3.10

Resources
http://elinux.org/Kernel_3.4_to_3.10_porting_guide

A lot of the Kconfigs I fixed I just used the 3.10 ones and they're missing a lot of drivers it seems. We might have to readd those Kconfig Options. Also the defconfig will be a pain in the ass to maintain until we have a final product

javelinanddart said:
A lot of the Kconfigs I fixed I just used the 3.10 ones and they're missing a lot of drivers it seems. We might have to readd those Kconfig Options. Also the defconfig will be a pain in the ass to maintain until we have a final product
Click to expand...
Click to collapse
yeah, I am just looking in it...

mikronac.ns said:
yeah, I am just looking in it...
Click to expand...
Click to collapse
1 sec then, I'm merging with the aosp source rather than mainline linux because it includes some android specific changes
Look at the mergeconflicts.txt or try compiling it.....
My god... never seen THAT many errors in the Kconfigs

wow @javelinanddart nice, hope to port this to the m7 soon in time for lollipop, If you are having problems with drivers try taking a look at the evita kernel source, due to its similar hardware

dd98 said:
wow @javelinanddart nice, hope to port this to the m7 soon in time for lollipop, If you are having problems with drivers try taking a look at the evita kernel source, due to its similar hardware
Click to expand...
Click to collapse
Sounds good, but does Evita have a 3.10 kernel? Hopefully HTC will do that because usually they're pretty OK at updating their kernels (if not android versions)
Also @dd98, this is from the Cm12 source so if you want to help, it can possibly be compatible with the M7 @phoenixita if you'd like to help that'd be great too

javelinanddart said:
Sounds good, but does Evita have a 3.10 kernel? Hopefully HTC will do that because usually they're pretty OK at updating their kernels (if not android versions)
Also @dd98, this is from the Cm12 source so if you want to help, it can possibly be compatible with the M7 @phoenixita if you'd like to help that'd be great too
Click to expand...
Click to collapse
I'll gladly help but still only getting there on the kernel development, hope I have some free time

dd98 said:
I'll gladly help but still only getting there on the kernel development, hope I have some free time
Click to expand...
Click to collapse
What's your github username? I'll add you as a collaborator rather than pull requests. It works faster

@javelinanddart F2Fs already works on Ville I already ported it [emoji1]

Flashalot said:
@javelinanddart F2Fs already works on Ville I already ported it [emoji1]
Click to expand...
Click to collapse
I know but this is meant to be like a CM kernel (i.e. no backported features unless absolutely necessary
On a completely unrelated note, how can I build a rom and recovery with f2fs support?

javelinanddart said:
I know but this is meant to be like a CM kernel (i.e. no backported features unless absolutely necessary
On a completely unrelated note, how can I build a rom and recovery with f2fs support?
Click to expand...
Click to collapse
Ahh I see my bad also if I told you I would have to kill you [emoji88]
Jk
I'll be making a thread some time this weekend with full documentation on how to do so especially recovery since we have 3 different types just on twrp

Flashalot said:
Ahh I see my bad also if I told you I would have to kill you [emoji88]
Jk
I'll be making a thread some time this weekend with full documentation on how to do so especially recovery since we have 3 different types just on twrp
Click to expand...
Click to collapse
Thanks. If we can switch to F2FS and use a Universal TWRP, developers will have a better time on source-based ROMs. It will also help speed up the file system actions. I tried compiling twrp but I couldn't figure it out

What source are you editing the 3.4 kernel source or the 3.10 kernel source ?

Wahaj.47 said:
What source are you editing the 3.4 kernel source or the 3.10 kernel source ?
Click to expand...
Click to collapse
"3.10 porting"

[KERNEL][LineageOS 14.1/CM12.x][r_12] Kernel12 | Oct 30th, 2017

༼ つ ◕_◕ ༽つIn the name of our great lord Helix!༼ つ ◕_◕ ༽つ
Welcome to the first custom CM12 kernel for the Z3 Compact
Kernel12
We're going on an adventure!​
AMAZING FEATURES:
They happen to change so often that you're better off checking the changelog, but if you're stubborn, here's the core ones:
Additional CPU and GPU steps
Faux123's Intelli_plug and Intelli_thermal
adreno_idler
Memory fixes up the arse
Countless battery life and overall performance optimizations
A reason for Myself5 to, as he says, compete
Custom installer that combines both the permissive and enforcing image in one tiny zip
Obviously there's more so go ahead and check my Github!
DOWNLOADS:
http://j.mp/kernel12-1
Generously hosted by Androidfilehost.com
Note that the newest old (stable or not) builds (CM 12.0) are still available on the original site for now: http://bit.ly/kernel12
HOW-TO:
* Use TWRP
* Flash zip
* Read what the zip tells you
SERIOUS DISCLAIMER!
Code:
I guarantee nothing except for squids taking over our planet by the year 3027. #squidmasterrace
I'd also like to point out that the kernel developers for this device are different people with different lives, schedules and priorities, which shows in many differences in their work. We are not enemies or competitors but rather friends and colleagues, but we each support what we do as we are able to and as we deem is best.​
Kernel sources: https://github.com/someone755/android_kernel_sony_msm8974 (cm12.x)
https://github.com/someone755/android_kernel_sony_msm8974-1 (cm14/lineageos 14)
༼ つ ◕_◕ ༽つPRAISE HELIX༼ つ ◕_◕ ༽つ
XDA:DevDB Information
Kernel12, Kernel for the Sony Xperia Z3 Compact
Contributors
someone755
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: r_12
Stable Release Date: 2017-10-30
Created 2015-02-22
Last Updated 2017-10-30

A quick FAQ that you'd better read before posting.
1. What was up with the nonsense naming scheme before 12.1?
A: Back then I believed people would actually test the unstable builds I pushed out very often, but I found out only a minority did so. With 12.1, I've decided to turn a new leaf and try to merge the two -- the builds won't be as extensively tested as the stable ones were before, but they will be released faster.
For now, all you need to know is that rperm means permissive and renf means enforcing builds.
2. How do I flash this?
A: Flash through recovery and read what the recovery tells you.
3. My bootloader is locked, HALP! OR I'm on stock/AOSP/CM7.
A: Then you don't get to install this kernel. Pretty simple but still, tough luck.
4.. What app do you recommend for dealing with CPU settings?
A: TricksterMod and Kernel Auditor work for me. Go around the internet, try different apps and see what works for you, then keep it.
5. Touch Control doesn't work in rXXX release, you suckas, fix plixe! OR My phone exploded, HALP!
A: Go away. I do not respond to bug reports without a proper description and log.
6. I have a bug to report!
A: Great! Unlike the guy in #5, you may submit the error either to DevDB or in the thread (just tag me if you're posting into the thread). Make sure your description of the error is detailed, and that you have a log (located in /proc/last_kmsg). It'd be best to upload the log via pastie.org If possible, please also list the way in which the error was triggered.
7. I want to support you and your work!
A: Awesome! Click thanks and/or share the thread with other guinea pigs who would like to participate!
8. OP is arrogant, I'm gonna call the Internet Police? OR Why are you such a derp and asshole
A: Indeed I am. Deal with it.
9. Where may I find the discussion thread?
A: This thread serves as both the development and discussion thread. Please to not litter (GTFO with "thanks" and "+1" posts), and try to keep to the topic. That said, if you're reporting a bug or requesting a new feature, you may use either DevDB or the thread, but please tag me should you opt for the latter. Just remember, reviews go in the "Reviews" tab!
Special shoutouts to (in no particular order, all help is equal help):
AndroPlus
funiewski
Myself5
sm4tik
nelvinchi
franciscofranco
Freexperia and jerpelea
faux123
Google, Sony and HTC
All Nozomi developers!

EXTREME CHANGELOG:
Releases since r_08: http://bit.ly/changelog12-1 (Nougat/Android 7.0)
Releases r_05 to r_07: http://bit.ly/changelog12 (Lollipop/Android 5.x)
Releases pre-r_05:
Code:
for a more detailed changelog, check my GitHub (although you're probably better off not doing that)
for STABLE BUILDS
[*] r_05 ### 16/8/2015 ***UPDATE***
-merge upstream CM commits (more WiFi commits)
-enable adreno_idler to reduce GPU frequency spikes
-even more fixes to the installer
[*] r_04 ### 30/7/2015 ***UPDATE***
-enable screen color control
-downgrade powersuspend to a version that Kernel Adiutor supports
-more memory tweaks
-fix a bug that caused the CPU to spike after thermal throttling kicked in
-enable a 2.5 GHz CPU step
-introduce some fixes to the new installer (code is _still_ dirty -- I'll be working on it)
[*] r_03 ### 29/7/2015 ***UPDATE***
-enable F2FS
-fix the 268 MHz and 2419 MHz steps and allow voltage control
-use the already-existing ramdisk instead of using our own
-merge the permissive and enforcing image into a single zip -- let the user choose what to do on install
[*] r_02 ### 18/7/2015 ***UPDATE***
-merge upstream CM commits (wifi updates)
-upgrade intelli_plug to 4.0
-improve GPU driver and allow apps to use more RAM
-introduce 268 MHz and 2419 MHz CPU frequencies
-disable mpdecision and enable intelli_plug in its place
-enable intelli_thermal by default, set throttling point to ~80°C and poll time to 3 seconds
[*] r_01 ### 18/7/2015 ***UPDATE***
-merge upstream CM commits, update the whole thing to better work with lp-mr1
-downgrade intelli_plug to 3.9 as 4.0 was causing issues -- future TODO!
-bring kexec support to stable builds (multirom is finally supported)
-move to a new download host (androidfilehost)
-go back to CM ramdisk
[*] O3 ### 15/4/2015 ***UPDATE***
-update intelli_plug
-disable Qualcomm's MP-Decision and enable intelli_plug by default
-merged CM upstream commits (including a LOT of wifi fixes)
-power (powersuspend) and fs tweaks
[*] O2 ### 12/3/2015 ***UPDATE***
-Motorola memutils
-upstream CM commits
-faux123's snake charmer
-intelliactive CPU governor
-kexec_hardboot
-removed recovery from the ramdisk; we're using the FOTA partition as recovery, and we save 3MB on size
[*] O1b ### 10/3/2015 ***UPDATE***
-LZ4 kernel compression
O1b ### 7/3/2015 ***UPDATE***
-upstream CM commits
-asynchronous file sync (reduces IO latency by as much as 34%)
-screen color calibration (KCAL)
[*] O1 ### 25/2/2015 ***UPDATE***
-GPU OC to 657 MHz, added 100 MHz step
-GPU idle set to 27 MHz
-KSM
-FSYNC
-intelli_plug
-intelli_thermal
-voltage control
I hope you like the colors.
Sorry for having 3 OPs, but I'd rather have more than 1 long one.

First off, thank you so much! There's been a massive lack of kernels for our device. Now for my real question, is there any chance you could make a Selinux Permissive variant so we can get xposed working? I'm only asking because you seem to be the only one with a CM12 kernel out :good:
EDIT: Never saw the tabs for feature requests in a thread before, so this should probably go there, my mistake.

C2fifield said:
First off, thank you so much! There's been a massive lack of kernels for our device. Now for my second question, is there any chance you could make a Selinux Permissive variant so we can get xposed working? I'm only asking because you seem to be the only one with a CM12 kernel out :good:
Click to expand...
Click to collapse
Hello yes I would like to science please.
I'll see what I can do, the layout of a boot image has changed drastically since 2012. xD
EDIT: @C2fifield: No biggie, I don't mind feature requests in the thread. To be honest I don't mind anything as long as it's about this kernel/thread.
EDIT2: I've spent two hours trying to set SELinux to Permissive. What I managed to create were a handful of ramdisks that were supposed to change it to permissive (but didn't) and a zImage that completely disables SELinux.
If anyone knows what in the world I have to do for permissive, please let me know. So far everything I've found on the internet about this is how to type "setenforce 0" in a su shell.
EDIT3: I am an idiot. Continue with your lives, the Permissive image will be up in a few minutes.

C2fifield said:
First off, thank you so much! There's been a massive lack of kernels for our device. Now for my real question, is there any chance you could make a Selinux Permissive variant so we can get xposed working? I'm only asking because you seem to be the only one with a CM12 kernel out :good:
EDIT: Never saw the tabs for feature requests in a thread before, so this should probably go there, my mistake.
Click to expand...
Click to collapse
You can use this method.
http://forum.xda-developers.com/showpost.php?p=58887725&postcount=230

was12 said:
You can use this method.
http://forum.xda-developers.com/showpost.php?p=58887725&postcount=230
Click to expand...
Click to collapse
It's alright, I already figured it out. What C2 wanted, if I understood correctly, was for init and onwards to be permissive. If I read that correctly, your proposal only turns SELinux into permissive on Android boot.
I don't know if this makes sense and it may or not be wrong.
EDIT: Also tried your suggested way, didn't work for me.

someone755 said:
It's alright, I already figured it out. What C2 wanted, if I understood correctly, was for init and onwards to be permissive. If I read that correctly, your proposal only turns SELinux into permissive on Android boot.
I don't know if this makes sense and it may or not be wrong.
EDIT: Also tried your suggested way, didn't work for me.
Click to expand...
Click to collapse
Try this. Create su.d folder in /system/ and create a text file that permissive.sh and insert code in permissive.sh and give permissions 755 to both folder and file.
Code:
#!/system/bin/sh
setenforce 0
He wanted to get xposed working. This way makes system permissive on boot and lets xposed framework working properly. This way works for him.
And also thanks for your kernel. Do you consider adding more features to your kernel such as OC,KSM,etc. ??

was12 said:
Try this. Create su.d folder in /system/ and create a text file that permissive.sh and insert code in permissive.sh and give permissions 755 to both folder and file.
Code:
#!/system/bin/sh
setenforce 0
He wanted to get xposed working. This way makes system permissive on boot and lets xposed framework working properly. This way works for him.
And also thanks for your kernel. Do you consider adding more features to your kernel such as OC,KSM,etc. ??
Click to expand...
Click to collapse
That sounds more like it! Still though, I've found it's only one line when putting the boot.img together:
Code:
androidboot.selinux=permissive
Ofc I intend to add more, you didn't think I'd open a thread for just two cherry picks? xD
Looking into a lot of things, my GitHub isn't even half of what I decide to push. KSM is literally just one push of a button in the config, and I just need to cherry-pick others and get them to work (the latter is really where most of the work is at, there's a lot of trial and error).

@someone755 thanks for your kernel!
As the script method with permissive.sh causes some serious issues with dialer and settings (FC) on my device (CM12 02/22) and this is only a not so clean workaround it would be very nice of you if you could consider a permissive variant of your kernel. Thanks in advance!

Zwulf said:
@someone755 thanks for your kernel!
As the script method with permissive.sh causes some serious issues with dialer and settings (FC) on my device (CM12 02/22) and this is only a not so clean workaround it would be very nice of you if you could consider a permissive variant of your kernel. Thanks in advance!
Click to expand...
Click to collapse
Have you tried version ZX1? It works for me but YMMV (which is also why I'm still labeling everything as beta).

someone755 said:
Have you tried version ZX1? It works for me but YMMV (which is also why I'm still labeling everything as beta).
Click to expand...
Click to collapse
Permissive! Gr8, thanks a lot!

someone755 said:
Hello yes I would like to science please.
I'll see what I can do, the layout of a boot image has changed drastically since 2012. xD
EDIT: @C2fifield: No biggie, I don't mind feature requests in the thread. To be honest I don't mind anything as long as it's about this kernel/thread.
EDIT2: I've spent two hours trying to set SELinux to Permissive. What I managed to create were a handful of ramdisks that were supposed to change it to permissive (but didn't) and a zImage that completely disables SELinux.
If anyone knows what in the world I have to do for permissive, please let me know. So far everything I've found on the internet about this is how to type "setenforce 0" in a su shell.
EDIT3: I am an idiot. Continue with your lives, the Permissive image will be up in a few minutes.
Click to expand...
Click to collapse
Thanks so much! I've been hoping for a permissive LP kernel for our device!

@someone755
Oh, I agree that was a fool question
Ok now, I'm waiting your next works. I hope you to add new features and create a good kernel for our device.

Maybe this is a stupid question but what kernel is this based on? The unified kernel? Or is it built from scratch?

@someone755 thx for your work. How about kexec? I know there is no multi rom for z3c yet but maybe it will come soon.

smorgar said:
Maybe this is a stupid question but what kernel is this based on? The unified kernel? Or is it built from scratch?
Click to expand...
Click to collapse
What do you mean, from scratch? o.o
It's based off the CM msm8974 repo's cm-12.0 branch. The branch unifies all Sony msm8974 devices' CM12 kernels, so I guess it's kinda unified.
funiewski said:
someone755 thx for your work. How about kexec? I know there is no multi rom for z3c yet but maybe it will come soon.
Click to expand...
Click to collapse
I'll worry about MultiROM when it gets here. Of course, if it gets here.

someone755 said:
What do you mean, from scratch? o.o
It's based off the CM msm8974 repo's cm-12.0 branch. The branch unifies all Sony msm8974 devices' CM12 kernels, so I guess it's kinda unified.
Click to expand...
Click to collapse
That answers my question perfecly. The 1:st post does not say wich kernel its based on so i just wanted to make sure
Edit: By "from scratch" i ment if you built it on your own based on nothing. It could be the case sinse you dont state wich/what kernel you based your kernel on.

smorgar said:
That answers my question perfecly. The 1:st post does not say wich kernel its based on so i just wanted to make sure
Edit: By "from scratch" i ment if you built it on your own based on nothing. It could be the case sinse you dont state wich/what kernel you based your kernel on.
Click to expand...
Click to collapse
But ... you have the sources right there... Says "forked from Cyanogenmod/android_kernel_sony_msm8974".
There really is only one source I could build something that boots into a CyanogenMod ROM, and it's from CyanogenMod sources.
I still don't understand what you mean by "from scratch" -- starting from either the base Linux kernel or the stock Sony ones is madness.

someone755 said:
But ... you have the sources right there... Says "forked from Cyanogenmod/android_kernel_sony_msm8974".
There really is only one source I could build something that boots into a CyanogenMod ROM, and it's from CyanogenMod sources.
I still don't understand what you mean by "from scratch" -- starting from either the base Linux kernel or the stock Sony ones is madness.
Click to expand...
Click to collapse
Sorry to confuse you. Maybe i did not read the post as i should have... My bad.
My thaught was like you say: madness to build from linux kernel or stock sony but i had to ask to be sure what this was since i did not read the post well enough as it seems
Gonna try this kernel ASAP. Thank you and keep up the work!

[ROM][5.1.1][Experimental] CyanogenMod 12.1 | Linaro 4.9 | Code Review

Overview:
Code:
[B]Experimental CyanogenMod 12.1 compiled with [URL="http://releases.linaro.org/14.10/components/android/toolchain/4.9"]Linaro 4.9 (14.10) Toolchain[/URL].[/B]
This is CyanogenMod 12.1 built straight from source with Code Review
cherry-picks and my own custom device trees and kernel.
CDMA carrier setup:
The following only needs to be done once to allow init to properly setup your carrier specific system properties.
This will set ro.boot.carrier to your specific carrier identifier and will persist through future flashes of this ROM.
Code:
From the bootloader issue the following commands depending on your carrier:
'fastboot oem config carrier verizon' (Verizon)
'fastboot oem config carrier pageplus' (Page Plus)
'fastboot oem config carrier reliance' (Reliance Mobile)
'fastboot oem config carrier sprint' (Boost Mobile)
Builds:
CM-12.1 06-08-2015 (MD5: (2414f09586228eb94bcda47c1f149ed0)
MMS Flashable Zip Fix Thanks @starkly_raving @Alberto97
TK Gapps Mini Modular 5.1 (05-30-2015)
Build Archives
Source Code:
codyf86/android_device_motorola_falcon
codyf86/android_device_motorola_msm8226-common
codyf86/android_kernel_motorola_msm8226 (Stock CM kernel Not even stock anymore kernel xD)
Code Review Cherry-Picks: (Latest build)
healthd: Use android blue for charge percentage
PowerManagerService: Fix updating of mUserActivitySummary
Add option to set default custom function to button recents (1/2)
Add option to set default custom function to button recents (2/2)
cmsdk: do not crash system if CustomTileListenerService isn't present
Note: When Items drop off the above list 9/10 they have been merged.
Changelog:
Code:
I don't believe in change logs; I believe in Github.
Please look above at the Code Review and also through
the source code commits to see what's changed.
The proof is in the [STRIKE]pudding[/STRIKE] Github.

Nice man ... Will be giving this a shot. Do you have a bug tracker set up or do you want logs and reports posted here?

Yummy. Also trying this out for sure.
Edit: Sub'd, Muuahahaha!....Oh.

starkly_raving said:
Nice man ... Will be giving this a shot. Do you have a bug tracker set up or do you want logs and reports posted here?
Click to expand...
Click to collapse
Feel free to post logs / bugs here. Mainly have time to build after work on weekdays. On the weekends is when I can actually work on fixing things.
For device specific things just post the bugs / logs here. For CM specific bugs I would use JIRA and post a link to the bug here. (More helpful/useful to the CM team to make an actual JIRA bug report.)

3 WORDS: STABLE AS ****!
thanks for the rom, this will forsure be my daily driver. only little problem is the no service icon (xt1031) but data is working. soft reboot fixes it though!

Can anyone please comment on the speed of this ROM since it is Linaro based? The other 5.1 ROMs on my phone are pretty responsive, but if even more speed can be gained with our limited hardware, that will be great.

@CodyF86,
Having a problem with the download link. Rom starts downloading but does not download the whole 251mb. Only partial download. Tried about ten times but still same result. Tried with a different browser but same result.
Edit: Nevermind. Downloaded the rom from my phone and copied it from download folder on phone to internal storage.

Hello there @CodyF86 ! Thanks for you work! One little request. Do you think you will be able to add a mirror or upload your work to another claudbased storage? Like MEGA or Mediafire or AndroidFileHost or whichever you want. This one you are using is insanely unstable for me. It gets interrupted every 5 minutes. I'll be really glad if you could change it or add other(s).
Cheers.

I'll upload to Google drive starting tonight also. Driving home from work, will do another one.

CodyF86 said:
I'll upload to Google drive starting tonight also. Driving home from work, will do another one.
Click to expand...
Click to collapse
Thank you very much! And sorry for bothering you with this. I really want to test your ROM since al Linaro builds seem gone from this forum. Thanks again. Drive safe
Cheers.

New build posted. Main link is to Google drive now.
Some more ARM assembly fun if you look under the kernel source commits.
Will fix the signal indicator so you don't have to do a soft reboot for it to work this weekend. Need to go through the soak test build.prop and compare a few other things...just need time this weekend.

CodyF86 said:
New build posted. Main link is to Google drive now.
Some more ARM assembly fun if you look under the kernel source commits.
Will fix the signal indicator so you don't have to do a soft reboot for it to work this weekend. Need to go through the soak test build.prop and compare a few other things...just need time this weekend.
Click to expand...
Click to collapse
thanks for both: new link and new build Can I dirty flash it over the build before? Just installed the first release lol
Cheers.

I've been dirty flashing; should be good to go.

Update: yes, this ROM is very fast indeed! Thanks for sharing.

This ROM is very fast! Especially for a CM ROM (which in my experience have gotten horribly slow over the last few versions) I haven't experienced nearly as many redraws, stutters, freezes or any other general unpleasantness. Good job @CodyF86

starkly_raving said:
This ROM is very fast! Especially for a CM ROM (which in my experience have gotten horribly slow over the last few versions) I haven't experienced nearly as many redraws, stutters, freezes or any other general unpleasantness. Good job @CodyF86
Click to expand...
Click to collapse
Same here. great work! Not as many customizable like other 5.1 based out there, but is enough fast and stable. Thanks.

just wondering what recovery you are using and do partitions need changed from stock?

What models are supported?

@CodyF86
thanks for your work!
I've a strange bug on last cm...every time i reboot time and data change and the year switch to 2025. I've read its time_daemon related bug...can you control? I've this issue with last cm12 builds

Shawnsch said:
just wondering what recovery you are using and do partitions need changed from stock?
Click to expand...
Click to collapse
CWM 6.0.5.1 I think 6.0.4.7 is the last one posted on CMs website, I'll post the latest one in the OP tonight, but they're basically the same. Nothing needs to be changed from stock.
Orjakone said:
What models are supported?
Click to expand...
Click to collapse
Theoretically they all should work, but I need someone to the GSM version to try it out.
The_Poison said:
@CodyF86
thanks for your work!
I've a strange bug on last cm...every time i reboot time and data change and the year switch to 2025. I've read its time_daemon related bug...can you control? I've this issue with last cm12 builds
Click to expand...
Click to collapse
Weird, I haven't noticed that, but tbh I haven't actually payed attention to what year my phone shows / I don't even have it set up to show me I'll have to look and see if mine does it also.
Will do another one tonight / it's the weekend can play around with it get some things done now.

[KERNEL] [MTD] [TW/CM9/CM11] [DEV] Watson Kernel (MTD support on Gingerbread!)

Hello guys,
This is a project I was working on for a kernel for our SGY.
I made it with a few things in mind:
>Improve it's performance
>Be universally compatible (after I nearly given up on trying to get a snappier CM11 and after the need for a snappier SGY, I decided to go back to GB. However, BML is terrible, and it is annoying to come back to. I decided to build a MTD kernel for Gingerbread then, and it works!)
>Experiment and upgrade as much as I can (thanks @robcore!!!!)
But since I lost my device, I cannot continue developing it. I am then releasing the source code (sorry, no flashable stuff, I deleted it long ago ) for any of you to continue(?) my work if your heart so desires.
If I ever get myself another SGY (or another BCM21553 device), I will gladly continue development (and support whoever does it too), but before I lose all my data and the kernel code alongside it, I am making it available.
This kernel features:
-OC up to 1040MHz (It's questionable even today if the bcm21553 OCs really work, but I tried hacking a way that works very similarly to MarocOS's one, maybe even better. Be warned though, the source around it is messy)
-GPU hacks for performance (Again, even I don't know if they do work, probably the values are just there to be seen, I'm not sure. I do know though that increasing the CPU speed will much likely increase the speed of V3D too)
-DVFS disabled (I found out DVFS is mostly the culpirit in the "832MHz crisis" where the kernel would forcefully scale itself to 832MHz, so I eliminated any reference to it in kernel code. Apparently DVFS on the processor is only available under the bcm21553 governor, but it is present on the other drivers as well. The idea for disabling DVFS came from my friend @robcore)
-A few additional governors and a buggy interactive governor (which is the default xd)
-MTD support for Gingerbread (Thanks Samsung Epic 4G! Although it only works on TouchWiz (I tried it with SL v2 and v2.1 and it works, but under NougatME(CM7) I got no success and loads of segfaults), it works ALMOST perfectly. See bugs for details )
-Some scraped source code from Samsung's FSR I found on the internet (barely compilable, though)
Bugs:
>Gingerbread version:
-IMEI won't appear in the Status screen, I also faced problems with non-working radio for calls. Data works just fine, but calling and receiving calls is unavailable. I believe it is EFS-related. My suggestion is backing up the EFS partition's file structure, then converting it to MTD, then restoring the backup.
-TWRP will crash and panic when exiting, a workaround is force rebooting
>ICS version:
-TWRP will crash and panic when exiting (I believe fixing it here will fix the bug above too)
>KitKat version:
-Flashing images fail randomly, you may also be unable to reboot normally if you do so. I tried addressing this but I couldn't get anywhere.
DOWNLOAD THE SOURCE: Here!
Thanks to:
 @robcore - his development on the Snapdragon S4 breathes life on my dev soul!
 @zman0900 - I saw his thread on an MTD TW kernel for the Samsung Epic 4G, which led me to believe MTD on GB is possible.

nice kernel
It sound nice. I'm a newbie developer, I'm building a kernel to fix audio bug on cm9, hope it work. And thank you for the source

vdhero said:
It sound nice. I'm a newbie developer, I'm building a kernel to fix audio bug on cm9, hope it work. And thank you for the source
Click to expand...
Click to collapse
Have you gathered enough info on it? I would like to fix it too, but I couldn't get any info on whether if the audio bug is a kernel-side issue or an OS -side issue.
Best of luck for you

Building and fixing
sonickles9 said:
Have you gathered enough info on it? I would like to fix it too, but I couldn't get any info on whether if the audio bug is a kernel-side issue or an OS -side issue.
Best of luck for you
Click to expand...
Click to collapse
I don't sure so I decided to build a kernel from your source and another cm9 version from Mohamad.Afaneh's source and I'll merge the audio on both of them for the best think to fix the bug.Thank you .

Link for kernel?
(img files...)(stock/cm9/cm11)

TheRealModder said:
Link for kernel?
(img files...)(stock/cm9/cm11)
Click to expand...
Click to collapse
Compile one for yourself,man. It only takes like 15-25 mins

vdhero said:
Compile one for yourself,man. It only takes like 15-25 mins
Click to expand...
Click to collapse
I don't know how to compile....

TheRealModder said:
I don't know how to compile....
Click to expand...
Click to collapse
He wrote a script already, just add your toolchain and run the script. There's a guide in the readme

vdhero said:
He wrote a script already, just add your toolchain and run the script. There's a guide in the readme
Click to expand...
Click to collapse
Ok. The watson-kernel-bcm21553-src is used with other files?
Because i want to make cm9 mohhamad afaneh optimized version

TheRealModder said:
Ok. The watson-kernel-bcm21553-src is used with other files?
Because i want to make cm9 mohhamad afaneh optimized version
Click to expand...
Click to collapse
To make it, you have to sync the cm9 source code then add the files from his github to your localmanifest. This thing is not in anyway related to that except the MTD. This one is a kernel-compile only source

Oh man, i give up. I can't build a kernel from source, but i can modify a kernel.
Can someone give me the zimage for ics Please....
Sent from my Zenfone 2 Laser using XDA Labs

TheRealModder said:
Oh man, i give up. I can't build a kernel from source, but i can modify a kernel.
Can someone give me the zimage for ics Please....
Click to expand...
Click to collapse
zlimage? We don't have that here, we only have boot.img for kernel

vdhero said:
zlimage? We don't have that here, we only have boot.img for kernel
Click to expand...
Click to collapse
Or you can give me the extracted boot.img files. (ICS/KK)
I will rebuild it using dsixda's android kitchen.
Sent from my Zenfone 2 Laser using XDA Labs

TheRealModder said:
Or you can give me the extracted boot.img files. (ICS/KK)
I will rebuild it using dsixda's android kitchen.
Sent from my Zenfone 2 Laser using XDA Labs
Click to expand...
Click to collapse
Sorry but I can't because I'm bored of making ROMs so I switched back to Windows. I'm planning on making a ROM, I'll compile the kernel for you once I get linux installed

vdhero said:
Sorry but I can't because I'm bored of making ROMs so I switched back to Windows. I'm planning on making a ROM, I'll compile the kernel for you once I get linux installed
Click to expand...
Click to collapse
Ok. If you want to install linux i recommend using ubuntu or linux mint.
Ubuntu official website:https://www.ubuntu.com/
Linux mint official website:https://linuxmint.com/
Sent from my Zenfone 2 Laser using XDA Labs

VDHERO Please But a New Galaxy t Gt-S5360 and start the Development!
vdhero said:
To make it, you have to sync the cm9 source code then add the files from his github to your localmanifest. This thing is not in anyway related to that except the MTD. This one is a kernel-compile only source
Click to expand...
Click to collapse
VDHERO Please But a New Galaxy t Gt-S5360 and start the Development!

Assabtigle said:
VDHERO Please But a New Galaxy t Gt-S5360 and start the Development!
Click to expand...
Click to collapse
Sorry but I can't since my sgy is dead for a long time ago. I'll try to make one if I can find one. I've heard that there are some places that sell sgy for about 5 bucks, i'll find one ì possible

Be fast bro!!
vdhero said:
Sorry but I can't since my sgy is dead for a long time ago. I'll try to make one if I can find one. I've heard that there are some places that sell sgy for about 5 bucks, i'll find one ì possible
Click to expand...
Click to collapse
BE fast BRO Love U and Your WORK!!
All Your DEVELOPMENT are Faster than The ORIGINAL one Please Buy a NEW one!
and Yeah install the Stock Rom in your Phone by ODIN it will be fine!:laugh:

[GUIDE] How to get DTS Eagle on non-supported kernels

The DTS Port has been released publicly is available from the following link:
https://forum.xda-developers.com/android/software/port-dtsx-ultra-dts-headphonex-t3896233
There are kernel patches still necessary (for both ports) and the new guide is here:
https://gitlab.com/dts_project/intro/blob/master/README.md
​

Used msm8998 for sdm660. Seems to be working fine so far. Thanks.

How to get it?
How to install on SD821?
Oneplus3T?

Actually we haven't released the kernel and stuff, yet. I'm working with those guys on it and we have a first beta Kernel running on my device, which is also a OP 3t. By now, it will be just for OxygenOS Oreo.

Gauravlonkar said:
How to get it?
How to install on SD821?
Oneplus3T?
Click to expand...
Click to collapse
OP3/T is MSM8996. Just pick the commits into your kernel source.

We are actually changing some stuff to get this fully running. We have already one kernel DTS eagle is fully working. Hopefully more devs will implement the driver.

Thanks for posting and porting this!
I know you guys are still working on fleshing out the commits for this, but as-is on the OP3 I needed to make a change in order for it actually compile the new dts_eagle_drv.o module and work:
https://github.com/holyangel/OP3/commit/c8b84a701fdcf82dc725beaaa40f740b13e84f7a
Basically was missing sourcing the dts_eagle/Kconfig file in drivers/misc/Kconfig, and had to remove the 'depends on CONFIG_SND_SOC_QDSP6V2' as i'm its not seeing that option during build time.
Once that was done it compiles and works great :good:

HolyAngel said:
Thanks for posting and porting this!
I know you guys are still working on fleshing out the commits for this, but as-is on the OP3 I needed to make a change in order for it actually compile the new dts_eagle_drv.o module and work:
https://github.com/holyangel/OP3/commit/c8b84a701fdcf82dc725beaaa40f740b13e84f7a
Basically was missing sourcing the dts_eagle/Kconfig file in drivers/misc/Kconfig, and had to remove the 'depends on CONFIG_SND_SOC_QDSP6V2' as i'm its not seeing that option during build time.
Once that was done it compiles and works great :good:
Click to expand...
Click to collapse
Take a look at the repo. @LazerL0rd force pushed new commits with the fix.

Will this work on SD625??

using this on hima "LineageOS 15.1 Unoffical" and "AICP 13.1 Official". Works great so far!

crian said:
Take a look at the repo. @LazerL0rd force pushed new commits with the fix.
Click to expand...
Click to collapse
yep builds now by itself without my commit :good:

HolyAngel said:
Thanks for posting and porting this!
I know you guys are still working on fleshing out the commits for this, but as-is on the OP3 I needed to make a change in order for it actually compile the new dts_eagle_drv.o module and work:
https://github.com/holyangel/OP3/commit/c8b84a701fdcf82dc725beaaa40f740b13e84f7a
Basically was missing sourcing the dts_eagle/Kconfig file in drivers/misc/Kconfig, and had to remove the 'depends on CONFIG_SND_SOC_QDSP6V2' as i'm its not seeing that option during build time.
Once that was done it compiles and works great :good:
Click to expand...
Click to collapse
sound/soc/msm/Kconfig
14:config SND_SOC_QDSP6V2
It's there alright. I fixed the other issues with a force-push btw.

@Claymore1297 @crian @HolyAngel another update has been pushed - I've joined the normal naming and folder placement scheme of the Linux Kernel and therefore have decided to move the Kconfig and dts_eagle folder to under drivers/misc/qdspv2 (well the Kconfig was added to drivers/misc/Kconfig as there is no child Kconfig for this folder)

shanks125 said:
Will this work on SD625??
Click to expand...
Click to collapse
There's no way you will know except you test it yourself. Pick 8996 commits, btw.
Sent from my Redmi Note 4 using XDA Labs

Do we need any application for controlling it?

NATO66613 said:
Do we need any application for controlling it?
Click to expand...
Click to collapse
Need, not really. Should have, yes. The module for that still isn't public yet because it's in beta. Join the ICESOUND group on TG for an show public version.
Kernel stuff works tho.

I'm on Omnidragon, the devs implemented DTS Eagle in kernel. As this an 'always on feature' I was wondering how this works/interferes with mods like v4a or James DSP?

mvn66 said:
I'm on Omnidragon, the devs implemented DTS Eagle in kernel. As this an 'always on feature' I was wondering how this works/interferes with mods like v4a or James DSP?
Click to expand...
Click to collapse
Works fine, it's just an addition to the many audio effects Android has. The kernel stuff is just a backend and allows it to be integrated deeply into the system.

LazerL0rd said:
Need, not really. Should have, yes. The module for that still isn't public yet because it's in beta. Join the ICESOUND group on TG for an show public version.
Kernel stuff works tho.
Click to expand...
Click to collapse
Can't find it can you please send it link

tested and seem working fine with SD435, really interesting sound enhancement.
Thanks