Related
For a few days now I've been trying to set up a build environment to compile (for starters) the stock kernel on my own.
I'm using Ubuntu 11.10 x64 and have tried to build an ARM EABI capable GCC using
vorkChain script
Linaro GCC
without success. Everytime the compilation process aborts with either libstdc++ missing ('/bin/bash: line 3: cd: arm-eabi/libstdc++-v3: No such file or directory') or some error with the strip command.
I'm now trying to get running with the sourcery toolchain but I'm unsure if that's the right direction or if it's just compiling a Tegra2-compatible but not optimized code.
How did you set up your build-environment for the LG-P990 kernel/ROM development?
Hello!
Did you read this guide!?!
http://forum.xda-developers.com/showthread.php?t=1104523
Did you follow this thread!?!
http://forum.xda-developers.com/showthread.php?t=1118091&page=4
Thanks for the hints. I had a look at both but unfortunately they are targeted at CM7 builds which have a specific and defined environment/structure, use loads of scripts to set up all requirements and would require me to download several GBs (~20GB?) just to begin working. Furthermore the guides require me to flash CM7 on my phone as at one step they extract propietary stuff from the phone to have a successful build. That's not exactly what I'm looking for.
What I'm looking for is a description on how to set up the compiler (+dependencies) environment which allows me just to build the official kernel on my own. I tried to get some hints out of the CM scripts but with no luck. All my searches in the forum also have been not successful.
Maybe someone more experienced than me can give me some info or hints on topics which could help me with my search?
Hello!
Well, I am not an expert in kernel-build myself but there where discussions in the ironkrnL threat and some people managed to build kernels from the devs github their (i.e. vodonka)...
Beginning somewhere here…
http://forum.xda-developers.com/showthread.php?t=1359307&page=33
And I found this…
http://www.mydroidworld.com/forums/...-how-compile-cyanogen-gingerbread-source.html
The HowTo from Cyanogen is for Debian and Red Hat…
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
…but it doesn’t say much about compiler setup itself anyway.
The best thing might be asking one of the people building kernel-Kangs frequently like rusty, temasek or koboltzz.
Medizinman I think you still don't understand, you keep giving links for cyanogen kernel!!
There is no way to compile stock kernel with cyanogen environment.....
Kosi you should ask for Spica and Koboltz in dev section they build stock kernels.
Hello!
Oh sorry, I overlooked this... ...of course he can't build a "stock kernel" from Cm7-source...my fault/mistake.
...forget what I wrote...
Yes, asking one of the "stock-kernel-devs" on xda like Spica (hp kernel for stock), Koboltz, Imperticus(NeoBlaze kernel) or dr4go (fps kernel) might be a good idea indeed...
Medizinmann said:
Hello!
Oh sorry, I overlooked this... ...of course he can't build a "stock kernel" from Cm7-source...my fault/mistake.
...forget what I wrote...
Yes, asking one of the "stock-kernel-devs" on xda like Spica (hp kernel for stock), Koboltz, Imperticus(NeoBlaze kernel) or dr4go (fps kernel) might be a good idea indeed...
Click to expand...
Click to collapse
Hi all,
Does any one have compiled kowalski kernel from sources (github(dot)com/pengus77/lge-kernel-star) ?
I have been using Linaro toolchain 4.6.2 to compile it, and it build ok. However, I can not boot using the generated zImage - it always stucks in the LG logo.
Can you give me some pointers concerning the compilation flags and/or environment?
Thanks!
So Guys,
on many places has been mentioned that there is/will be some devs who take a look on a possible future 3.0 Kernel for our tabs with ICS/CM9. As I am an "experienced noob" (my special word for "power-user ;-)) and not a dev, please could somebody enlighten me what benefits such a 3.0 Kernel would bring us? Performance? Features?
Thanks for your answers...
If allowed in forum rules (dunno for shure) you can discuss related stuff in here as well from my side.
Which kernel are you referring to??
TheATHEiST said:
Which kernel are you referring to??
Click to expand...
Click to collapse
Afaik there is no such kernel yet, as I said, but some devs are working on (humberos?!)
spike1985 said:
Afaik there is no such kernel yet, as I said, but some devs are working on (humberos?!)
Click to expand...
Click to collapse
So then why has it got a version number of 3.0? Which other kernel are you referring to if there has been a v1 & v1?
Or are you confused and referring to Android 4.0?
TheATHEiST said:
So then why has it got a version number of 3.0? Which other kernel are you referring to if there has been a v1 & v1?
Or are you confused and referring to Android 4.0?
Click to expand...
Click to collapse
Not confused... go to your devices details and you will see what I mean in kernel version...
Yeah, like in Linux, kernel version was 2.4 on the old days, then 2.6
For last decade, then now 3.0.
In Linux the 3.0 includes some android codes I think.
Sent from my GT-P1000 using XDA
spike1985 said:
So Guys,
on many places has been mentioned that there is/will be some devs who take a look on a possible future 3.0 Kernel for our tabs with ICS/CM9. As I am an "experienced noob" (my special word for "power-user ;-)) and not a dev, please could somebody enlighten me what benefits such a 3.0 Kernel would bring us? Performance? Features?
Thanks for your answers...
If allowed in forum rules (dunno for shure) you can discuss related stuff in here as well from my side.
Click to expand...
Click to collapse
I don't think this would directly affect us users (or as you say it "experienced noobs"). More likely affect kernel builders (efficiency and compatibilities). Please correct me if I was wrong.
first we need the leaked ICS rom from Samsung and then Samsung releases the kernel source code. No doubt this will be the version 3.0 of the kernel.
Kernel 3.0 brings many benefits to users because many optimizations are included
----
Google translate
I've been using Codename ever since it came out but I got tired of the problems related to the Kernel and switched to ProjectX. I and I'm sure others really want to use a smooth and working JB ROM.
Is there anyone working on the 3.0 Kernel for our device? I know Nik said he contacted someone to help us out but there's been no news on that front yet.
If anyone knows how to modify Kernels, Adi_pat gave some tips here -
http://forum.xda-developers.com/showthread.php?p=33291894
He'll probably help us out if we make some progress in booting up Codename with it at least
TheDareDevil said:
I've been using Codename ever since it came out but I got tired of the problems related to the Kernel and switched to ProjectX. I and I'm sure others really want to use a smooth and working JB ROM.
Is there anyone working on the 3.0 Kernel for our device? I know Nik said he contacted someone to help us out but there's been no news on that front yet.
If anyone knows how to modify Kernels, Adi_pat gave some tips here - http://forum.xda-developers.com/showthread.php?t=1899335&page=38
He'll probably help us out if we make some progress in booting up Codename with it at least
Click to expand...
Click to collapse
Upon the exit of JB roms ago, were used GB modified kernel, now with source code maybe will be possible to compile a fully working kernel, but afaik there are no 3.x kernel for JB, maybe someone is working out of xda on irc channel but don't known..
Sadly I do not have much competence, plus I don't have the phone it's to repair....
There is kernel 3 for incredible 2 and desire s..may be someone can port it..
Sent from my HTC Incredible S using xda app-developers app
I might be crazy, but I remember reading a post not too long ago about a dev that was writing the 3.0 kernel from source for our phones. I haven't heard an update since then, but I remember hearing it was someone with relation to the cm9 team. It sounded promising, but that development was very slow.
Sent from my HTC Incredible S using xda app-developers app
TheMegosh said:
I might be crazy, but I remember reading a post not too long ago about a dev that was writing the 3.0 kernel from source for our phones. I haven't heard an update since then, but I remember hearing it was someone with relation to the cm9 team. It sounded promising, but that development was very slow.
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
Off the top of my head I seem to recall Noverbose saying he was trying to write a 3.0 Kernel. I also remember at least one other person mentioning something similar to, so there are people working on this. From what I understand it's not easy - I doubt we'll see anything this side of Christmas tbh. I hadn't realised that the Inc 2 and DS had a 3.0 Kernel though. Anyone know if they are actually a made from source version, rather than the same hacked version that we have in Codename, for example?
Well tbh honest a working GB kernel would do too.
Like the front camera and chrome and screen flickering etc.
Damn I wish kaijura was here
Sent from my HTC Incredible S using xda app-developers app
CyanideJack said:
Off the top of my head I seem to recall Noverbose saying he was trying to write a 3.0 Kernel. I also remember at least one other person mentioning something similar to, so there are people working on this. From what I understand it's not easy - I doubt we'll see anything this side of Christmas tbh. I hadn't realised that the Inc 2 and DS had a 3.0 Kernel though. Anyone know if they are actually a made from source version, rather than the same hacked version that we have in Codename, for example?
Click to expand...
Click to collapse
Yes those 3.0 kernels are compiled from source. I checked out AOSP ROM threads in the Desire S and Inc 2 section that had 3.0 kernel, then looked up the creator of the ROM on github and found the sources. I was going to try tackle the 3.0 kernel to get a hang of the make system before building CM9, but I don't have enough monthly data left to download the kernel toolchain! Nov 1st is close, so I can get to work soon! :highfive:
The best way to build an AOSP 3.0 kernel for our device would probably be to look at the source code for 3.0 kernels on our sister devices, and figure it out from there.
ZaySk said:
Yes those 3.0 kernels are compiled from source. I checked out AOSP ROM threads in the Desire S and Inc 2 section that had 3.0 kernel, then looked up the creator of the ROM on github and found the sources. I was going to try tackle the 3.0 kernel to get a hang of the make system before building CM9, but I don't have enough monthly data left to download the kernel toolchain! Nov 1st is close, so I can get to work soon! :highfive:
The best way to build an AOSP 3.0 kernel for our device would probably be to look at the source code for 3.0 kernels on our sister devices, and figure it out from there.
Click to expand...
Click to collapse
Well holy crap, dude, get on that! Seriously though, getting a working 3.0 kernel for our device would go a long way to making JB a usable ROM for our device. Would it be possible to port JellyTime or a similar JB ROM to our device as well?
The source doesn't need changing, it is the ramdisk that is the problem. I have been trying to get help, but so far no luck, adi_pat said he would take a look, but it is hard for me to test as I no longer have an inc s
CyanideJack said:
Well holy crap, dude, get on that! Seriously though, getting a working 3.0 kernel for our device would go a long way to making JB a usable ROM for our device. Would it be possible to port JellyTime or a similar JB ROM to our device as well?
Click to expand...
Click to collapse
I'm gonna worry mainly about compiling CM9 from source once November hits, that's gonna take up the majority of my time. After I get the first release of CM9 out, I'll start work on a 3.0 kernel if it hasn't been done yet. I have no experience whatsoever dealing with kernels though, except for small ramdisk edits, so don't expect any miracles.
It should be possible to port other JB ROM's over using one of nik's ported JB ROM's as a base and reference point, the only problem is I don't know exactly what files I have to substitute to port a ROM. I've PM'd nik about that a few hours ago, so hopefully I'll get some more information on the subject. Nik has been a big help to my dev efforts as a whole.
l0st.prophet said:
The source doesn't need changing, it is the ramdisk that is the problem. I have been trying to get help, but so far no luck, adi_pat said he would take a look, but it is hard for me to test as I no longer have an inc s
Click to expand...
Click to collapse
Interesting, if it's only the ramdisk that needs changing, couldn't you look at the ramdisk from one of niks JB ROM's? Or is it not as simple as that? I'm assuming the latter, seeing as if it were that obvious I'm sure someone would've done it by now. If you ever need help testing, send me a PM I'd be more than willing to test for you.
ZaySk said:
I'm gonna worry mainly about compiling CM9 from source once November hits, that's gonna take up the majority of my time. After I get the first release of CM9 out, I'll start work on a 3.0 kernel if it hasn't been done yet. I have no experience whatsoever dealing with kernels though, except for small ramdisk edits, so don't expect any miracles.
It should be possible to port other JB ROM's over using one of nik's ported JB ROM's as a base and reference point, the only problem is I don't know exactly what files I have to substitute to port a ROM. I've PM'd nik about that a few hours ago, so hopefully I'll get some more information on the subject. Nik has been a big help to my dev efforts as a whole.
Interesting, if it's only the ramdisk that needs changing, couldn't you look at the ramdisk from one of niks JB ROM's? Or is it not as simple as that? I'm assuming the latter, seeing as if it were that obvious I'm sure someone would've done it by now. If you ever need help testing, send me a PM I'd be more than willing to test for you.
Click to expand...
Click to collapse
About using one of Nik's JB roms as a reference
What I understood was that the rom has been built around the old 2.6.x kernel and has to be modified again to work with the 3.0.x kernel, if you guys get one up and running. If that is the case, wouldn't you be going down the wrong path if you model it around nik's existing 2.6.x roms?
We need kaijura here, he was our AOSP kernel master. Hopefully he is doing ok, and has found something else other than xda because he hasn't been online for months. At least other devs, like lordclokan and kali- have moved on and are active with other devices... kaijura hasn't been on at all. Anyone been in contact with him/her?
markj338 said:
About using one of Nik's JB roms as a reference
What I understood was that the rom has been built around the old 2.6.x kernel and has to be modified again to work with the 3.0.x kernel, if you guys get one up and running. If that is the case, wouldn't you be going down the wrong path if you model it around nik's existing 2.6.x roms?
We need kaijura here, he was our AOSP kernel master. Hopefully he is doing ok, and has found something else other than xda because he hasn't been online for months. At least other devs, like lordclokan and kali- have moved on and are active with other devices... kaijura hasn't been on at all. Anyone been in contact with him/her?
Click to expand...
Click to collapse
I know, it would be going down a pretty redundant path. If I was able to port over a JB ROM using nik's ROM's as a base, then my ported ROM would inherit all the same bugs nik's ROM's already have.
I wish kaijura was still around, I have so many questions I want to ask about compiling from source! Luckily lordclokan was a massive help to me in that regard. Kaijura's github hasn't seen action in months either, sadly.
Forgive my ignorance, but isn't the Desire HD essentially our device with a bigger screen and less memory? That being the case, could we not just port across one of the 3.0 Kernels from that?
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
The only problem with the desire HD kernel would be that our front camera would not work
+ I forgot to link to adi_pat's post - http://forum.xda-developers.com/showthread.php?p=33291894
Sent from my HTC Incredible S using xda app-developers app
l0st.prophet said:
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
Click to expand...
Click to collapse
Well you can prolly get ideas from adi ( he posted http://forum.xda-developers.com/showpost.php?p=33302707&postcount=387 not sure if you saw it) he seems to know what's up.
TheDareDevil said:
The only problem with the desire HD kernel would be that our front camera would not work
+ I forgot to link to adi_pat's post - http://forum.xda-developers.com/showthread.php?p=33291894
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
So it looks like the furthest things got regarding a 3.0 Kernel was;
Adi_Pat said:
chan
Ok so 2.6.35 works with Jellybean. Why not pack the ramdisk with zImage compiled from 3.0.y sources(Considering you are using standard boot.img format[?]) Because to get it to boot, you would not require any hacks/changes to source, editing ramdisk(init.rc) is enough to make it boot initally.
EDIT: You may also need to change init binary.
Click to expand...
Click to collapse
l0st.prophet said:
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
Click to expand...
Click to collapse
Very interesting, thanks for the informative post. :good:
zaysk said:
very interesting, thanks for the informative post. :good:
Click to expand...
Click to collapse
happy november!!!
markj338 said:
happy november!!!
Click to expand...
Click to collapse
A very happy November indeed
I apologize for my bad English I am Italian and use google translate
I need a guide on how to compile Android from source
(the ParanoidAndroid for accuracy)
which linux distro to use?
which packages to install?
which commands to use?
I have a lot of time free
and a core i5 cpu
I think that to compile Android from source
but I need a guide
then I ask you developers, you can post a guide
----------------------------------------------------------------------------------------
write from my pc using win8 e programming a websites
bomdia said:
I apologize for my bad English I am Italian and use google translate
I need a guide on how to compile Android from source
(the ParanoidAndroid for accuracy)
which linux distro to use?
which packages to install?
which commands to use?
I have a lot of time free
and a core i5 cpu
I think that to compile Android from source
but I need a guide
then I ask you developers, you can post a guide
----------------------------------------------------------------------------------------
write from my pc using win8 e programming a websites
Click to expand...
Click to collapse
Well, you need a lot of work to get a working build, as i currently compile CM9 for SXL.
Recommended distros: Ubuntu 12.04 Precise / Linux Mint 13 Maya with Cinnamon interface to have the best linux experience << The best linux distro i ever used
Packages: Well, you need to check the Paranoid site to download the repo for ICS or JB variant of source-code.
Commands: Lots of commands, there are tutorials online. Example >> here
After this, you will need the device tree for SXL, i have one that is deprecated (not updated for some time), it does not work the variant uploaded here, but i will upload it.
You will need the vendor files, i also have the files but as the build of CM9 don't work, i haven't upload them anywhere untill i can get an at least experimental build that boots
Link for android device tree for sxl by me here
There is a lot of work and there aren't any specific guides on how to do this, you need to join communities and be a pain on the ass for them untill you learn how to do this.
I hope this helps anyways
Lexmazter said:
Well, you need a lot of work to get a working build, as i currently compile CM9 for SXL.
Recommended distros: Ubuntu 12.04 Precise / Linux Mint 13 Maya with Cinnamon interface to have the best linux experience << The best linux distro i ever used
Packages: Well, you need to check the Paranoid site to download the repo for ICS or JB variant of source-code.
Commands: Lots of commands, there are tutorials online. Example >> here
After this, you will need the device tree for SXL, i have one that is deprecated (not updated for some time), it does not work the variant uploaded here, but i will upload it.
You will need the vendor files, i also have the files but as the build of CM9 don't work, i haven't upload them anywhere untill i can get an at least experimental build that boots
Link for android device tree for sxl by me here
There is a lot of work and there aren't any specific guides on how to do this, you need to join communities and be a pain on the ass for them untill you learn how to do this.
I hope this helps anyways
Click to expand...
Click to collapse
thanks a lot I think I start tomorrow I'm a little tired
Hi just so you know you won't be able to compile Paranoid Android for ICS from source as it was never released.
If you can get JB to work then you will not only be a hero but also be able to use Paranoid Android source
I have a problem I can not download the sources of the paranoid in any way
help (or build the sources normal Android?)
Did you follow a guide how to set up the environment in linux? Or Mac.. the way you can download sources is git clone and then the git link. There are many guides on doing that part. Also when I download source it times out in a 4 mb/s connection and I need to use a better connecyion
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
anders3408 said:
Did you follow a guide how to set up the environment in linux? Or Mac.. the way you can download sources is git clone and then the git link. There are many guides on doing that part. Also when I download source it times out in a 4 mb/s connection and I need to use a better connecyion
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Click to expand...
Click to collapse
aa ok but the guide I was reading did not say that it was necessary to clone each of the sources piece by piece, but he said to use a single link.
I have linux mint 14 with cinnamon (from the 13 consigliatami lextmazter I do not work)
both in Italy and in spite of my connection is approximately 16 mb / s (88% above the national average)
Post link to guide.
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
bomdia said:
aa ok but the guide I was reading did not say that it was necessary to clone each of the sources piece by piece, but he said to use a single link.
I have linux mint 14 with cinnamon (from the 13 consigliatami lextmazter I do not work)
both in Italy and in spite of my connection is approximately 16 mb / s (88% above the national average)
Click to expand...
Click to collapse
I do not recommend Linux Mint 14 as it is new edition, based on new Ubuntu version 12.10 if i remember good, don't know for sure, that's why, on Ubuntu 12.04 building is supported, even though on some guides it is said that on 12.04 it is experimental, well, it was, now it should be stable.
Also, if you want to port things like Paranoid or PAC you should start with AOSP or CM9 or AOKP, to put it short, versions that have guides and source codes on their sites. In my opinion CM is the best thing to start with, that's why i started CM9, after that you can easily port every 4.0.4 AOSP based ROM.
The same thing applies to JB, if you can port or build AOSP or CM10, you can port every JB AOSP based ROM very easily following only a few basic steps, that's how things work in this hood
Off-topic: I was a little distracted from building/testing/devving because of the school affairs, but today i will resume my work on CM9, if things work well, i will have a bootable build this very evening.
same as lexmazter, sound correct. the hard part is build CM9 rom, rest is pretty easy.
Lexmazter, i am about to try take a ramdisk from cm9 primou and make changes in every lines and see if i can get it to work with runnymede. if it does we will have a working aosp bootimg. i have compiled a zimage from source and it works with wifi and bt and so on in sense rom, also zimage works with cm9 with wifi.
lexmazter, can you please take a bencmark test with antutu 3.0.1, the new one, and post screenshot of the score and wich rom you are in ? they have made the test much diffrend so score is diffrend in 3.0.1 than older , so i have nothing to compare it to
anders3408 said:
same as lexmazter, sound correct. the hard part is build CM9 rom, rest is pretty easy.
Lexmazter, i am about to try take a ramdisk from cm9 primou and make changes in every lines and see if i can get it to work with runnymede. if it does we will have a working aosp bootimg. i have compiled a zimage from source and it works with wifi and bt and so on in sense rom, also zimage works with cm9 with wifi.
lexmazter, can you please take a bencmark test with antutu 3.0.1, the new one, and post screenshot of the score and wich rom you are in ? they have made the test much diffrend so score is diffrend in 3.0.1 than older , so i have nothing to compare it to
Click to expand...
Click to collapse
5941 no OC with LTX Kernel v0.7 and Sense 3.0 by fshami, also, i think i found the right ramdisk for now for CM9, it solved the dalvik-permissions, now i still need to boot the build, still trying to figure what is wrong here and why it hangs after Android is upgrading... >> Starting applications.
I can work more on my device now as i have a cheap second phone to use if for calls and sms.
so then I decided, when I start buildare the source of AOSP Android 4.2 jellybean I think it's easier for me to start.
I had to use because the new mint old man crashed always
bomdia said:
so then I decided, when I start buildare the source of AOSP Android 4.2 jellybean I think it's easier for me to start.
I had to use because the new mint old man crashed always
Click to expand...
Click to collapse
As a recommandation, i would recommend building AOSP 4.0.4, it is easier to start and has more chances of working, after that, you have the experience and the headstart to work on 4.1 and only after that on 4.2.
Just start with baby-steps, it is easier and increases the chances of success.
Lexmazter said:
As a recommandation, i would recommend building AOSP 4.0.4, it is easier to start and has more chances of working, after that, you have the experience and the headstart to work on 4.1 and only after that on 4.2.
Just start with baby-steps, it is easier and increases the chances of success.
Click to expand...
Click to collapse
ahh ok then I try to go with 4.1 if I can not then step 4.0.4
bomdia said:
ahh ok then I try to go with 4.1 if I can not then step 4.0.4
Click to expand...
Click to collapse
Well, i recommend this because i'm still building 4.0.4 and i haven't successfully booted a build, so that's why i say this, because if you get the 4.0.4, in short terms, all you need to change for 4.1 is the graphics driver, but for 4.2 i don't know for sure, too new for me and i'm still trying to get 4.0.4 to air
then my kernel is not so bad 5838 with sense 4.1 v. 1.5.1 and still missing some improvments
which ramdisk are you using, zimage from stock rom should get it to boot, but the ramdisk as you know need to be changed to cm9. when you compile from source it should also make a ramdisk that will fits the rom, i think it is best to check what the diffrence in the new ramdisk and the old one with VM errors and then fix them, perhaps it will boot then ? one specific compiled by you ? post a logcat in your cm9, had also some bootloop in my cm9 port but got it booting.
anders3408 said:
then my kernel is not so bad 5838 with sense 4.1 v. 1.5.1 and still missing some improvments
which ramdisk are you using, zimage from stock rom should get it to boot, but the ramdisk as you know need to be changed to cm9. when you compile from source it should also make a ramdisk that will fits the rom, i think it is best to check what the diffrence in the new ramdisk and the old one with VM errors and then fix them, perhaps it will boot then ? one specific compiled by you ? post a logcat in your cm9, had also some bootloop in my cm9 port but got it booting.
Click to expand...
Click to collapse
just enter the irc channel, will talk more there, no need to spam the forum with this.
The boothanging is because of the audio, the ramdisk is good, i use the LTX v0.7 zImage and ramdisk from stock edited to fit the build.
Also, the ramdisk is not made with the build, maybe if you compile the kernel with the rom, and for this you need to put the kernel online and othe things, and because of proxy, i can't and won't do that. For more details, like i said, find me on the irc.
link here
you say that jelly beans to need a new kernel? because sifting through the Internet I found this: https://developer.qualcomm.com/mobile-development/mobile-technologies/gaming-graphics-optimization-adreno/tools-and-resources there are also drivers for jelly bean of adreno 2xx
bomdia said:
you say that jelly beans to need a new kernel? because sifting through the Internet I found this: https://developer.qualcomm.com/mobile-development/mobile-technologies/gaming-graphics-optimization-adreno/tools-and-resources there are also drivers for jelly bean of adreno 2xx
Click to expand...
Click to collapse
yeah, those are the drivers
But they do not require a new kernel
Lexmazter said:
yeah, those are the drivers
But they do not require a new kernel
Click to expand...
Click to collapse
but I need or I do not need?
Hi
I read this topic https://forum.xda-developers.com/showthread.php?t=3453464 and just want to k ow is there anyone make it something like this ?
It's disabled Knox on kernel side and users of the kernel can use Samsung pay, Samsung pass etc.
I read the kernel topics before posting but there is no kernel like I mention it.
Help ?
Ozgurce said:
Hi
I read this topic https://forum.xda-developers.com/showthread.php?t=3453464 and just want to k ow is there anyone make it something like this ?
It's disabled Knox on kernel side and users of the kernel can use Samsung pay, Samsung pass etc.
I read the kernel topics before posting but there is no kernel like I mention it.
Help ?
Click to expand...
Click to collapse
As he stated it needs to be disabled via defconfig which means you need the source and to compile the kernel yourself. Stupid simple just need the source
Hmm. I Will try it then. Is there any good articles you know for learning basic kernel repacking I mean yes I can search it too but if you suggest anything? Do I need anymore then basic coding ?
Sorry but I'm really noob on the kernels.
I just know pack-repack apks, I know some apktool and some update script for recovery.
AFAIK there is source code for note 5 do I need more then that ? Like exynos sources ? It's didn't released though.
Ozgurce said:
Hmm. I Will try it then. Is there any good articles you know for learning basic kernel repacking I mean yes I can search it too but if you suggest anything? Do I need anymore then basic coding ?
Sorry but I'm really noob on the kernels.
I just know pack-repack apks, I know some apktool and some update script for recovery.
AFAIK there is source code for note 5 do I need more then that ? Like exynos sources ? It's didn't released though.
Click to expand...
Click to collapse
You need to do more than just unpack and pack the boot.img.
You also need to a pc with Linux to compile the kernel. Ubuntu is the most common/used in guides as it's pretty simple "install and play" distro. Personally use/prefer Arch.
But @TheSickness has a pretty legit guide and script for the s6 which should be easily used/adapted for the n5.
https://forum.xda-developers.com/galaxy-s6/general/guide-how-to-build-samsung-kernel-july-t3429355