Dear XDA-Community!
Im new here so i'd like to introduce me quickly.
Im Alex, 18 years old (at the time of this writing) and im from Austria.
Before i owned a Galaxy Ace and got our p970 some months ago.
Now to my question
I tried my hands on building cyanogenmod 10.1 for the p970.
i build it with the standard toolchain and it worked perfectly.
now im trying to build it with the Linaro 4.8 Toolchain, but it isnt booting and i do know its a kernel fault.
i know this because if i flash my Cyanogenmod Build, it doesnt boot, BUT if i flash it and then flash the ZeroGravitiyKernel from here
http://forum.xda-developers.com/showthread.php?t=2082740
it boots up perfectly.
So i would like to know, if someone had succcess with building our kernel with a Linaro Toolchain and which patches i may or may not have to apply.
i tried using the ZeroGravitiySources but still it fails to boot up after flashing.
(also i did a quick benchmark test with rom toolbox and the build with the standard toolchain gets 7.3 and with using linaro and the other kernel i get 10.2)
any help is much appreciated
Yes the problem is the kernel. ....it was not easy to make the kernel boot...
Use my patch from my topic...
http://forum.xda-developers.com/showthread.php?t=2184519
This patch is for ICS v30c.....you can diff the patch with original files....and put the same in your kernel...
You can find original files from Nooby's git...and dowload only those specific files to see the diff......
Sent from my LG-P970 using xda app-developers app
rajeshmk2012 said:
Yes the problem is the kernel. ....it was not easy to make the kernel boot...
Use my patch from my topic...
http://forum.xda-developers.com/showthread.php?t=2184519
This patch is for ICS v30c.....you can diff the patch with original files....and put the same in your kernel...
You can find original files from Nooby's git...and dowload only those specific files to see the diff......
Sent from my LG-P970 using xda app-developers app
Click to expand...
Click to collapse
Thank you very much, already used it some days before and got it working, forgot to update here
Cherry Picked a lot of patches etc.
i just wondered, because i cloned his source and compiled without changing anything with the same toolchain as he was using and i didnt got it to boot.
Related
Just wondering if the Linero Code optimizations would have any impact on the captivate and if so, are any ROMS going to be implementing them?
From what I understand the Linaro optimization is a kernel mod not a rom tweak. With that being said Icy Glitch uses an older version of Linaro and he is looking at updating it to the newest version but had problems downloading the source. AOKP has their default kernel as Icy Glitch so maybe in the next update, but not really sure.
This has been a hot topic after the video of the new optimization that was posted.
That is a bit depressing if true.
It was my understanding that it was an optimization to the operating system itself. I really wish they would clarify these things in articles.
Oh well...
fryboy3k said:
From what I understand the Linaro optimization is a kernel mod not a rom tweak. With that being said Icy Glitch uses an older version of Linaro and he is looking at updating it to the newest version but had problems downloading the source. AOKP has their default kernel as Icy Glitch so maybe in the next update, but not really sure.
This has been a hot topic after the video of the new optimization that was posted.
Click to expand...
Click to collapse
Where did you hear this about glitch?
Sent from my SGH-I897 using XDA
Read the OP for the icy glitch thread under development, it shows 4.4 linaro was used i believe. In the AOKP thread sixstrings replied to a question about linaro.
Sent from my SGH-I897 using XDA
I believe Linaro optimizations is both kernel (toolchain) and rom modifications. Glitch does use a older version of said toolchain and I know that DerTeufel1980 and Stratosk where messing with it. Feed back about the actual kernel optimization has been very mixed. i9k semaphore alot of ppl say its amazing. Other devices say not big difference. All I know we have to be patience and wait until your great devs get it set up (all of it) right and really see if this works
I will try to compile the kernel 3.1.10 for galaxy mini.
I wanted to have a very detailed guide. since they are in the early stages.
[email protected] said:
I will try to compile the kernel 3.1.10 for galaxy mini.
I wanted to have a very detailed guide. since they are in the early stages.
Click to expand...
Click to collapse
good luck, but you only cluttering dev section with that... post "i will do" in general
my computer is suddenly broken, can someone fill this kernle using this config file (do not change the config file) and uplodarlo in men flashable zip so that I can test it?? please file config name
cyanogenmod_tass_defconfig
Good jobs man
GT-S5570 with Forum Runner
Please make it first n try to make sure it working before u create new thread..
many people already say want to make this , make that but
they just keep silent without any news ..
i not judge u but i feel boring when people keep say / ask same thing everyday
and not make some research about it..sorry if i hurt u feeling but as the one of xda dev members , i think i should inform u..
Peace & have a nice day ....
Wtf? U have almost said this in 10-12 post spamming around in all threads!.
Sent from my GT-S5570 using xda premium
What's the point? It's 100% it won't boot. Samsung hasn't released 3.x with changes needed for Mini's drivers... You have to forward port a lot of things.
Yeah it is like try running ics kernel on defy (which have kernel from froyo). That's why i think kernel 2.6.35.14 have some bugs and the 2.6.35.7 doesn't have.
@TheWhisp you tested on Cm10 which kernel is more stable 2.6.35.7 or 2.6.35.14 or you just tested cm10 with the 2.6.35.14?
gabrielking9 said:
Yeah it is like try running ics kernel on defy (which have kernel from froyo). That's why i think kernel 2.6.35.14 have some bugs and the 2.6.35.7 doesn't have.
@TheWhisp you tested on Cm10 which kernel is more stable 2.6.35.7 or 2.6.35.14 or you just tested cm10 with the 2.6.35.14?
Click to expand...
Click to collapse
2.6.35.7 kernel was made by Maclaw, and I don't see the point on restarting a older kernel (they will have to backport the same and probably other things again) as 2.6.35.14 is stable enough.
a 3.0 kernel won't be bad, but look at other Galaxy legacy devices forum (I think it was Galaxy i5500 or something like that), they have been working on a 3.0 kernel for a while and it doesn't even boot, they are making progress, but they have to change a LOT of things (partition scheme is a example, this means it won't be compatible with Odin anymore). It's pointless.
The development of the 3.1.10 kernel release Pottete expect between 15-20 days.
In the meantime, I was wondering, since I am very busy could fill kernel 2.6.37.6 based on this (CM9) http://forum.xda-developers.com/showthread.php?t=1804646 and last config TheWhisp JB in order to have a more updated kernel, also enter toolkit linato When completed please post the kernel of quests theater
If u ar determined to create 3.x.x kernel I suggest u take reference of CYANMOBILE LATEST STABLE kernel its already a version 3.3.3 kernel.
Anindya JV said:
If u ar determined to create 3.x.x kernel I suggest u take reference of CYANMOBILE LATEST STABLE kernel its already a version 3.3.3 kernel.
Click to expand...
Click to collapse
Such kernel does not exist! Squadzone rename his kernel like this when he compiled it. So please don't say something like this. Kernel 3.x.x exist onlt for high end device like gs3 or others.
Sent from my GT-S5570 using xda premium
lightstar3103 said:
Such kernel does not exist! Squadzone rename his kernel like this when he compiled it. So please don't say something like this. Kernel 3.x.x exist onlt for high end device like gs3 or others.
Sent from my GT-S5570 using xda premium
Click to expand...
Click to collapse
Sorry,I didn't know that.
THANKS FOR THE INFO BY THE WAY.
Guys I have made a custom rom based on CM7.nAa 14 kernel is compatible with CM7.But I want my custom rom also to support it.http://forum.xda-developers.com/images/smilies/crying.gifI have downloaded the .ftf kernel file and I have also extracted it.What changes do I have to do in my rom to make my rom work with the kernel?
Please give a detailed answer.
@OP
Well kudos to you for finding the right section. And what CM7 ROM exactly have you based your ROM on?
It already started working.But thanks for you trying to help.
What I want to know is that there is no networking in my rom.
Please help me fix it.I am talking about a custom rom developed by me based on cm 7.1.
What CM7.1 ROM have you based this on? I'm asking whether you have based your work on any existing ROM or not and the name of that ROM. If that ROM supports nAa-14 kernel, then your ROM will support nAa-14 kernel too.
My rom is supporting the nAa 14 kernel,I have tested it I have a bug in the network. It has no network at the moment. Do you know a fix for this bug ? I am running a rom that is developed by me and I am now testing it.
I haven't released the from here yet.
Sent from my X8 using xda app-developers app
Network bug? I don't even know if logcats can be used to debug. Can you try re-flashing the kernel and the ROM?
Basically you not need to change anything in the kernel. You need change the userspace drivers in the rom to match with the kernel level drivers. Both active x8 gb kernel (nAa and alfs) use similar drivers, except the proximity sensor (nAa use a modded one, alfs use the stock driver), you can use both with the correct libsensorservice and hw libs. And not 100% sure, but nAa use the older kgsl driver (1.1) alfs use newer (1.2), need to change the driver in the rom (libgsl.so).
To solve the network errors, you need to check the RIL related binaries and settings. Better if you give more detailed infos your base rom, the "cm7.1 rom" is not enough. CM7 but the origins? CM7 exists on thousands of phones. Better if you use x8 rom, or rom from a phone what use same hardware (msm7x27 like lg p500, galaxy mini, htc legend, etc...)
Sent from my E15i using xda app-developers app
What more should I add to"cm 7.1"? Please make it clear. Its downloaded from the cyanogen mod download center. It is used as my base rom. I modded it with certain tweaks and replaced many apps and also added many other mods
Sent from my X8 using xda app-developers app
You could have said that it was downloaded directly from cyanogenmod.com for a start. It's pretty confusing when you say just CM7.1 because there are hundreds of CM7.1 ROMs lying around the Development forum, some for stock kernel, some for nAa-gb and others for alfs-gb.
Let me give you a tip if you're just adding tweaks and other mods, and not modifying it on a large scale. Instead of releasing a ROM, why not release a flashable-zip that will make required changes to the existing ROM that users are on. It will be unique and if you want, I can help you with it.
Summary: Why waste time releasing a ROM (~80MB) when you can release a flashable-zip (~10-15MB)?
Cheers.
sgt. meow
I just asked what is your base rom because we not have official cyanogenmod support. If you use only the cm repo to build a complete rom, it will be really hard, due the missing device specific parts. So, the question again (I hope it is clear): you use only the cm repo as base OR use unofficial cm repo from nAa (with working device specific settings/codes) OR use prebuild cm7.1 rom from x8 OR use prebuild cm7.1 rom from other phone. All options is a cm7.1 rom, but all need different works.
From the best to the worst:
1. Use the minicm repo from nAa (nothing to do to get fully working rom)
2. Use prebuilt x8 rom as base (basically not need to do anything)
3. Use the official cm repo (need lot of work because missing a lot of thing)
4. Use any non x8 prebuilt rom (basically the hardest way, need large amount of work with hw related things)
Sent from my E15i using xda app-developers app
@pilu1978
We used to have official CM support till CM7.2 (I guess). It's stated in the CM Shakira page. And you can build CM7 from source as EET has explained in his tutorial. But in any case his best option (if he's going to compile from source) is to use MiniCM7 repo. It's the most updated one.
Plus it will support nAa-14 without any modifications.
The OP wrote this is cm7.1, not 7.2 As I know the official cm7 support is not complete, but my knowledge is NOT unlimited And we not have cm kernel.
Sent from my E15i using xda app-developers app
pilu1978 said:
I just asked what is your base rom because we not have official cyanogenmod support. If you use only the cm repo to build a complete rom, it will be really hard, due the missing device specific parts. So, the question again (I hope it is clear): you use only the cm repo as base OR use unofficial cm repo from nAa (with working device specific settings/codes) OR use prebuild cm7.1 rom from x8 OR use prebuild cm7.1 rom from other phone. All options is a cm7.1 rom, but all need different works.
From the best to the worst:
1. Use the minicm repo from nAa (nothing to do to get fully working rom)
2. Use prebuilt x8 rom as base (basically not need to do anything)
3. Use the official cm repo (need lot of work because missing a lot of thing)
4. Use any non x8 prebuilt rom (basically the hardest way, need large amount of work with hw related things)
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
I am using a prebuild x8 rom and modding it
And what is the original rom, what you use as base rom? If it is a stock kernel based rom, you need to change the drivers (sensors, gsl, egl, etc) to work with nAa kernels, if it is a minicm based rom, nothing need to do it will work with nAa kernel.
Sent from my E15i using xda app-developers app
I think he got over that problem by now. LOL.
No man its not working.
See I will explain my question once more. I am using this rom as my base rom: http://download.cyanogenmod.org/?type=stable&device=shakira
I want to make this rom compatible with custom kernels like nAa 14 and alfs etc so what should I do exactly?
If I have to change my drivers then please explain to me how to change my driver to these kernels and also tell me where to find the driver files in the rom and also tell me the download link for the drivers please.
I will be very grateful!
THANKS in advance. Please someone help me.
CyanogenMod 7.2 Specific BASIC Kernel - Cooperve
We are planning to release a kernel that con work on both devices, a BCM21553-common kernel, but that is hard work, as we must compare all the files from kernel, and test everychange.
FEATURES:
Due to the kernel is pretty advanced, we are not talking of a TO-DO list, we are talking about a FEATURES list, so the FEATURES are:
Kernel just compatible with CM7
Specific Basic - Samsung official not-modded sources
EXT4 support
CWM Inclluded on kernel with EXT4 support too
Images of CWM patched to show good colors
Bluetooth and Wifi configs added to work with CM7
Common ramdisk used based on kissingmylove and PsychoGame
Ramdisk optimized for CM7 and EXT4
Compressed through LZMA
IMEI working on CM7
Offline charging working on EXT4 CM7
SOURCES:
KERNEL SOURCE (GPL) is the official samsung kernel, as it is a specific BASIC kernel:
Sources of kernel: http://opensource.samsung.com/
I needed to modify the configs to get a BT, Wifi, and EXT4 working, this is not included on Samsung stock kernel, so I leave here the config source:
Source of defconfigs: https://github.com/broadcomCM/android_kernel_bcm21553-common_configs
Ramdisk has been also modd to create a bcm21553-common ramdisk that all users could use. SOurces to ramdisk can be found extracting from my kernel (LZMA) or also on github.
Sources of Ramdisk: https://github.com/broadcomCM/android_device_samsung_bcm21553-common_ramdisk
If other kernel developers want to contribute on this, shot me a PM, and I'll talk with you.
Thanks, Biel.
CHANGELOG
Version 4.0
Same build as version 3.0 , #7
Bigger cleanup ever made on ramdisk, to match CM7 and CM9 requiriments.
Added new BroadcomCM temp. CWM, with colors fixed.
Reduced booting time
Built with first 100% BCM21553 common ramdisk working based on AOSP ROMs.
Version 3.0
Clean Ramdisk as always
Included EXT4 and RFS (for not causing bricks) mounts on init.charge.rc
Start EXT4-fix in init.charge to mount syste, data, cache on inir.charge.rc and solve offline charging.
Version 2.1
Cleaned Ramdisk
Added permissions to camfash - for CM7
New built from same source and config
Version 2.0
Re-built ramdisk based on kissingmylove ramdisk
Delete all tweaks he added - BASIC KERNEL
EXT4 file system support for CM7
Hacked CWM Images to have a good color (no blues anymore)
Added some bootscripts to have better compatiblity with EXT4
Recovery has been updated to CWM 5.0.2.8
Mount USB mass storage is now working
CWM "HD" Edition, much more clear and tiny
Much more faster recovery
Version 1.0
First release of this kernel builded from source
First kernel with my name on it
Added new modify it ramdisk
Compressed throug LZMA using Lopicl.00 kitchen
Added CONFIG_SENSORS_COOPERVE=y
Added all the configs necessary to use Bluetooth on CM
Bluetooth working on new CM7 release, which should be RC1
Fixed CM7 bootanimation - thanks Prototype-U
Version 0.1
First release of this kernel
Not builded from source
Using Hell-lock kernel (Prototype-U) as zImage base
Modify lopicl.00 ramdisk and ad it to this kernel
Used LZMA to compress ramdisk
Fixed WIFI and torch on the ramdisk CM7.2
Not compatible with STOCK!
Issues with the kernel:
SIM contacts reading
Sometimes CWM can not find cache/recovery/log
DOWNLOADS
All downloads can be found here:
DOWNLOAD HERE
Last kernel verison download:
http://www.mediafire.com/download/7188za13itwcnim/kernel_CM7_v4.0_cooperve.zip
THANKS
BroadcomCM Team
Spacecaker
Lopicl.00
Kissingmylove
Percy-g2
Others:
Savie
Prototype-U
First poster! xD
By the way, I can help you, but I have to learn more about kernels! (you know! Mentioned in chat! )
Inviato dal mio GT-S5830i con Tapatalk 2
PM sent.
Man, seeing this and not being able to help makes me feel useless.
Sent from my GT-S5830i using xda app-developers app
Nice work biel, appreciate it.
mathm2013 said:
Man, seeing this and not being able to help makes me feel useless.
Sent from my GT-S5830i using xda app-developers app
Click to expand...
Click to collapse
Dude, dont feel useless. Maybe we are not as experienced as them, different people are better at different things. So relax.
Sent from my GT-S5830i
Great,:thumbup:
my kernel also coming .
Sent from my LT22i using Tapatalk 2
First kernel built. On samsung sources, and just zImage at the moment. Dunno if will boot or not keeping u informed.
bieltv.3 said:
First kernel built. On samsung sources, and just zImage at the moment. Dunno if will boot or not keeping u informed.
Click to expand...
Click to collapse
I can check.
Only then how to restore the phone, if one does not work?
Maslin Sergey said:
I can check.
Only then how to restore the phone, if one does not work?
Click to expand...
Click to collapse
Flash another kernel bro if it won't work
Sent from my GT-S5830i using xda premium
biel can you do a git diff and git status with the boot.img of yours and the boot.img of hell lock/rafael ?
with that we can see what has changed and fix it on the sources
Sent from my S500 using xda app-developers app
SpaceCaker said:
biel can you do a git diff and git status with the boot.img of yours and the boot.img of hell lock/rafael ?
with that we can see what has changed and fix it on the sources
Sent from my S500 using xda app-developers app
Click to expand...
Click to collapse
I cant make a diff from a boot.img
If nkt working flash with ODIN solve problems
Enviado desde mi GT-S5830 usando Tapatalk 2
bieltv.3 said:
I cant make a diff from a boot.img
If nkt working flash with ODIN solve problems
Enviado desde mi GT-S5830 usando Tapatalk 2
Click to expand...
Click to collapse
no from extracted boot.img i meant
Sent from my S500 using xda app-developers app
SpaceCaker said:
no from extracted boot.img i meant
Sent from my S500 using xda app-developers app
Click to expand...
Click to collapse
Yes well I'll push changes to kernel asap as I make
Other idea:
Okey guys I got it after lot of searching and thinking + confirmed by psyke83 (developer from Galaxy 5) the reason why not booting is the kernel. ANd it's weird because Hell-lock kernel was fine till now
http://pastebin.com/zYFQf8Z0
Error could seem a ROM error, but init.rc script must to be modifyied to locate dalvik. Probaly dalvik and cahce in EXT4. So we need the port from the other kernel to work new CM7. That will be long without the device, really long...
Thanks, Biel
bieltv.3 said:
Yes well I'll push changes to kernel asap as I make
Other idea:
Okey guys I got it after lot of searching and thinking + confirmed by psyke83 (developer from Galaxy 5) the reason why not booting is the kernel. ANd it's weird because Hell-lock kernel was fine till now
http://pastebin.com/zYFQf8Z0
Error could seem a ROM error, but init.rc script must to be modifyied to locate dalvik. Probaly dalvik and cahce in EXT4. So we need the port from the other kernel to work new CM7. That will be long without the device, really long...
Thanks, Biel
Click to expand...
Click to collapse
also change the bootclasspath to the proper CM7 BootClassPath
Trying to port PsychoGame's 2.6.35.14 kernel... https://github.com/Lopicl/android_kernel_samsung_cooperve_cm_port-2.6.35.14
Lopicl.00 said:
Trying to port PsychoGame's 2.6.35.14 kernel... https://github.com/Lopicl/android_kernel_samsung_cooperve_cm_port-2.6.35.14
Click to expand...
Click to collapse
That is done already by me, psychogame and kissingmylove. Give a try, you will probably give us more information about it.
Enviado desde mi Nexus 7 usando Tapatalk 2
Hi all,
First of all, I hope that is this question was not yet in the forum. At least, I have searched for it.
Well, I'm trying to compile LG P990 kowalski kernel from @pengus77 from it's github sources (github(dot)com/pengus77/lge-kernel-star)
Currently, I'm using the oldBL and I'm compiling the kernel using Linaro toolchain 4.6.2 (in Ubuntu).
I can compile the kernel without major problems, and both zImage and modules are generated. After, I used the the anykernel script (for old bootloader - oldBL), the same used by @pengus77 to distribute the kowalski.
The problem is that I can not boot the phone using the zImage compiled by myself. It always stucks in LG Logo.
Do you have hint to this? It might be a problem with environment setup and/or with Linario toolchain version?
All your possible help will be appreciated.
Many thanks!