Develop Bugs

[Kernel] .29 Alpha for Cyanogenmod 5 Based ROMs 【aHero】 - For the Impatient

[Kernel] .29 Alpha for Cyanogenmod 5 Based ROMs 【aHero】 - For the Impatient
Here's a quick and dirty kernel compile with bluetooth and SetCPU OC both working for this ROM (and any Cyanogenmod based Hero ROM really). Should not be overclocking on boot.
Uses koush anykernel format to make it compatible for any CM based ROM.
I don't plan to update this. I had no intentions of making a Hero kernel so I probably wont be updating this. It was kind of an accident. I don't even have a GSM Hero. Anyways flash and enjoy! Devs can take what I did on my .config and make it good. There's some weird stuff in it.
If this eats your phone please do not hunt me down.
jaymac407 said:
Boots, testing more now..
Update: Wifi works, bluetooth works, OC seems to work (I THINK)
Good work.
Click to expand...
Click to collapse
I copied the netfilter options too. If someone can try to see if Wifi-tether works that would be awesome.
So apparently my kernel boots this aHero and fixes bluetooth. It's a .29 kernel based on the new source code.
Mind you that I might be missing some things. I took around 20 minutes comparing the existing .config and making one that is more similar to the Cyanogenmod .config by eyeballing differences and copying pasting code (yes really). I got really lazy toward the end because the .config was so damn long.
I at least enabled squashfs so the .sqf files decompress for sure now. Set localversion to cyanogenmod. You can see what I did to it in the download link as well, where I have a pastebin of what I did before I disabled perflock.
I also disabled a crap load of debug options that were enabled for some reason.
credits:
cyanogen for CM5. Based .config off his ROM
toastcfh for the kernel source code and being the father of all MSM7K overclocks
koush anykernel
.config here:
http://forum.xda-developers.com/showpost.php?p=6548814&postcount=53

how do i use this on ahero ? just flash it over the rom ?

Is this applicable to VanillaEclair?

Just flash this zip over my aHero?

Re: [Kernel] .29 Beta for Cyanogenmod 5 Based ROMs 【aHero】 - For the Impatient
Dont work for me om cyanogen mod, runs so slow it freezes. Cant get in set cpu and look
Sent from my HTC Hero using Tapatalk

going to test this now. I will update.

it sseems to freeze at boot (aHero 1.0 with JIT)

mine freeze at hero screen

Does it need a wipe and reflash first, or should it be ok to try over current CM ROM ( Vanillain 3.0 test version) ?

furrypotato said:
Does it need a wipe and reflash first, or should it be ok to try over current CM ROM ( Vanillain 3.0 test version) ?
Click to expand...
Click to collapse
There specific patches for the villain roms, theres one for Vanillain 3. There is a thread with them on xda
I tired it on Vanillian but cant seem to get past the lockscreen

I downloaded toastcfh's kernel source, but I didn't have time to compile..
anyway thanks for compiling, and I'll test it and report back soon..

Demologic said:
There specific patches for the villain roms, theres one for Vanillain 3. There is a thread with them on xda
I tired it on Vanillian but cant seem to get past the lockscreen
Click to expand...
Click to collapse
And me. Best wait I guess for a fix later.

Heh, awesome.
Be advised that this sometimes freezes randomly, that's the only bug I can see so far. Especially during going from and to sleep. That's the only issue that needs to be resolved. Apart from that, everything seems to work.

jaymac407 said:
Heh, awesome.
Be advised that this sometimes freezes randomly, that's the only bug I can see so far. Especially during going from and to sleep. That's the only issue that needs to be resolved. Apart from that, everything seems to work.
Click to expand...
Click to collapse
Try in setcpu to make the governor performance, if not msm7k
the ondemand governor code was broked in HTC source in .27

can i download the zip and flash it on ahero 1.0????

xaueious said:
Try in setcpu to make the governor performance, if not msm7k
the ondemand governor code was broked in HTC source in .27
Click to expand...
Click to collapse
Only options are performance and ondemand. Neither option seems to help with the crashes.

i have downloaded the zip on first page and flash over ahero 1.0 without JIT my phone boots and come to lockscreen and then i cant anything

