[ROM] AOSP 4.3.1 Stable [DanKang] Slim + optimizations (11/04/13) - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

4.3.1 Stable [DanKang] Slim + optimizations (11/04/13)
I am not responsible for any bricks or issues you might encounter, This ROM is tested and stable and should only be flashed on I747/I747M devices​
As many of you may know Slimbean is one of the most popular ROMs out there and the team has released the last stable until Android 4.4, on top of that our device maintainer is MIA and busy with real life.
I noticed 2 issues in stable 2 that prompted me to take this masterpiece the slim team as created for us and fix them, I take no credit for this the bugged back animation (this made me dizzy) and returning to stock DPI causing the Google services framework to frequently disconnect that made it into stable build 2 are resolved in this ROM, I also ship the ROM with a stock minimal GAPPS package that will allow the apps to be properly updated in the market Everything else is butter I take no credit for this! all the credit goes to the slim team
For a full list of ROM features, see this chart
Other changes I made to make this my personal daily driver build...
-Stock S3 DPI
-Changed default notification sound and ringtone
-CM alarms, notifications and ringtones
-Organized settings (Much cleaner now IMO)
-APK's that aren't required have been removed
-Lockscreen unlock and lock handles are once again default AOSP
-Default AOSP walpaper on boot
-Stock Nexus boot animation
-Official Google Keyboard
-AOSP email included
-Inverted MMS by default - Look at the app settings before posting questions Mark read, etc is all there
-Added clock widget from CM 10.2 (System/app)
-Fixed glitched back animation
-Full GPU rendering (the way it should be)
-No ROM branding, you will not see the words Dan and Kang anywhere on the ROM
-Latest KT Kernel
-MPdecision disabled (This is recommended for KT kernel)
Install Instructions
-Full wipe (Caches, system, etc.)
-Install ROM
-Flash GAPPS provided
-Reboot
-Enable root in developer settings
Q) Root doesn't work! (4.3 only)
A) From a clean build you need to enable root access for Superuser itself. This is different from 4.2.2 in which Superuser by default had root access on a new install. To do this, go toSettings -> Developer options -> Root access. If an app attempts to request root access before Superuser itself has access, it may cause problems with that app in the future where root requests are silently denied.
Instructions to enable root on Android 4.3
Open Settings>about
Tap on the build info 7 times to enable dev settings
open developer settings and enable root (select Apps + adb)
enjoy
WIFI connection problem?
anyone having issues with WIFI should check the region code in Wifi advanced setting (Settings>Wifi>Advanced)
Changelog
Code:
11-04-2013
-Removed music.apk (wasted space)
-Ship with latest KT kernel (will fix wakelocks and greatly improve battery life)
-mpdecision removed (unneeded, use ktoonservative governor in KTweaker)
(if your not using Ktoonservative, remember to check auto hotplug on all NON hotplugging governors)
-Final build
10-30-2013
-Removed Dark UI, if you need this don't update
-Fixed MMS security limit
-Stock CM kernel
-Should be rock solid now ;)
10/28/2013
-Initial release
Credits:
Slim team - Donate to these guys, seriously....
Ktoonsez - A very solid AOSP kernel
CM team
AOKP
XDA Developers
More that I might be forgetting
Downloads:
DanKang 4.3.1 11/04/2013 STABLE
md5: c4512e1e6141cda663b54184301734af
DanKang 4.3.1 1.9 RC 10/20/2013
md5:827b3f18cf1a1b839d863b0f8eedb895
-Older video drivers, may or may not solve random reboots for some devices, do not use a custom kernel past 10/16. some report better Bluetooth so experiment..
GAPPS - use this one
-Slimmed down version of the stock GAPPS, This will allow apps to update properly from the Market
Kernel Source:Here
Donate to ktoonsez here: http://forum.xda-developers.com/donatetome.php?u=4325945
If you like this ROM, Donate to the SLIM team here: http://www.slimroms.net/index.php/donations
I take no credit for this

OK!
Since Slim-Halo has been my driver for awhile, I'll give this one a try. You did a great job on Dandroid.......looking forward to trying this one.
Download in progress.............................:silly:

Been on Dandroid since the last update without a single issue.
Love your work Dan will definitely try this out.

Everyone knows this is gonna be great as always. :thumbup:
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Nice
Up and running.
From Slim Halo, wiped cache, davlik, system..................flashed and everything looks great. Have no use for Halo so I'll see what a difference the new kernel makes!!
Thanks for your work!

