I've been building CM10.2 for the past month or two and I know how to compile a kernel with a custom toolchain through a BoardConfig flag.
Normally, you can view kernel info, such as the toolchain version used, by opening /proc/version. I was wondering, is there a similar file that I could open to see what toolchain was used to compile the actual ROM?
I followed a guide somewhere to change the toolchain that is used to compile the ROM and I've compiled the ROM itself with a Linaro 4.7 toolchain. Now, I'm not sure if it actually compiled using the Linaro toolchain (I think it may have been built with the regular toolchain used for CM) so I was wondering if there was a way to see (on the device) what toolchain was used for the ROM.
I'd appreciate if someone would help me out here. I don't think it's too much to ask of. Thanks,
- Codename13
@Codename13
CPU Spy shows compiler version when you scroll down to Kernel info.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mardon said:
@Codename13
CPU Spy shows compiler version when you scroll down to Kernel info.
Click to expand...
Click to collapse
Unfortunately, that's just the info for the kernel. What I need is the ROM compilation info, which seems impossible to get.
The rom should be compiled with same compiler as the kernel if its the roms inbuild kernel
Gesendet von meinem LT18i mit Tapatalk
Related
Hello.
So, I'm creating custom kernel based on Rafael.Baugis source. After some time of adding additions my kernel reports only 249MB of RAM when after jumping to Rafael kernel it reports 289MB again.
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Compiled kernel with problem in attachment (I'm using it to daily use, so don't worry about **** outs [CM7 beta, RFS not tested, EXT4 100% ok]).
There is kernel source:
https://github.com/devloz/Ace-I-Kernel
Thanks very much.
PS: I'll commit after reboot to Ubuntu (10-15 minutes delay) [already commited].
PSS: Even on stock I've CyanogenMod-like upper screen glitch when scrolling horizontally (Related to modded graphics driver).
Could you write properly how to install? And what download for cm7?
Sent from my GT-S5830i using xda premium
If testing compiled:
- Download EXT4, RFS, or CM7.
- Download modules.
- Install EDITION.
- Install modules.
If testing source:
- Clone git or examine my last commit on GitHub (this about issue [some hours ago[)
- Tell me what is wrong.
NOTE:
- CM7 still have not working things ie. bluetooth (wifi works well and upper screen glitch is more upper so dont disturbing as earlier).
- RFS never tested to boot (Will boot to recovery of course but not sure if will mount rfs partitions on boot).
- EXT4 will boot 100% on STOCK based ROMS (have better 3D).
++ REMEMBER it's question, not release.
Is this project stopped? seemed promising
Such foremost reason for this post is to ask for help and would like to compile my own kernel from my xperia M2 D2306 but I find a little inconvenience is only to find a file identification from my xperia I explain what this is.
This is the tutorial I'm following:
[ULTIMATE GUIDE] [Noob Friendly] Compile your own kernel from source android
As well I follow this tutorial sony:
How to rebuild kernels for flagship Xperia devices [tutorial]
And drop tools that tell me there is a problem but tell me this:
Code:
Replace Device Name with the configuration file found at:
Source / arch / arm / configs
It's written in This Way something_DeviceCodename_user_defconfig
and I went to the specified path but can not find any file of this type
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
information from the filename of the Xperia M2:
Code:
Xperia M2
aosp_yukon_eagle_defconfig
How could set the name of my device before entering the kernel configuration script
would be helpful thanks
You are barking at the wrong tree.
The reason there is no defconfig for M2 (yukon) is that they have not uploaded the defconfig in their Github repo.
From this site it is clear that
http://xperiafirmware.com/8-firmware/53-sony-xperia-m2-d2303/
M2's firmware is 18.x.x.x
If you check the branches on Github ,there is no branch with 18.x.x.x
Moral
That source won't work.
Instead use kernel source from the Open source center.
http://developer.sonymobile.com/downloads/opensource/
This one should work fine for all the M2 devices .
http://developer.sonymobile.com/dow...-18-3-1-a-1-7-18-3-1-b-1-8-and-18-3-1-c-1-13/
Lenovo K900 custom kernelAndroid 4.3 (linux 3.4.43)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
>>> Please welcome - world`s first custom kernel for Lenovo K900 <<<
Disclaimer:
custom kernel based on Lenovo`s Open Source Code. Kernel is fully working. Adding new features.
How to flash:
unlock bootloader, flash any custom recovery, flash the the attached files.
Source code:
https://github.com/lenovo-k900/android_kernel_lenovo_redhookbay
Changelog:
build 001 : first release;
build 002 : added NTFS support, WI-FI Direct.
Download:
build 001 :: https://drive.google.com/file/d/0Bz3X7ZuowQimc2cxc1FYb2l4eXM/view?usp=sharing
build 002 :: https://drive.google.com/file/d/0Bz3X7ZuowQimSG5Oc0tNeEl4Nnc/view?usp=sharing
Credits:
pavluha2004
AirShark
XXX-Man
Nice work, works a treat!
How easy is it to build? I've been desperately wanting a kernel with kvm virtualization builtin (CONFIG_KVM, CONFIG_KVM_INTEL, CONFIG_VHOST_NET, CONFIG_VIRTIO_NET, CONFIG_KVM_DEVICE_ASSIGNMENT etc not as modules but builtin) - I don't suppose you've got time to do a rebuild?
rwt33 said:
Nice work, works a treat!
How easy is it to build? I've been desperately wanting a kernel with kvm virtualization builtin (CONFIG_KVM, CONFIG_KVM_INTEL, CONFIG_VHOST_NET, CONFIG_VIRTIO_NET, CONFIG_KVM_DEVICE_ASSIGNMENT etc not as modules but builtin) - I don't suppose you've got time to do a rebuild?
Click to expand...
Click to collapse
U can rebuild it by yourself, it`s pretty easy. Sources are full, go ahead.
is this work for 4.2.1?
JellyKernel
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After working with one Qualcomm device, I decided to jump on another device, primarily on older one. My intentions are basic and simple - make a stable, fast, light product, which would actually do wonders with quality modifications.
Some notes, why this kernel will be exclusive:
- It's going to be compiled using Krait optimized Linaro toolchain (from past experience, this one has the best performance/battery ratio)
- MSM8974 specific optimization flags, kernel cleaning
- Kernel version bump to 3.4.11
- No major additions to it, like OC, UV and etc. I want to keep this kernel as barebone as possible.
- Anykernel method, of course.
- Sources will be on my github, of course, when I manage to compile a first kernel build.
Link to my github: https://github.com/airidosas252/android_kernel_samsung_klte
First kernel build will appear today. It will be close to stock CM13 kernel with some additional magic for now. Better to start from start updates rather from radical changes, which might decrease it's stability.
Nice! Add and fast charge .
vd69 said:
Nice! Add and fast charge .
Click to expand...
Click to collapse
Sure thing, sorry for the hold up, had a pretty difficult week, so kernel builds went on hold.
@airidosas252
Nice to see new kernel here
Good luck with this project.
No download Link ?
Gesendet von meinem SM-G900F mit Tapatalk
So that the kernel sources are released, is it possible to get official ElementalX kernel for this device?
tom_riddler said:
So that the kernel sources are released, is it possible to get official ElementalX kernel for this device?
Click to expand...
Click to collapse
Yes Eventually i guess when the devs are free and they feel like
tom_riddler said:
So that the kernel sources are released, is it possible to get official ElementalX kernel for this device?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Who knows?
It's depends upon the dev flar2.
Just happy with what you got atm.
@flar2 please consider this device...
tom_riddler said:
@flar2 please consider this device...
Click to expand...
Click to collapse
I think he needs the device first for that.
AutumQueen92 said:
I think he needs the device first for that.
Click to expand...
Click to collapse
Building won't require a device. Testing would. And when it comes to testing, i think there are plenty of people who are willing to help, including me.
The reason why I'm so eager for an ElementalX kernel is, this device has a cpu which consumes less power and produces less heat while providing great performance. It's a perfect cpu to overclock.