[ROM][Unofficial/Experimental][Android 4.3] CyanogenMod 10.2 for SGS4A (int'l)

-------------------------Warning!-------------------------------------
This ROM is for SGS4A (int'l) ONLY. Does not work on SGS4 from AT&T as it has a locked bootloader.
Please refer to this thread for a bounty on the bootloader.
-------------------------Please note---------------------------------
This is an experimental build of CyanogenMod 10.2 running Android 4.3.
Meaning there's a couple of known issues with the camera. It is my hope these will be sorted out over time.
If anyone has any interest in helping out, please PM me. Or simply fork the code if you want.
-------------------------Instructions---------------------------------
Install CWM recovery from here.
Download most recent ROM from here.
Download most recent Google Applications for Android 4.3 from here.
Boot into recovery by holding the Volume Up button as the phone is booting.
Back up your current ROM inside CWM recovery.
Flash CyanogenMod ROM to your device using CWM recovery.
Flash Google Applications to your device using CWM recovery.
Do a wipe data/factory reset from within CWM recovery.
Reboot system
---------------------------Known issues-----------------------------
Several camera functions such as HDR don't work.
---------------------------Build from source------------------------
Please consult this guide for setting up CyanogenMod for compile.
Please use
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
when you initialize the CyanogenMod repository so you get the source for CM-10.2.
Download roomservice.xml (see below) and put in ~/android/system/.repo/local_manifests/.
Run 'repo sync' and compile with 'brunch jactiveltexx'. You can get the proprietary files from the ROM.
As always, I take no responsibility in case your phone blows up.
And thanks to the CM team for all their hard work.

Downloads
---------------------------CM-10.2 ROM (Android 4.3) -------------------
---------------------------cm-10.2-20130917-----------------------------------
CyanogenMod 10.2 - 20130917
CyanogenMod 10.2 - 20130917 (mirror - thanks to mrvovven)
---------------------------cm-10.2-20130910-----------------------------------
CyanogenMod 10.2 - 20130910
CyanogenMod 10.2 - 20130910 (mirror - thanks to mrvovven)
---------------------------CM-10.1 ROM (Android 4.2.2) ----------------
CyanogenMod 10.1 - 20130810
----------------------------Google apps -------------------------------
Download the official Google apps. Need to download this in order to have apps like Google Play.
For CM-10.1 choose Android 4.2 apps.
For CM-10.2 choose Android 4.3 apps.
http://goo.im/gapps
------------------------------------- KERNELS ---------------------------------
- SGS4A android 4.2.2 kernel for CM10.1
https://www.dropbox.com/s/oo1hr2n6evp3zu9/sgs4a-cm10-1kernel.zip

----------------------- Changelog--------------------
-------CyanogenMod 10.2 - 20130917----------
- Fixed video preview resolution
- Disabled zsl for slightly more stable camera app.
-------CyanogenMod 10.2 - 20130910----------
- Updated kernel to most recent version of cm-10.2 for SGS4.
- Replaced all sensor drivers with SGS4A kernel sources.
- Replaced several camera blobs in /system/lib/* with SGS4A versions enabling basic camera functionality.
-------CyanogenMod 10.1 - 20130810----------
Initial build.

Good job.
Sent from my Nexus 7 using Tapatalk 4

hello
anyone tried this out ?
feedbacks ?
thanks in advance

pdf5 said:
hello
anyone tried this out ?
feedbacks ?
thanks in advance
Click to expand...
Click to collapse
This is not something you should install unless you want to be compiling and debugging yourself. It's far from usable as day to day rom. I hope I'm clear on that.

Fixed wifi and a number of small issues. Should be a lot more stable. Seems the main remaining issue is, not surprisingly, the camera. If anyone knows how the entire camera driver setup is supposed to work in android, I'd love some help

LeJay said:
Fixed wifi and a number of small issues. Should be a lot more stable. Seems the main remaining issue is, not surprisingly, the camera. If anyone knows how the entire camera driver setup is supposed to work in android, I'd love some help
Click to expand...
Click to collapse
Call it just a hunch. But have you tried the camera drivers from the s3 ? I would say that it's basically the same camera and has been added in s4 active because after 1 year it became very cheap to continue manufacturing and this way compensate for the more expensive case and water proofing.

aurelm said:
Call it just a hunch. But have you tried the camera drivers from the s3 ? I would say that it's basically the same camera and has been added in s4 active because after 1 year it became very cheap to continue manufacturing and this way compensate for the more expensive case and water proofing.
Click to expand...
Click to collapse
Honestly, not exactly sure how the setup is. I assume it's mostly in some proprietary libs separate from the kernel, but it's hard to find good information on it.
Sent from my GT-I9295 using xda premium

Thank you for you work!!
But search another File hoster!! DropBox close your account if the trafic is to big!!

So S4 Active Original is the intl i9295 ?
EDIT: oh ok the real dev thread
Sent from my GT-I9295 using xda app-developers app

I've a MicroSD in my SGS4A and i can't choose the external_sd in the CM File Explorer.
Is there any solution?
For example creating symlink or mounting in /sdcard
I've never tried anything of that!

It's working really well Wifi works yay, well done! Hopefully you can get the camera working too.

Building from source
Hi,
I'm happy to see such great progress already, and am only diving in to this because I'd like to be able to lend a hand in any way I can.
Is it too soon to be asking questions about how to build for 10.2? I'm having a go at it right now, and if I use Lejay's kernel and device configuration (jactivelte), the kernel fails to compile, something about BUG_ON rcu error, I can come back to that if its relevant. So I tried Epsylon3's suggestion to use tpruvot's kernel and device config. This builds a rom, but black screen, can't see anything or get into adb. If I flash Lejay's kernel over the top of my 10.2 build, it boots. Phone (dialer) keeps force closing in a loop, which is annoying, but asides from that it seems to boot.
Keep up the good work, can't wait to get some 10.2 love.

snadge said:
Hi,
I'm happy to see such great progress already, and am only diving in to this because I'd like to be able to lend a hand in any way I can.
Is it too soon to be asking questions about how to build for 10.2? I'm having a go at it right now, and if I use Lejay's kernel and device configuration (jactivelte), the kernel fails to compile, something about BUG_ON rcu error, I can come back to that if its relevant. So I tried Epsylon3's suggestion to use tpruvot's kernel and device config. This builds a rom, but black screen, can't see anything or get into adb. If I flash Lejay's kernel over the top of my 10.2 build, it boots. Phone (dialer) keeps force closing in a loop, which is annoying, but asides from that it seems to boot.
Keep up the good work, can't wait to get some 10.2 love.
Click to expand...
Click to collapse
Comparing the 9295 and 9505 kernels, there's quite a lot of differences. Cyanogenmod tried to merge the two, but apparently gave up. The question is really if we should start with the 9505 and add the camera or start with the 9295 and make it compatible for CM. The stuff i uploaded here is a port of the 9505 kernel, but now I'm looking into starting out with the 9295 kernel instead.
The problem with 10.2 is of course there's no released 9295 kernel for android 4.3. I'm guessing there are not that many differences, so it might not be too hard.
I think I'm getting the same compile error you were with 10.2. Not sure what it means.

Are you going to try to make CM 10.2?

LeJay said:
Comparing the 9295 and 9505 kernels, there's quite a lot of differences. Cyanogenmod tried to merge the two, but apparently gave up. The question is really if we should start with the 9505 and add the camera or start with the 9295 and make it compatible for CM. The stuff i uploaded here is a port of the 9505 kernel, but now I'm looking into starting out with the 9295 kernel instead.
The problem with 10.2 is of course there's no released 9295 kernel for android 4.3. I'm guessing there are not that many differences, so it might not be too hard.
I think I'm getting the same compile error you were with 10.2. Not sure what it means.
Click to expand...
Click to collapse
I had a chat with noobnl about it, and he pointed out a patch on gerrit: http://review.cyanogenmod.org/#/c/44552/
I spent hours manually merging it with cm jf kernel, to finally end up with a kernel that gives me. You guessed it, a black screen. After investing about a days worth of effort into it, I ended up with a buggy unstable CM10.2 build, that will boot if I flash LeJay's kernel zip, but its unuseable. It's going to take some serious effort to come up with a functioning CM10.2 kernel for the International S4 Active. In the meantime, a CM10.1 build with a non functioning camera, is still way better than the stock TouchWiz rom, so I'm happy. :laugh:

Ok, I got bored and had another play around with 10.2 and the CM jf kernel. With the black screen problem, if you power the device down, then boot into recovery (power + vol up), you can adb pull /proc/last_kmsg and it tells an interesting story. It looks like the init scripts are totally borked. init.qcom.rc and init.carrier.rc are completely missing. I tried simply copying them into the root, but it looks like its a bit more complicated than that. The problem is clear that it is unable to mount /system for whatever reason, because it can't find /system/bin/sysinit, then pretty much gives up after that.
This looks like a pretty simple problem for a relatively experienced device maintainer, or rom kernel dev to be able to fix. It would be nice if we could get some more developer attention for this device.

snadge said:
Ok, I got bored and had another play around with 10.2 and the CM jf kernel. With the black screen problem, if you power the device down, then boot into recovery (power + vol up), you can adb pull /proc/last_kmsg and it tells an interesting story. It looks like the init scripts are totally borked. init.qcom.rc and init.carrier.rc are completely missing. I tried simply copying them into the root, but it looks like its a bit more complicated than that. The problem is clear that it is unable to mount /system for whatever reason, because it can't find /system/bin/sysinit, then pretty much gives up after that.
This looks like a pretty simple problem for a relatively experienced device maintainer, or rom kernel dev to be able to fix. It would be nice if we could get some more developer attention for this device.
Click to expand...
Click to collapse
You probably forgot to add jactivelte to the list at the bottom of device/jf-common/Android.mk. I didn't want to fork their repo just to add one word on a line, so you have to do this manually. It's probably also a good idea to extract rom files from a cm.10.2 rom for something like jfltexx.

LeJolly said:
Are you going to try to make CM 10.2?
Click to expand...
Click to collapse
I have cm10.2 running. The problem is really the camera.

[KERNEL] [GPL] [4.4] FuguMod kernel for nexus 5 (secure)

FuguMod is a secure, open, reliable and no nonsense kernel
This is probably the only custom kernel for the Nexus 5 which adds security instead of removing it.
Current features are:
- compiled with linaro gcc4.7.4
- various small fixes
You can download the kernels at:
http://fugumod.org/nexus5
Source and changelog can be found here:
https://github.com/renaudallard/nexus5_kernel
IRC channel:
irc.freenode.net #fugumod
Flashing
Kernel zips are intended to be flashed with CWM ot TWRP, if you want to flash using fastboot, you need to unpack the zip and flash the boot.img which is inside
Versions
Kernels are based on the below version scheme
kernel_FuguMod_20131104_r1-4.4.img
20131104 is the date it has been packaged
r1 is the release number
4.4 is the ROM it is compatible with
Stable vs Testing
There are sometimes kernels in testing folder. These may be very stable or may not boot at all. Be sure to have an USB cable and fastboot under the hand if you try one of these. That said, in general, if they stay into testing folder for more than 15 min, they should at least boot and work more or less. I tend to remove non booting kernels from testing folder in less than 10 min (depending a little bit on the speed testers take them), and so if you see them one hour later, you should assume they are safe enough to flash.
So, in general Stable is the safest bet, but Testing may be the best. I, myself, generally run testing one.
Deprecated folder
In general, unless you really know what you are doing, you should avoid flashing those, they are mainly there for historical reasons.
Check for vulnerabilities
http://www.xray.io
Compatibility with hackish style apps
All apps which require direct memory write, access to symbols or memory offsets or modules will NOT work. And, no, don't ask they won't be supported in the future. Example: Arararagi's light is only provided as a module and will not be supported unless he produces a patch.
Security
If you want good security when your phone is stolen, in addition to encryption, don't forget to turn debugging off. Also, use enpasschanger to change your encryption password, any short PIN encryption can be cracked in a few minutes easily (for example, using my script at http://pastebin.com/Mdu06RZN)
Redistribution
As per GPL, you are authorized to redistribute this kernel with any of your custom ROMs provided you give out the source code like I do. You can link to my github in your distribution site.
However, if you modify the kernel yourself, whatever the modification is (compiling it yourself with a different compiler is a modification), you are not authorized to name it FuguMod, although you can credit me and tell the base comes from FuguMod but you cannot call the kernel itself FuguMod.
XDA:DevDB Information
FuguMod, a Kernel for the Google Nexus 5
Contributors
renaud, http://forum.xda-developers.com/member.php?u=2859799
Kernel Special Features: Open, stable, reliable and secure
Version Information
Status: Testing
Created 2013-11-04
Last Updated 2014-01-29

Glad to see you here renaud. I loved your Galaxy Nexus kernels.

First test version is now available
If anyone can confirm it was flashed correctly and boots, that would be great.

I'll test it right after the postman makes me happy

Haeretik said:
I'll test it right after the postman makes me happy
Click to expand...
Click to collapse
Just got a confirmation that mine will come tomorrow

flashed kernel_FuguMod_20131104_r1-4.4.zip and it reboots to bootloader.

Hello @renaud.
It's really nice to find a lot of people coming from Galaxy Nexus to the Nexus 5. As the Galaxy Nexus is an oldie (yes, two years), there are less and less threads supported. I hope, you will still support the Galaxy Nexus - but also the Nexus 5, of course. Good to have you in here! :laugh:

proxuser said:
flashed kernel_FuguMod_20131104_r1-4.4.zip and it reboots to bootloader.
Click to expand...
Click to collapse
When flashing or when booting?

renaud said:
When flashing or when booting?
Click to expand...
Click to collapse
after booting, i flashed it via bootloader.

proxuser said:
after booting, i flashed it via bootloader.
Click to expand...
Click to collapse
I suppose you meant you flashed with fastboot.
Whatever, till how far does it go?
I am wondering, did you unpack the zip and flashed boot.img through fastboot, or did you flash the whole zip through fastboot??

I'm glad you got the new nexus because I've been waiting for your kernels for awhile now.
Sent from my Nexus 4 using Tapatalk

tried out your kernel, alot of nice features but stock seemed to run faster. cant wait to see what the community has to offer over the next couple of months. pushing the phone to its limits / extending battery life.

dandwhelan said:
tried out your kernel, alot of nice features but stock seemed to run faster. cant wait to see what the community has to offer over the next couple of months. pushing the phone to its limits / extending battery life.
Click to expand...
Click to collapse
Thank you for confirming that it boots. Currently it has no features except being smaller than the stock one. I was waiting for the boot confirmation before developing.

Nice to see you again Renaud. Glad to be owning a device you're deving on again.

I have now received my N5. Real stuff will begin.

OK, thanks for some reporting as booting, but in fact it does not because my img doesn't support dtb yet.

Glad you got the phone and now hopefully fugukernel updater will work for this phone.
Sent from my Nexus 5 using Tapatalk

unforgivenmercy said:
Glad you got the phone and now hopefully fugukernel updater will work for this phone.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I was not doing it myself, but I guess I can ask for the code to not have to rewrite everything by myself

r3 is out.
It boots and is compiled with linaro GCC 4.8
Further optimizations are on the road.

Whats with colour calibration?
Sent from my Nexus 5 using xda app-developers app

[DEV] AOSP-Based ROM Development Thread

Since joshuabg posted his build of AICP, countless other people decided they would continue his mission of bringing AOSP-based custom roms to this wonderful device
however in doing this people started stealing the AICP thread to talk about compile problems(i know im the biggest offender) so im fixing that.
Post all ROM development talk below so we can attempt to help each other and get the rom problems out of the way and finally get development for this amazing, game-changing, sexy slice android off the ground
Hey guys, if anyone is looking for how to build a rom for the nexus 9(and theyre forced to use a prebuilt kernel) i wrote up a tutorial on how to do that at the top of page 5:
http://forum.xda-developers.com/nex...evelopment-thread-t2995510/page5#post58089268

Based on my convo with Josh, he indicated that disabling SELinux in the prebuilt kernel (with help from USBHost) would assist in allowing the build to boot. However, I honestly do not want to disable SELinux AT ALL. I will find a way to make this work without disabling SELinux.

The issues I had with getting the AICP to boot without a Setup Wizard has stopped loop was 100% to blame on SELinux. ROM was disabled kernel was enforcing, and they didn't want to play nicely together. As soon as I used a kernel with SELinux disabled, it booted right up no problems. Should someone maybe ask flar2 with a mention in here to get his two cents?

SwoRNLeaDejZ said:
The issues I had with getting the AICP to boot without a Setup Wizard has stopped loop was 100% to blame on SELinux. ROM was disabled kernel was enforcing, and they didn't want to play nicely together. As soon as I used a kernel with SELinux disabled, it booted right up no problems. Should someone maybe ask flar2 with a mention in here to get his two cents?
Click to expand...
Click to collapse
i dont think thats right...i could be doing something wrong, but im fairly certain that when i compiled by build i set both the ROM and Kernel to SElinux disabled(or at least enforcing) and the kernel wouldnt even try to boot...
however, i do have to say that im not 100% certain how to disable SElinux in the ROM so i did what i thought would work, so maybe thats why mine doesnt boot...once i figure out compiling this kernel and either praise you or stand by my point
also i havent heard anything of flar2 since november 24th so idk what happened there

zawata said:
i dont think thats right...i could be doing something wrong, but im fairly certain that when i compiled by build i set both the ROM and Kernel to SElinux disabled(or at least enforcing) and the kernel wouldnt even try to boot...
however, i do have to say that im not 100% certain how to disable SElinux in the ROM so i did what i thought would work, so maybe thats why mine doesnt boot...once i figure out compiling this kernel and either praise you or stand by my point
also i havent heard anything of flar2 since november 24th so idk what happened there
Click to expand...
Click to collapse
You could very well be right. All I was speaking from was my experience of every kernel I tried using that didn't have SELinux disabled, the build wouldn't boot.

SwoRNLeaDejZ said:
You could very well be right. All I was speaking from was my experience of every kernel I tried using that didn't have SELinux disabled, the build wouldn't boot.
Click to expand...
Click to collapse
what do you mean by not boot? like exacty? because for me, a kernel not booting means stuck at the google splash screen

The ROM does not control selinux
Only the kernel controls it

Well guys, i finally got CM to build without breaking a few days ago but the kernel didnt work so i did a bunch of testing a research and i think ive concluded that theres something wrong with the build process that breaks the kernels, once i figure out what, we'll have the reliable build system that doesnt rely on prebuilt kernels
on a side note i figured out how to build AOSP with prebuilt kernels
SO we finally have a CM build that can stand on its own and run well(shockingly well, i havent found any problems) and it doesnt rely on USBhost's feature-rich kernel or his prebuilt one that no-one really understands...lol no offense intended usbhost, FIK is pretty damn good
@SwoRNLeaDejZ : selinux is currently disabled so im going to see what happens when i renable it @USBhost : is SElinux disabled the same thing as permisive? im guessing no and which one would be the best to set for a custom rom. im guessing permissive?

zawata said:
Well guys, i finally got CM to build without breaking a few days ago but the kernel didnt work so i did a bunch of testing a research and i think ive concluded that theres something wrong with the build process that breaks the kernels, once i figure out what, we'll have the reliable build system that doesnt rely on prebuilt kernels
on a side note i figured out how to build AOSP with prebuilt kernels
SO we finally have a CM build that can stand on its own and run well(shockingly well, i havent found any problems) and it doesnt rely on USBhost's feature-rich kernel or his prebuilt one that no-one really understands...lol no offense intended usbhost, FIK is pretty damn good
@SwoRNLeaDejZ : selinux is currently disabled so im going to see what happens when i renable it @USBhost : is SElinux disabled the same thing as permisive? im guessing no and which one would be the best to set for a custom rom. im guessing permissive?
Click to expand...
Click to collapse
I built a stock kernel that's so awesome that no one can comprehend or understand it
Haha aren't I awesome lol
About selinux if its disabled
It means it was not compiled with the kernel
so you can't simply enable it
I would recommend permissive on the kernel command line
So it would be easier to debug what is preventing stock kernel from not booting
Because you can see what would have selinux prevented from running
on /proc/kmsg or /dev/kmsg

USBhost said:
I built a stock kernel that's so awesome that no one can comprehend or understand it
Haha aren't I awesome lol
About selinux if its disabled
It means it was not compiled with the kernel
so you can't simply enable it
I would recommend permissive on the kernel command line
So it would be easier to debug what is preventing stock kernel from not booting
Because you can see what would have selinux prevented from running
on /proc/kmsg or /dev/kmsg
Click to expand...
Click to collapse
haha well no one could figure out how to use it(but i did I FIGURED YOU OUT!! YOUR A PHONY!!) jokes aside though
so setting permissive in the boardconfig.mk? :
BOARD_KERNEL_CMDLINE := androidboot.selinux=permissive
then make menuconfig and re-enable the options you told me to disable in tha PM(i dont fee like typing them out lol)

zawata said:
haha well no one could figure out how to use it(but i did I FIGURED YOU OUT!! YOUR A PHONY!!) jokes aside though
so setting permissive in the boardconfig.mk? :
BOARD_KERNEL_CMDLINE := androidboot.selinux=permissive
then make menuconfig and re-enable the options you told me to disable in tha PM(i dont fee like typing them out lol)
Click to expand...
Click to collapse
Yep that should do it
If not tell me

USBhost said:
Yep that should do it
If not tell me
Click to expand...
Click to collapse
currently building the boot image(btw im using your flashable zip as a base thanks )
will report back
EDIT: hmm nope it didnt seem to work, i think it might have been my fault ill tryt it again

USBhost said:
Yep that should do it
If not tell me
Click to expand...
Click to collapse
im not sure if its me being stupid or something else but i cant reenable SElinux
im thinking its because i dont know if im specifying the right config file...im not 100%
maybe you could just give me a kernel binary with selinux reenabled but not tonight, i should really get to sleep lol

zawata said:
im not sure if its me being stupid or something else but i cant reenable SElinux
im thinking its because i dont know if im specifying the right config file...im not 100%
maybe you could just give me a kernel binary with selinux reenabled but not tonight, i should really get to sleep lol
Click to expand...
Click to collapse
Lol will do

CM compiles fine for me with prebuilt kernel and a few minor source changes. I have a zip from 1/6/15 if anybody will like to test (I really don't feel like wiping right now lol)
Sent from my SCH-I545 using Tapatalk

joshuabg said:
CM compiles fine for me with prebuilt kernel and a few minor source changes. I have a zip from 1/6/15 if anybody will like to test (I really don't feel like wiping right now lol)
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
yeah what im trying to do now is get it to compile now straight from source(figure out why it wont) and also prepare the kernel for build teams to want to take it
i actually have CM(built on the 5th) and my kernel(no changes but selinux disabled(working on it)) running on my tablet right now and im shocked by how smooth it is! its amazing!

zawata said:
yeah what im trying to do now is get it to compile now straight from source(figure out why it wont) and also prepare the kernel for build teams to want to take it
i actually have CM(built on the 5th) and my kernel(no changes but selinux disabled(working on it)) running on my tablet right now and im shocked by how smooth it is! its amazing!
Click to expand...
Click to collapse
CM android_build currently does not support arm64 kernels
Sent from my SCH-I545 using Tapatalk

Just throwing this out there, but if anyone comes up with any type of test builds, or test kernels, that they need someone to flash and try out, let me know. Always more than willing to give some experimental builds a test drive.

joshuabg said:
CM android_build currently does not support arm64 kernels
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yeah I know, which is why I'm going to *hackily implement it*(until Steve finishes his implementation) or cherry pick his attempt and see if I can get it too work
I just got off work(I hate training!!!) And I'll see what I can do about it
I will not deny that anything the CM team will cook up, will be miles better than what I can make but I'm just trying to make it build for a single device, not all of the devices it a super efficient manner
Actually I think I might start some unnoficial nightlies for CM if people want, once I finish my build script then I shouldnt have very much difficulty making it each night
SwoRNLeaDejZ said:
Just throwing this out there, but if anyone comes up with any type of test builds, or test kernels, that they need someone to flash and try out, let me know. Always more than willing to give some experimental builds a test drive.
Click to expand...
Click to collapse
lol bold offer, you're so brave, unlucky for you though, this is a nexus device so if know it boots then we pretty much know everything works so the beta testing isnt as necessary as say on a samsung/htc/lg device,
however, ill see if i can find something i need testing
EDIT: device is now selinux status: permissive(apparently i still dont know how to build kernels...lol but i figured it out)

zawata said:
Yeah I know, which is why I'm going to *hackily implement it*(until Steve finishes his implementation) or cherry pick his attempt and see if I can get it too work
I just got off work(I hate training!!!) And I'll see what I can do about it
I will not deny that anything the CM team will cook up, will be miles better than what I can make but I'm just trying to make it build for a single device, not all of the devices it a super efficient manner
Actually I think I might start some unnoficial nightlies for CM if people want, once I finish my build script then I shouldnt have very much difficulty making it each night
lol bold offer, you're so brave, unlucky for you though, this is a nexus device so if know it boots then we pretty much know everything works so the beta testing isnt as necessary as say on a samsung/htc/lg device,
however, ill see if i can find something i need testing
EDIT: device is now selinux status: permissive(apparently i still dont know how to build kernels...lol but i figured it out)
Click to expand...
Click to collapse
Love the unofficial nightlies idea

[KERNEL] [SHIFT][AOSP][LOLLIPOP]

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.