great work man. (;
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Looks like I'll be making the switch from DanDroid until the official 4.3 TW update drops. Thanks for your hard work!

tallsilver said:
Up and running.
From Slim Halo, wiped cache, davlik, system..................flashed and everything looks great. Have no use for Halo so I'll see what a difference the new kernel makes!!
Thanks for your work!
Click to expand...
Click to collapse
Leankernel does quite a few things
First of all it's linux 3.4.67 which merged these commits
Code:
commit 3cebd7931a6f3007c3eb53942934772cc3b6ee08
Author: Greg Kroah-Hartman <[email protected]>
Date: Tue Oct 22 09:19:41 2013 +0100
Linux 3.4.67
commit 47bed364d1eed775c358204b9eb7affb0ce64033
Author: Linus Torvalds <[email protected]>
Date: Wed Feb 27 08:36:04 2013 -0800
mm: do not grow the stack vma just because of an overrun on preceding vma
commit 09884964335e85e897876d17783c2ad33cf8a2e0 upstream.
The stack vma is designed to grow automatically (marked with VM_GROWSUP
or VM_GROWSDOWN depending on architecture) when an access is made beyond
the existing boundary. However, particularly if you have not limited
your stack at all ("ulimit -s unlimited"), this can cause the stack to
grow even if the access was really just one past *another* segment.
And that's wrong, especially since we first grow the segment, but then
immediately later enforce the stack guard page on the last page of the
segment. So _despite_ first growing the stack segment as a result of
the access, the kernel will then make the access cause a SIGSEGV anyway!
So do the same logic as the guard page check does, and consider an
access to within one page of the next segment to be a bad access, rather
than growing the stack to abut the next segment.
Reported-and-tested-by: Heiko Carstens <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Cc: Xishi Qiu <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
commit 9a63af54974c73f5723bf9a5c03d195f4d473c20
Author: Cyril Hrubis <[email protected]>
Date: Mon Apr 29 15:08:33 2013 -0700
mm/mmap: check for RLIMIT_AS before unmapping
commit e8420a8ece80b3fe810415ecf061d54ca7fab266 upstream.
Fix a corner case for MAP_FIXED when requested mapping length is larger
than rlimit for virtual memory. In such case any overlapping mappings
are unmapped before we check for the limit and return ENOMEM.
The check is moved before the loop that unmaps overlapping parts of
existing mappings. When we are about to hit the limit (currently mapped
pages + len > limit) we scan for overlapping pages and check again
accounting for them.
This fixes situation when userspace program expects that the previous
mappings are preserved after the mmap() syscall has returned with error.
(POSIX clearly states that successfull mapping shall replace any
previous mappings.)
This corner case was found and can be tested with LTP testcase:
testcases/open_posix_testsuite/conformance/interfaces/mmap/24-2.c
In this case the mmap, which is clearly over current limit, unmaps
dynamic libraries and the testcase segfaults right after returning into
userspace.
I've also looked at the second instance of the unmapping loop in the
do_brk(). The do_brk() is called from brk() syscall and from vm_brk().
The brk() syscall checks for overlapping mappings and bails out when
there are any (so it can't be triggered from the brk syscall). The
vm_brk() is called only from binmft handlers so it shouldn't be
triggered unless binmft handler created overlapping mappings.
Signed-off-by: Cyril Hrubis <[email protected]>
Reviewed-by: Mel Gorman <[email protected]>
Reviewed-by: Wanpeng Li <[email protected]>
Signed-off-by: Andrew Morton <a[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Cc: Xishi Qiu <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
commit 27eea92a6552a4163e17175511791f1951ffc8e9
Author: wojciech kapuscinski <[email protected]>
Date: Tue Oct 1 19:54:33 2013 -0400
drm/radeon: fix hw contexts for SUMO2 asics
commit 50b8f5aec04ebec7dbdf2adb17220b9148c99e63 upstream.
They have 4 rather than 8.
Fixes:
https://bugs.freedesktop.org/show_bug.cgi?id=63599
Signed-off-by: wojciech kapuscinski <[email protected]>
Signed-off-by: Alex Deucher <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
commit d3c113cbc827fcd0d4b4cf7a4ad7a6954e16a9ed
Author: Dan Carpenter <[email protected]>
Date: Fri Aug 23 11:40:59 2013 +0300
watchdog: ts72xx_wdt: locking bug in ioctl
commit 8612ed0d97abcf1c016d34755b7cf2060de71963 upstream.
Calling the WDIOC_GETSTATUS & WDIOC_GETBOOTSTATUS and twice will cause a
interruptible deadlock.
Signed-off-by: Dan Carpenter <[email protected]>
Reviewed-by: Guenter Roeck <[email protected]>
Signed-off-by: Wim Van Sebroeck <[email protected]>
Cc: Jonghwan Choi <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
commit 8958138db8b16cca3c2fa1516fb9a800d1c0b6fb
Author: Helge Deller <[email protected]>
Date: Tue Oct 1 21:54:46 2013 +0200
parisc: fix interruption handler to respect pagefault_disable()
commit 59b33f148cc08fb33cbe823fca1e34f7f023765e upstream.
Running an "echo t > /proc/sysrq-trigger" crashes the parisc kernel. The
problem is, that in print_worker_info() we try to read the workqueue info via
the probe_kernel_read() functions which use pagefault_disable() to avoid
crashes like this:
probe_kernel_read(&pwq, &worker->current_pwq, sizeof(pwq));
probe_kernel_read(&wq, &pwq->wq, sizeof(wq));
probe_kernel_read(name, wq->name, sizeof(name) - 1);
The problem here is, that the first probe_kernel_read(&pwq) might return zero
in pwq and as such the following probe_kernel_reads() try to access contents of
the page zero which is read protected and generate a kernel segfault.
With this patch we fix the interruption handler to call parisc_terminate()
directly only if pagefault_disable() was not called (in which case
preempt_count()==0). Otherwise we hand over to the pagefault handler which
will try to look up the faulting address in the fixup tables.
Signed-off-by: Helge Deller <[email protected]>
Signed-off-by: John David Anglin <[email protected]>
Signed-off-by: Helge Deller <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
commit 2eec4f8e8f10e97104649c0a8fa0fbf6f3f51792
Author: Paul Mackerras <[email protected]>
Date: Sat Sep 21 09:53:28 2013 +1000
KVM: PPC: Book3S HV: Fix typo in saving DSCR
commit cfc860253abd73e1681696c08ea268d33285a2c4 upstream.
This fixes a typo in the code that saves the guest DSCR (Data Stream
Control Register) into the kvm_vcpu_arch struct on guest exit. The
effect of the typo was that the DSCR value was saved in the wrong place,
so changes to the DSCR by the guest didn't persist across guest exit
and entry, and some host kernel memory got corrupted.
Signed-off-by: Paul Mackerras <[email protected]>
Acked-by: Alexander Graf <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
commit 85005d18bddd858908230089476d64fc8ecb47aa
Author: Dave Jones <[email protected]>
Date: Thu Oct 10 20:05:35 2013 -0400
ext4: fix memory leak in xattr
commit 6e4ea8e33b2057b85d75175dd89b93f5e26de3bc upstream.
If we take the 2nd retry path in ext4_expand_extra_isize_ea, we
potentionally return from the function without having freed these
allocations. If we don't do the return, we over-write the previous
allocation pointers, so we leak either way.
Spotted with Coverity.
[ Fixed by tytso to set is and bs to NULL after freeing these
pointers, in case in the retry loop we later end up triggering an
error causing a jump to cleanup, at which point we could have a double
free bug. -- Ted ]
Signed-off-by: Dave Jones <[email protected]>
Signed-off-by: "Theodore Ts'o" <[email protected]>
Reviewed-by: Eric Sandeen <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
commit 5187f535beeb3731677c6f6d05402f9adec6e034
Author: Linus Torvalds <[email protected]>
Date: Mon Sep 30 08:35:10 2013 -0700
vfs: allow O_PATH file descriptors for fstatfs()
commit 9d05746e7b16d8565dddbe3200faa1e669d23bbf upstream.
Olga reported that file descriptors opened with O_PATH do not work with
fstatfs(), found during further development of ksh93's thread support.
There is no reason to not allow O_PATH file descriptors here (fstatfs is
very much a path operation), so use "fdget_raw()". See commit
55815f70147d ("vfs: make O_PATH file descriptors usable for 'fstat()'")
for a very similar issue reported for fstat() by the same team.
Reported-and-tested-by: ольга крыжановская <[email protected]>
Acked-by: Al Viro <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
commit c2f271001295e9d4b1cca3a01502795e4f0d1639
Author: Theodore Ts'o <[email protected]>
Date: Tue Sep 10 10:52:35 2013 -0400
random: run random_int_secret_init() run after all late_initcalls
commit 47d06e532e95b71c0db3839ebdef3fe8812fca2c upstream.
The some platforms (e.g., ARM) initializes their clocks as
late_initcalls for some unknown reason. So make sure
random_int_secret_init() is run after all of the late_initcalls are
run.
Signed-off-by: "Theodore Ts'o" <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
commit dad61bad4267b922a9386d9772f80fbac496c05e
Author: Takashi Iwai <[email protected]>
Date: Tue Oct 8 19:57:50 2013 +0200
ALSA: hda - Add fixup for ASUS N56VZ
commit c6cc3d58b4042f5cadae653ff8d3df26af1a0169 upstream.
ASUS N56VZ needs a fixup for the bass speaker pin, which was already
provided via model=asus-mode4.
Bugzilla: https://bugzilla.novell.com/show_bug.cgi?id=841645
Signed-off-by: Takashi Iwai <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
commit 863b6d816a79d03eb39d1fac938d624cc61bf9a0
Author: Daniel Mack <[email protected]>
Date: Wed Oct 2 17:49:50 2013 +0200
ALSA: snd-usb-usx2y: remove bogus frame checks
commit a9d14bc0b188a822e42787d01e56c06fe9750162 upstream.
The frame check in i_usX2Y_urb_complete() and
i_usX2Y_usbpcm_urb_complete() is bogus and produces false positives as
described in this LAU thread:
http://linuxaudio.org/mailarchive/lau/2013/5/20/200177
This patch removes the check code entirely.
Cc: [email protected]
Reported-by: Dr Nicholas J Bailey <[email protected]>
Suggested-by: Takashi Iwai <[email protected]>
Signed-off-by: Daniel Mack <[email protected]>
Signed-off-by: Takashi Iwai <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
The kernel also ships with InteractiveX modified and tweaked for the S3, This governor is basically interactive but it limits the CPU to 860mhz while the screen is off, it sips battery and is a very underrated kernel.
there's more features but I honestly recommend sticking with stock as it sips the battery and doesn't need tweaking

Tempted to switch off stock 4.3 to this. Just not sure if I should use my nandroid I made from your dandroid or try just flashing it off this?

talkingmonkeys said:
Tempted to switch off stock 4.3 to this. Just not sure if I should use my nandroid I made from your dandroid or try just flashing it off this?
Click to expand...
Click to collapse
just full wipe and flash not sure if the boot loader will affect you though

Danvdh said:
just full wipe and flash not sure if the boot loader will affect you though
Click to expand...
Click to collapse
Awesome and I just grabbed the old bootloader from newmans post in case.
http://forum.xda-developers.com/showpost.php?p=46899102&postcount=373
Testing now to see how it handles the MJ2 bootloader

Screenshots? Please

AlexGardunio said:
Screenshots? Please
Click to expand...
Click to collapse
Stock AOSP. no fancy stuff just pure vanilla android. Settings menu is organized, no fancy names or clutter

Danvdh said:
Stock AOSP. no fancy stuff just pure vanilla android. Settings menu is organized, no fancy names or clutter
Click to expand...
Click to collapse
Thanks Dan. Any bugs as far? I should just install rom and gapps? The kernel link is just for info?

AlexGardunio said:
Thanks Dan. Any bugs as far? I should just install rom and gapps? The kernel link is just for info?
Click to expand...
Click to collapse
Thats the source code Just the ROM and GAPPS
I would not have released a stable if it was buggy This ROM is very smooth and should serve many you a Daily Driver a select few and myself have been using these builds for 5 weeks or so

Danvdh said:
Thats the source code Just the ROM and GAPPS
I would not have released a stable if it was buggy This ROM is very smooth and should serve many you a Daily Driver a select few and myself have been using these builds for 5 weeks or so
Click to expand...
Click to collapse
I ain't wanted to sound rude mate sorry. Maybe silly question hehe. No risks if I want to go back to my nandroid? Btw... I've to say your work is very nice!

Running perfect with no issues coming from MJ2 and the new bootloaders are working fine on here for me with att. Mobile data works and I'm experiencing no bugs. Just want to be sure about this superuser note you have in the op. What do I choose when I go into developer settings root? Apps, adb or both? Awesome work too man this ROM is perfect

talkingmonkeys said:
Running perfect with no issues coming from MJ2 and the new bootloaders are working fine on here for me with att. Mobile data works and I'm experiencing no bugs. Just want to be sure about this superuser note you have in the op. What do I choose when I go into developer settings root? Apps, adb or both? Awesome work too man this ROM is perfect
Click to expand...
Click to collapse
just enable both
Instructions to enable root on Android 4.3
Open Settings>about
Tap on the build info 7 times to enable dev settings
open developer settings and enable root (select Apps + adb)
enjoy

Can this be dirty flashed if coming from most current version of Slimbean?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

sbs8331 said:
Can this be dirty flashed if coming from most current version of Slimbean?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Worked with SlimHalo!

Related

[KERNEL][ICS][22.02.2012] Team Eos ROM - kernel collaboration & kernel thread

Hi guys,
in the future I will post the current modified kernel-source for the Team Eos ROM for kernel I'm using on my Xoom (and probably also the current compiled )
edit1:
current kernel-source - which I'm using with nightly #49 right now - is here:
Kernel Source:
tiamat-kernel-mod on github
update:
latest branch is at:
ics_tiamat_mod07
Installation:
either compile the kernel via ./xoom.sh and then flash the zip-package in release/Xoom
or
flash the attached compiled kernel in this post (which I'm currently using)
md5sum: ce0fdf52a8b0e28b6028a0e9cbd3f834 release/Xoom/ICS_20120222_Platypus_for_Xoom_r6.zip
Characteristics:
- hardfloat floating point (up to 40% more performance) + VFP-optimized flags
- cgroups timer slack to group together similar tasks to improve (lessen) cpu load [and potentially improve battery runtime]
- ck-patchset (by Con Kolivas): more efficient memory management & preparation for improved swap handling
- mmc/microSD card increased write timeout: fix against data loss when writing to slow cards
- quiet binder: (might not be a problem on this kernel but just in case)
- mmc: core: Claim host while freeing card: fix a BUG_ON while removing the sdcard
- pmem: fix buddy free memory corruption bug
- LOAD_FREQ (4*HZ+61) to avoid loadavg Moire
- more tighter CFS (cpu scheduler) timings: more smoothness and less delay / lags
- conservative governor tweak: to make it a min/max governor
- unlikely-likely cleanups & optimizations: less false branch-prediction
- vmscan: move referenced VM_EXEC pages to active list
- enable advanced congestion control (for network) & set YeAH TCP to be the default
- a few filesystem/inode integrity improvements
- improved memcpy & memmove
- nohz/sched: delay going tickless when CPU is loaded should in total cut down power consumption e.g. while MP3 playback
- FuguMod network security enhancements (thx to nikademus !)
- add nofail variants of kmalloc kcalloc kzalloc for the filesystems
- BFQ i/o scheduler v3-r2 for 2.6.39
- to be built with Linaro 4.5 toolchain
- graphite + other optimization flags [testing & need feedback - battery, performance, stability, etc.]
- kernel compiled with stack-smashing protector support
- UACCESS_WITH_MEMCPY disabled (higher latency)
- syncookies enabled
- (access to) DEVMEM & DEVKMEM disabled
- paranoidly initialize SD
- make kernel panic & reboot during hardlock
- debug memory during bootup (once)
- add some crypto algorithms
- add support for unaligned accesses (more performance)
- improved sha1-implementation
- smartass V2 governor (for testing)
- remove the generic_file_aio_read() plug [should improve performance & fix a regression - not sure if it plays that much of a role on the Xoom]
update:
some more stuff got added (among those: tailored CFLAGS to the tegra2 architecture/processor) - will add those here in the list later
Kudos:
Bigrushdog
Coolbho3000
Solarnz
Kcrudup
Cybertronic
Steady Hawkin
TDR
Bazar6
and all the other kernel devs out there
DISCLAIMER: the kernel (binary) and driver modules are provided as is. If problems occcur they most probably are from upstream and can be fixed with the newest version. Since I'm doing this in my free spare time as a hobby (quenching my thirst for tweaks & performance) updates will occur irregularly as time permits and I see fit (most probably when new features & bugfixes arrive). YOU are responsible for the actions that you take (such as over- or underclocking), etc. You agree that I can not be held liable for any potential damage that arises from your actions in combination with or the usage of this kernel and other related parts.
edit0:
a few questions for the start:
- anyone attempted & was crazy enough to test grsecurity stuff on their kernel ?
- until now I only flashed the kernel via fastboot flash:raw and by linking to the initramfs - how to build the gzipped cpio file into the kernel ?
--> adding it to CONFIG_INITRAMFS_SOURCE="" ?
Looking forward to improving the Xoom experience !
Thanks !
Xoom Xoom
Hey I Post little question... Hope you could help me ?
http://forum.xda-developers.com/showpost.php?p=22127704&postcount=463
Thanks a lot!
tb-killa said:
Hey I Post little question... Hope you could help me ?
http://forum.xda-developers.com/showpost.php?p=22127704&postcount=463
Thanks a lot!
Click to expand...
Click to collapse
*) nope the whole repo is cloned, not sure if there's on option only to clone ics branch
*) you need an ARM toolchain to compile it (e.g. https://android-build.linaro.org/ , use 4.5 toolchain for this; https://android-build.linaro.org/builds/~linaro-android/toolchain-4.5-2011.10/)
*) it naturally should be make stingray_defconfig - but better get the config from the running kernel on your Xoom zcat /proc/config.gz and place it in arm/arm/configs/tingray_defconfig then attempt to build
hope that helps
I'm currently still looking for SLQB and classic rcu or another more light-weight RCU implementation for the 2.6.39 kernel for SMP
there exists Tiny preemptible RCU but this only for UP (uniprocessor) so doesn't apply
any ideas ?
Ok ok I'll talk with Solarnz and see if we can post something soon. There's been ALOT of config80211 coming from upstream. When we publish it'll be a doozie
And ill publish a version for the module fans out there
ok, got some time to test the BFS scheduler which might have or not have improved battery runtime
but definitely might have improved smoothness (e.g. on the galaxy s it does)
unfortunately it doesn't play nice with the android kernel (such as the same problem occured with the kernel 2.6.35-based kernel on the gt-i9000/galaxys s and only really started to work more or less properly after it got ported to 3.0-kernel)
so there must be another way to improve smoothness ...
zacharias.maladroit said:
*) nope the whole repo is cloned, not sure if there's on option only to clone ics branch
*) you need an ARM toolchain to compile it (e.g. https://android-build.linaro.org/ , use 4.5 toolchain for this; https://android-build.linaro.org/builds/~linaro-android/toolchain-4.5-2011.10/)
*) it naturally should be make stingray_defconfig - but better get the config from the running kernel on your Xoom zcat /proc/config.gz and place it in arm/arm/configs/tingray_defconfig then attempt to build
hope that helps
I'm currently still looking for SLQB and classic rcu or another more light-weight RCU implementation for the 2.6.39 kernel for SMP
there exists Tiny preemptible RCU but this only for UP (uniprocessor) so doesn't apply
any ideas ?
Click to expand...
Click to collapse
Thanks man you made my day !!
Now i got kernel compiled but have the same problem like you without insert initramfs file ... did you fixed these problem ?
Does you could check out if we could combine xoom kernel with V4L Stuff ??
Great would be the chance to get also UVC integrated !!
tb-killa said:
Thanks man you made my day !!
Now i got kernel compiled but have the same problem like you without insert initramfs file ... did you fixed these problem ?
Does you could check out if we could combine xoom kernel with V4L Stuff ??
Great would be the chance to get also UVC integrated !!
Click to expand...
Click to collapse
like bighrushdog or solarnz already answered:
the initramfs is preserved while flashing the kernel via cwm
you can however also extract the initramfs and flash it via fastboot (that's what I usually do)
to be honest I'm currently trying to keep the footprint of kernel development as low as possible for me & I'm rather uninterested in that camera stuff right now
sorry
edit:
@all that are interested:
please give the latest kernel a try and tell what you like or don't like about it (e.g. governors, etc.)
when it works well I'll issue an pull-request to get it "upstream" into the tiamat kernel
the current kernel (ICS_20120222_Platypus_for_Xoom_r6.zip) has been tested on Team Eos nightly #70
Thanks !
Flashed! I hope in a no drain battery. Native gov is Ondemand (where's SmartAssv2?) let's test it and wait few days
EDIT : mmmmmhhhh it seems like CPU doesn't sleep. Keep testing
Sent from my Xoom on EOS ICS Everest
Support USB Mass Storage ?
like rogue kernel support fat-32?
zacharias.maladroit said:
like bighrushdog or solarnz already answered:
the initramfs is preserved while flashing the kernel via cwm
you can however also extract the initramfs and flash it via fastboot (that's what I usually do)
to be honest I'm currently trying to keep the footprint of kernel development as low as possible for me & I'm rather uninterested in that camera stuff right now
sorry
edit:
@all that are interested:
please give the latest kernel a try and tell what you like or don't like about it (e.g. governors, etc.)
when it works well I'll issue an pull-request to get it "upstream" into the tiamat kernel
the current kernel (ICS_20120222_Platypus_for_Xoom_r6.zip) has been tested on Team Eos nightly #70
Thanks !
Click to expand...
Click to collapse
As you know, the modules are the easy part. Implementation is a nightmare and not high on the priority list. However, I've spent the last few days tearing bcmdhd and wpa_supp apart looking for the final piece of the adhoc puzzle. I have alot of info. If you're interested we can open a discussion. Cause its kicking my ass atm
I figured out the adhoc problem but i'm not sure just how to fix it yet. See my post in the EOS rom threads. Also, i merged your mod8 branch with my ics_drivers branch. I'm gonna build and flash. I bet it kicks serious ass!

[ROM][Unofficial] Synergy's CyanogenMod 13.0 for Jflte GSM/CDMA - Build May 15, 2016

Introduction
This is a my own modified CyanogenMod ROM for the Galaxy S4 jflte devices built with UBER Toolchains, globally applied compiler optimization flags and other cherry-picks from around XDA, Github, or Gerrit. The ROM is only filled with what I feel helps performance and battery life, so the commits are constantly changing and it's not tied down to one toolchain or optimization. Building these ROMs is a fun hobby of mine that I want to share with everyone on XDA.
DISCLAIMER: I am not responsible for any damages to your device, always have a nandroid on hand if anything happens.
​
Features
ROM:
Using the CyanogenMod 13 Nightly base
Built with the UBER GCC 4.9.x Toolchain
Compiled with optimized compiler flags by @Arter97
Add ability to hide SU icon in statusbar, off by default (Settings > Status Bar)
Add switch to enable full-screen recents (Settings > Developers Options)
Added Quick Unlock for PIN Lockscreens
Tweaked Ambient Display schedule
Display the current app being optimized during boot
Smoother Upload/Download status bar animation
Improve scrolling and scrolling cache
Sped up framework animations slightly
Update stock audio to the Nexus 5 factory image audio
Added SuperSU to Settings menu, if installed
Developer Options should be enabled by default
Allow MultiWindow option to be shown in userdebug builds
Slightly tweaked ART and bionic repos thanks to @Arter97
Updated jemalloc and SQLite repos thanks to @Arter97
AdAway v3.1 included
Marshmallow bootanimation included from here
Added default Nexus 6P wallpaper, removed default live wallpapers
Kernel:
Updated to the linux 3.4.110 kernel base
Built with UBER GCC 5.2.x Toolchain
Intelli-plug Hotplug, MPDecision disabled
Intelli-plug
Added Sweep2Sleep. Sweep from above the Back button across to above the Menu button to put screen to sleep.
Sensors: Add SM-S975L and SGH-S970G to variants list
Updated Interactive CPU Governor from @Temasek's Hlte kernel
Updated CPU boost driver from @Temasek's Hlte kernel
ROW I/O Scheduler set by default
CPU Voltage Control
Dynamic Fsync toggle (disabled by default)
Power Efficient Workqueues for powersaving
Reduced bcmdhd wakelocks
Modified Ramdisk
Many more various tweaks that can be found here
Supported Devices
Jfltecdma
jfltecri / SCH-R970C
jfltecsp / SCH-R970X
jfltespr / SPH-L720
jflteusc / SCH-R970
jfltevzw / SCH-I545
Jfltegsm
jflteatt / SGH-I337
jflteaio / SGH-I337Z
jfltecan / SGH-I337M
jfltetfnatt / SM-S975L
jfltetftmo / SGH-S970G
jfltetmo / SGH-M919
jfltexx / GT-I9505
jgedlte / GT-I9505G
Install Instructions
Nandroid
Fully wipe (If not upgrading from a previous build)
Flash ROM
Flash compatible GApps
Downloads
ROM:
SynergyCM13.0-20160515-jfltegsm-fa4bf8f7ae.zip
SynergyCM13.0-20160515-jfltecdma-dc306c3791.zip
Kernel ((Flash Loki after)):
SynergyCM13-jflte-kernel-20160515-oc.zip
SynergyCM13-jflte-kernel-20160515-stock.zip
Addons:
Boot animation courtesy of @Creeper36:
TWRP Flashable Zip
Bootanimation Preview:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Older ROMs:
SynergyCM13.0-20160410-jfltecdma-6f1b455e78.zip
SynergyCM13.0-20160410-jfltegsm-d39c57752f.zip
SynergyCM13.0-20160316-jfltecdma-654a826fda.zip
SynergyCM13.0-20160316-jfltegsm-06080a981b.zip
SynergyCM13.0-20160228-jfltecdma-fd4ed30bbd.zip
SynergyCM13.0-20160228-jfltegsm-0762a7ad9d.zip
SynergyCM13.0-20160215-jfltecdma-1b370249ab.zip
SynergyCM13.0-20160215-jfltegsm-7f288783d8.zip
SynergyCM13.0-20160207-jfltecdma-34d82243a4.zip
SynergyCM13.0-20160207-jfltegsm-09c5c7032d.zip
SynergyCM13.0-20160111-jfltecdma-9498e12bef.zip
SynergyCM13.0-20160111-jfltegsm-492ebd3066.zip
SynergyCM13.0-20160103-jfltecdma-fix.zip
SynergyCM13.0-20160103-jfltegsm-8f288e8fab.zip
SynergyCM13.0-20151229-jfltecdma-411890214d.zip ((Needs build.prop edits to resolve SIM issues))
SynergyCM13.0-20151229-jfltegsm-2c7ed5db80.zip
SynergyCM13.0-20151224-jfltecdma-af77161288.zip ((Needs build.prop edits to resolve SIM issues))
SynergyCM13.0-20151224-jfltegsm-8c75a5b76c.zip
SynergyCM13.0-20151222-jfltegsm-6813b1cedd.zip
SynergyCM13.0-20151221-jfltegsm-195a8b91d9.zip
SynergyCM13.0-20151216-jfltegsm-8e9074b8f4.zip
SynergyCM13.0-20151213-jfltespr-2a450efe6b.zip
SynergyCM13.0-20151213-jflteusc-c403d96978.zip
SynergyCM13.0-20151213-jfltevzw-1ae903c134.zip
Older Kernels:
SynergyCM13-jflte-kernel-20160410-stock.zip
SynergyCM13-jflte-kernel-20160316.zip
SynergyCM13-jflte-kernel-20160228.zip
SynergyCM13-jflte-kernel-20160215.zip
SynergyCM13-jflte-kernel-20160207.zip
SynergyCM13-jflte-kernel-20160111.zip
SynergyCM13-jflte-kernel-20160103.zip
SynergyCM13-jflte-kernel-20151229.zip
Bugs
Bluetooth audio stream (A2DP) may work in most cases.
Having an incoming call while connected to bluetooth audio devices can lock up your phone. Turn off your bluetooth device immediately to answer the call. Disable Phone Audio on your Bluetooth device to prevent the lock up in the future.
Wifi may lose connection during sleep (For some people)
If LTE may not connect on boot, go to APN settings choose another APN, then switch back to the default one
SuperSU: Read up in this thread about flashing the proper version: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
ROM Overview thanks to @shark jungle
XDA:DevDB Information
Synergy's Unofficial CyanogenMod Builds, ROM for the Samsung Galaxy S 4
Contributors
Synergy510
Source Code: https://github.com/xsynergy510x?tab=repositories
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2015-12-17
Last Updated 2016-05-16
Changelog
Build May 15th
ROM:
Sync up
Kernel:
Sync Up
Perfomance tweaks for snappier UI
Older Changelogs:
Build April 10th
ROM:
Add Jfltespr, jflteusc and jfltevzw variants to Jfltegsm flash barrier
Remove the spinner during App Optimization boot screen, releases CPU resources for faster boot up time.
Reduced minimum screen brightness value.
Updated jemalloc and SQLite repos.
Sync up with CM up until April 10th @ 12 noon PST
Kernel:
Update Interactive tunables.
Switch back to MPDecision as the default hotplug, for better smoothness
Switch to OnDemand GPU gov, for better smoothness
Change to LZO boot.img compression for faster boot up
Sync up with CM up until April 10th @ 12 noon PST
Build March 16th
ROM:
ART: Disable JIT
Ambient Display: Disable doze right after screen off
Enable call recording. Let me know if this works, my SIM isn’t in my S4 anymore
Bluetooth: Sync up with JDCTeam’s AOSP -MM-JF repo
Sync up with CM Up until 3/16 @ 6:00PM PST
Kernel:
USB Fast Charging, it works in Kernel Adiutor, not sure about other kernel editors
Sync up with CM Up until 3/16 @ 6:00PM PST
Build Feb 28th
ROM:
Cherry-picked Bluetooth related fixes from JDCTeam’s AOSP 6.0 ROM. It’s less broken, but still broken.
Sync with CM up until this weekend
Kernel:
Ramdisk: Re-tune Interactive, no longer super power saving and should no longer lag during games/app installation
Reverted Interactive and CPU boost commits
Removed LMK ADJ RBTree
Added jfltetf* variants to the flash barriers
Kernel re-haul. Back to CM13 base and added:
Intelli_plug
Dynamic Fsync (Disabled by default)
Simple GPU Gov (Enabled by default)
FauxSound
Faux123 improvements
Power efficient workqueues
Arter97 improvements
S970 & S975 Sensor compatibility
WiFi improvements
sweep2sleep
GZIP Compression
Sync with CM up until this weekend
Build Feb 15th
ROM:
Re-added Live Wallpapers
Reverted my picked Mobile Data fixes - Caused the No SIM issue
Sync with CM Upstream up until Feb 15 @ 1:00PM PST
Fixes Mobile Data after reboot
Kernel:
Picked commit related to fixing WiFi drop outs - Let me know if this works
Disabled Dynamic Fsync for better performance
Added cpufreq limiter driver - Nothing you guys can change, but something I may be able to use later
Sync with Google’s android-3.4 - Lots of Backports/Upstream security patches and improvements
Sync with CM Upstream up until Feb 15 @ 1:00PM PST
Build Feb 7th
JflteGSM:
Add support for Jfltetfatt, Jfltetfatt, Jflteaio (GSM Crickett)
ROM:
Audio_policy.conf: A2DP Add 48kHz Sampling Rate
Sync with CM Upstream up until Feb 7 @ 7:30AM PST
Kernel:
Tuned Interactive for powersaving, parameters are tuned best for UI scrolling. See here for more info http://forum.xda-developers.com/showthread.php?t=2769899
Disabled Touch/Input boost. If things are too laggy, re-enable this with a Kernel editor
Compressed with GZIP for SuperSU Compatibility
Update Bluetooth and bcmdhd (WiFi) Driver to GPE OH2
Enabled ARCH_POWER
From upstream: Sensors: add S970 & S975
Picked WiFi patches from d2lte
Sync with CM Upstream up until Feb 7 @ 7:30AM PST
Build January 11th
ROM:
Added ART enhancements
Add ability to hide SU icon in statusbar, off by default (Settings > Status Bar)
Add switch to enable full-screen recents (Settings > Developers Options)
Added Quick Unlock for PIN Lockscreens
Merged Auto LED Notifications early, generate LED color based on App’s Icon, but it doesn’t seem to work for me
Lowered some Ambient Display parameters
Attempt to fix data after reboot
Turned off some debugging within the frameworks
Display the current app being optimized during app optimization
Smoother Upload/Download status bar animation
Improve scrolling and scrolling cache
Speed up animations
Update stock audio to the Nexus 5 factory image audio
Added SuperSU to Settings menu, if installed
Developer Options should be enabled by default
Allow MultiWindow to be shown in userdebug builds
Sync up with CM up and until Jan 10 @ 7:00PM PST
Sync with Android 6.0.1_r10
Removed stock Camera in favor of Snap, the Snapdragon Camera
Default to compiling with Clang
They removed Busybox in favor of Toybox, a busybox alternative. This will break your apps that rely on Busybox and haven’t updated with support for Toybox. A great example is Kernel Adiutor, Grarak immediately added support for Toybox.
Kernel:
Added Sweep2Sleep. Sweep from above the Back button across to above the Menu button to put screen to sleep.
Sensors: Add SM-S975L to variants list
Sync up with CM up and until Jan 10 @ 7:00PM PST
Build January 3rd
Jfltecdma
Remove Jfltevzw eri.xml overlay
Set permissions for certain files on flash
Added common CDMA MMS overlay
Firmware link vidc blobs
Common
Sync TCP parameters with upstream
Sync with CM upstream up until Jan 3 @ 5PM PST
Kernel
Revert some WiFi commits that possibly caused some WiFi drain
Disable MPDecision on boot in favor of Intelli-plug
Set intelli-plug on the system-wide power efficient workqueue
Sync with CM upstream up until Jan 3 @ 5PM PST
Build December 29th
Common:
Unify jf variants in the init script, should fix Jfltecdma (Please verify)
Fix for the “invalid number” at the end of calls (Please verify)
Removed some default wallpapers
Added Nexus 6P stock wallpaper
Sync up with CM up until Dec 29th @ 4PM PST
Kernel:
Built with UBER GCC 5.2.x
Sync with Franciscofranco’s hammerhead kernel
Updates to Interactive and cpu-boost
Added Dyanmic Fsync, disabled by default
Westwood TCP sched enabled by default
Different adj rb tree implementation enabled
Sched updates
Voltage control
Ramdisk updates to Interactive and CPU boost values
Various misc updates
Sync up with CM up until Dec 29th @ 4PM PST
​
Build December 24
Jfltecdma:
Add missing jf-common parts, jfltecdma should boot now
Jfltegsm:
Apply GSM RIL properties to all devices. So if you do have a GSM devices, you will get RIL properties added, however if you are not one of the supported devices, you will not receive device specific properties such as: ro.build.fingerprint, ro.build.description, ro.product.model, ro.product.device. This can change if someone with an un-supported GSM model can give me all of these along with the output of “getprop ro.bootloader” in the terminal on their device
ROM:
Sync up with CM up and until Dec 24 @ 11:30AM PST
Kernel:
Remove “optimized low memory killer adj RBTree”, caused memory issues. I've seen lots of memory improvements and less launcher re-draws.
Build December 22
Jfltecdma:
Jfltecdma is still in beta
Change how blobs are unpacked, not being able to boot might be related to not having certain blobs if they're not unpacked.
Common:
Removed boot_* services. No more annoying LEDs and other services that don’t work yet
Sync with CM upstream: They fixed A2DP! (But there are bugs)
Kernel:
Use ROW I/O scheduler, it gives better real world performance than BFQ
Revert NVIDIA power saving commits
Build December 21
Jfltecdma:
Unpack proper blobs per variant
Jfltegsm:
Fix Loki path in updater script, should fix Loki assertion during flash
Build libcnefeatureconfig, supposedly helps with WiFi and Mobile Data handoff. It's found in the CDMA builds, but may not have any effect on GSM
Common:
Cherry-picked possible A2DP fixes, so far hasn't worked for me, may be missing some related commits
Changed Doze schedule, see my commit for more details: https://github.com/xsynergy510x/and...mmit/c91634a0ed29d4d81bcfd262b604f46073e0e4c3
Kernel compressed with GZIP
Sync up with CM upstream up and until Dec 20 @ 2:00PM PST
How To Report Bugs
In order to get your questions answered the fastest, please use these questions as a template in your posts. This reduces the amount of back-and-forth I need to do when trying to give you an answer. This also makes it easier for anyone else to give you an answer.
What build did you flash? Jfltegsm/Jfltecdma.
Which GApps did you use?
Did you flash anything else? (e.g. SuperSU, Viper4Android, Xposed)
What version and variant of TWRP are you using? (e.g. TWRP 2.8.7.0 for jfltetmo, TWRP 2.8.7.0 by Antares)
Did you verify the MD5 sum on the packages you flashed?
Are you able to reproduce the issue?
Is it an issue that not listed in the OP?
Were you able to find this issue on any other CM based ROM?
Please copy and paste this into your replies for the fastest and easiest response.
Hey guys!
Finally got this project off the ground as soon as my first jfltecdma build completed. I advise any CDMA users to try out the variant ROMs found in my cm12.1 thread here: http://forum.xda-developers.com/showpost.php?p=64298864&postcount=1620. This is to ensure thatyou start on something solid before moving onto something experimental. Yes, the CDMA build is untested, so I may be missing something from that build, and I need your help to make it a working build!
Jfltegsm should work fine, I test that personally because I have a jfltetmo variant. I still need someone to verify that jflteatt works, though.
A separate kernel zip will come once I get the time to do that.
Please guys, let me know what you think and I hope you all enjoy!
I will be testing. Brb and gud stuff synergy, you bring light in this dark tunnel.
Microsd exfat working?
Wysłane z mojego SM-G903F przy użyciu Tapatalka
Thank you so much!
Is the SDCard working? Do I need to format the SDcard (backup first, format, copy data back) with this ROM? What are the know issues?
nothing working.. can't flash (did full wipe)
slawrumia said:
Microsd exfat working?
Wysłane z mojego SM-G903F przy użyciu Tapatalka
Click to expand...
Click to collapse
I'm unsure of that, if this is related to the kernel supporting exFat, I can tell you that the kernel hasn't gone through many changes between cm12.1 and cm13.0, so if you have issues in 12.1, you may have issues now.
GoodSoul said:
Is the SDCard working? Do I need to format the SDcard (backup first, format, copy data back) with this ROM? What are the know issues?
Click to expand...
Click to collapse
SD Card works for me, I use the default format (I believe I formatted it through Android a long long time ago). There is a list of bugs in the OP
mbaier said:
nothing working.. can't flash (did full wipe)
Click to expand...
Click to collapse
We need more information than this. Which version did you flash, GSM or CDMA. What GApps did you use? Was there a TWRP error code? Please be more detailed in the future to minimize the amount of back-and-forth on XDA and you get your answer sooner.
Do you have a link for the compatible GApps?
Thanks
Is the Dec. 17 build only for CDMA devices or does it add compatibility for CDMA? In other words are the Dec. 16 and 17 builds the same but for different variants?
gc_geforce said:
Do you have a link for the compatible GApps?
Thanks
Click to expand...
Click to collapse
http://opengapps.org/ Is what I use. Make sure you choose ARM and 6.0. I've only used Mini, the one time I tried Full it gave me an Error code 70. But you can give it a shot too.
mperez19 said:
Is the Dec. 17 build only for CDMA devices or does it add compatibility for CDMA? In other words are the Dec. 16 and 17 builds the same but for different variants?
Click to expand...
Click to collapse
Yes, it is a build for CDMA devices. It's an entire ROM, not a patch.
gc_geforce said:
Do you have a link for the compatible GApps?
Thanks
Click to expand...
Click to collapse
https://wiki.cyanogenmod.org/w/Google_Apps
EDIT: A bit late here..
Nana Ayeh's REVIEW of SYNERGY Marshmallow on JFLTESPR
Awesome Boot Animation
Great Battery life 4 hours+ SOT playing clash of clans on stock battery
ROM is very fast and stable
I personally find it fit for a daily driver
Wifi works just fine
Ability to switch LTE 3G and 2G is awesome!
Keep the good work mate! If you are looking for a tester for subsequent builds, you just found one.
Nana Ayeh said:
Nana Ayeh's REVIEW of SYNERGY Marshmallow on JFLTESPR
Awesome Boot Animation
Great Battery life 4 hours+ SOT playing clash of clans on stock battery
ROM is very fast and stable
I personally find it fit for a daily driver
Wifi works just fine
Ability to switch LTE 3G and 2G is awesome!
Keep the good work mate! If you are looking for a tester for subsequent builds, you just found one.
Click to expand...
Click to collapse
I appreciate the review!
Is this on the jfltespr build or the jfltecdma build? I'm glad the variants work, but I'd like to get people's feedback on the unified builds
Jflteusc would not boot past splash screen with unified build. Had no problem with other build
Turns out I messed up on some blob placement for jfltecdma, and lots of people have downloaded jfltecdma without any feedback and that worries me because you are probably using a different set of blobs not intended for your variant. I'll fix this soon.
In the meantime, could any CDMA users chime in and let me know if they have these files on their phone? This way I know the blob placement worked at the very least. I'll build again with the proper blobs after work
jflteusc/cri/csp:
/system/bin/efsks
/system/bin/ks
/system/bin/qcks
/system/lib/libreference-ril.so
/system/lib/libril.so
/system/lib/libsec-ril.so
/system/vendor/lib/libqmi.so
/system/vendor/lib/libqmiservices.so
jfltespr:
/system/bin/efsks
/system/bin/ks
/system/bin/qcks
/system/lib/libreference-ril.so
/system/lib/libril.so
/system/lib/libsec-ril.so
/system/vendor/lib/libqmi.so
/system/vendor/lib/libqmiservices.so
jfltevzw:
/system/bin/efsks
/system/bin/ks
/system/bin/qcks
/system/lib/libreference-ril.so
/system/lib/libril.so
/system/lib/libsec-ril.so
/system/vendor/lib/libqmi.so
/system/vendor/lib/libqmiservices.so:
/system/etc/firmware/q6.b00
/system/etc/firmware/q6.b01
/system/etc/firmware/q6.b03
/system/etc/firmware/q6.b04
/system/etc/firmware/q6.b05
/system/etc/firmware/q6.b06
/system/etc/firmware/q6.mdt
/system/etc/firmware/vidc.b00
/system/etc/firmware/vidc.b01
/system/etc/firmware/vidc.b02
/system/etc/firmware/vidc.b03
/system/etc/firmware/vidc.mdt
is supersu working for you guys?

[KEXEC] [ARM64] Kexec-Hardboot Patch

Note:
Kernel Developers: I would like to ask you to merge this patch to your kernels, because it is essential part of MultiROM (MR) - it allows MR to boot any kernel without changing the boot partition. I realize that it is no small request, but the patch is not big, touches relatively stable parts of kernel and should not cause any problems outside its intended function.
The Patch:
You'll need to cherry pick a total of 5 commits (if anyone feels like squashing them to help me out, feel free to link me to it).
Cherry-pick against: http://github.com/multirom-nexus6p/android_kernel_huawei_angler.git on the branch 'mm2'.
Commit hashes in order:
2641ac7979c0b4ef7d8c33bae57404fea89ca0de
ff67f9fae243fea2b513b1721c8cff4584f229ba
58154995579253a2ee864b839aa4a9271afdb1c5
fb7e7c6212f59fce48f83235a99c244e2432b1f3
1fb02d265b4170e193018d513de11f9a47e5e775
Related defconfig options, and their explanations:
Code:
CONFIG_KEXEC=y # Enables the Kexec SysCall to allow loading the new 'secondary' kernel into memory
CONFIG_KEXEC_HARDBOOT=y # Enables the HardBoot flag, which allows 'cold-booting' a new kernel
# CONFIG_ATAGS_PROC is not set # Prevents potential atags related discrepancies, this must be either removed or commented out
CONFIG_PROC_DEVICETREE=y # Allows us to read out the kernel config, and tell that the kernel has all the necessary configs enabled (read out from /proc/config.gz)
User-space Kexec binary: here (you'll need to extract the zip, and it will be in 'multirom/kexec')
A quick guide to use Kexec: here
Authors:
- This patch was made by Mike Kasick for Samsung Epic 4G.
- Tassadar built on this patch, and partially rewrote it to support the Nexus 4, 5, and 6.
- Zhuowei Zhang rewrote the patch from scratch for arm64.
- Myself for maintaining MultiROM for the 6P, and managing the patch.
XDA:DevDB Information
[KEXEC] [ARM64] Kexec-Hardboot Patch, Kernel for the Huawei Nexus 6P
Contributors
npjohnson, 500 Internal Server Error
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: Version 1
Stable Release Date: 2016-06-11
Created 2016-06-12
Last Updated 2016-06-12
None of the above links working
The links of commits you have mentioned are not working.
shenoy13 said:
The links of commits you have mentioned are not working.
Click to expand...
Click to collapse
Been a long while, because the related MultiROM project is no longer maintained, but the links now work

[JDCTeam] 🥧 Pixel Experience Pie 🥧 Release 12 [26 Dec][9.0.0_r46][unofficial] [EOL]

[JDCTeam] 🥧 Pixel Experience Pie 🥧 Release 12 [26 Dec][9.0.0_r46][unofficial] [EOL]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Pixel Experience for Galaxy S4 (jflte)
What is this?
Pixel Experience is an AOSP based ROM with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device
Based on Android 9.0
DON'T FLASH GAPPS AS ALREADY INCLUDED
Download from AndroidFileHost
JDC Team Aroma addon - here
Translation
Help with project translation
Telegram channel
Stay tuned​
SUPPORTED DEVICES
All following Galaxy S4 variants with Qualcomm Snapdragon 600 are supported:
GT-i9505 - jfltexx
GT-i9507 - jtfddxx
GT-i9508 - jfltezm
SCH-i545 - jfltevzw
SCH-r970 - jflteusc
SGH-l337 - jflteatt
SGH-l337m - jfltecan
SGH-l337z - jfltecri
SGH-m919 - jfltetmo
SGH-s970g - TracFone / Straight talk
SM-s975l - TracFone / Straight talk
SPH-l720 - jfltespr
SPH-l720t -jflterefreshspr
jfltezm - China mobile
jfltecsp
jfltetfnatt
jfltetfntmo
All Variants with a locked bootloader are currently unavailable until the unified tree is further updated.
AT&T USERS: since your bootloader is locked, you must be on the UCUAMDB or UCUAMDL bootloader.
VERIZON USERS: since your bootloader is locked, you must be on the VRUAMDK bootloader.​Do 'getprop ro.bootloader' in Terminal Emulator or through ADB shell to find out which bootloader you have.​
TWRP
You are REQUIRED to be using TWRP 3.2.3-0 or newer to be able to flash any Pie rom.
If your device does not have an updated relevant version then you can use the standard JFLTE version.
If you have a device with a locked but exploitable bootloader as above (AT&T + Verizon) then use the Loki-patched version.​
Latest recommended JDC TWRP Recovery v3.3.0-0 for JFLTE: HERE.
Official TWRP Recovery v3.2.3-0 for JFLTE Loki-patched by @mattgyver: HERE.
Other variants may require a different recovery. ​
UNSUPPORTED DEVICES
GT-I9515 is not / will never be supported (slightly different hardware)
GT-I9500 is not / will never be supported (completely different hardware)​
Thanks
Side
Arco
JDCTeam
jhenrique09 + Pixel Experience team
OpenGapps
SPECIAL THANKS
Donators
JDCTeam-pie test team / Slack testers
AndroidFileHost
All of you!
JDCTeam
Buff - @buff99
Chibbo - @chibbo
Creeper - @creeper36
Diego Monaco - @alucard_24
Dimitris Katikaridis - @side
Franck Rohée - @franzyroy
Ray Daley - @gadget!
Jim Silverlock - @Jimsilver73
Marco Zanin - @-+BB+-
Matthew Booth - @MattBooth
Mattia D'Alleva - @AntaresOne
Mike Atkins - @FernBch
Oliver - @angelcalibur
Paul Harris - @hawkerpaul
Paul Keith - @javelinanddart
SalimPS - @SalimPS
Simeon Ivanov - @smstiv
Stefano Meroni - @smeroni68
Yannis Menexes - @SkL*
Be sure to check out our official aroma addon installer by @salimPS HERE
You are welcome to join the official JDC Team chat / test group in Slack jdcteam-pie
XDA:DevDB Information
🥧 Pixel Experience Pie 🥧 for S4 unified, ROM for the Samsung Galaxy S4
Contributors
Buff99, side
Source Code: https://github.com/PixelExperience
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Lollipop compatible
Based On: AOSP
Version Information
Status: Stable
Created 2018-11-13
Last Updated 2020-05-17
Installation​Required for installation: Recovery - Latest version of TWRP - 3.2.3-0
If you require a LOKI-patched version of TWRP, try this version patched by @mattgyver.
Firmware - Lollipop supporting bootloader and modem / non-hlos. Look in _Bon_Bon's great MODEMS and BOOTLOADERS collection​The following are "best practice" recommendations for installation, you may be successful using your own routine.
1st install - " clean install "
Make a full nandroid backup <always backup!>.
** OPTIONAL Properly remove previous root solution (recommended - flash Magisk uninstaller and UnSU). **
Fully wipe device (At least system, cache, dalvik and data. Recommended - fully clean by wiping internal and external SD).
Make sure your partitions are formatted as EXT4. Do not use F2FS on pie.
Install Rom.
DO NOT Wipe cache and art / dalvik (rom is partially pre-deodexed).
Reboot.
Wait for 1st boot.
Run through Gapps setup.
** OPTIONAL Reboot back in to TWRP.
** OPTIONAL Install desired root solution (recommended - Magisk).
** OPTIONAL Do not clear caches, boot back into Android.
Enjoy.
2nd and subsequent installs - " dirty flash "
** OPTIONAL Uninstall all Substratum overlays **
Make a full nandroid backup <always backup!>.
Properly remove previous root solution (recommended - flash Magisk uninstaller and UnSU).
Wipe system, cache and art / dalvik (wiping system is ESSENTIAL for Magisk).
Install Rom.
Install desired root solution. (recommended - Magisk).
DO NOT wipe cache and art / dalvik (rom is partially pre-deodexed).
Reboot.
Wait for app optimisation.
Enjoy.
While dirty flashing may be possible for some updates, be prepared that progress means you will occasionally need to clean install updates (usually when settings files are changed)!
Nandroid backups are your friend!​
Latest changelist
Release 12- 26th December 2019
release_12-PixelExperience_jflte-9.0-20191224-0101-UNOFFICIAL.zip - 675.8MB
md5sum - 281d8447f69eff26b1fec744bab95efb​
Release 12
December 2019 security patches
Changed to different Arm-optimized repo and removed a couple of bionic tweaks
Snap camera - handle sdcard removed case and dont spam exceptions
BT fixes
Translations
Drop AmbientPlay
Remove weather client
CPU tuned and JIT profiles changed to speed
Buffcore Kernel 10.2 - removed autosleep & quickwakeup
See attached changelist file for specifics
Release 11
September 2019 security patches.
Longshot screenshots added
Recorder app added
Miracast / casting enabled
performance tuned - Interactive governor & AutoSMP
Buffcore kernel 10.0
Row IO scheduler set as default
See attached changelist file for specifics.
Release 10
August 2019 security patches.
Buffcore kernel 10.0
See attached changelist file for specifics.
Release 09
June 2019 security patches.
Buffcore kernel 6.5b - more tweaks, fixes and optimisations.
See attached changelist file for specifics.
Release 08
June security updates
Buffcore kernel 6.12b
See attached changelist file for specifics
Release 07
May 2019 security patches
Push libsec-ril libraries
Disable Vsync for cpu rendered apps
Load dummy initial BT MAC address
Dex optimizations
Bionic optimizations
Finalize the UI improvements ( Finally 60fps smoothness on UI)
Tune interactive governor
Tune PegasusQ governor
Fix the touch boost never been enabled
Stop BT location scannings
Add pseudo-bokeh on Snap camera (Its on ISO modes as PORTRAIT)
Clean up some logs and sources
Reduce camera to api1 for better response (api2 is not working good on custom jf roms anyways)
A better sleep drain
init: Set min freq to 216000
overlay: Let light sensor warm up before work
Clean out some double sounds
Bug fix "Wallpaper is half black after rotating quickly "
Fix some wifi issues ( i believe )
Relocate location QS icon to main icons
core: Zygote: Disable any DEBUG reference
Kernel changes:
Upgrade kernel to 6.1 version with the following changes
Zip it with GZIP
Enable ZRAM/Zcache/zsmalloc
Optimized LMK
Kill some debug spams
ARM optimization flags here and there
Fix memory leak on wifi and general clean up
Enable autodetection of OOM
Fix BT and wifi memory leaks
Compress ramdisk,kernel and zram with a faster compression type (faster boot and executions)
Increase swappiness to 60
Clean up CPU's behavior code
Release 06
April security patches
Enable full Dexpreopting . Faster boot and response
Enable call recording for the countries that legally support it
Camera improvements ( Greatly improve preview quality, faster focus, greater quality on images and videos)
Reduce kernel spam logs
Clean up the power services (Better balance between battery-performance)
Clean up graphics services and drivers.
Interactive and intelliplug changes
Reduce GPU's voltage by 25ma
kernel: New and updated governors:
ABYSSPLUG
ADAPTIVE
BADASS
CONSERVATIVE
DANCEDANCE
DARKNESS
INTERACTIVE
KTOONSERVATIVE
NIGHTMARE
ONDEMAND
PERFORMANCE
PEGASUSQ
POWERSAVE
SLP
WHEATLEY
BIOSHOCK
USERSPACE
Release 05
BT defaulted on
change graphic renderer
camera improvements
governor changes including on charger
call recording in supported countries
translation updates
Improve ambient play layout on keyguard
Introduce smart clock
Improvements for battery percent inside icon
Smart clock: Fix clock showing then device is on landscape and QS expanded
full dex pre-opt applied
launcher pinning removed
Kernel: Buffcore 4.3b.
March 2019 security updates applied for Pix, AOSP.
Pix and AOSP code grabbed 24th March 2019.
Release 04
Whitelist Whatsapp and other social media apps in order to use HAL1 camera
BlueTooth Changes
WiFi Changes
RIL Changes
Pin HOME app in order to go home faster
Add a missing RIL blob
Fix encryption (?)
Kernel edits about increasing performance and general CPU scaling
Graphics should be smoother now.
gps:Log only if error
kernel:Enable AddRandom and disable IOStats
Lots other stuff changed
Kernel: Buffcore 4.3b.
March 2019 security updates applied for Pix, AOSP.
Pix and AOSP code grabbed 16th March 2019.
Release 3
BT calling works
Lots other stuff changed
Kernel: Buffcore 4.3b.
February 2019 security updates applied for Pixel, AOSP.
Pixel and AOSP code grabbed 00:00 9th February 2019.
Release 2.93
Advanced reboot (from dev options);
Built in dark Pixel theme (basic but functional);
Launcher icon shape setting;
Translations updated;
AOSP camera shipped (may change back to snap though?)
Buffcore 3.1 app
Buffcore Kernel 4.3b
January 2019 security updates applied for PIX, AOSP.
PIX and AOSP code grabbed 07:00 19th January 2019.
Release 2.9
Wifi much better.
Hotspot / tethering fixed.
Some display changes.
LMK tweaked.
Kernel: Buffcore 3.04. Netfilter / wireless fixes.
December 2018 security updates applied for PIX, AOSP.
PIX and AOSP code grabbed 05:00 5th December 2018.
Release 02
Wifi stability improved;
OptLos "special sauce" added;
Buffcore app added (full JF optomised fork of Kernel Aduitor);
Default vibration reduced;
Some BT edits (Arco);
Toolchain changed to BB's JF optimised Linaro 7.1.1;
Kernel: Buffcore 3.01 (some Buffcore 2 tunings and optimisations added back in);
November 2018 security updates applied for PIX, AOSP.
PIX and AOSP code grabbed 02:00 22nd November 2018.
Thanks to JDCTeam chat / test group in Slack jdcteam-pie .
Current issues
Release 12​
This rom is as close as you will get to a stock Google Pixel style phone.
It is an unofficial version of Pixel Experience, so only report issues to this XDA thread, not Pixel Experience team.
Release 12 has even more @side OptLos super smooth speed optimisations applied…. - It's super smooth!.
Installs about 1.3 gb in system including gapps (** so WILL NOT WORK on i9505g / google version **)
System folder is re-sized to full 2.7gb.
Unified rom so should work on all S4 variants APART FROM i9505g DUE TO SIZE.
Remember this is an almost stock google pixel rom!
Gapps is already pre-installed and mandatory
DO NOT attempt to manually install any gapps package over the top, you will break it.
Don't work
MHL video (? we think ?)
Does work
Miracast / casting.
BT calling.
SE Linux is set as permissive.
Wifi is much improved.
Hotspot working.
GPS is great.
Make sure your partitions are formatted as EXT4. Do not use F2FS on pie.
CDMA phones work??
Magisk 19.3 works fine.
Magisk sound mods appear to work e.g. ViperFX.
Substratum works fine.
Sound changes may mean older sound mods no longer work.
The google sound app may crash, update to version 2.1.
This rom will not work / will never work on i9515, i9500 and i9506 variants of S4.
Reporting bugs​
Proper reporting of issues will help me spend time productively fixing bugs rather than tail chasing vague issues.
Please follow these guidelines.
Reporting bugs
If you wish to report an issue, then the onus is on you to prove the issue.
If you provide exact replication instructions, an idea of how often the issue occurs and logs that enable me to replicate the issue then a fix will be possible ("if you do action 1 then action 2 then action 3 you will find that bug X occurs 100% of the time").
If you give a vague complaint about an issue then I will not look at it without explicit replication instructions and preferably logs ("phone overheats when using game XYZ").
Issues about overheating, battery life or performance should be backed up with information from relevant monitoring apps.
One-off issues generally do not get investigated unless they are well documented and have provided logs.
Issues that are specific to one piece of software will generally not get investigated without logs. I am not very keen on installing software to investigate bugs, especially if I need to create user accounts. If you can replicate the issue on more than one piece of software it will increase the chance of being fixed.
Issues to do with speaker or microphone related issues need to be explicit about which speaker and mic is in use (internal, head phones, earphones, bluetooth headset, Bluetooth speakers), whether normal earpiece or hands free mode is in use, Audio mods that have been installed. Logs may be helpful too.
Issues with media / streaming / playback should be provided with examples.
A picture is worth a thousand words; a movie is thousands of pictures. If you cannot describe your problem in words, post pictures or movies to help show your issue. The rom has in-built screen capture and screen recording tools, so please use them.
It can often be difficult to tell what is going on with logs from a fully loaded system. It can help if you make a nandroid of your current system, format and then make a clean install, with gapps only if needed, and only the app that causes the issue - as minimal a system for replication as possible - then replicate the bug and capture logs. If I then have to replicate the issue I can easily replicate your system.
If you want to send logs for a bug, I would like you to use Syslog.
Perform some of the functionality that is bugged and then capture logs in the app.
If you have had a reboot then capture a set of logs immediately when the system reboots. If the last-kmsg file is empty then the logs are useless.
Type a brief description of the problem in the notes field and your XDA username .
Select to scrub personal information.
Upload it to a web based host (gdrive, dropbox, etc.) and PM the link to me.
And remember:The Drill ...​​
you stole my pie icon at the thread title
muehehehe <3 finally released .
loved it <3
side said:
you stole my pie icon at the thread title
muehehehe <3 finally released .
loved it <3
Click to expand...
Click to collapse
That Pie-con is JDC property.
I love that you love it.
:highfive:
Pies...Pies everywhere ?
@Buff99 @side ARTISTS !
Finally
Video by me
You killed it bro, amazing work & amazing team, love it <3
Dear Buff99,
Thank you for PE Pie ROM.
redacted
sghi747love said:
https://forum.xda-developers.com/re...-fix-signal-issues-fluctuations-t3811950/amp/
Click to expand...
Click to collapse
this guy removed his commit.
redacted
Beautiful ROM, great work! Definitely a daily driver for me if Bluetooth will be fixed!
I was looking for a lot this rom, thanks to the developers.
Inconveniences: at the first power-up, my device became excessively hot to the point of burning the screen, and turned off only.
Remove the battery, and let it cool for 10 minutes, now it seems to work normal.
Still this I am a user of this type of ROM (pixel experience) on all my devices with twrp installed.
thanks again
Release 02 is now available - see:
post #1 for download link
post #2 for installation instructions
post #3 for changelist
post #4 for updated current issues
post#5 for bug reporting instructions
Dirty flashing should work fine.
BT calling is still broken, but release 03 will see it fixed as good progress is being made.
Hotspot may be broken for this build, sorry.
This build is much faster and smoother than release 01.
[deleted]
Thanks. Waiting for stable rom.

[KERNEL] [11.0.0] Kazuki Kernel [February 18, 2022]

Introduction
Kazuki Kernel is a kernel based on Sultan's kernel with some additional modifications aiming to give a better experience than the stock kernel.
Compatibility
This kernel only supports devices running the latest firmware (vendor.img), and will NOT BOOT on anything else.
Features
Everything from Sultan Kernel
Backports from Sultan's Pixel 4/XL kernel
Patches from kdrag0n's Pixel 2/XL kernel
New set of optimized CPU frequencies and EAS energy model
Wi-Fi WPA3 support
Miscellaneous treewide optimizations
Downloads
Latest kernel
Enable support for flip covers (optional)
Credits
Sultan Alsawaf (Sultanxda/kerneltoast) for his kernel and help
Danny Lin (kdrag0n) for his patches and freqbench
Everyone else who I cherry-picked from
Source code
https://github.com/Kaz205/android_kernel_google_wahoo/commits/20220218
Changelog
February 18, 2022:
• Massively reduce latency
• Fixed a regression which caused performance to drop when executing heavy tasks
• More EAS patches from android-4.4-p
• Merged February ASB
October 26, 2021:
• Fixed the deadlock (finally!)
Thanks to @ab123321 for the help
October 14, 2021:
• Fixed a deadlock (for real this time).
October 11, 2021:
• Fixed a deadlock
September 28, 2021:
• EAS patches from android-4.4-p
• Optimized lock usage in various subsystems
• Lowered idle drain
September 12, 2021:
• Fix high power consumption when playing video
September 8, 2021:
• Bring back support for AFWall
• Allow vibration when the Camera is used
September 7, 2021:
• Complete revamp! Cleaned up broken commits
and rebased onto Sultanxda's 11.0.0-sultan branch
• Revert back to v4.4.223
• Update compiler to GCC 11.2
• Save power when rendering static images
• Massively save power when playing video
• Merge September ASB
• Further backports from Sultan's Pixel 4/XL kernel
• New set of optimized CPU frequencies for performance and battery life
July 11, 2021:
*Further tweak scheduler for better performance and battery life
*Better low-memory-killer performance (Thanks Sultan)
*Update WireGuard to v1.0.20210606
*Merge linux-stable v4.4.275
*More stuff that I forgot about
May 12, 2021:
*Switch compiler to GCC 11.1 for improved performance
*Merge April and May ASB
*Merge linux-stable v4.4.265
*Update Simple LMK
*Enable zram deduplication (saves 100~200mb of memory)
*Massively optimize Unity games (thanks Sultan)
*Further backports from Sultan's Pixel 4/XL kernel
*Micro-optimize Qualcomm secure channel manager
April 26, 2021:
*Revert zram compressor back to zsmalloc as z3fold was causing problems
*Slightly reduce overall power consumption
*Minor bug fixes from Qualcomm
April 24, 2021:
*Switch zram compressor backend to z3fold (for hopefully better long term performance)
*Micro-optimize Qualcomm G-link driver
*Slightly reduce overall power consumption
*Minor scheduler improvements
April 18, 2021:
*Initial release
Flashing straightaway!
Thanks for your work
Working fast and snappy on taimen running ProtonAOSP 11.4.0
Is anyone successful in flashing on crdroid? What's the experience like
Flash in walleye run 11.4 proton OS . Boot fail. Auto boot to bootloader
Show notify yellow at the bottom: ERROR: BootLinux Failed: Not Found
Can i use this on Android 10?
ValKyre said:
Flash in walleye run 11.4 proton OS . Boot fail. Auto boot to bootloader
Show notify yellow at the bottom: ERROR: BootLinux Failed: Not Found
Click to expand...
Click to collapse
Did you flash the kernel correctly? It appears that your boot image is corrupted.
Prattham said:
Can i use this on Android 10?
Click to expand...
Click to collapse
No, only Android 11 phones with the latest firmware are supported.
Kaz205 said:
Did you flash the kernel correctly? It appears that your boot image is corrupted.
Click to expand...
Click to collapse
Download your kernel.
And flash via twrp
It appears that I had removed important dtb files which made the kernel unbootable on walleye. I uploaded a new build to (hopefully) fix the issue. The new build should be called "Sultan-kernel-plus_20210418-fixup.zip".
EDIT: It's fixed and is safe to flash.
Kaz205 said:
It appears that I had removed important dtb files which made the kernel unbootable on walleye. I uploaded a new build to (hopefully) fix the issue. The new build should be called "Sultan-kernel-plus_20210418-fixup.zip".
Click to expand...
Click to collapse
Yay... It boot now. But do u know why it same issue like other kernel ? (kirisakura, sultan old version,...) .
The issue is: when restart, the boot amination very very slow. Some time when the screen of press power key to turn on phone it take 3-5s to open (sometimes not usually) .
New build is up with some original commits. Nice!
Kaz205 said:
新建了一些原始提交。好的！
Click to expand...
Click to collapse
希望优化的更好,感谢
any settings for rgb to eliminate the yellowish from white?
Newwwww build
@Kaz205 I've been following your github repo for a while and there was a period of time where you used PELT and is no longer using it. Just wanted to know what are your findings regarding PELT?
Chaninoza said:
any settings for rgb to eliminate the yellowish from white?
Click to expand...
Click to collapse
Yes it's present.
neekless said:
@Kaz205 I've been following your github repo for a while and there was a period of time where you used PELT and is no longer using it. Just wanted to know what are your findings regarding PELT?
Click to expand...
Click to collapse
I initially switched to PELT in hopes of lower jank. However I switched back because it turns out that PELT breaks live frequency stats and that jank is more or less the same as WALT with some proper tuning.
New build is out with lots of cool changes!
May I use this kernel for 10?
Sui77 said:
May I use this kernel for 10?
Click to expand...
Click to collapse
No. Already answered by dev before in this thread... Post#6
Kaz205 said:
New build is out with lots of cool changes!
Click to expand...
Click to collapse
hehe less jank
flashed for some testing....

Categories

Resources