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
Related
[ 02/09/2012: Screen Flicker / Brightness is an issue. I'll be looking at it. ]
Hi guys,
In an attempt to help further kernel development for the Kindle Fire, I'd like to share my stock defconfig. It's a bit different than the original otter_android_defconfig that g1011999 came up with.
I was never able to get a usable kernel. So I took some time and built up mine.
https://github.com/KFire-Android/kernel_omap/blob/stock/arch/arm/configs/otter_android_defconfig
This kernel builds using the preferred TI compiler used in all of their walk-thrus: CodeSourcery 2010-q1
Moving forward into CM9/ICS, some changes need to happen to the kernel over time. The migration kernel is found in a branch: "L27.13.1-ICS". The END result of this will be a kernel / source that fully support hw codecs for ICS.
[02/08/2012] FLASH ZIP FOR THOSE RUNNING NIND'S BUILDS: http://bit.ly/xYOf0V
The following ROM is built from the sources at GitHub under the KFire-Android org. Many of those files and configurations are the result of countless hours of development by JackpotClavin. I don't want there to be any confusion as to who put in a ton of time getting this to work.
[02/09/2012] FULL ROM INSTALL: http://bit.ly/ygVvQB
Changelog:
- Screen flicker IS an issue right now. Digging into it
- Touchscreen "Slop" set to 16. This should help touches register on the touchscreen.
- Working Data usage stats (xt_qtaguid / xt_quota2 kernel modules)
- TUN, CIFS support
- USB mounting fixes
Thanks Hashcode, currently building a latest ICS version of it.
A little note for those who also want to compile: arm-eabi-4.4.3 and arm-eabi-4.4.0 did not work for me, they ended the compile without any errormessage in the middle of nowhere, arm-eabi-4.3.1 did the job. Took me some time to figure that out ...
nind said:
Thanks Hashcode, currently building a latest ICS version of it.
A little note for those who also want to compile: arm-eabi-4.4.3 and arm-eabi-4.4.0 did not work for me, they ended the compile without any errormessage in the middle of nowhere, arm-eabi-4.3.1 did the job. Took me some time to figure that out ...
Click to expand...
Click to collapse
If you want to follow a very good step by step guide for setting this up the same way TI (the CPU maker) intended, then follow this:
http://www.omappedia.com/wiki/PandaBoard_L27.12.1-P2_Release_Notes#Setting_up_build_environment
Obviously, that's for PandaBoard, but the Toolchain source and setup are very good.
It goes into deep sleep for me and turning off the stay awake option in settings, developer options, the screen goes off like its supposed to.
Hashcode said:
Hi guys,
In an attempt to help further kernel development for the Kindle Fire, I'd like to share my stock defconfig. It's a bit different than the original otter_android_defconfig that g1011999 came up with.
I was never able to get a usable kernel. So I took some time nd built up mine.
https://github.com/KFire-Android/kernel_omap/blob/stock/arch/arm/configs/otter2_android_defconfig
This kernel builds using the preferred TI compiler used in all of their walk-thrus: CodeSourcery 2010-q1
Tonight, I'll go back to both of my in-progress kernels and do some testing to see if they'll boot.
EDIT:
Current issues being looked at with this kernel:
- Power off doesn't really power all the way down. It goes to a black screen, but requires long press to turn off.
- Deep sleep isn't happening. The backlight is on a tad while the screen should be off.
But this config is still MUCH better than trying the original.
Click to expand...
Click to collapse
So does this boot cm7 or anything? My kernel builds boot stock kindle but not cm7
Its something to do with netd/dnsproxyd. Just finding a fix that works is a PITA common issue, but then people dont say how they fixed it..
Right now ive only tested this with CM9
Sent from my DROID RAZR using XDA App
touch points
Any chance you're looking into enabling more than 2 touch points in this kernel?
foxdog66 said:
It goes into deep sleep for me and turning off the stay awake option in settings, developer options, the screen goes off like its supposed to.
Click to expand...
Click to collapse
I'm running nind/sitic's cm9-02-04 build with this kernel baked in. I, too, have Stay Awake disabled in Developer Options, and my Kindle is going into deep sleep. I am experiencing the power down issue, though.
It's something I'm absolutely willing to live with for the time being. This is good stuff. Thanks Hashcode!
jabdo79 said:
Any chance you're looking into enabling more than 2 touch points in this kernel?
Click to expand...
Click to collapse
Thats really the future of this kernel. I needed a solid base to start from.
Sent from my DROID RAZR using XDA App
Well reason I asked was because my kernel wont boot cm7 or cm9. It boots the stock kindle fire os okay. Im getting netd/dnsproxyd errors in the kernel when I try booting cm7.
death2all110 said:
Well reason I asked was because my kernel wont boot cm7 or cm9. It boots the stock kindle fire os okay. Im getting netd/dnsproxyd errors in the kernel when I try booting cm7.
Click to expand...
Click to collapse
Right now the difference between this kernel and stock is:
- About 8 ip6 netfilter modules were added
And that's about it.
death2all110 said:
Well reason I asked was because my kernel wont boot cm7 or cm9. It boots the stock kindle fire os okay. Im getting netd/dnsproxyd errors in the kernel when I try booting cm7.
Click to expand...
Click to collapse
Are you using the stock ramdisk or the modified ramdisk for cm? I know there must be a difference, as intersectRaven puts out several different variations of his kernel in boot.img form, but I haven't gotten around to diffing them yet
wdfowty said:
Are you using the stock ramdisk or the modified ramdisk for cm? I know there must be a difference, as intersectRaven puts out several different variations of his kernel in boot.img form, but I haven't gotten around to diffing them yet
Click to expand...
Click to collapse
ill look into insectraven's cm kernel thanks!
Edit: That worked! Thanks!
he starts the dnsproxyd differently than what I've seen. But it works!
So I noticed that /mnt/ is mounted read-only which causes issues with apps installing to the sdcard and probably the issue people are having with mounting the sdcard to the computer. Some apps insist on installing to the sdcard (I hate that)
Edit: or do I have this all wrong? Lol I'm no dev remounting it r/w gets the job done.
Is there any websites or anything that you guys would recommend to learn about the Linux kernel and development of it?
Tonight, I went back through and cleaned up my config some more. Removed extra power controls, usb mtp settings and omap mmc host controller (for sd card slot boards).
From my tests, everything deep sleeps correctly and the power off issue is fixed.
https://github.com/KFire-Android/kernel_omap
will you be posting a installable zip or boot.img? I'm running nind's cm9-02-05 build which has this kernel and its by far the most stable for me. I would like to update without waiting for someone to include it in a rom please
foxdog66 said:
will you be posting a installable zip or boot.img? I'm running nind's cm9-02-05 build which has this kernel and its by far the most stable for me. I would like to update without waiting for someone to include it in a rom please
Click to expand...
Click to collapse
I'll see what I can do. boot.img would be ok?
Sent from my XT912 using XDA App
Hashcode said:
I'll see what I can do. boot.img would be ok?
Sent from my XT912 using XDA App
Click to expand...
Click to collapse
Yeah that's cool.
foxdog66 said:
Yeah that's cool.
Click to expand...
Click to collapse
Here's an updated boot.img for nind's 2/5 build:
[ UPDATED OP W/ FLASH.ZIP FILE ]
looking for a kitkat kernel that is all stock but with selinux toggled to permissive. my only objective is to run linux on top of android. anyone who has a guide to getting this compiled would get his thank meter filled:good:
edit: kind @xluco has built a kernel just for us:
http://forum.xda-developers.com/show....php?t=2756679
ionflux said:
looking for a kitkat kernel that is all stock but with selinux toggled to permissive. my only objective is to run linux on top of android. anyone who has a guide to getting this compiled would get his thank meter filled:good:
edit: for p600. thanks!
Click to expand...
Click to collapse
I am looking for this too. You can download the kernel source from samsung. I wonder whether, if you build without reconfiguring, you end up with the stock kernel. I would try doing this and only changing selinux mode if I thought there was a reasonable chance it would work. Did you try this kernel ?
http://forum.xda-developers.com/showthread.php?t=2725193
I have not yet. But I have zero interest in performance tweaks that might reduce stability.
injola said:
I am looking for this too. You can download the kernel source from samsung. I wonder whether, if you build without reconfiguring, you end up with the stock kernel. I would try doing this and only changing selinux mode if I thought there was a reasonable chance it would work. Did you try this kernel ?
http://forum.xda-developers.com/showthread.php?t=2725193
I have not yet. But I have zero interest in performance tweaks that might reduce stability.
Click to expand...
Click to collapse
i'm currently using it and helping the dev wherever i can. selinux is disabled on that kernel, so i'm running linux deploy just fine.
i'm not sure about compiling the kernel from source because i don't have a linux box and i'm scared of something going wrong if i flash or configure it wrongly BUT if even anyone can show me the guide to doing this i would be very grateful
ionflux said:
i'm currently using it and helping the dev wherever i can. selinux is disabled on that kernel, so i'm running linux deploy just fine.
i'm not sure about compiling the kernel from source because i don't have a linux box and i'm scared of something going wrong if i flash or configure it wrongly BUT if even anyone can show me the guide to doing this i would be very grateful
Click to expand...
Click to collapse
I was trying to edit my last post because I saw that you have tried that kernel.
I have spent way more time compiling kernels over the past 20 years than I care to, which is one reason I haven't tried this task yet. I flashed the pre-kitkat selinux permissive kernel a while back and it simply wouldn't boot. I had saved the stock kernel with online nandroid backup. I reflashed stock kernel and there was no problem. I guess, the same would happen with an any unbootable kernel. I never have built an android kernel though.
Here you go guys, try this.. Stock KitKat kernel with SELinux in permissive mode and Knox removed: d-h.st/uCX
EDIT: slight update with NTFS support / HTCP and Multi-core scheduler support.. all completely stable as they're already in the kernel just not selected
EDIT 2: http://d-h.st/ziH - V3 [19/05/2014] (fixes a small derp in ramdisk)
http://forum.xda-developers.com/showthread.php?t=2756679
Any chance of a p605 kernel with SElinux enabled?
patchseven said:
Any chance of a p605 kernel with SElinux enabled?
Click to expand...
Click to collapse
samsungs opensource website is so slow, it would literally be about 5 hours of download time to get the source, I can do it but it'd be next week now
Thanks, that would be great, no rush at all, take as much time as needed. There are quite a few users who have asked for this for a long time, but a severe lack of p605 developers has meant it has not yet eventuated. Happy to shout you a beer or two for the option of linux on the p605.
patchseven said:
Thanks, that would be great, no rush at all, take as much time as needed. There are quite a few users who have asked for this for a long time, but a severe lack of p605 developers has meant it has not yet eventuated. Happy to shout you a beer or two for the option of linux on the p605.
Click to expand...
Click to collapse
Check the thread over in original development if you haven't already, p605 for jellybean just added
UnityROM-2 v.3.0.1
LG Optimus G - Sprint US ONLY ( LS970 )
(INTERNATIONAL VERSION NOT HAPPENING || NO GEE/B EVER!!! || DO NOT ASK)
Basic Overview
Source built Cyanogenmod 11.0 with a bucket of butter poured on top .
Compiled and Built with SaberMod GCC 4.8 Toolchains with a lot of optimization flags set.
BUILDTYPE = SNAPSHOT ONLY
(Not meaning only once a month or so like CM Inc.)
Aroma Installation.
Purpose
Just trying to make a cleaner, faster, and generally more optimized build basically, without changing the ROM itself (apps & such). With some extra nice things thrown in even if there's is no visible difference in the ROM
Credits
@IAmTheOneTheyCallNeo for all of his help getting GCC 4.8 up and running finally. I owe you big man.
@Captain_Throwback for his original commits and help with the original thread & in this one as well.
@gruesomewolf for all of his help learning how to build a custom kernel.
Cyanogenmod Inc. & Google Inc. of course. For everything they do, way too much to try listing here.
LiquidSmooth for some additional build flags.
And please, if you like my work or the work others have contributed to this project, hit the thanks button. Thanks.
Features & Links
*** Global O3 & Strict-Aliasing=3 Optimizations & lots more ***
Full-Modular Aroma ROM & Gapps WITHIN the main package, yet still in separate directories.
Clean or Dirty ROM Flashing Options in Aroma.
Multiple LCD Density Options in Aroma.
System App Remover in Aroma.
Works with or without Gapps Installed
***UnityKernel-3.0.1 Features***
Optimized same as the UnityROM-2 only with GCC 4.9.
I/O Schedulers: SIO & FIOPS.
Governors: Intellidemand & Intelliactive.
LZ4 Compression/Decompression.
Current Release:
https://www.androidfilehost.com/?fid=95784891001602827
UnityKernel-3.0.1 Updater (includes previous 2.7.0 Kernel)
Current Release (UnityKernel Only):
Not available yet sorry
Development Section
Please anyone who downloads the test. Report back. Then we know if we are going to continue our work here or not
LiquidSmokeX64 said:
Please anyone who downloads the test. Report back. Then we know if we are going to continue our work here or not
Click to expand...
Click to collapse
will this work on geeb?? ill defintely test if so
Extract the build.prop. It will tell you cause I really don't know lol. All I really know is I added the LS970 dependencies to my repo, did the UnityKernel mod and built it. So you tell me cause I'm not at my PC
dr3adl0ckd said:
will this work on geeb?? ill defintely test if so
Click to expand...
Click to collapse
LiquidSmokeX64 said:
Extract the build.prop. It will tell you cause I really don't know lol. All I really know is I added the LS970 dependencies to my repo, did the UnityKernel mod and built it. So you tell me cause I'm not at my PC
Click to expand...
Click to collapse
I am fairly certain it will run, but you might not have access to SD card or camera. If not, find out if there is a GEE/b kernel you can flash afterwards or if the OP can create a GEE/b kernel since it looks like it has a new kernel, aside from any other currently available. I know I've never seen UnityMod kernel anywhere.
To the OP, if you ask any of the other kernel devs what changes they made to produce a Gee/b kernel of the same settings I am sure they would provide some advice.
EDIT: some changes may be necessary in the build.prop as well to allow access to GSM.
EDIT: Don't really want to be part of this thread anymore and I haven't said anything useful
Ok. I am the OP BTW. Founder/Creator.
The UnityKernel cannot be found. It's the major unique feature of UnityROM-2. How it is done is quite simple. To me. But I remember when I had this phone. How badly it needs a good stable ROM. Just like jewel did till I did this.
So trying to do y'all a favor lol. The best ROM for Evo LTE now coming to the next Sprint "Problem Device".
LiquidSmokeX64 said:
Ok. I am the OP BTW. Founder/Creator.
The UnityKernel cannot be found. It's the major unique feature of UnityROM-2. How it is done is quite simple. To me. But I remember when I had this phone. How badly it needs a good stable ROM. Just like jewel did till I did this.
So trying to do y'all a favor lol. The best ROM for Evo LTE now coming to the next Sprint "Problem Device".
Click to expand...
Click to collapse
I saw you were the OP, that's why I quoted you too LOL. No worries. Thank you for building this ROM. I haven't tested it yet because I am working on getting the G3 port to work on our Sprint OG. But I am happy to check it out. I just wanted to let you know that you can build the geeb kernel too. I don't think it takes much, I think only adding or switching a branch for your build.
Also, if you created this ROM and built from sources, you might want to think about having this thread moved to Original Development instead of Development. This one is more for ports and changes to an existing rom in order for it to work on our phone. The new Roms and creations should go in the Original Development.
EDIT: Don't really want to be part of this thread anymore and I haven't said anything useful
LiquidSmokeX64 said:
Please anyone who downloads the test. Report back. Then we know if we are going to continue our work here or not
Click to expand...
Click to collapse
You did a great job, it works fine. I think you should continue to work on perfection of Rom. As far as I understand, you need to go to another forum thread(Optimus G Original Android Development). When using the camera - got two crashes . everything else works perfectly, quickly and smoothly! Antutu received 20673 balls without my optimization. Thank you for a wonderful job. I know little about it, but it seems to me that all is well. This gproj or aosp based? You use the new driver for the camera? Excuse me for my english.
Well thanks for the feedback. I'll run 2.7.0 for LS970 now. Tons of new things added for the build and kernel
dopy25 said:
I saw you were the OP, that's why I quoted you too LOL. No worries. Thank you for building this ROM. I haven't tested it yet because I am working on getting the G3 port to work on our Sprint OG. But I am happy to check it out. I just wanted to let you know that you can build the geeb kernel too. I don't think it takes much, I think only adding or switching a branch for your build.
Also, if you created this ROM and built from sources, you might want to think about having this thread moved to Original Development instead of Development. This one is more for ports and changes to an existing rom in order for it to work on our phone. The new Roms and creations should go in the Original Development.
Click to expand...
Click to collapse
interesting.. @LiquidSmokeX64 let us know if you do the geeb kernel def anxious to try this rom out!
+1 would also want a geeb kernel for this.
dr3adl0ckd said:
interesting.. @LiquidSmokeX64 let us know if you do the geeb kernel def anxious to try this rom out!
Click to expand...
Click to collapse
Well if I knew what I need for geeb I would gladly make it for you guys. I just grabbed the stuff listed in CMs LS970 device cm.dependencies file.
I can always add more or a new defconfig file to have it look at while building. Either way will work
If I can get my net to cooperate, I have 2.7.0 ready and attempting to upload.
Y'all ready for this?
LiquidSmokeX64 said:
If I can get my net to cooperate, I have 2.7.0 ready and attempting to upload.
Y'all ready for this?
Click to expand...
Click to collapse
Yes sir!
LiquidSmokeX64 said:
If I can get my net to cooperate, I have 2.7.0 ready and attempting to upload.
Y'all ready for this?
Click to expand...
Click to collapse
with impatience [emoji14] [emoji14] [emoji14]
Vadik56 said:
with impatience [emoji14] [emoji14] [emoji14]
Click to expand...
Click to collapse
UnityROM-2 v.2.7.0 has arrived and is now posted
Fully featured now with all my normal modifications.
Yes Google apps are built-in... technically...
The separated internal directories make it OK to do this legally.
Enjoy everyone
LiquidSmokeX64 said:
UnityROM-2 v.2.7.0 has arrived and is now posted
Fully featured now with all my normal modifications.
Yes Google apps are built-in... technically...
The separated internal directories make it OK to do this legally.
Enjoy everyone
Click to expand...
Click to collapse
Thank you, download started. I feel will be a bomb-)-)
UnityROM-2 v.2.7.0 has arrived and is now posted
Installation fails
View attachment cm-UnityROM-2-v.2.7.0-ls970.zip.log.txt
Vadik56 said:
UnityROM-2 v.2.7.0 has arrived and is now posted
Installation fails
View attachment 2974972
Click to expand...
Click to collapse
Looks like you're flashing for the wrong device, or wrong recovery.
Hello all,
I've started working on CM12 for RedMi 1S. So here I'm going to discuss about the further status and builds for the rom.
For those who wants to join and help out :-
Current Status :-
Tree is now buildable without any sort of errors
ROM doesn't boots stucks at MI logo
So Kernel ain't loading up yet
I'd request to make pull request if you've any fix for anything.
CREDITS :-
armani-dev(fefifofum, Kra1o5 for all their work and base tree)
CyanogenMod
If anyone missed here please pm me
ADB IS CURRENTLY NOT WORKING
DMESG LOG
http://pastebin.com/raw.php?i=62sUgm5F
kD said:
ADB IS CURRENTLY NOT WORKING
DMESG LOG
http://pastebin.com/raw.php?i=62sUgm5F
Click to expand...
Click to collapse
its mostly the SELinux i feel trying taking a look at this commit n see if it helps https://github.com/SeannyM/android_...mmit/b8e22d4cb5c6ea0782b8c9d47c959cd05a66a707
Tarun93 said:
its mostly the SELinux i feel trying taking a look at this commit n see if it helps https://github.com/SeannyM/android_...mmit/b8e22d4cb5c6ea0782b8c9d47c959cd05a66a707
Click to expand...
Click to collapse
We're already running SELinux at permissive mode. I'm going to apply this commit in our device and build again. let's see.
kD said:
We're already running SELinux at permissive mode. I'm going to apply this commit in our device and build again. let's see.
Click to expand...
Click to collapse
i can see you are running the build in permissive in the boardconfig.mk but the prebuilt kernels we are using are of kk AFAIK that the main issue in my understanding if you can just try to disable the selinux n build the boot.img flash it on the current lollipop built
and try adding that commit and just build the boot.img in my understanding it should work pls correct me if m wrong pal
Tarun93 said:
i can see you are running the build in permissive in the boardconfig.mk but the prebuilt kernels we are using are of kk AFAIK that the main issue in my understanding if you can just try to disable the selinux n build the boot.img flash it on the current lollipop built
and try adding that commit and just build the boot.img in my understanding it should work pls correct me if m wrong pal
Click to expand...
Click to collapse
SELinux is not only built in kernel, It is built under whole control. I'm adding that commit. Let's see what happens.
kD said:
SELinux is not only built in kernel, It is built under whole control. I'm adding that commit. Let's see what happens.
Click to expand...
Click to collapse
kkkkkkkkk keep me updated i will dig more info i can
kD said:
ADB IS CURRENTLY NOT WORKING
DMESG LOG
http://pastebin.com/raw.php?i=62sUgm5F
Click to expand...
Click to collapse
How did you get dmesg log if adb is not working? Anyway, I think the problem you are facing is related to the display, same that happened in cm11. Kernel is probably loading fine. If you are patient, next week I'll start looking into cm12.
jsevi83 said:
How did you get dmesg log if adb is not working? Anyway, I think the problem you are facing is related to the display, same that happened in cm11. Kernel is probably loading fine. If you are patient, next week I'll start looking into cm12.
Click to expand...
Click to collapse
Dmesg log were taken after booting into recovery,
Did CM11 caused the same issue?
I don't mind waiting for you guys to work on CM12.
But if you could let me know what kind changed display needs maybe i can trigger it?
jsevi83 said:
How did you get dmesg log if adb is not working? Anyway, I think the problem you are facing is related to the display, same that happened in cm11. Kernel is probably loading fine. If you are patient, next week I'll start looking into cm12.
Click to expand...
Click to collapse
kD said:
Dmesg log were taken after booting into recovery,
Did CM11 caused the same issue?
I don't mind waiting for you guys to work on CM12.
But if you could let me know what kind changed display needs maybe i can trigger it?
Click to expand...
Click to collapse
Hello,
I've merged your display and media changes from cm11 to newer caf-display at CM12.
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
https://github.com/keyur2maru/andro...mmit/4732996db82d80f7b7ede28ce2c1685bc61eb137
After applying them, I've ran into some newer build errors could you checkout?
error is at building surfaceflinger and libstagefright
Here are the errors:
http://pastebin.com/0ZFpTmjw
http://pastebin.com/HyYEgFjP
Any workaround for it?
Awesome!
kD said:
Hello,
I've merged your display and media changes from cm11 to newer caf-display at CM12.
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
https://github.com/keyur2maru/andro...mmit/4732996db82d80f7b7ede28ce2c1685bc61eb137
After applying them, I've ran into some newer build errors could you checkout?
error is at building surfaceflinger and libstagefright
Here are the errors:
http://pastebin.com/0ZFpTmjw
http://pastebin.com/HyYEgFjP
Any workaround for it?
Click to expand...
Click to collapse
I suggest you to try to build a working cm11 with that approach, it will be easier than cm12 and it will help you understand our current situation. As I said I won't start looking into cm12 until next week, and to be honest things don't look too good without stock rom 4.4 or kernel source.
i do agree with jsevi83 pal even i tried with my noob knowledge now m bored
jsevi83 said:
I suggest you to try to build a working cm11 with that approach, it will be easier than cm12 and it will help you understand our current situation. As I said I won't start looking into cm12 until next week, and to be honest things don't look too good without stock rom 4.4 or kernel source.
Click to expand...
Click to collapse
I went through your changes. I've came to some conclusions.
Add display_config header
Well it adds display_config header at CM11 but at CM12 it is already present.
display_config header at CM12 just add this line at the bottom rest all is same.
Code:
// set the view frame information in hwc context from surfaceflinger
int setViewFrame(int dpy, int l, int t, int r, int b);
This is the only extra part at CM12's display_config header?
So can you tell em do actually need to comment out this line?
Now libmemtrack is already present at CM12.
Now at media
mm-core/inc/QCMetaData.h is edited to disable few components but if i do the same at CM12 it throws the build error?
Build error is already posted above.
Any idea for fix would be really helpful.
good luck
:fingers-crossed: i am not a dev , but i can be a tester for yu guys .. good job friends , i wish to apreciate your effort towards redmi 1s.. hope to seee lolipop on our devices soon
the first error:
revert this commit in media-caf-legacy
https://github.com/CyanogenMod/andr...mmit/dab6ad4665dcfaaf1be426c4e35da61f735f7f09
edit:
revert your commit here:
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
thewisenerd said:
the first error:
revert this commit in media-caf-legacy
https://github.com/CyanogenMod/andr...mmit/dab6ad4665dcfaaf1be426c4e35da61f735f7f09
edit:
revert your commit here:
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
Click to expand...
Click to collapse
I've done those commits for fixing display. They were applied at CM11 same needs to be applied at CM12. So I need them.
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
this commit is for fixing ffmpeg plugin collisions. ffmpeg was added by cyanogenmod in cm11, and hasn't yet been added in cm12. so, it'd be best to revert that commit for now (till cm adds ffmpeg (which'll take time))
thewisenerd said:
https://github.com/keyur2maru/andro...mmit/013f890aafed9f863bbb3597fabe049f40e3279b
this commit is for fixing ffmpeg plugin collisions. ffmpeg was added by cyanogenmod in cm11, and hasn't yet been added in cm12. so, it'd be best to revert that commit for now (till cm adds ffmpeg (which'll take time))
Click to expand...
Click to collapse
yeah just figured out you're right. changes at media were just done to override the path because it was changed display-caf-legacy.
Removed those edits.
Now just need to fix display build error.
Building now will post error here soon.
p.s. thank you
Any update ?
I thought of developing a kernel so that i can use it with my CM11 that im going to port shortly. I thought I'll compile the stock kernel from source itself. I use android pre-built tool chain (arm-eabi-4.6)
I get a lot of compiler errors on stock kernel without any modifications itself...
Do i need to change my tool chain?
Sent from my One V using XDA Free mobile app
I never tried to build the stock kernel, but I think they did it with the android 4.0 toolchain.
To run CM, you need a CM-Kernel. You have to port things from the stock or a custom kernel (like Hellboy by maxwen) to the cm11 kernel.
Try to use rastomanchiks kernel sources (https://github.com/rastomanchik/android_kernel_htc_primou). This kernel is mostly working, stable and has a good battery life now.
I'd also like to build cm11, but my download speed is to slow to download the sources.
Exactly. Even my download speed is slow. And i have a cap also. After 8GB, my download speed drastically decreases. It takes ages to sync the sources...
Sent from my One V using XDA Free mobile app
How different is Cm kernel from stock? I mean what changes should i make?
Sent from my One V using XDA Free mobile app
Cm needs many features which aren't included in the stock kernel and also you should get ION memory allocator working.
Help
jonas2790 said:
Cm needs many features which aren't included in the stock kernel and also you should get ION memory allocator working.
Click to expand...
Click to collapse
Yeah. How do I port?
What happened to your CM12 project?
hehaichi said:
Yeah. How do I port?
What happened to your CM12 project?
Click to expand...
Click to collapse
I started working on cm12 again yesterday and finally have cm11 sources now, so expect a cm11 build in some days
I can't help you with porting, because all the porting work was done by rastomanchik and I chatted with him. You'd have to ask him about this, but he wasn't online the last weeks and can't speak english without google translator.
jonas2790 said:
I started working on cm12 again yesterday and finally have cm11 sources now, so expect a cm11 build in some days
I can't help you with porting, because all the porting work was done by rastomanchik and I chatted with him. You'd have to ask him about this, but he wasn't online the last weeks and can't speak english without google translator.
Click to expand...
Click to collapse
Actually I insist on porting myself so that I can learn building properly.
Actually these things are also interesting.. fixing bugs and all...
Have series of exams till May end. I cant build properly until then. I thought why not learn something..
Where did you learn about building and other stuff. Also I want to build the device tree on my own.
If you could specify some sources to learn, that would be grateful!
hehaichi said:
Actually I insist on porting myself so that I can learn building properly.
Actually these things are also interesting.. fixing bugs and all...
Have series of exams till May end. I cant build properly until then. I thought why not learn something..
Where did you learn about building and other stuff. Also I want to build the device tree on my own.
If you could specify some sources to learn, that would be grateful!
Click to expand...
Click to collapse
This is exactly the same point of view I had when I started some months ago
Sadly, there isn't much documentation about own device trees and own kernels out there.
There also is no reference device tree, so every dev does it in his own way. I'm always trying to have a clean, easy device tree and use the CM ones as a reference.
You can find some tutorials about building cm, but only with downloading a ready-to-use device config and kernel.
I just played around with it one or two weeks and learned the most.
If you have enough time, please at least try to get into this stuff, maybe we can get cm12 running.
You can reach me on irc in the channel #hov on freenode.
jonas2790 said:
This is exactly the same point of view I had when I started some months ago
Sadly, there isn't much documentation about own device trees and own kernels out there.
There also is no reference device tree, so every dev does it in his own way. I'm always trying to have a clean, easy device tree and use the CM ones as a reference.
You can find some tutorials about building cm, but only with downloading a ready-to-use device config and kernel.
I just played around with it one or two weeks and learned the most.
If you have enough time, please at least try to get into this stuff, maybe we can get cm12 running.
You can reach me on irc in the channel #hov on freenode.
Click to expand...
Click to collapse
I have sufficient time only after May. Till then I'll have to do some research and learn the basics.
I saw on the CM wiki page, it says you can run a prebuilt kernel also... So would it work if we could tweak the stock kernel a bit?
And how do I apply patches to the kernel?
hehaichi said:
I have sufficient time only after May. Till then I'll have to do some research and learn the basics.
I saw on the CM wiki page, it says you can run a prebuilt kernel also... So would it work if we could tweak the stock kernel a bit?
And how do I apply patches to the kernel?
Click to expand...
Click to collapse
Yes you can use a prebuilt kernel, but it will only work if the kernel supports you cm version.
You apply patches to a kernel by changing files or directories in the kernel. For example you can use another fs module (maybe with more functions) by copy and pasting the folder for the module from another kernel. The problem is, the new module may require some functions your kernel does not have so it won't compile.
Hey i had mailed rastomanchik and he said 3.4.x kernel is an impossibility for cm11? Why?
Sent from my One V
hehaichi said:
Hey i had mailed rastomanchik and he said 3.4.x kernel is an impossibility for cm11? Why?
Sent from my One V
Click to expand...
Click to collapse
1. It would be much, much, much work.
2. I think there are some device-specific drivers that only work with 3.0
I'm ready to do that work only if i knew how to...
Sent from my One V
hehaichi said:
I'm ready to do that work only if i knew how to...
Sent from my One V
Click to expand...
Click to collapse
Try to get into it yourself or talk with people who know about kernel developement, I'm also new to android developement.