This Kernel is based off the sources of AndreiLux Perseus Kernel (alpha35).
If you consider to thank me, please also consider to thank him http://forum.xda-developers.com/showthread.php?t=1927852
This kernel only supports roms of android version 4.3.x (sammy and aosp) and 4.4.x!
You can dualboot any of those roms
if you were using this kernel on aosp based roms, and want to use another kernel, you need to reflash the rom, of course without any wipe, it's just to restore modified files
Features (changes compared to Perseus):
- merges samsung open source update12
- dual sound engine
- compiled with linaro gcc 4.8.3
- updated Linux Kernel base to 3.0.101
- updated block subsystem (i/o schedulers) to linux 3.4
- updated memory management subsystem to linux 3.4
- partial updated kernel main system to linux 3.4 (current work in progress)
- zram, zsmalloc and lowmemorykiller updated from 3.9
- DevilQ cpu governor (default)
- fiops v2 i/o scheduler
- working for Aosp and Sammy at once (Big thx to Gokhanmoral for making this possible)
- Portet Ezekeel's Touchwake Feature (from nexus s)
- Oc up to 2.0 Ghz
- Backport from Linux 3.5 smp driver parts
- Wifi driver updated from note3
- backported zswap from linux 3.13 (this replaces zram now)
- backported cpu-boost driver
- possibility to set high/low power mode for wifi when screen is off
- LulzactiveQ cpu governor (from siyahkernel, thx again to Gokhanmoral)
- Hotplug Cpu Governor
- Proportional Rate Reduction for TCP
http://kernelnewbies.org/Linux_3.2#head-1c3e71416a9fdc2f59c1c251a97963f165302b6e
- improve memcopy/memmove
- Using Voodoo Sound and Boeffla Sound
- LED Control by yank555-lu
- ExFat support (thx to samsung for opensourcing the driver)
if your rom is based off PAC, Bam, Fusion, ... :
IMPORTANT: As per notice of 01.11.2013, my CM10.2 kernels do NOT support proprietary Custom Rom frameworks anymore. So if your Custom Rom did not implement the generic framework class framework-2.jar but his own naming convention, you will receive a boot loop. Do not cry about this here but advise your Custom rom cooker to fix this. I will not change this ever again.
The most prominent custom kernels for CM will follow the same approach (aligned between Yank555, Googy, LordBoeffla, Psndna, Temasek and me).
So please do pass this message along to your favorite ROM devs.
If they don't fix their rom, it won't be compatible with custom kernels any more!
Kernel app http://forum.xda-developers.com/showthread.php?p=41346443#post41346443
How to post bugs:
http://forum.xda-developers.com/showthread.php?t=1520508
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Dualboot Faq:
For more detailed instructions, please take a look at this thread from RichMd (thank you for it):
Dualboot Faq thread
Important: if you want to use this kernel for dualboot, i highly recommend flashing my recovery as well.
General information about the recovery:
dualboot menu.
in this menu you can:
* create the secondary system partition (needed to be run once, if you want to install a second rom)
Install-zip menu:
you'll notice there is a new menu, where to select what you want to flash.
if you select kernel, rom or recovery, the zip gets installed as it is.
if you select zipt to pri./sec. filesystem, it is selfexplanary
if you select rom to secondary fs, the zip gets modified to install to the sec. fs. IF YOU WANT TO INSTALL IT TO PRIMARY FS LATER SOME TIME, YOU NEED TO REDOWNLOAD THE FILE!
if you select rom to primary filesystem, it gets installed there, and you can use the same zip later again.
How to install a second rom:
make sure you have already created ssecondary system partition! if not, go to dualboot menu and create it now (this may take some minutes)
The savest way is the way by using nandroids: if you don't have a nandroid already, create one now. Then just select your backup, and restore it to secondary filesystem.
you now should already be able to boot into primary or secondary rom (which are both the same now).
now you can install any other rom as primary.
if you want to install a new rom directly as secondary,
make sure there are no spaces in the filename!,
then just go to install zip. you'll notice there's a new menu at some point.
in this menu you can select where you want to install, and what type of file it is.
if you choose rom to sec. fs, your zip files itself gets modified to be installed to secondary fs. this may take a minute, because the files needs to get zipped again. Imporant: this file is permanently modified. if you think you need it later again, you should redownload it, because the modified one would always install as secondary.
installing a rom as primary, a zip to primary or zip to secondary fs, does not modify the zip.
Additional information:
roms coming with an aroma installer are hard to handle, as every dev can place own commands into it. It's impossible for me, to take care of every possibility. Because of this, it should be the best method, to flash a rom with aroma installer as primary one (and then move it to secondary, by using the nandroid method, if you want it to be secondary).
Click to expand...
Click to collapse
Many Thanks to:
- RichMD
- Gokhanmoral
- Andreilux
- DAGr8
- simone201
- ptmr3
- Stratosk
- RolloS
- kasper_h
- Philz (for his recovery source, although i had to implement my own touch )
- all the others mentioned in the changelogs
reserved
could someone please upload sammy 4.3 stock kernel? i want to build a seperate kernel for sprint, but i need the stock kernel for extracting some files before. thanks
My links to current devil stuff
New devil recovery with f2fs support for system and cache (data partition to come later). Note you dont need f2fs to use the recovery or kernel but you do need the kernel and recovery to use f2fs. If you convert to f2fs and want to use a different recovery then you must format file systems back to ext4 before changing. Bad things will happen if you do not convert before changing recoveries. Also the rom you are flashing must have an installer script setup for f2fs. I will be updating all my roms to support f2fs when I do their next releases.
Recovery link
https://www.androidfilehost.com/?fid=23622183712470601
MD5sum 1f15bb6c56d1fc65b00c8af188a37cda
Devil tools 1.1.2
https://www.androidfilehost.com/?fid=23622183712470603
MD5sum bcb3e3b4d7ec969b43bd68e47e6b556f
May post a current kernel if approved.
Thank you thank you thank you! Been hoping someone would make us a custom mk4 kernal
Thanks DerTeufel980.... we all really appreciate this.
So I can use this with a Samsung mk4 ROM? I'm on digiblur.
Sent from my SPH-L900 using xda app-developers app
krobinso2295 said:
So I can use this with a Samsung mk4 ROM? I'm on digiblur.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Once it is done.
Sent from my SPH-L900 using XDA Premium 4 mobile app
kernel is up
dualboot coming in the next days. i need to compile my recovery for you...
Sweet!!
Sent from my SPH-L900 using XDA Premium 4 mobile app
So the kernel posted will work on twiz 4.3?
From My Classic 4.3 n2/3
Chaz187 said:
So the kernel posted will work on twiz 4.3?
From My Classic 4.3 n2/3
Click to expand...
Click to collapse
It's in the first post... Working on Android 4.3 and above...
Gesendet von meinem Note II mit Tapatalk 2
DerTeufel1980 said:
It's in the first post... Working on Android 4.3 and above...
Gesendet von meinem Note II mit Tapatalk 2
Click to expand...
Click to collapse
Just flashed and it wont boot past splash screen. Button backlights flash on but that is all. What extra info do ypu need?
Sent from my SPH-L900 using XDA Premium 4 mobile app
Will this work on cm 4.3 4.4 or have to wait for the dual boot
Sent from my SPH-L900 using Tapatalk
It should but it is untested. Dual boot is just a special recovery that allows you to run two roms without flashing or nanding between the two.
Sent from my SPH-L900 using XDA Premium 4 mobile app
jlmancuso said:
Just flashed and it wont boot past splash screen. Button backlights flash on but that is all. What extra info do ypu need?
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Does the screen turn black after splash? Or does it sit with my kernel logo all the time?
Is adb shell working?
sliverr7x said:
Will this work on cm 4.3 4.4 or have to wait for the dual boot
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
It should work already... But as written above, it does not work on sammy currently.
Please report if there are same issues with cm.
Gesendet von meinem Note II mit Tapatalk 2
OK I just read about pac roms so I see It won't work according to the op
Sent from my SPH-L900 using Tapatalk
Can't wait for this to be working.... will it support stweaks
From My Classic 4.3 n2/3
Chaz187 said:
Can't wait for this to be working.... will it support stweaks
From My Classic 4.3 n2/3
Click to expand...
Click to collapse
The older version stweaks workes sort of but there is a devil tools in the market that works.
DerTeufel1980 said:
Does the screen turn black after splash? Or does it sit with my kernel logo all the time?
Is adb shell working?
It should work already... But as written above, it does not work on sammy currently.
Please report if there are same issues with cm.
Gesendet von meinem Note II mit Tapatalk 2
Click to expand...
Click to collapse
Sits on devil logo. Not sure about adb not around pc. Anything specific just list it and will try later.
Sent from my SPH-L900 using XDA Premium 4 mobile app
I would need someone to try on cm11 or omnirom (generally any aosp rom), to know if the issue is caused by sammy initram files, or the main init file.
Gesendet von meinem Note II mit Tapatalk 2
Related
Advanced Stock ICS Kernel for Xperia SHere is a kernel based on the Stock ICS kernel with some features which come from DoomLord's GB kernel.
Features
autorooting
CWM recovery (with reboot recovery support)
init.d support (thanks DoomLord)
TUN/TAP driver
Download links
Build 17 (Fastboot)
Build 17 (CWM)
Build 16 (Fastboot)
Build 16 (CWM)
Prerequisites
An unlocked bootloader: Tuto here.
A stock ICS ROM (6.1.A.0.452 to 6.1.A.2.55). Don't expect this kernel to work with CM9/10.
How to flash
For elf files :
Read DoomLord's guide
You just have to replace kernel.elf by the name of the downloaded kernel in the flash command (eg : ics4.elf)
For zip files:
Flash the zip file from the recovery
Changelogs
Build 17 (08/12/12) :
Merge 6.1.A.2.55 kernel sources
Autodetect rom version in default.prop based on build.prop
Updated recovery, adbd and busybox (JB version)
Build 16 (01/11/12) :
Random reboot issue probably fixed (patch from CM10 kernel, thanks Kali)
Rom version increased to 6.1.A.2.50
Updated recovery, adbd and busybox (JB version)
SD card mounted by default in recovery
Vibration at boot removed, only led and backlight now
Build 15 (05/09/12) : Increase ROM version in default.prop from 6.1.A.0.452 to 6.1.A.2.45
Build 14 :
New MMC driver (from codeaurora) : it fixes issue while formatting partitions in CWM
Wifi module built from source (in the ramdisk)
Updated recovery
Disable again hardware clock
Build 13 :
Backup / Restore fixed with dedupe
Backlight enabled in CWM
Better "reboot recovery" handling in adbd / busybox and recovery
Build 12 :
Updated recovery
Hardware clock correctly saved (from CM9 kernel)
Build 11 : Go back to GCC 4.4 (fix artifacts with camera preview)
Build 10 :
Kernel built with GCC 4.6
Several autoroot fixes (Superuser app pushed just once and correctly removed in /data)
Working reboot recovery command (with adb too)
Updated su (3.1.1) and Superuser (3.1.3)
A bunch of new command included in the new busybox (ifconfig, wget, vi, and many more !)
Build 9 :
Kernel built from sources
TUN/TAP driver included (for VPN)
Build 8 : Fix mass storage in CWM
Build 7 : Fix MTP
Build 6 : Key mapping in CWM fixed
Build 5 :
New recovery built from latest CM9 sources
Fixed generation of md5sum with nandroid
Increased font size in CWM
Boot partition backup and restore
New adbd built from CM9 sources (fixed an issue with hardcoded sh path in /system)
Build 4 :
Correct su binary
Don't wait 3 sec if /cache/recovery/boot exists
Build 3 :
Leds and vibrator at startup fixed
Sources
Ramdisk sources
Kernel sources
Credits
DoomLord : many thanks to him for its kernel and all his scripts.
championswimmer and sminki for their help
FreeXperia team for their work on CM
makes it perfectly start does not make any errors
greetings and thanks
yes it boots!
(maybe you can help with my Question here )
Hey, I also have tested several times to include recovery, but withut succes, didn't get any further then a booting kernel without recovery or vibration and LED on to enter recovery but no entering recovery and kernel that doesn't boot.
Please pm me if you want to work together, I saw your kernel is from ICX team? I know nick very well so I'd would be a pleasure to work with you too
sminki said:
yes it boots!
(maybe you can help with my Question here )
Click to expand...
Click to collapse
for this question and any other other question similar to this
head here
http://forum.xda-developers.com/showthread.php?t=1659584
it has menu driven process to extract and repack kernel.elf (ramdisk also can be extracted and packed )
Welcome Champ, good to see you mate.
I will leave the thread here as knowing you, you will have a kernel ready for us in a few hours.:fingers-crossed:
thanks for the test guys... so now i'm diving into including recovery....
good to know i could pull off kernel.elf editing in my first attempt lol
@colossus if not in hours, then definitely within 1 or 2 days
EDIT :
can someone send me the kernel.elf from FXP122 cm9 ??
will save me the time to download the whole ROM
This is sweet, good job!!
john9 said:
This is sweet, good job!!
Click to expand...
Click to collapse
Only a few files to edit now
We'll keep you updated
Sent from my LT26i using XDA
championswimmer said:
btw if anyone wishes to do this before me,
this diffstats should help you
https://github.com/championswimmer/xps-ramdisk/commit/a61969aefca00ce3a6e4e112e97403fb6f0c79e9
it shows how doomlord added recovery to gb kernel..
Click to expand...
Click to collapse
cool.. well that's a hell of a lot easier than the manual route I was taking. This was my goal, but for personal rather than pseudo "xda glory" as I'm working with DooM's stuff I didn't feel right posting it without his permission, but he's probably too busy to care
go for it championswimmer :victory:
Excuse my noob-ish question, but... what's the difference between a 'stock' kernel with recovery and a completely custom kernel like DoomLord's? Is it to do with core frequencies/governors?
fNOOB said:
Excuse my noob-ish question, but... what's the difference between a 'stock' kernel with recovery and a completely custom kernel like DoomLord's? Is it to do with core frequencies/governors?
Click to expand...
Click to collapse
Frequencies and governors are one possible customicing for kernels, for the most users the most important thing. also Kernel modifing can allows you init.d support, undervoltscripts and also allows (or denies) MSC support... and, for shure, clean out some tings, make things more efficiently and and and... a dev is nearly totaly free to create a very customiced kernel with or without special Driver support or so
noob.fl said:
Frequencies and governors are one possible customicing for kernels, for the most users the most important thing. also Kernel modifing can allows you init.d support, undervoltscripts and also allows (or denies) MSC support... and, for shure, clean out some tings, make things more efficiently and and and... a dev is nearly totaly free to create a very customiced kernel with or without special Driver support or so
Click to expand...
Click to collapse
Cheers mate
sminki said:
cool.. well that's a hell of a lot easier than the manual route I was taking. This was my goal, but for personal rather than pseudo "xda glory" as I'm working with DooM's stuff I didn't feel right posting it without his permission, but he's probably too busy to care
go for it championswimmer :victory:
Click to expand...
Click to collapse
using someone's work just because 'he's too busy to care' is not the aim which we at xda strive for ...
i've already talked with Doomlord regarding using his recovery... and as long as I clearly mention it's his work and provide links back to his thread, he has no issues with anyone else using it...
(and i'll surely do that ^^ when i release a kernel containing his recovery, if i ever do that)
championswimmer said:
using someone's work just because 'he's too busy to care' is not the aim which we at xda strive for ...
i've already talked with Doomlord regarding using his recovery... and as long as I clearly mention it's his work and provide links back to his thread, he has no issues with anyone else using it...
(and i'll surely do that ^^ when i release a kernel containing his recovery, if i ever do that)
Click to expand...
Click to collapse
cool, i was only making a bad joke, we all know DooM cares
sminki said:
cool, i was only making a bad joke, we all know DooM cares
Click to expand...
Click to collapse
lol.. ok
and i'll bring you some unicorns soon
championswimmer said:
lol.. ok
and i'll bring you some unicorns soon
Click to expand...
Click to collapse
I can't wait! :victory:
so this kernel has the ro.secure property in default.prop set to 0??
Tnaks mate for your job!
tested right now the test version and the sony logo fades and reboots
can you plug it into a pc and run a logcat from command prompt and give me the output of any comes??
Perseus for the E300K, E300S & E300L
Please read the FAQ.
Notes:
* I have not tested and have no way of testing the E300L. I have made the initramfs files available. If something doesn't work and you have any experience with ramdisks, please try to fix. At this point if something doesn't work it could be the zImage or the ramdisk.
Test 3 for E300L:
I haven't given up on the e300l but I won't have any time until after 9/23.
cwr-perseus-e300l-test1.zip (5.2 MB)
odin-perseus-e300l-test1.tar (5.1 MB)
cwr-perseus-e300l-test2.zip (5.2 MB)
odin-perseus-e300l-test2.tar (5.1 MB)
Click to expand...
Click to collapse
Changelog:
- build 091413 Latest
separate defconfig for each device (perseus_e300k_defconfig, etc)
MH2 OSRC source code
added support for E300L (untested)
removed some unnecessary code
made sperate kernels for each device
- build 090513
updated initramfs to fix bootloop on E300S
- build 090313
fully compatible with E300S
build with linaro toolchain
updated initramfs
- build 090213
DMB fixed
- build 082913
perseus alpha9 (as of Aug 29)
perseus_e300k_defconfig updated
Ad-hoc (IBSS) support added to kernel
audio tab removed from stweaks
battery tab added to stweaks
- build 082713
perseus alpha8 (as of Aug 17)
samsung mg2
first build
hardware added ymu831, dmb, modem
stweaks support
Kernels - flash via recovery:
cwr-perseus-e300k-091413.zip (6.6 MB)
cwr-perseus-e300l-091413.zip (6.5 MB)
cwr-perseus-e300s-091413.zip (6.6 MB)
Kernels - flash via Odin:
odin-perseus-e300k-091413.tar (6.4 MB)
odin-perseus-e300l-091413.tar (6.5 MB)
odin-perseus-e300s-091413.tar (6.4 MB)
Kernel Source Code:
perseus-e300x-091413-src.tar.gz (116.2 MB)
Ramdisks:
e300k_initramfs.tar.gz (2.4 MB)
e300l_initramfs.tar.gz (2.3 MB)
e300s_initramfs.tar.gz (2.4 MB)
Be sure to thank AndreiLux for making this possible.
How-To
This is how I set my E300K. You can do it however you want but I know this works. If you have an E300S you need to use the firmware for your phone.
- backup and important data on SD and microSD
- shutdown
- remove sim & microSD
- vol up + home + power to cwr - factory reset - power off
- vol down + home + power to odin - [No Auto Reboot] - flash (E300KKKUAMG2_E300KKTTAMG2_HOME.tar.md5 or firmware for E300S) - remove battery
- vol up + home + power to recovery but will boot to OS
- quick setup OS ("next", "skip" or "no" to everything)
- settings - accounts - backup & reset - factory reset
- quick setup OS ("next", "skip" or "no" to everything)
- settings - more - unknown sources
- connect to PC - copy UPDATE-SuperSU-v1.32.zip to SD
- vol down + home + power to odin - [No Auto Reboot] - flash (i9500-cwm-recovery-6.0.3.2-2.tar) - remove battery
- vol up + home + power to cwr - install zip from sd (UPDATE-SuperSU-v1.32.zip)
- reboot
- shut down
- insert sim
- boot
- enable data or wifi - software update - "modified .. blah, blah"
- open Play - update superSu app & install Busybox or Busybox Pro
- exit Play
- superSU - update binary (Normal) - exit
- Busybox - Root Perm. (Grant) - Backup (No) - Install (Smart Install) - Option "Auto Update Busybox" (No) - exit
- if using microSD - BEGIN
make directory /etc/init.d
make script for exfat
---
#!/system/bin/sh
insmod /lib/modules/exfat_core.ko
insmod /lib/modules/exfat_fs.ko
---
change permission of script to 755
- if using microSD - END
- boot OS
- update all apps via Google Play, Olleh Market, Samsung Apps, etc.
- restart
- vol up + home + power to cwr - install zip from sd (kernel)
FAQ:
1. Why is this in the i9500 thread?
The Galaxy S4 has many variations. SHV-E300K is one of three models sold in South Korea. Since XDA only has a small number of users of this variation, the moderators do not make separate sections for this device.
2. Will you make a kernel for the e300s and e300l?
This depends on if the people testing the devices I don't own can help me make them work. The more useful information you give me, the more likely the kernels will work.
3. XYZ doesn't work. What can I do?
PM me, not AndreiLux. Tell me as much as you can so I can try to recreate the problem.
3. How do I use init.d feature?
make folder /etc/init.d
put your scripts in /etc/init.d/
chmod your scripts
4. How do I mount an SD Card?
4a. (Option 1) load exfat_core & exfat_fs from terminal and then Settings - More (Tab) - Storage - Mount SD Card
4b. (Option 2) load modules via init.d5. Can you add xyz feature?
I will certainly try.
6. STweaks is force closing. What can I do?
The "unexpected error" seems to mostly occur due something messing with busybox in /sbin.
If you are using Busybox Installer (Stericson), Uncheck or decline the option to disable busybox in /sbin.
To get to the Settings page, swipe two pages to the left. There is a check box at the top. This option disables the copy of busybox built into the kernel.
Glad to meet you koe1974 again
Can I add the link of your thread in my thread?
can we also get perseus kernel for E300L ? would love it. please try to develop this kernel for E300S and E300L
I've been waiting for this, anyone know where I can buy a SHV-E300K for a reasonable price?
You know that perseus kernel is for universal 5410 exynos?
SHV-E300K is a i9505 variant which uses snapdragon and you cannot port every feature
btw: this is the wrong section and without kernel source you will get into trouble
Grarak said:
You know that perseus kernel is for universal 5410 exynos?
SHV-E300K is a i9505 variant which uses snapdragon and you cannot port every feature
btw: this is the wrong section and without kernel source you will get into trouble
Click to expand...
Click to collapse
SHV-E300K is an Exynos 5410 phone with LTE support.
Research before posting useless posts.
Grarak said:
You know that perseus kernel is for universal 5410 exynos?
SHV-E300K is a i9505 variant which uses snapdragon and you cannot port every feature
btw: this is the wrong section and without kernel source you will get into trouble
Click to expand...
Click to collapse
The SHV-E300K is not a variant of the I9505. It is a variant of the I9500. And yes, while the source code is for a "UNIVERSAL" 5410 chipset, there are still tons of things that need to be done in order to actually make it work with either phone. I.E. .. ril code, wifi supplicants, cpu governers, audio, and the list does go on. It takes a lot of hard work and patients to get it to work with either phone to be honest. And no this isn't the wrong section due to the fact that it is part of the the I9500 family. We do not have and will not have our own thread for this phone because it is considered a localized phone branding.
lunerceli said:
The SHV-E300K is not a variant of the I9505. It is a variant of the I9500. And yes, while the source code is for a "UNIVERSAL" 5410 chipset, there are still tons of things that need to be done in order to actually make it work with either phone. I.E. .. ril code, wifi supplicants, cpu governers, audio, and the list does go on. It takes a lot of hard work and patients to get it to work with either phone to be honest. And no this isn't the wrong section due to the fact that it is part of the the I9500 family. We do not have and will not have our own thread for this phone because it is considered a localized phone branding.
Click to expand...
Click to collapse
Sorry my bad
Samsung just released too many s4
Sent from my GT-I9500 using xda app-developers app
Grarak said:
Sorry my bad
Samsung just released too many s4
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
Its all good. I wasnt trying to be mean ir anything. Just heloing out with the knowledge flow.
Sent from my SHV-E300K using Tapatalk 2
Koe, getting random crashes with compatibility layer, cloud service agent, and random with com.android.phone. I went back to your old kernel until I get off work and then I will reinstall this kernel and send a log cat...
Also getting baseband service stopped responding. But it recovers once the phone boots completely.
Sent from my SHV-E300K using Tapatalk 2
lunerceli said:
went back to your old kernel until I get off work and then I will reinstall this kernel and send a log cat...
Sent from my SHV-E300K using Tapatalk 2
Click to expand...
Click to collapse
Also let me know if you have frozen/hibernated/uninstalled things from the stock rom.
I am testing against a rom with only a few things frozen and nothing removed.
Sent from my SHV-E300K
koe1974 said:
Also let me know if you have frozen/hibernated/uninstalled things from the stock rom.
I am testing against a rom with only a few things frozen and nothing removed.
Sent from my SHV-E300K
Click to expand...
Click to collapse
Nope, nothing frozen/hibernated/uninstalled from stock rom. I know the baseband service stopped error only happens at boot and then it recovers itself. The others will randomly stop and then quickly recover .. maybe you could turn off show error msg dialogue within the kernel since these services are actually recovering and not hindering anything?? Oh, and I have started work on the K device tree today, made a little bit of progress. It is just going to take all weekend to download the CM10.2 sources. But what I was planning on doing, with your permission of course, is adding your sources into the kernel build of CM and working it that way. With things like this, we would be working together on making this build possible and working out the bugs for each would be a lot faster .. let me know what you think...
lunerceli said:
let me know what you think...
Click to expand...
Click to collapse
It is all open source so what's mine is yours.
Sent from my SHV-E300K
koe1974 said:
It is all open source so what's mine is yours.
Sent from my SHV-E300K
Click to expand...
Click to collapse
Yeah, but it's still the principle of asking permission though. I am old fashioned like that .. LOL.
Thanks
I use E300K~!
Thanks!
But Stweaks is not Working..
and Please UPDATE Matcl..
[Sorry. I don`t speak English..]
DukoOsu said:
But Stweaks is not Working.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2404954
Sent from my SHV-E300K
And dmb is not working too.
No dmb signal.
Same problem korea E300K user.
---------------------------------------------------
Sorry. I don't speak English
Sent from my Korea GS4 E300K
I cannot repair the error of the STweaks at all.
Isn't there kerenl problem ?
---------------------------------------------------
Sorry. I don't speak English
Sent from my Korea GS4 E300K
DukoOsu said:
I cannot repair the error of the STweaks at all.
Isn't there kerenl problem ?
Sent from my Korea GS4 E300K
Click to expand...
Click to collapse
You must tell me more information. What rom are you using? Which Busybox installer? Logcat log, please. Etc..
Sent from my SHV-E300K
F2FS (born Flash-Friendly File System) - file system, focused on the use of flash memory, and now it on the Nexus 5!
Attention! Erases all data, including those from the /data/media! Save the data to a computer
1.Boot in FastBoot
2.Flash recovery http://d-h.st/vFQ
3.Boot in recovery
4.Goto Wipe-> Format Data-> enter 'yes' and click go
5.Flash firmware through sideload(AOSP, Stock, Cm) // If already installed you may skip this
6.1.Flash kernel(FOR CM) http://d-h.st/Bqa
6.2.Flash kernel(FOR AOSP(Stock too ) http://d-h.st/7V8
6.3.Flash kernel(FOR Purity) http://d-h.st/2Yz
7.Reboot in and go through the setting
Code:
ANOTHER KERNELS
[LIST=1]
[*] [URL="http://forum.xda-developers.com/showpost.php?p=50947848&postcount=102"]Franco kernel F2FS[/URL]
[*] [URL="http://forum.xda-developers.com/showthread.php?t=2524557"]Bricked Kernel[/URL]
[/LIST]
Code:
OLD KERNELS(CM)
[LIST=1]
[*] [url]http://d-h.st/Snw[/url] 03-03-2014
[*] [url]http://d-h.st/kGE[/url] 03-05-2014
[*] [url]http://d-h.st/aWU[/url] 03-17-2014
[*] [url]http://d-h.st/GvP[/url] 03-27-2104
[/LIST]
Code:
OLD KERNELS(AOSP)
[LIST=1]
[*] [url]http://d-h.st/6w5[/url] 03-06-2014
[*] [url]http://d-h.st/GCb[/url] 03-27-2014
[/LIST]
Code:
OLD RECOVERY's
[LIST=1]
[*] [url]http://d-h.st/X8v[/url] 03-03-2014
[*] [url]http://d-h.st/p7u[/url] 03-08-2014
[*] [url]http://d-h.st/sbk[/url] 03-17-2014
[*] [url]http://d-h.st/a0x[/url] 03-27-2014
[/LIST]
For Developers
AOSP-F2FS kernel
CyanogenMode-F2FS kernel
Purity-F2FS kernel
Device patches
https://github.com/dennes544/androi...mmit/da7287a70eda7363b28013ac15e8cc899ef0b0a3
https://github.com/dennes544/androi...mmit/534542f9fc89107afba2cb967ac40fed032f6e7f
https://github.com/dennes544/androi...mmit/a947b29ed4fead6618e358cdc0314916639fa024
https://github.com/dennes544/androi...mmit/b1dd255793efdc5dcce4ca60e725c406acc7e868
https://github.com/dennes544/androi...mmit/01584fdec616856da33a47e4f07e0bdf40d0f03a
AND use this patch for f2fs-tools
f2fs-tools you can take here
And use ONLY omnirom's recovery(because only omnirom's recovery have "inline_xattr" patch)
Support me Buy me a juice Click!
Just before anyone jumps into this headfirst, make sure you understand what it is, as the OP is a bit spartan.
http://en.wikipedia.org/wiki/F2FS
One question : what is that ... I understand this not .....
so basically this converts user data partition to a new file system (f2fs) ?
Might be worth a read: http://www.raspberrypi.org/phpBB3/viewtopic.php?f=31&t=65330
Essentially its a lot faster for read/writes compared to EXT4
sykomaniac said:
Might be worth a read: http://www.raspberrypi.org/phpBB3/viewtopic.php?f=31&t=65330
Essentially its a lot faster for read/writes compared to EXT4
Click to expand...
Click to collapse
Yup. Couple of other quick examples from other forums of people trying this:
- http://forum.xda-developers.com/showthread.php?t=2634271
- http://forum.xda-developers.com/showpost.php?p=49979584&postcount=1116&nocache=1&z=358057577411342
Be very careful when using f2fs... Basically it's very very fast, BUT you are stuck with it. You can't flash other kernels, and you can flash only certain roms that support f2fs, otherwise the rom reformats the system partition to ext4. I had this on my galaxy s3, and it got me in tons of trouble when I tried to flash anything to it. I had to go back to stock twice and restore my efs partition... It's a lot of work basically.
@op
please enhance your original post with more info about the F2FS that other can benefit from it.
your thread is a little misty.
thx in advance
cool! been looking forward to this
Nexus 5 F2FS
So, what I should do is to reformat the partitions with the recovery, install CyanogenMod M3 release via sideload, and then do the same thing for your special kernel, right?
Sent from my Nexus 5 using Tapatalk
sorceforge said:
So, what I should do is to reformat the partitions with the recovery, install CyanogenMod M3 release via sideload, and then do the same thing for your special kernel, right?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah.
do I have to install your kernel every time after cm update
willybarca said:
do I have to install your kernel every time after cm update
Click to expand...
Click to collapse
i can create zip with boot and you should just flash him, but yes every time after update
I'm tempted, really tempted. May have to wait till it catches on a bit more. Glad to see real progress here though
Sent from my Nexus 5 using xda app-developers app
So CM is absolutely necessary? With S3 any ROM can be restored after F2FS format and it worked
Sent from my Nexus 5 using XDA Premium 4 mobile app
on s3 f2fs by default, right? on nexus 5 f2fs is port, and so far only on CM
No its not default on the S3, and yes and other CM based ROMs
I will release AOSP-based kernel very soon
dennes544 said:
I will release AOSP-based kernel very soon
Click to expand...
Click to collapse
Awesome! (Y)
Sent from my Nexus 5 using Tapatalk
CM kernel updated!
This is a kernel you can flash on any rom for amami, which uses the caf-based libraries and stock rom.
The most work on this was not done by me, this is more a package of work done by other people.
See the next post for installation instructions.
Features
- f2fs support
- cpuquiet cpu hotplug driver(disabled mpdecision automatically)
- lz4 support and lz4 kernel compression
- optional underclocking to 268 Mhz
- fiops i/o scheduler
- lcd color calibration support
- cpu undervolting support
- enabled zram
- faux123's sound control
- fastcharge support
- dynamic sync control by faux123
- '-Ofast'-optimizations
- 'proc/last-kmsg'
- vibration density sysfs interface
- TWRP recovery with f2fs support(stock-based only)
- [WIP] f2fs-compatible ramdisk(stock-rom only, for aosp-based check this
- init.d support(stock romonly, but already included in the most aosp-based roms)
- disabled ric service(stock only, not needed with aosp-based roms)
- prima wifi module
Issues
- exfat sdcards and usb storage can't get mounted
XDA:DevDB Information
MoshKernel-amami[aosp-based + stock], Kernel for the Sony Xperia Z1 Compact
Contributors
CoolDevelopment, faux123, DooMLoRD, FreeXperia, every android kernel developer
Kernel Special Features:
Version Information
Status: Testing
Current Beta Version: 0.3
Beta Release Date: 2014-09-08
Created 2014-07-16
Last Updated 2014-09-08
Reserved
How to configure cpuquiet
You can configure cpuquiet to the pefect use with your phone. You need root permissions and any shell, i. e. Terminal Emulator.
First run 'su' to get root permissions.
Change the minimum and maximum amount of online cpu cores:
Code:
file for max. amount of online cpus: /sys/devices/system/cpu/cpuquiet/cpuquiet_driver/max_cpus
file for min. amount of online cpus: /sys/devices/system/cpu/cpuquiet/cpuquiet_driver/min_cpus
Example:
echo 3 > /sys/devices/system/cpu/cpuquiet/cpuquiet_driver/max_cpus
echo 2 > /sys/devices/system/cpu/cpuquiet/cpuquiet_driver/min_cpus
The cpuquiet driver supports different governors, a bit like cpufreq governors. The governors which are currently present are: "runnable", "rq_stats", "load_stats", "balanced"
Find the best one for you by yourself
Code:
sysfs file: /sys/devices/system/cpu/cpuquiet/current_governor
Example: echo balanced > /sys/devices/system/cpu/cpuquiet/current_governor
Change the max screen-off cpu frequency and online cpus:
Code:
sysfs file for max. screen-off-freq: /sys/devices/system/cpu/cpuquiet/cpuquiet_driver/screen_off_cap
syfs file for max. screen-off online cpus: /sys/devices/system/cpu/cpuquiet/cpuquiet_driver/screen_off_max_cpus
Example:
echo 960000 > /sys/devices/system/cpu/cpuquiet/cpuquiet_driver/screen_off_cap
echo 1 > /sys/devices/system/cpu/cpuquiet/cpuquiet_driver/screen_off_max_cpus
Disable cpuquiet(and enable mpdecision):
Code:
sysfs file: /sys/devices/system/cpu/cpuquiet/cpuquiet_driver/enabled
Example:
echo 0 > /sys/devices/system/cpu/cpuquiet/cpuquiet_driver/enabled
start mpdecision #enable mpdecision
These settings only stick until you reboot. So better setup an init.d script, which applies your settings every boot.
If you aren't sure, what init.d scripts are, ask google.
Reserved
AOSP-based roms
The kernel for asop-based roms gets flashed using a special .zip, which only flashes zImage and dt. That means, there are no ramdisk-problems, which you didn't got before. The scripts inside the script are also modifying the ramdisk to don't have mpdecision enabled by default.
Installation
1. Flash the zip file through a recovery
Download
https://s.basketbuild.com/devs/CoolDevelopment/MoshKernel-amami/aosp-based/
Source: https://github.com/CoolDevelopment/MoshKernel-amami/tree/caf
Stock rom/Stock-based roms
Installation
1. Be sure you have an unlocked bootloader
2. Be sure you have installed busybox
3. Flash the zip file through a recovery
Download
https://s.basketbuild.com/devs/CoolDevelopment/MoshKernel-amami/stock-based/
Source: https://github.com/CoolDevelopment/MoshKernel-amami/tree/14.4.A.0.xxx
https://github.com/CoolDevelopment/MoshKernel-amami-stock-based-initramfs
Changelog
0.1
- initial commit
0.1.1
- revert back to row as default i/o scheduler
0.1.2
- update f2fs to current upstream
- replace Cyanogenmod branding with mine
- strip kernel modules, you don't need to download 30mb+ anymore
0.2
- removed intelliplug
- added cpuquiet cpu hotplug driver
- automatically disabled mpdecision(the scripts are modifying the ramdisk)
- fastcharge support
- '-O3'-optimizations
- lz4 support and kernel compression
- remove overclocking
0.3
- stock-rom support
. dynamic fsync control by faux123
- changed default configuration for cpuquiet
- prima wifi module for stock rom
- upstreamed f2fs commits from linux 3.17rc4
Any roms, Also cm11?
Inviato dal mio Xperia Z1 Compact
cicci0 said:
Any roms, Also cm11?
Inviato dal mio Xperia Z1 Compact
Click to expand...
Click to collapse
Yes
Whaa!! for CM based ROMs and Sony based ROMs!! that would be interesting,
also I like the idea of not having a ramdisk inside the zip, I'll probably use it for next releases of Pimped kernel,
And did you strip the kernel modules before putting them inside the zip??
the wlan.ko module is 43.5MB!! the kernel's zip is around 35MB!!!! that is alot.
BTW, great work, thanks for contributing again and again for our beloved device,
hope you the best:angel:
OmarEinea said:
Whaa!! for CM based ROMs and Sony based ROMs!! that would be interesting,
also I like the idea of not having a ramdisk inside the zip, I'll probably use it for next releases of Pimped kernel,
And did you strip the kernel modules before putting them inside the zip??
the wlan.ko module is 43.5MB!! the kernel's zip is around 35MB!!!! that is alot.
BTW, great work, thanks for contributing again and again for our beloved device,
hope you the best:angel:
Click to expand...
Click to collapse
I am sorry but it may not work on sony roms, you can try if you want. I didn't test it.
I did not even know that kernel modules can be stripped
Sent from my Xperia Z1 Compact using XDA Premium 4 mobile app
CoolDevelopment said:
I am sorry but it may not work on sony roms, you can try if you want. I didn't test it.
I did not even know that kernel modules can be stripped
Sent from my Xperia Z1 Compact using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well yeah that is the problem, I'm kinda sure that you can't use the same kernel for Sony and AOSP based ROMs in the same time!!
so you should mention in OP or in title that this kernel is for AOSP based ROMs so that users don't get confused...
Also if you haven't searched and found out about the stripping, you can do it by executing this:
<dir-to-toolchain>/bin/arm-eabi-strip --strip-unneeded <dir-to-modules-folder>/*
of course the arm-eabi-strip part depends on what toolchain you're using.
Hopefully that would help.
Works on unofficial slimkat
Sent from my Xperia Z1 Compact using XDA Premium 4 mobile app
It also works great with this : http://download.mokeedev.com/?device=amami
ps: Always love to use the FauxSound Audio/Sound Control and FauxClock apps
Thank You !!!!
:good:
Version 0.1.2:
- update f2fs to current upstream
- replace Cyanogenmod branding with mine
- strip kernel modules, you don't need to download 30mb+ anymore
If you want to use f2fs, I really suggest you to install this, the fixed bugs are really important. Else it is almost unneccessary
@CoolDevelopment
Very nice job! Finally we get a dedicated custom kernel for Amami
Oh and I saw the commits on CM gerrit. Nice job man :good:
I'll try flashing this on PAC. If what you say is true, that it doesn't modify the ramdisk, then it should boot. Otherwise I'll get stuck in a bootloop because PAC has custom jar files.
Finally some exciting development on Amami, testing now
EDIT: just a tip, you should ask a mod to move this thread to original development, because it really belongs there
EDIT2: it works perfectly
Yes it doesnt work on pa aslo :/
ygecesefa said:
Yes it doesnt work on pa aslo :/
Click to expand...
Click to collapse
Please give me details else i can't help
Sent from my Xperia Z1 Compact using XDA Premium 4 mobile app
it work on candykat rom
@cooldevekopment Is it possible to include TWRP instead of CWM in your kernel. I know there is a patch for f2fs that has TWRP buid-in, but anyway.
da900 said:
@cooldevekopment Is it possible to include TWRP instead of CWM in your kernel. I know there is a patch for f2fs that has TWRP buid-in, but anyway.
Click to expand...
Click to collapse
this kernel has no ramdisk, meaning it doesn't contain nether CWM nor TWRP,
whatever recovery you'll flash the kernel through, it won't be replaced with any other recovery
OmarEinea said:
this kernel has no ramdisk, meaning it doesn't contain nether CWM nor TWRP,
whatever recovery you'll flash the kernel through, it won't be replaced with any other recovery
Click to expand...
Click to collapse
Does this mean I can flash it even on a rooted stockrom?? 4.4.4 108 for example
djdana said:
Does this mean I can flash it even on a rooted stockrom?? 4.4.4 108 for example
Click to expand...
Click to collapse
Nope, because it is based on AOSP kernel source, which won't work on Sony based ROMs,
this kernel will only work on AOSP-based (CM-based) ROM..
To bad haha thanks for the quick reply
Shift Lollipop Kernel
This kernel supports only Lollipop AOSP. Should support all roms but not sure about Slim, if it doesn't work for a ROM please upload the boot.img from the ROM and post it here and I will see about adding support. Basically this kernel was developed only for CyanideL ROM but has progressed into a decent standalone kernel from reports as I do not own this device, so I thought I would just go ahead and share it so it was known and people could use it for other Lollipop Roms since I keep the source updated for the ROM I figured a kernel with some features and up to date source would be worth posting. Hopefully you all enjoy it
CPU GOVERNORS: smartass, smartassV2, ondemand, powersave, interactiveX, performance, userspace, zzmoove, wheatley and nightmare
I/O GOVERNORS: noop, deadline, cfq, row, sio
default cpu governor: InteractiveX
default I/O governor: row
F2FS/EXT4
OverClock to 1881
CPU Voltage Control
GPU Step Control
Advanced TCP Controls
Faux Sound Mod
Quick Charge
Compiled with Linaro GCC 4.9.1
Install Instructions: Standard flash in recovery, wiping caches in recommended but usual shouldn't be required
Current version is 3.0
Downloads: Shift Kernel
Thank you and enjoy!!
If you like our work, then maybe you would like to give a small donation or buy me a beer. You know you want to lol :victory:
Donate to @rogersb11
Thank you and ENJOY!!!!!
XDA:DevDB Information
Shift Kernel, Kernel for the AT&T Samsung Galaxy S III
Contributors
rogersb11
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 3.0
Stable Release Date: 2015-02-19
Created 2015-02-20
Last Updated 2015-02-19
Nice work here man ?
GS3-T999L : SOKP-MS-04-KK444
Hey rogersb11. I just installed on my sgh-i747m. Running an alpha self built pacman ROM. I will test it out today and report back results. Thanks for all your contributions in the Dev world. Cheers!!!!
Sent from my SAMSUNG-SGH-I747 using Xparent Cyan Tapatalk 2
exfat?
Thanks! This kernel has been working great on Cyanide L.
Quick question, does it have exfat support built in?
This kernel is working great on Oct-L
jason2678 said:
Thanks! This kernel has been working great on Cyanide L.
Quick question, does it have exfat support built in?
Click to expand...
Click to collapse
Top of my head I'm not sure and I'm not by my build machine to check the source. If it's not I can look into adding it tho. I have it in my they kernel source so I'm sure I can port it over
Thanks. I have a microsd that may be of dubious quality. It works best as exfat. I've found I have to be really cautious with it. I'm pretty sure I didn't try it with cyanide.
Doesn't seem to support exfat, but it's nice and smooth on the official Slim weekly.
Loving your kernel, hey I am wondering about f2fs, is it new? I tried formating my system and data to f2fs flashed shift v2.2 and didn't boot I tried this on cyanide L and I am a currently on it (ext4), if there are different steps I need to take please let me know other wise I am loving v3!!!
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Johnnyy9262 said:
Loving your kernel, hey I am wondering about f2fs, is it new? I tried formating my system and data to f2fs flashed shift v2.2 and didn't boot I tried this on cyanide L and I am a currently on it (ext4), if there are different steps I need to take please let me know other wise I am loving v3!!!
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
You need the kernel changer from the f2fs thread to allow ROM to boot
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Would this work for d2tmo?
gvsukids said:
You need the kernel changer from the f2fs thread to allow ROM to boot
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
Link me? It would be amazing if actually get f2fs working in lollipop [emoji1]
Sent from my SAMSUNG-SGH-I747 using Tapatalk
roogerrisboredd said:
Would this work for d2tmo?
Click to expand...
Click to collapse
Yes it SHOULD. Comes with cyanide ROM and it's for tmobile as well
gvsukids said:
You need the kernel changer from the f2fs thread to allow ROM to boot
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
F2fs ramdisk support was added in 3.0. I only added it for data and cache tho and that's where the improvements are to be had
Shift 3.0 bootloops on CyanideL
I've been running CyanideL with the Shift kernel for a couple of months with no problems. The latest version (20150220) bootloops on me, though. I tried a dirty flash, then factory reset but either way it shows the Samsung flash screen, buzzes and then back. I tried flashing Shift 3.0 separately after this happened, as suggested by @TheGeekyNimrod, but that produced the same result. But then I flashed Shift 2.2 D2 over CyanideL-20150220, and now it's booting fine.
I tried to take a logcat while it was booting with adb logcat>logfile but I got the message -waiting for device- and nothing more. The logifle was empty. Is there another way to take a boottime logcat? My recovery is TWRP 2.8.4.0.
Thanks, @rogersb11, for all your work on this.
pixbuf said:
I've been running CyanideL with the Shift kernel for a couple of months with no problems. The latest version (20150220) bootloops on me, though. I tried a dirty flash, then factory reset but either way it shows the Samsung flash screen, buzzes and then back. I tried flashing Shift 3.0 separately after this happened, as suggested by @TheGeekyNimrod, but that produced the same result. But then I flashed Shift 2.2 D2 over CyanideL-20150220, and now it's booting fine.
I tried to take a logcat while it was booting with adb logcat>logfile but I got the message -waiting for device- and nothing more. The logifle was empty. Is there another way to take a boottime logcat? My recovery is TWRP 2.8.4.0.
Thanks, @rogersb11, for all your work on this.
Click to expand...
Click to collapse
Yea this seems to be a very random issue. Geeky himself has this on a previous kernel I gave him. After failed boot you can boot straight to recovery and pull the last_kmsg. I can't remember exactly the command but a quick search will tell you. That's the kernel log
3.0 running great on Oct-L. Awesome work!
rogersb11 said:
Yea this seems to be a very random issue. Geeky himself has this on a previous kernel I gave him. After failed boot you can boot straight to recovery and pull the last_kmsg. I can't remember exactly the command but a quick search will tell you. That's the kernel log
Click to expand...
Click to collapse
I tried this but there was no last_kmsg. I did get one from a successful boot with the 2.2-D2 kernel; that one said "no errors" at the bottom. But I guess it doesn't get far enough to even create the kmsg file with the 3.0 kernel. The last time I tried it stayed on the Samsung flash screen with the LED pulsing blue for about 10 minutes before I pulled the battery.
pixbuf said:
I tried this but there was no last_kmsg. I did get one from a successful boot with the 2.2-D2 kernel; that one said "no errors" at the bottom. But I guess it doesn't get far enough to even create the kmsg file with the 3.0 kernel. The last time I tried it stayed on the Samsung flash screen with the LED pulsing blue for about 10 minutes before I pulled the battery.
Click to expand...
Click to collapse
If it stays on the Samsung screen very long at all then it's just not gonna boot. Well that's unfortunate man, 3.0 is a massive improvement. Not sure how to help you since almost all haven't had this issue. Maybe next build will work for you. Not sure what else I will add but I'm sure I'll find something. Anybody have any requests?
rogersb11 said:
If it stays on the Samsung screen very long at all then it's just not gonna boot. Well that's unfortunate man, 3.0 is a massive improvement. Not sure how to help you since almost all haven't had this issue. Maybe next build will work for you. Not sure what else I will add but I'm sure I'll find something. Anybody have any requests?
Click to expand...
Click to collapse
You're awesome, I know I'll be happy when a new build comes out that works. Fiops please, and I don't know if f2fs support for sdcard would work but that seems like the best file format for an sdcard to me. :good:
JDC2389 said:
You're awesome, I know I'll be happy when a new build comes out that works. Fiops please, and I don't know if f2fs support for sdcard would work but that seems like the best file format for an sdcard to me. :good:
Click to expand...
Click to collapse
I'll look into fiops. F2fs should work on an sdcard. Kernel supports f2fs cache and data so internal and external should work that way
Cool stuff, I flashed the newest twrp recovery and latest modem/baseband NJ1 using Exodus rom from team Vanir http://www.vanir-exodus.net/exodus/d2att/ shift kernel 2.2 works sortof, zzmoove hardlocks the phone and xposed alpha won't work[works on exo kernel]. 3.0 is broken for me still on a clean flash the splash loads this time then after a bit the screen goes black, oddly enough touching the power button causes a vibrate but other then that phone won't wake. Phone is unresponsive from pc side using adb logcat etc when on 3.0 so I don't know how I would report any bugs.