Related
Hi everyone,
The forum didn't let me post in the relevant thread, so I hope I'll get noticed here.
For starters, I've successfully built and used additional modules with pershoot's kernel so I have the basics down.
Next, I'd like to use oprofile, unfortunately oprofile can't be loaded as a module unless the kernel is rebuilt with profiling enabled. Inspired by this tutorial I built a full kernel, grabbed boot-cm_2636.4_ux-oc-xtra-vfpv3-d16_fp-091311.zip and replaced zImage, dhd.ko and scsi_wait_scan.ko in the zip and flashed it with CWM.
Unfortunately it doesn't work, when booting the tab shows the logo and padlock, there it gets stuck and nothing more happens. Using the original kernel config without any changes doesn't help either.
The procedure I used to build the kernel (using codesourcery 2010.09) is in short:
git clone git://github.com/pershoot/galaxy-2636.git
make pershoot_samsung_p4wifi-ux_defconfig
make -j8 ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-
Kernel modules from the build can be insmoded and used on the device. Any suggestions on how to get the entire custom built kernel up and running is greatly appreciated.
/Lakristrolle
OPROFILE is already enabled in this kernel:
grep OPROFILE arch/arm/configs/pershoot_samsung_p*
arch/arm/configs/pershoot_samsung_p3_defconfig:CONFIG_HAVE_OPROFILE=y
arch/arm/configs/pershoot_samsung_p4lte_defconfig:CONFIG_HAVE_OPROFILE=y
arch/arm/configs/pershoot_samsung_p4-ux_defconfig:CONFIG_HAVE_OPROFILE=y
arch/arm/configs/pershoot_samsung_p4wifi_defconfig:CONFIG_HAVE_OPROFILE=y
arch/arm/configs/pershoot_samsung_p4wifi-ux_defconfig:CONFIG_HAVE_OPROFILE=y
Hi pershoot,
Tanks for your reply. That option doesn't enable oprofile, I have no idea what it does. This can easily be verified with "grep oprofilefs /proc/filesystems" on the tab, it comes up blank when running your kernel.
To enable it for real, add the following to the config:
CONFIG_PROFILING=y
CONFIG_OPROFILE=y (or m)
If you could do this in your kernel builds it would be awesome!
Otherwise, I'd really appreciate it if you can give some instructions or point me to a tutorial on how to make my own kernel.
/lakristrolle
i will enable profiling in the next update.
pershoot said:
i will enable profiling in the next update.
Click to expand...
Click to collapse
Thanks a million!
In the mean time I'll be off on the next adventure, finding or building the user-space oprofile tools.
/lakristrolle
Did we just get a second kernel dev! Hooray GT10 developers!
Feature request: I'd like the next kernel to "pop" and taste great smothered in butter.
This is a dev thread. Do not install this release unless you know what you're doing. Do not post if you have nothing to contribute.
This is very early build, we're behind other qsd8k devices but will eventually catch up
Big thanks to all qsd8k developers working on this (N1, Desire, HD2, X10).
[KERNEL]
- ol' good 2.6.29-SEMC
- fixed touchscreen driver (now backward-compatibile with Gingerbread)
[ROM]
- partially based on drewis release (thanks!) - currently I don't have access to PC that could handle compilation of the whole thing
If someone could compile clean es209ra build and upload it would be awesome.
[WORKING]
- it boots
- radio, calls, txt (sms)
- audio partially working (in-call is fine, playing mp3/ringtones leads to WLOD)
- bluetooth, GPS seem to work
- wifi almost working ("can't find wlan0 device")
- mobile data (it gets IP but disconects afterwards, needs investiagtion)
[NOT WORKING]
- most of the stuff does not work
- quite unstable
[SOURCES]
Will upload all of the useful code/fixes here.
- ICS + GB compatibile touch driver: es209ra_touch_mt.c
- compatibile ramdisk (props FXP): http://www.mediafire.com/?1n51pn1upwv79ur
[DOWNLOAD]
Alpha1 ROM (for CWM5) + corresponding kernel (flashtool) is here:
http://www.mediafire.com/?ht6p6tbpj2988d4
Cheers,
z
Just did a major clean up on this thread mates....no more "thanks" posts please. If thankful... click the thanks button.
Regards,
M_T_M
Finally we get it. aZuZu is working on ASOP ICS 4.0.1. This may help him work easier. So with locked bootloader, can we flash cause' you wrote there CWM5?
VIDEO
here's a video for ics on x10 alpha build 1
http://www.youtube.com/watch?v=bsOFn4YLvZU
@frosty666 please kindly include this on your ics discussion thread.
thankz
hi zdzihu, its great to see you back! is this only temporary or, are you going to be more active, like before?
mmmkay, I'm not dev, but I want to ask if you're compiling this from ground up (like Jerpelea's CM7), or you're like just mashup of current SE and ICS sources. if its a mashup, I can help. but I do very little design from ground up things.
Sent from my X10i using xda premium
if you have fixed audio hw sources i could recompile..
altho i have complete es209ra compile with ics hw, old cm gralloc / copybit sources and generic audio..
So for me doesn't even boot
As i came from night shift i will try later on more...
Here you are libhardware.so, libhardware_legacy.so & wpa_supplicant from my compiled ICS build so if someone can boot z rom maybe it could test this too
p.s.
it is searching ar6000.ko as normal stock one not wifi.ko as sdk port
aZuZu said:
So for me doesn't even boot
As i came from night shift i will try later on more...
Here you are libhardware.so, libhardware_legacy.so & wpa_supplicant from my compiled ICS build so if someone can boot z rom maybe it could test this too
p.s.
it is searching ar6000.ko as normal stock one not wifi.ko as sdk port
Click to expand...
Click to collapse
Hi Azuzu, I am able to compile single libs and binaries (libhw_legacy, supplicant), it's just dex and stuff causing problems (1GB of ram + 1.6GHz). As for libaudio, I will take a look soon
Cheers,
z
I help if u want
Hello guys, I'm new to the forum and I hope to see well with you.
I would be willing to help compile the source since EXCLUSIVELY use only Linux operating system and is much easier to work on programming because most of the libraries are already installed by default, I hope I was clear.
greetings
Joseph
zdzihu said:
Hi Azuzu, I am able to compile single libs and binaries (libhw_legacy, supplicant), it's just dex and stuff causing problems (1GB of ram + 1.6GHz). As for libaudio, I will take a look soon
Cheers,
z
Click to expand...
Click to collapse
yaay Z!!!
glad to see back!
now i feel so bad & depressed that i dont have a working x10 with me
hope that service center guy is able to repair it again...
@aZuZu
can u please upload ur work-in-progress sources to git... i know how much fixing u have done... it might help other too
aZuZu said:
So for me doesn't even boot
As i came from night shift i will try later on more...
Here you are libhardware.so, libhardware_legacy.so & wpa_supplicant from my compiled ICS build so if someone can boot z rom maybe it could test this too
p.s.
it is searching ar6000.ko as normal stock one not wifi.ko as sdk port
Click to expand...
Click to collapse
so good
I will try to build ICS this weekend!
I have no time this weekday
Zdzihu, if the wifi still reports the same error (can't find wlan0 device), it probably means that the kernel refers to wlan interface as eth0. Try changing the wifi.interface entry in build.prop to eth0.
little help for folks that compile ICS on weak pc
make: *** [out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/noproguard.classes-with-local.dex] Killed << if processes during compile get killed try this script > Fix Swap
Well to me helped so maybe it helps other ppl.
Has anyone pulled this Kernel apart, i'm trying to lock down some of the touch screen info but I can't gunzip the ICS ramdisk...not even sure if i should be able to.
I GPIO the main files out, can't see anything pertinent in there, so I can only assume its in this ramdisk...biggest problem is that if it is a corrupted archive I can't get ubuntu to open a recovery tool cos it's implementation of the Zlib system sucks dice
WHAT IS IT WITH SOME OF YOU GUYS, IT IS DEV ONLY THREAD AT THE REQUEST OF THE DEVELOPER, IF YOU CAN'T FOLLOW SIMPLE RULES THEN INFRACTIONS WILL BE HANDED OUT, YOU HAVE NOW BEEN WARNED!
wbbigdave said:
Has anyone pulled this Kernel apart, i'm trying to lock down some of the touch screen info but I can't gunzip the ICS ramdisk...not even sure if i should be able to.
I GPIO the main files out, can't see anything pertinent in there, so I can only assume its in this ramdisk...biggest problem is that if it is a corrupted archive I can't get ubuntu to open a recovery tool cos it's implementation of the Zlib system sucks dice
Click to expand...
Click to collapse
gunzip -c <ramdisk.gz> | cpio -i
Cheers,
z
The next member who disregards a developers request and posts in a non helpful way will be banned for a week.
i encourage any dev or helpful member to pm me or any other mod with the offending post and the user will be dealt with
Please don't reply tp them to tell them they are breaking th rules as you post will then also be rule break worthy
Hugs and kisses
PiLoT
http://review.cyanogenmod.com/#q,status:merged+project:CyanogenMod/android_frameworks_base,n,z
sorry for posting here. but is for development. for ICS, can we used modified 2.6.29, and modify, like what zdzihu did, it so it 100% or do we have to use 3.x (or whatever) becuase I'm starting to do kernel mods and I want to see what I can contribution.
so in all, does the newest kernel have to be ported? or can we continue using good old 2.6.29 and keep Modding it? (hopefully camera will work, drivers have to be rewritten for kernel. and no one likr to write drivers)
Sent from my X10i using xda premium
In case, we can see here how they get the SD Card working
http://forum.xda-developers.com/showthread.php?p=19774268#post19774268
I've had a search and a look around but can't see anything specific enough to answer this.
I have read that the SGS2 uses the new BCM4330 chipset for it's WiFi-N support.
It looks to me that for existing kernels they are using either the existing kernel support or possibly the b43 driver.
I need to find out, and while I have compiled custom kernels in nix in the past, I have never done so in Android, so I'm a little out of my comfort zone here.
I want to compile a kernel where the WiFI driver will support monitor mode, ideally it would be the CM7 kernel with just this extra functionality added, however a number of the tools that I would use to identify the existing configuration do not seem to be available in the standard CM7 build (lspci being one).
I don't want to frack around too much without having read up first so could anyone point me at a good guide for creating my own Android Kernel, even better if the guide was specific to the CM7 version.
Lastly I mostly run a Fedora environment, however the bits I have read seem to suggest a number of tools are only available in a Ubuntu guise (heimdall springs to mind and while I'm sure it's possible to recreate it for Fedora I'm trying to reduce the number of dependencies I'll have to recreate as much as possible). Therefore can I get some advice regarding the least complicated way to generate an Android build environment in Linux.
Thanks
For kernel compilation on android, you can check the several repositories there are for the several kernels. Depending on each kernel/repository/user, you can find a predefined .config inside them, so you can get the basic configuration to compile the kernel, don't know if CM7 has it in its repository...
As for the enviorment, I haven't tried compiling a kernel, but I did compile some ROM on Gentoo Linux, so I suppose it could also be done in Fedora without many problems. The main thing about using Ubuntu is that is very extended, so they're using it as main Linux base, but that doesn't mean it can't be done in other linux distros. You can check CM7 wiki for building from source to install the required packages for your enviorment. In my case I cross checked the Ubuntu packages with Gentoo to install gentoo's version of that packages/tools to be able to compile without problems.
Also in the case of building kernels, you need a toolchain to be able to compile, but there are several webs/tutorials with info on how to use that.
EDIT: You have a complete tutorial for CM7 in their wiki with the needed packages for both Debian and Red Hat based distributions...
Very useful, thanks for the info.
Very useful info.
Hi,
I'm interested in compiling a custom kernel to support wifi monitor mode, but I read in a previous post that it can be a hardware limitation which makes it impossible to use monitor mode. Can anyone confirm that? Maybe a statement/answer from Broadcom?
I'm just asking it because I don't want to start playing with kernel compilation and driver hacking if it can't be done because of some missing code on the chipset or something.
Thanks.
kepten said:
Can anyone confirm that? Maybe a statement/answer from Broadcom?
Click to expand...
Click to collapse
I doubt Broadcom will answer that, but you can try to search the chipset info in Broadcom's web and see if its supported. Also you can check kernel modules if they can compile against that version.
AzureusPT said:
I doubt Broadcom will answer that, but you can try to search the chipset info in Broadcom's web and see if its supported. Also you can check kernel modules if they can compile against that version.
Click to expand...
Click to collapse
Well, Broadcom's website says nothing about monitor mode but I've found a driver (https:// github.com/cyanogen/galaxy-2636/blob/ics/drivers/net/wireless/bcm4330/src/include/wlioctl.h#L1153) which at least mentions it. This is for Galaxy Tab 10.1 which has the same chipset so maybe someone with a Tab 10.1 could verify if monitor mode works with that kernel/driver? ??
Hi all,
In short i want to modify Android 4.2.2 on my MK802IIIS to allow me to use an external USB WIFI Adapter. The one i have uses a Ralink (MediaTek) RT5372 chipset.
I'm not a beginner, but by no means an expert. I have compiled firmware for my Linux based routers. But compiling Android, or parts of, seems much more complicated. I only want to add support for a USB adapter. Do i need to build the kernel from scratch, or can i create a module? Do i need to cross compile a module or can it be "made" in Ubunutu and just copied across?
I have searched for a RT5372.ko file online, finding references to RT5370, but i dont think it's the same.
I downloaded the driver from the Mediatek website and proceeded to attempt to create a .ko file by making it in Ubuntu but it only created a RT5372STA.dat file. Does this driver need to be cross compilied for android? Also how do i turn it in to a module that i can just load into my currently installed ROM?
I have been poking around for a while so i havent covered everhything i've tried. I'd really like to understand how building for Android works. If anyone can answer any of these questions for me, it'd help me imensely. Or if there is a resource covering these topics that i have yet to come across please point me at it. I know there are a lot of very detailed How-To's for compliling but i seem to get lost with the amount of detail.
Many thanks
More info regarding my setup:
Building in Ubuntu 14.04, 64bit.
The current ROM appears to have been built using the Linaro 4.6.2 toolchain, so u have downloaded that, currently stored in /home/wriggerz/RK3066/Toolchains
Also downloaded the RK3066 Kernel Source, stored in /home/wriggerz/RK3066/RK3066-Kernel
The RT5372 driver has been extracted to /home/wriggerz/RT5572NEW
I've been mashing bits of different guides and suggestions found on other forums together to try and frankenstien this KO module. From within the drivers folder i ran the two commands below. From what i've read this needs to be done to specify which "Toolchain" and "Compiler" to use.
Code:
export CROSS_COMPILE=~/home/wriggerz/rk3066/toolchains/arm-eabi-linaro-4.6.2/bin/arm-eabi-
export ARCH=arm
Then i ran the make command like below to try and have the driver built for the correct Toolchain with the correct Compiler:
Code:
make ARCH=arm CROSS_COMPILE=arm-eabi-linaro-4.6.2
However i get the following response:
Code:
make -C tools
make[1]: Entering directory `/home/wriggerz/RT5572NEW/tools'
gcc -g bin2h.c -o bin2h
make[1]: Leaving directory `/home/wriggerz/RT5572NEW/tools'
/home/wriggerz/RT5572NEW/tools/bin2h
cp -f os/linux/Makefile.6 /home/wriggerz/RT5572NEW/os/linux/Makefile
make -C /lib/modules/3.16.0-30-generic/build SUBDIRS=/home/wriggerz/RT5572NEW/os/linux modules
make[1]: Entering directory `/usr/src/linux-headers-3.16.0-30-generic'
Makefile:652: Cannot use CONFIG_CC_STACKPROTECTOR_REGULAR: -fstack-protector not supported by compiler
make[1]: arm-eabi-linaro-4.6.2-gcc: Command not found
CC [M] /home/wriggerz/RT5572NEW/os/linux/../../common/crypt_md5.o
/bin/sh: 1: arm-eabi-linaro-4.6.2-gcc: not found
make[2]: *** [/home/wriggerz/RT5572NEW/os/linux/../../common/crypt_md5.o] Error 127
make[1]: *** [_module_/home/wriggerz/RT5572NEW/os/linux] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-3.16.0-30-generic'
make: *** [LINUX] Error 2
Someone knowledgeable will hopefully look at the steps i have just taken to rip it to shreds...... :fingers-crossed:
If not, is there anyone with any ideas of where i'm going wrong?
I think i've put this in the wrong section....
If anyone has to go out of their way to move it they have my sincere apologies.
J Double You said:
I think i've put this in the wrong section....
If anyone has to go out of their way to move it they have my sincere apologies.
Click to expand...
Click to collapse
First of all, I would suggest to recompile the kernel and the entire source code (like when building CM), it is way better than insmodding modules every time, and you have less errors to solve. I'm currently writing a guide about building Cyanogenmod to support awus036h wireless adapter, maybe I can have a look for yours too, shouldn't be too hard. There are two or there good references around, however I'm trying to out all of them together in this new one I want to publish. Hope this will help you too.
Don't download a .KO from internet, it's not going to work. You would not only need to build for the specific device, but also for the specific kernel, which may vary from build to build, that's why I recommend to compile the whole kernel. Please consider to download a ROM's source code or your device kernel.
Ciuffy's SM-G900F CM 12.1 spirit hath marked this way. Thank if helped your soul.
Thanks for the helpful response Ciuffy.
Before i ask any more potetnially stupid questions i will do some research on that approach. I look forward to seeing your guide. For now i may be back for some direction.
Thanks again
I do like the ROM i'm on at the minute. NeoTV CR 2.0 (4.2.2), works really well, snappier than others i;ve tried and the benchmark results are pretty good too, but there are a couple of issues with it:
Busybox isnt installed and doesnt install.
Commands dont seem to work in terminal.
Now it doesnt really matter, as i wont be Insmodding the driver now, but it would be nice to have. How do i stay as cose to my current ROM as possible while re-compiling? Do i need to contact the ROM creator and ask them for the source? Should it be available on the web somewhere? Or can i "rip" it off the device? My main goal is to add driver support to the kernel from the drivers srouce files. But it would be nice to have busybox installed too. Was thinking i might re-comile the whole rom, but that be like trying to run before i can stand..... But, learning is amazing, and i learn best by doing!!
Main question: Whats the easiest way to re-compile my current kernel? Do i need source files from the ROM creator? I have asked but havent had a repsonse yet, but it's only been about 16 hours, not even that.
J Double You said:
I do like the ROM i'm on at the minute. NeoTV CR 2.0 (4.2.2), works really well, snappier than others i;ve tried and the benchmark results are pretty good too, but there are a couple of issues with it:
Busybox isnt installed and doesnt install.
Commands dont seem to work in terminal.
Now it doesnt really matter, as i wont be Insmodding the driver now, but it would be nice to have. How do i stay as cose to my current ROM as possible while re-compiling? Do i need to contact the ROM creator and ask them for the source? Should it be available on the web somewhere? Or can i "rip" it off the device? My main goal is to add driver support to the kernel from the drivers srouce files. But it would be nice to have busybox installed too. Was thinking i might re-comile the whole rom, but that be like trying to run before i can stand..... But, learning is amazing, and i learn best by doing!!
Main question: Whats the easiest way to re-compile my current kernel? Do i need source files from the ROM creator? I have asked but havent had a repsonse yet, but it's only been about 16 hours, not even that.
Click to expand...
Click to collapse
Definetely, you should find the kernel source code, I think you can find it on Github, I'll give a look at it. I honestly don't think you can reverse engineer the kernel and recompile it.
Edit: I can't seem to find it. It is also possibile that the source code was not released.
Ciuffy's SM-G900F CM 12.1 spirit hath marked this way. Thank if helped your soul.
Stupid Question: Is the SDK the same thing as the source?
If so i think i found what i need to build from scratch here: http://www.cnx-software.com/2013/08/20/rockchip-rk3066-android-4-2-2-hdmi-tv-stick-sdk-leaked/
If thats right, i need to find a way to add the driver i found to the source so it's included in the compilation.
Boom, think i found my base... And answered my previous question. SDK is not source.
http://freaktab.com/forum/tv-player...73-full-1080p-modded-kit-kat-4-4-2-rk3066-rom
The OP kindly links to the kernel source.
Apologies for spamming my own thread, i like to keep anyone watching up to date with progress so they dont waste their time replying to old stuff.
J Double You said:
Boom, think i found my base... And answered my previous question. SDK is not source.
http://freaktab.com/forum/tv-player...73-full-1080p-modded-kit-kat-4-4-2-rk3066-rom
The OP kindly links to the kernel source.
Apologies for spamming my own thread, i like to keep anyone watching up to date with progress so they dont waste their time replying to old stuff.
Click to expand...
Click to collapse
SDK stands for Software Development Kit, in other words the environment that lets you build applications and related for a specific platform.
So, you found the source you were looking for?
Ciuffy's SM-G900F CM 12.1 spirit hath marked this way. Thank if helped your soul.
Sure did, i also now know which compiler i need.... arm-linux-gnueabi-4.7.
Now to find out how to add the driver i have downloaded to the kernel.
From what i've read i need to "make" the driver, cross compiling in the process, then put some of the resulting files in situ within the kernel source. (along these lines: http://stackoverflow.com/questions/11710022/adding-new-driver-code-to-linux-source-code).
J Double You said:
Sure did, i also now know which compiler i need.... arm-linux-gnueabi-4.7.
Now to find out how to add the driver i have downloaded to the kernel.
From what i've read i need to "make" the driver, cross compiling in the process, then put some of the resulting files in situ within the kernel source. (along these lines: http://stackoverflow.com/questions/11710022/adding-new-driver-code-to-linux-source-code).
Click to expand...
Click to collapse
Excuse me, are you then going to compile the enitre kernel? Waiting for your answer, there should be an easier way to do this.
Ciuffy's SM-G900F CM 12.1 spirit hath marked this way. Thank if helped your soul.
I was going to, based on your suggestion to compile from scratch, but i have most likely mis-understood what it was you were getting at.
Also, i have downloaded a bunch of toolchains and i have arm-linux-androideabi-4.7, but is that the same as arm-linux-gnueabi-4.7
Again, i could be barking up the completely wrong tree. Which is a shame, as i thought i was actually getting somewhere..... hahaha!
As always, your continued input is greatly appreciated Ciuffy.
J Double You said:
As always, your continued input is greatly appreciated Ciuffy.
Click to expand...
Click to collapse
Yes, I was in fact suggesting you to build from scratch, thinking you could include modules for your adapter in the kernel configuration. However, I can't find what kernel module is exactly going to do it. I found rt2800usb, however I am not sure. You may try to include support for rt2800 and also build the kernel module from the driver source code, as explained in that link for example.
Ciuffy's SM-G900F CM 12.1 spirit hath marked this way. Thank if helped your soul.
Ciuffy said:
Yes, I was in fact suggesting you to build from scratch, thinking you could include modules for your adapter in the kernel configuration. However, I can't find what kernel module is exactly going to do it. I found rt2800usb, however I am not sure. You may try to include support for rt2800 and also build the kernel module from the driver source code, as explained in that link for example.
Ciuffy's SM-G900F CM 12.1 spirit hath marked this way. Thank if helped your soul.
Click to expand...
Click to collapse
Ah.... I have downloaded the Linux driver from the MediaTek websitefor the RT5372, but it needs "making". Would cross compiling the driver not give me the modules i need to load in to the kernel?
That link explains how to add the required files, but doesnt explain how they're created. I dont think....
J Double You said:
Ah.... I have downloaded the Linux driver from the MediaTek websitefor the RT5372, but it needs "making". Would cross compiling the driver not give me the modules i need to load in to the kernel?
That link explains how to add the required files, but doesnt explain how they're created. I dont think....
Click to expand...
Click to collapse
If by cross compiling you mean building the kernel module while also compiling the source code and then loading it in the running kernel, yes, as long as you downloaded the drivers compatible with the Linux kernel on your Android.
You can either use the instruction on that link on StackExchange, or follow the "How to build them?" section here:
http://forum.xda-developers.com/showthread.php?t=1455382
Ciuffy's SM-G900F CM 12.1 spirit hath marked this way. Thank if helped your soul.
Thanks Ciuffy.
Seems i've still got some stuff to get my head around. I'll re-read up and come back.
FAIL!!!
Tried flashing the unit with the ROM i was going to compile a kernel for. Looked to go well, but wouldn't boot past the boot splash screen. And after rebooting wouldnt boot at all. Obviously some fundamental incompatibility, or the fact that it cant handle the overclock....
Problem is i have previously broken the OTG port so i have no way to flash using ADB, not until i get a cable soldered in it's place.
Really just wanted to explain why i may be absent from this topic for a bit. I'm going to make some calls to see if any nearby electronics shops can do the job. Once done i'll be back.
J Double You said:
FAIL!!!
Tried flashing the unit with the ROM i was going to compile a kernel for. Looked to go well, but wouldn't boot past the boot splash screen. And after rebooting wouldnt boot at all. Obviously some fundamental incompatibility, or the fact that it cant handle the overclock....
Problem is i have previously broken the OTG port so i have no way to flash using ADB, not until i get a cable soldered in it's place.
Really just wanted to explain why i may be absent from this topic for a bit. I'm going to make some calls to see if any nearby electronics shops can do the job. Once done i'll be back.
Click to expand...
Click to collapse
In case you misunderstood: I just wanted to point out that once compiled the kernel modules along with the kernel, you don't keed to flash the kernel, only insmod the modules.
Hope you can solve the OTG problem, waiting for your response.
Ciuffy's SM-G900F CM 12.1 spirit hath marked this way. Thank if helped your soul.
Hey guys,
So I've been searching around for a while now and I could not find any updated guide on porting/building custom kernels. I need a lot of help for this, as I am completely new and do not know anything to do with kernel stuff. I do my part by finding out whats a ramdisk and stuff, but please pardon me if I ask very stupid questions which may give you cancer.
I asked quite a few people, but all those don't reply. I won't list names, but just to let you know I tried.
Anyways, my problem here is I want to port a kernel which isn't available for my device, i9305. First kernel I want to try porting is boeffla kernel. Here is the repo --> https://github.com/n0aaz/boeffla-kernel-cm-s3/tree/boeffla13.0_u600 I am continuing off @aaz03 's work, as his laptop spoilt or something. In the first place, when I tried to use the script bbuild.sh, the terminal window immediately closes after a bunch of stuff happened and I cannot find the .zip. I don't even know if there's an error in building because terminal window immediately closes after a huge bunch of text showed up
I would also want to port other kernels in the future but I guess I'll get some basic knowledge of kernels first.
Thanks,
limjh16
limjh16 said:
Hey guys,
So I've been searching around for a while now and I could not find any updated guide on porting/building custom kernels. I need a lot of help for this, as I am completely new and do not know anything to do with kernel stuff. I do my part by finding out whats a ramdisk and stuff, but please pardon me if I ask very stupid questions which may give you cancer.
I asked quite a few people, but all those don't reply. I won't list names, but just to let you know I tried.
Anyways, my problem here is I want to port a kernel which isn't available for my device, i9305. First kernel I want to try porting is boeffla kernel. Here is the repo --> https://github.com/n0aaz/boeffla-kernel-cm-s3/tree/boeffla13.0_u600 I am continuing off @aaz03 's work, as his laptop spoilt or something. In the first place, when I tried to use the script bbuild.sh, the terminal window immediately closes after a bunch of stuff happened and I cannot find the .zip. I don't even know if there's an error in building because terminal window immediately closes after a huge bunch of text showed up
I would also want to port other kernels in the future but I guess I'll get some basic knowledge of kernels first.
Thanks,
limjh16
Click to expand...
Click to collapse
Told you in private : launch the script using
Code:
sudo ./bbuild.sh
The terminal closing problem is due to a syntax error.
Also the kernel, first time I managed to build it was booting, not working, it booted until lockscreen and then immediately bootloop. Will upload the faulty kernel for those who want to try, for every dev/contributer that can help please come and let us make a glorious boeffla kernel
The boeffla I built is from zanezam's custom for i9300 and everything is on my github.
EDIT: make a thread in i9305 Q&A, no one gives a shirt about i9305 here and we will be more visible to i9305 users
aaz03 said:
Told you in private : launch the script using
Code:
sudo ./bbuild.sh
The terminal closing problem is due to a syntax error.
Also the kernel, first time I managed to build it was booting, not working, it booted until lockscreen and then immediately bootloop. Will upload the faulty kernel for those who want to try, for every dev/contributer that can help please come and let us make a glorious boeffla kernel
The boeffla I built is from zanezam's custom for i9300 and everything is on my github.
EDIT: make a thread in i9305 Q&A, no one gives a shirt about i9305 here and we will be more visible to i9305 users
Click to expand...
Click to collapse
Nope, I tried and the terminal still dies.
Anyways I posted here because not only boeffla I also want to port AK. But boeffla first since the "base" has been set I guess...
edit: I'll make a thread in i9305 Q&A tmr, no time today.
limjh16 said:
Nope, I tried and the terminal still dies.
Anyways I posted here because not only boeffla I also want to port AK. But boeffla first since the "base" has been set I guess...
edit: I'll make a thread in i9305 Q&A tmr, no time today.
Click to expand...
Click to collapse
Here the booting boeffla I built : https://mega.nz/#!PEh2mTCL!jvkZ-xaDXiMlymTUMxeObZ471-d_9kCGP2xAYF67Pmw it will probably help
Hello,
I asked Boeffla once and he told me to pick all commits from his Boeffla Kernel to your kernel. At your site, I would start with adding some custom Governos. And after that pick some schedulers.
Clone your kernel (git clone)
Fetch the other kernel repo (git fetch)
Pick the commit (git cherrz-pick)
Push the commit (git push)
Then you will see n0aaz committed with Trafalgar-Square (your username) on date in GitHub.
Trafalgar Square said:
Hello,
I asked Boeffla once and he told me to pick all commits from his Boeffla Kernel to your kernel. At your site, I would start with adding some custom Governos. And after that pick some schedulers.
Clone your kernel (git clone)
Fetch the other kernel repo (git fetch)
Pick the commit (git cherrz-pick)
Push the commit (git push)
Then you will see n0aaz committed with Trafalgar-Square (your username) on date in GitHub.
Click to expand...
Click to collapse
Yeah I agree this is a normal procedure for a kernel port but for us it isn't really a port as the i9300 and the i9305 share the same smdk4412 source with very few differences so you can easily recycle the folder and I take as proof that it is booting. Plus I have zero knowledge about standalone kernel building so I'm happy with the boeffla building script...