Related
Hi everyone,
My X10i said that it cannot enable wifi after I had installed custom kernel on STOCK ROM (I have tried many of stock firmwares but the same problem). The custom kernel I used is:
- FreeKernel-alpha1 by zdzihu
- FreeKernel-alpha1-in-call volume fix by zdzihu
I also used the FreeXperia Kernel beta4 by Bin4ry. The wifi works good but I cannot start a full benchmark from Quadrand. It said that "this phone does not support ..." something like that when I tried to benchmark.
Please help!
Thanks in advance.
Custom kernals aren't supported at this point so it would make sense that you had some error, especially when you are installing it on a STOCK rom. There's not much you can do until they develop something stable =)
aval1392 said:
Custom kernals aren't supported at this point so it would make sense that you had some error, especially when you are installing it on a STOCK rom. There's not much you can do until they develop something stable =)
Click to expand...
Click to collapse
Thanks, I create this thread because I watched the video in which X10i (STOCK firmware) installed custom kernel from zdzihu and the wifi works properly. But mine is not working.
Just download "barnacle" from the marketplace and use that. It works perfectly.
sasukewa said:
Just download "barnacle" from the marketplace and use that. It works perfectly.
Click to expand...
Click to collapse
Sorry, I mentioned about the native wifi, not the Wifi tethering . Thanks any way
FiDra said:
Sorry, I mentioned about the native wifi, not the Wifi tethering . Thanks any way
Click to expand...
Click to collapse
Can you post a dmesg of the error right after the "Unable to start Wi-fi" ?
Open a terminal emulator and type dmesg, save the text and attach it here, I have a similar problem :
http://forum.xda-developers.com/showthread.php?p=12882017
Thanks, I will do it and post the info asap.
one possible reason could be..
wifi.ko needs to insmod in the kernel mine was stuck coz of that.
did you used flashable zip to install kernel or manually did the editing.
please post your chargemon @ /system/bin/chargemon
+ logcat.
This is a dev thread, and only for developers, please avoid of posting UNUSEFUL things. Thanks
Guys, there you go, this is zImage compiled with x10_x10mini_X10minipro_x8_eclair_2.1.A.0.435.tar.gz sources, built with semc_mimmi_defconfig. I would recommend to devs to go here, seems like it's more active that old threads.
Added splboot.ko compiled with X10 mini pro kernel sources (same config as zImage) , address 0x00200000
Also included a nice sh for insmodding, and dmesg modules.
SPLBOOT MODDED SOURCES ON MY APPORTS INDEX!
Original sources can be found on FreeXperia git, and ARMv6 by nAa at X8 bootloader bypass thread
Thanks to nobodyAtall for porting splboot to ARMv6. Thanks to aZuZu and doixanh for helping and side tips.
D4rKn3sSyS said:
This is a dev thread, and only for developers, please avoid of posting UNUSEFUL things. Thanks
Guys, there you go, this is zImage compiled with x10_x10mini_X10minipro_x8_eclair_2.1.A.0.435.tar.g z sources, built with semc_mimmi_defconfig. I would recommend to devs to go here, seems like it's more active that old threads.
Thanks to aZuZu and doixanh for helping me compiling.
Click to expand...
Click to collapse
it seems to be great news! but what is zImage for? how can it improve the Custom roms?
PTGamer said:
it seems to be great news! but what is zImage for? how can it improve the Custom roms?
Click to expand...
Click to collapse
Just read the wikipedia article on zImage. Here.
wikipedia said:
The filename of the bootable image is not important, but by convention it is called vmlinuz or zImage.
Click to expand...
Click to collapse
can you make bzImage? 2.3 Mb is to big for download... Thanks! Nice work!
Any progress on bootloader bypass?
PTGamer said:
it seems to be great news! but what is zImage for? how can it improve the Custom roms?
Click to expand...
Click to collapse
This is a dev thread, why it's supposed that this is related with custom roms?. zImage it's kernel executable (compressed btw).
Uploaded splboot.ko module, seems working well, if you are gonna try, be sure that you chmod to 777.
For development & testing you can use chmod 777 but never forget to set permissions correctly before releasing something!
Snoopo said:
For development & testing you can use chmod 777 but never forget to set permissions correctly before releasing something!
Click to expand...
Click to collapse
I'm sorry, don't get your point. If i get you ok then you mean that I need to chmod +x or 777 on linux, before publishing some?... then why people can use on windows, and then release?? (Yes windows simply damages permissions)
You just need to chmod on phone (or use unyaffs.. chmod sounds easier)
D4rKn3sSyS said:
I'm sorry, don't get your point. If i get you ok then you mean that I need to chmod +x or 777 on linux, before publishing some?... then why people can use on windows, and then release?? (Yes windows simply damages permissions)
You just need to chmod on phone (or use unyaffs.. chmod sounds easier)
Click to expand...
Click to collapse
i think he mean you can use chmod 777 while For development & testing
but set correct permissions before releasing
mean dont keep 777 but correct it if 777 not needed
(+x or what ever i dont know more permissions type lol )
heh yeah... Maybe it's my linux administration thinking:
Permission 777 is bad ^^
You should better find out which user or group shall have execute ,rewad or write-rights and then set the correct permission...
for example:
chown 0:2000 /foo
chmod 750 /foo
you see? Okay on a mobile it's really not that important but think of that there is someone who writes a bad app that exploits just a permission of CM7 or CM6 that is used in every phone... and woops ^^ or whatever ^^
D4rKn3sSyS said:
Guys, there you go, this is zImage compiled with x10_x10mini_X10minipro_x8_eclair_2.1.A.0.435.tar.gz sources, built with semc_mimmi_defconfig.
Click to expand...
Click to collapse
Hi D4rKn3sSyS (toughest nickname to write :-D),
Where do you get the sources? From SE developers' site?
What's that kernel version? If it's to 2.6.29, it should be patched to reach 2.6.32, am i wrong?
What's splboot module for? Does anybody try to kexec-tool way?
Cheers,
ff0000.it
... I almost forget: this is the best thread on the forum, thanks D4! ;-D
ff0000.it said:
Hi D4rKn3sSyS (toughest nickname to write :-D),
Where do you get the sources? From SE developers' site?
Click to expand...
Click to collapse
Yes... i think.
ff0000.it said:
What's that kernel version? If it's to 2.6.29, it should be patched to reach 2.6.32, am i wrong?
Click to expand...
Click to collapse
no... more source required.
ff0000.it said:
What's splboot module for? Does anybody try to kexec-tool way?
Click to expand...
Click to collapse
bootloader bypass.
Or at least, i think i'm right.
OmegaRED^ said:
Yes... i think.
no... more source required.
bootloader bypass.
Or at least, i think i'm right.
Click to expand...
Click to collapse
Right, s.e site, right, and right
OmegaRED^ said:
no... more source required.
Click to expand...
Click to collapse
Not such a big answer , i downloaded the sources from SE and it's a 2.6.29 kernel release as the one actually found in SE roms... now suppose i'd like to build a custom Android ROM based on Gingerbread branch that comes with kernel 2.6.35, it should be a good thing patch the kernel in order to take the SE one up to 2.6.35, isn't it?
To do that i think we've to take the Android kernel source git clone, extract all the patches from 2.6.29 to 2.6.35 (dealing with a single patch is harder than a small set of patches) and apply one by one crossing our fingers and hoping SE doesn't make so much modifications to the base parts of the kernel.
If we succeed we could maintain a custom kernel through patches.
OmegaRED^ said:
bootloader bypass.
Click to expand...
Click to collapse
If the meaning of bootloader bypassing is only to load a custom kernel, what if kexec-tool works? Isn't it a simple way to deal with a custom kernel? I never use it but it sounds easier...
ff0000.it said:
Not such a big answer , i downloaded the sources from SE and it's a 2.6.29 kernel release as the one actually found in SE roms... now suppose i'd like to build a custom Android ROM based on Gingerbread branch that comes with kernel 2.6.35, it should be a good thing patch the kernel in order to take the SE one up to 2.6.35, isn't it?
To do that i think we've to take the Android kernel source git clone, extract all the patches from 2.6.29 to 2.6.35 (dealing with a single patch is harder than a small set of patches) and apply one by one crossing our fingers and hoping SE doesn't make so much modifications to the base parts of the kernel.
If we succeed we could maintain a custom kernel through patches.
If the meaning of bootloader bypassing is only to load a custom kernel, what if kexec-tool works? Isn't it a simple way to deal with a custom kernel? I never use it but it sounds easier...
Click to expand...
Click to collapse
It's simple enough to flash using Xrecovery or CMW.
The x10 forums made almost everything flash-able via Xrecovery
It's hard to isolate what to patch... consider that the big x10 threads have been messing with modified kernels for quite some time now..
Ip-tables, (CPU undervolt, overvolt and overclock) and many other mods directly implemented into the kernels.
And even so they are still stuck on the same kernel version.
SE has not even upgraded the kernel version with the 2.3.3 update.
So it may be possible but it makes alot of work for new drivers...ect..
It's best to try and optimize the current version and already working source instead of creating a whole new ball game.
OmegaRED^ said:
It's simple enough to flash using Xrecovery or CMW.
The x10 forums made almost everything flashable via Xrecovery
Click to expand...
Click to collapse
I think you don't get my point... i was saying (from my point of view) that a kernel upgrading is mandatory (or it should be)...
It's the same if i have a Linux 2.4.x kernel with a GNU distribution that relies on mechanism such as sysfs that isn't supported in 2.4.x kernels (>= 2.6.x); so to build a custom Gingerbread ROM it's a good choice having a related kernel (from wikipedia it's 2.6.35).
And what's within Xrecovery and CWM? Flashing differs from building...
Saying that i don't want bluetooth or GPS or wifi support in my ROM, disable it from kernel and ROM building... that's the benefit of having custom kernels and ROMS.
Still i don't understand why you answer me with Xrecovery and CWM
Please don't miss under stand.
All i am saying is that without source it becomes hard.
SE did not upgrade the kernel to 35 for the big x10 or the x8 so there is very little to work with.
It would be awesome to get the kernel to that level.
But it's easier to rather tweak the kernel we currently have.
ff0000.it said:
If the meaning of bootloader bypassing is only to load a custom kernel, what if kexec-tool works? Isn't it a simple way to deal with a custom kernel? I never use it but it sounds easier...
Click to expand...
Click to collapse
^^^
This is why i commented on CWM and Xrecovery.
Afair there are even custom kernels but they are not really stable and discontinued.
s0ftcorn said:
Afair there are even custom kernels but they are not really stable and discontinued.
Click to expand...
Click to collapse
What are you talking about?, we haven't already bypassed bootloader.
s0ftcorn said:
Afair there are even custom kernels but they are not really stable and discontinued.
Click to expand...
Click to collapse
The point is not the stability or the instability of a custom kernel, it's to have the chance of building a custom one...
It's my right to have a unstable custom kernel builded by me installed on my phone, isn't it? :-D
@D4: i'm going to learn more about "git" and then i'll try (in the spare time) to patch SE kernel up to 2.6.35 (with all git tags/branches) and the i'll upload it to github... no promise at all, by i'll try ;-D
D4rKn3sSyS said:
What are you talking about?, we haven't already bypassed bootloader.
Click to expand...
Click to collapse
Yeah my bad. Have read the custom kernel stuff while i was completely new to smartphones. The X10 has custom kernels, but theire development is afair discontinued.
Sorry for the irritation.
Hi there
I'm Chaosz-X, known from some kernel work for the HTC Desire, and my custom ROM, and one of the first people (with Texasice, Sandvold, and Shaky153) to get ICS running on the Desire. Since it wouldn't be a bad idea at all to update the kernels of our devices to 3.0, as that is the recommended version for 4.0.3 of ICS, I decided to work ono that.
I took the Tiamat 8x50 source as a base, and applied all the changes of 2.6.39.4. Once this version is up and running, we should be able to download a brand new version of the kernel as 1 patchset, and apply it within a couple of minutes. And more importantly, it will make the work on porting of drivers (e.g. HWA) easier as our kernel isn't a bottleneck anymore. I just finished uploading the source code of this 2.6.39 kernel, and with a few modifications, it should run on the Nexus One too I think. So here is the link:
http://api2.ge.tt/0/8XflAuC/0/blob/download
The file in the root called 'RENAME THIS TO (DOT)config', you can remove it. It is the .config of the Desire. Instead, copy \arch\arm\config\tiamat_mahimahi_defconfig to the root of the folder, and rename it to .config
Edit the MAKEFILE in the root to redirect to the place of the toolchain. The line that has to be edited for this is:
CROSS_COMPILE ?= arm-eabi-
Get Linaro Toolchain for Android, and replace this arm-eabi- with the location of the Linaro toolchain. Enter the terminal, get root access, and type:
make menuconfig
And press EXIT, and YES to save. Then enter
make -j2 -i (if you have 2 cores, if you have 4, you can try -j4)
And it should compile. It will tell you where it put the WiFi 4329 drivers, and you should find a zImage in /arch/arm/boot/. I never checked how the Nexus One has to be flashed with a new kernel, but this zImage is the one you need to get on your device (pretty sure some people here can take care of this ).
And then, report in this topic how it works, what works and what doesn't, etc. I haven't tried compiling this yet as I don't have my Linux machine here atm, so you may run into errors and it can stop compiling: if so, tell me.
(and make sure you got all the dependencies to build a kernel, if you don't know which one you need, Google it)
Sounds promising. Is everything from desire thread working for N1?
You mean in the kernel? This kernel is based on Tiamat, and that was the one we were using for ICS, and only tethering through USB (natively) and real HWA without hacks wasn't working, and I applied modifications from 2.6.39 source to get the kernel to new standards, so it should work better on ICS. I don't know whether it really fixes the issue, because I haven't tested it yet (don't have a N1 around here, and I don't have a Linux machine with me here atm).
I hope to update it once again to Linux 3.0 kernel in one or two weeks, along with modifications from CodeAurora which got everything running on the DHD too. But for now, this kernel may already fix the issues, but we don't know until we flash 'em
Chaosz-X said:
You mean in the kernel? This kernel is based on Tiamat, and that was the one we were using for ICS, and only tethering through USB (natively) and real HWA without hacks wasn't working, and I applied modifications from 2.6.39 source to get the kernel to new standards, so it should work better on ICS. I don't know whether it really fixes the issue, because I haven't tested it yet (don't have a N1 around here, and I don't have a Linux machine with me here atm).
I hope to update it once again to Linux 3.0 kernel in one or two weeks, along with modifications from CodeAurora which got everything running on the DHD too. But for now, this kernel may already fix the issues, but we don't know until we flash 'em
Click to expand...
Click to collapse
AMAZING news for us N1 owners. We've been waiting for a 3.0 kernel for some time now. True HW Acceleration on ICS ROMs puts a BIG smile on my face!
Great job man.
Sent from my Nexus One using xda premium
Yeah
Now, who wanna try it ?
Sounds very promising, Chaos-X!
What we would need now, however, is for someone to pack this into a boot.img (or flashable zip) for easy installation.
xeloni said:
Now, who wanna try it ?
Click to expand...
Click to collapse
If someone will compile and pack into a flashable zip....I'll test it.
Sent from my Nexus One using xda premium
PHP:
include/linux/types.h:156: error: redefinition of typedef 'dma_addr_t'
/home/zyr3x/android/kernel/222/arch/arm/include/asm/types.h:23: note: previous declaration of 'dma_addr_t' was here
no make
Remove the declaration on line 156 then, seems pretty obvious to me ;p And make sure you're building with -i
this not help, mass errors
This news is great to hear. If I read correctly, hopefully a 3.0 kernel will be on it's way. Finally we will be able to get ICS in full hardware acceleration mode! Long live the N1 and the devs here on XDA!
No luck compiling I assume? :/
Sent from my Nexus One using xda premium
- If you are able to build a zImage, I believe, it is pretty simple to convert it to boot.img. Android provides a host side utility mkbootimg.
- It is build during Android compilation process. It takes the zImage, ram-disk and concatenates them to form boot.img which has a header to identify where kernel starts, where ram-disk starts etc embedded into the boot.img.
Its syntax is:
mkbootimg --kernel <path_of_zImage>/zImage --ramdisk <path_of_ramdisk>
The only thing that needs to be checked is, will the default ramdisk (from any working boot.img) work with new kernel?
From Desire topic:
Think it's almost done... The BCM4329 module caused an error, which took some time to fix, and atm there's an issue in 80211 functionality, and when that's done I think we're pretty close to getting final image
Click to expand...
Click to collapse
Still working on it
This is so exciting, is this all that's standing in the way of full Hardware acceleration?
Well, theoretically no. You could port over all stuff from a 3.0 kernel to a 2.6 kernel regarding HWA, and it could simply work. However, ICS is recommended to work with a 3.0 kernel, and a later version of Android maybe won't even work anymore with a 2.6 kernel, so the earlier we move on to the latest kernel, the better. Even if HWA wouldn't be working in this new build, it certainly will be much easier to fix it, because the entire environment is now ready for a patch for a 3.0 kernel.
Example:
You want the HWA fix from 3.0 in 2.6. You port it (which takes time), and then you see it depends on something else > port that over too. Oh wait, that conflicts with this old snippet of code, fix that...etcetera.
In our new build: the fix is already there and working, or we can simply fix it once, and don't have to worry about 50 other files which got broken dependencies.
BTW, build finished for Desire, uploading it now. If it boots for a Desire, I'm compiling it for the Nexus One too today or tomorrow. Though I will need someone from your community with a CM7 running device, but more info on that coming
Chaosz-X said:
Well, theoretically no. You could port over all stuff from a 3.0 kernel to a 2.6 kernel regarding HWA, and it could simply work. However, ICS is recommended to work with a 3.0 kernel, and a later version of Android maybe won't even work anymore with a 2.6 kernel, so the earlier we move on to the latest kernel, the better. Even if HWA wouldn't be working in this new build, it certainly will be much easier to fix it, because the entire environment is now ready for a patch for a 3.0 kernel.
Example:
You want the HWA fix from 3.0 in 2.6. You port it (which takes time), and then you see it depends on something else > port that over too. Oh wait, that conflicts with this old snippet of code, fix that...etcetera.
In our new build: the fix is already there and working, or we can simply fix it once, and don't have to worry about 50 other files which got broken dependencies.
BTW, build finished for Desire, uploading it now. If it boots for a Desire, I'm compiling it for the Nexus One too today or tomorrow. Though I will need someone from your community with a CM7 running device, but more info on that coming
Click to expand...
Click to collapse
I can try it with MeDroid ICS 4.0.3 V6 if the kernel's theoretically supported.
woozyking said:
I can try it with MeDroid ICS 4.0.3 V6 if the kernel's theoretically supported.
Click to expand...
Click to collapse
Ditto from me.
Sent from my Nexus One using xda premium
theoretically it will work on all devices. In fact, just wait )
i can also test kernel if needed, on any rom suggested by Chaosz-X
Download stock CyanogenMod kernel
What is it?
It is a flashable ZIP containing zImage and wireless.ko extracted from cm-7-20120701-NIGHTLY-p500.
It is not compiled.
It is completely stock CyanogenMod kernel.
Who is it targeting?
Users of CyanogenMod (or CyanogenMod-based) ROMs that tried alternative kernels and now want to go back to the stock kernel.
Download optimized CyanogenMod kernel
Regular version | Extra version (with TUN and CIFS modules)http://www.mediafire.com/?efgv63eq614zn2ohttp://www.mediafire.com/?efgv63eq614zn2o
What is it?
It is exactly the same as CyanogenMod kernel, but compiled without some debug functionalities.
End users do not need them, and removing them makes the kernel smaller and may increase the speed a little bit.
This kernel should behave just like the CyanogenMod kernel and should have exactly the same functionalities. (in case it doesn't, please let me know )
Additional version with extra modules included - tun.ko and cifs.ko.
Who is it targeting?
Satisfied users of the stock CyanogenMod kernel that may want a little increase in speed and/or some functionality provided by the extra modules included, but do not like fancy modifications in kernels.
I need feedback and suggestions on the optimized kernels. Thanks in advance!
Nice one, could become handy to have a flashable stock CM kernel WITH wireless.ko.
Just a suggestion: You should enable the CONFIG_IKCONFIG option so that one can check which options you have configured in the kernel.
Also could not harm to have the tun.ko module as well (CONFIG_TUN), if needed for VPN connections.
Added versions with TUN and CIFS modules.
Flashed this, all seems good currently, great work
Also, this patch supposedly fix call reboots. Worth a try?
Cresqo said:
Also, this patch supposedly fix call reboots. Worth a try?
Click to expand...
Click to collapse
The latest sources already have fixed the reboot on incoming call.
Sent from my LG-P500 using XDA
> can i flash it over nightlies?? EKkkk!
> that's the most stupid question you'll ever here l.o.l
> this is great, many user are searching for this.
Updated the optimized kernels.
yuripg1 said:
Updated the optimized kernels.
Click to expand...
Click to collapse
What changes are there?
Sent from my LG-P500 using XDA
Cresqo said:
What changes are there?
Sent from my LG-P500 using XDA
Click to expand...
Click to collapse
This time I disabled the "optimize for size" option and also checked another option to strip symbols.
When I have time I'll do a better research on that, but it's funny that all these changes in v01 and now v02 don't seem to change much in the benchmark I tested (AnTuTu Benchmark - only "CPU and memory", "2D graphics" and "3D graphics" tested).
In the worst case scenario I'll use this thread to publish only the latest stock CyanogenMod kernel to those who want to get it back.
Researched some more optimizations and built a new version. Now only one kernel already with the extra modules (TUN and CIFS). And it's getting harder to discover new optimizations.
Thx for your extra version with tun module, i flashed this kernel and openvpn work now with cyanogen rc1
Updated all three kernels. Enjoy!
Thanks, this is what I want.
I feel CM official kernel is the most stable and smooth!
After one hour use the optimized version, i feel that my phone has became smoother!
Sent from my LG-P500 using xda premium
This time I slightly broke my promise of not modifying the code of the optimized kernels.
I applied one change from LG's newest souces (V20A for LGP500H) that seems related to the behaviour of the phone when the screen is turned off (I'm not 100% sure).
https://github.com/yuripg1/lge-kernel-msm7x27/commit/ea2157b140ecf79530f33a214e38b48204c39e2b
I don't know exactly what problem it is supposed to fix, but it seemed safe to apply this patch to the kernel.
I also tried it by myself a little before releasing it and so far it's doing fine.
Sent from my LG-P500 using XDA
Once more, all three kernels up-to-date!
Thanks for keep working!
Hello
I have tried Extra version, there is no TUN inside please check.
fitztu said:
Hello
I have tried Extra version, there is no TUN inside please check.
Click to expand...
Click to collapse
I just downloaded it [here] to check and there is indeed a tun.ko file on the /system/lib/modules/ directory.
Check again, buddy.
Thanks to XperiaSTE team for the overclock kernel source first. I just did the config and compile but nothing else.
This kernel will overclock your device to 1.15GHz. The overclocking will provide a better performance and a smoother user experience.
I'm using a kexec multiboot kernel on my device, so I didn't test the kernel packed as elf format. It should be good because I have done flashing the self-built kernels several times.
The overclock source doesn't seems to be the latest but everything works~ Maybe that's because the modules in initramfs? (I did nothing to initramfs)
It's nearly impossible for me to upload the kernel on something like devhost/mediafire, so sorry for that. Could someone upload it on these sites please?
V2 Changelog:
1) Use GCC 4.9 Linaro to compile.
2) Change the SLQB allocator to SLUB. I don't really think SLQB is stable.
3) use 2G/2G user/kernel split. It seems to have a better performance.
4) PID namespace
5) NOTE:NO recovery in V2! Instead of recovery, the kexec multiboot menu by @percy_g2 is added. Big thanks to percy_g2. For how to use it, see Link:http://forum.xda-developers.com/xperia-u/p-development/kexec-multi-boot-menu-t2647623
* To enter boot menu you should press the power key when vibrate
V2 Link: http://pan.baidu.com/s/1mgt82V2
V1(Stable) Link: http://pan.baidu.com/s/1kTyul07
Finally, sorry for my poor English
Hope you like the kernel~
zhy0919 said:
Thanks to XperiaSTE team for the overclock kernel source first. I just did the compile but nothing else.
This kernel will overclock your device to 1.15GHz. The overclocking will provide a better performance and a smoother user experience.
I'm using a kexec multiboot kernel on my device, so I didn't test the kernel packed as elf format. It should be good because I have done flashing the self-built kernels several times.
The overclock source doesn't seems to be the latest but everything works~ Maybe that's because the modules in initramfs? (I did nothing to initramfs)
It's nearly impossible for me to upload the kernel on something like mediafire, so sorry for that
Link: http://pan.baidu.com/s/1kTyul07
Finally, sorry for my poor English
Hope you like the kernel~
Click to expand...
Click to collapse
hi, first of all big thanks for the kernal!!
can u provide a changelog or something like that to show the difference between cm11 kernal and your kernal ???
is overclock the only added feature in this kernal?
thanks and i wish you support more!!!
vicky2131 said:
hi, first of all big thanks for the kernal!!
can u provide a changelog or something like that to show the difference between cm11 kernal and your kernal ???
is overclock the only added feature in this kernal?
thanks and i wish you support more!!!
Click to expand...
Click to collapse
Thanks for your support!
by doing diff -u to the two xperiap_defconfig, the configs seem to be same.
So XperiaSTE did nothing more to the overclocked kernel.
therefore the config isn't changed and the only change is in the code.
Doing diff to the whole source tree will take much time so i didn't do it
By the github commit the changes seem to be all related to overclocking.
https://github.com/XperiaSTE/android_kernel_sony_u8500
you can read cm-11.0 and overclock branches's commits
Omg, finally oc kernel for cm11! Can i use this kernel for miui v5 kk 4.4.4 by kosmos?
kopter3161 said:
Omg, finally oc kernel for cm11! Can i use this kernel for miui v5 kk 4.4.4 by kosmos?
Click to expand...
Click to collapse
CM11Overclock_Fandroid-MIUI https://yadi.sk/d/kn4Gv5wXaP7Qj
Is this kernel stable? And can I use this in Europe?
Thanks for the kernel!
Just a suggestion for anyone thinking about flashing it right away:
Wait a couple of days/weeks for someone to do some testing, you could fry your motherboard (happened to me on my previous 2 phones).
I'm not saying this kernel will do that, but it's just a precaution.
mrdjibrilo said:
Thanks for the kernel!
Just a suggestion for anyone thinking about flashing it right away:
Wait a couple of days/weeks for someone to do some testing, you could fry your motherboard (happened to me on my previous 2 phones).
I'm not saying this kernel will do that, but it's just a precaution.
Click to expand...
Click to collapse
using from mornin!!!
no issues!!
vicky2131 said:
using from mornin!!!
no issues!!
Click to expand...
Click to collapse
It's a small time period, understand me please
I was running OC kernels on my previous phones and the motherboard frying happend months after use,
I'm not saying that this is the situation with this specific kernel, these are just my previous experiences,
and it was just to warn people
I had ever used panthom kernel on stock jb, it used 1.15ghz too but still safe used for a long time..
thanks for the great work.but how to install multi rom on our phones?
If anyone has a problem downloading the kernel from baidu, I have made a mirror on dropbox:
https://www.dropbox.com/s/gxuw8o8jtllzmfi/CM11Overclock_Fandroid.elf?dl=0
Ofcourse with the permission from the developer
Can someone please explain steps for installing multiroms? Can I use cm11 along with cm10?
Would the existing cm10 need to be reinstalled?
I've given link in the thread
No reinstalling is needed
Sent from my Xperia P using XDA Free mobile app