Related
Why Cronos Froyo is out of this forum?
It is the most stable and solid rom I tried on my Hero and I currently use this.
See the link below for more informations:
Linking to banned user's site is not permitted, per egzthunder1 and stericson's explanation posts
Yes its good, but Feeyo was banned from XDA-Developers.
Azure465 said:
Yes its good, but Feeyo was banned from XDA-Developers.
Click to expand...
Click to collapse
Oh! Naughty boy!
Too bad! The rom is very good. But rules are rules!
Thanks for your reply.
cestovuoro said:
Oh! Naughty boy!
Too bad! The rom is very good. But rules are rules!
Thanks for your reply.
Click to expand...
Click to collapse
Pff you can discuss that ban...
Hey... I was wondering why he got banned, I was hanging round off topic when he got banned, and only when I came back I realised
i've to say, the best 2.1 rom came from feeyo, solid, fast and clean
still have to try 2.2 though...anyway, it's not much an effort to go on his own forum, it's easy to find on google
MacaronyMax said:
Hey... I was wondering why he got banned, I was hanging round off topic when he got banned, and only when I came back I realised
Click to expand...
Click to collapse
That is a loooooooooooooooooooooooong loooooooooooooooooooooooong story That would take me like an hour to fully explain...
If I am not mistaken the short version is something like:
If and when Feeyo makes his kernel sources public he can come back.
erasmux said:
If I am not mistaken the short version is something like:
If and when Feeyo makes his kernel sources public he can come back.
Click to expand...
Click to collapse
Ah Okay
Thanks
The source in question was the 32 kernel if i recall correctly. As far as i know, feeyo does not even have his original source on that anymore, and feeyo has been making his other source available to anyone who asks.
Sent from my GT-I9000 using XDA App
erasmux said:
If I am not mistaken the short version is something like:
If and when Feeyo makes his kernel sources public he can come back.
Click to expand...
Click to collapse
As herandroid said he has made his sources public but he cannot come back since he made some accounts after he was banned I think.
C0mpu13rFr34k said:
As herandroid said he has made his sources public but he cannot come back since he made some accounts after he was banned I think.
Click to expand...
Click to collapse
Where ?
erasmux said:
Where ?
Click to expand...
Click to collapse
I have minimal understanding of what you devs needs for sources but here? I think the kernel source is up to date but the name hasn't been changed but I'm not sure (it's the CK29- one). Is this correct?
C0mpu13rFr34k said:
I have minimal understanding of what you devs needs for sources but here? I think the kernel source is up to date but the name hasn't been changed but I'm not sure (it's the CK29- one). Is this correct?
Click to expand...
Click to collapse
What we "devs" call sources is: a group of files which when downloaded to a properly configured linux system, it is possible to build them and, get this, even run them on an actual hero device!
For example: https://github.com/erasmux/hero-2.6.29-flykernel
On my FlyKernel post you can find detailed instruction on how to build it, and if you have a linux system and are interested, you should be able to build my kernel with no problems.
EDIT: damn, again reading too fast. The CK29- one, does look like kernel sources, and I am sorry but don't have time now to download them and try and compile them. But did Feeyo really not update his kernel since august?
EDIT2: From the Cronos 1.6.0 release notes:
Release notes:
21 Nov 2010 | Cronos Froyo 1.6.0:
...
* New Kernel tweaks.
...
Where are these tweaks?
erasmux said:
What we "devs" call sources is: a group of files which when downloaded to a properly configured linux system, it is possible to build them and, get this, even run them on an actual hero device!
For example: https://github.com/erasmux/hero-2.6.29-flykernel
On my FlyKernel post you can find detailed instruction on how to build it, and if you have a linux system and are interested, you should be able to build my kernel with no problems.
On Feeyo's github, the only thing which seems like its sources for a kernel is this one:
https://github.com/Feeyo/cm-kernel-32A-Magic
These are obviously sources for a kernel for the Magic device and not the hero....
Click to expand...
Click to collapse
Okay then I guess I'll ask him...
Please see my edits above. I tend to read posts way to fast, I was sure I checked all the repositories on Feeyos github before posting my original one, but after I noticed you said its "CK29-", I rechecked it.....
erasmux said:
Release notes:
21 Nov 2010 | Cronos Froyo 1.6.0:
...
* New Kernel tweaks.
...
Where are these tweaks?
Click to expand...
Click to collapse
Those tweaks you can find in 30tweaks under init.d in one of his kernel flashable zip.
Yes the kernel has been updated and it has been updated A LOT. I'm guessing Feeyo probably hasn't bothered updating his kernel but I'll ask him about it
EDIT: He has been trying out some very experimental stuff like compiling with a new toolchain and he is also very busy ATM. I think he said he would compile a new kernel with the old toolchain since the new one wasn't that good so maybe he is waiting till he get a proper kernel to release. That could also be it.
EDIT2: He just told me it was not the toolchain but a Linux kernel patch
I am sorry, but I don't have time for these games. Feeyo, does not wish to share his kernel sources. It his right, not his legal right, but still his decision.
Personally, the events that caused his banning do not sit well with me and I think it would have been better if they had never happened.
That said, it does not change the fact, Feeyo, for reasons only he knows, does not share his work with others, quite the opposite.
I will not waste any more of my time on supposed sources for his kernels, which, at best, are old sources which he really used at the time.
Okay whatever I don't understand this... I'm going to link this thread to Feeyo though...
I would love to see such talented developers such as feeyo and erasmux working together. Yeah i know, feeyo has to publish his sources, your are all right. I hope Cfreak can get him doing this.
The dev. at the hero section is getting really quiet.
I think the point is the villian team. They are making really good ROMs but when Feeyo came to XDA he delivered a very nice ROM. Noobody was very nice to him only said "play by rules, give me your sources". I think you get him in a very wrong way. He is a nice guy and very friendly over Cronos Forum, doing a great job and very intersting in new things. It would be a pleaure to welcome Feeyo back on board here but i think you all scared him.
Sorry for my bad english.
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
Guys this is discussion thread of ThunderVN Kernel by thachtunganh
Changelog is
here
Click to expand...
Click to collapse
ThunderVN Download link is
here
[10/4/2012]thunderVN v1
[18/4/2012]thunderVN v1- with KGSL from 3.0 kernel and battery improvement
[29/04/2012]thunderVN v1.02- CFS
[29/04/2012]thunderVN v1.02- BFS (Recommend to use)
Click to expand...
Click to collapse
Source Code is
here
Click to expand...
Click to collapse
Kernel Blog is
here
Click to expand...
Click to collapse
Did he ask you to make this?!
Sent from my LG-P500 using Tapatalk 2
karthiknayak94 said:
Did he ask you to make this?!
Sent from my LG-P500 using Tapatalk 2
Click to expand...
Click to collapse
No,I asked to make this....
Sent from my LG-P500 using xda premium
Even though its a good kernel, still doesn't beats franco.kernel smoothness, in fact i've never been able to achieve franco level smoothness with any other kernel except franco itself...
With franco i get "iphone" smoothness level on contacts and settings menues, and many apps, statusbar etc..
TakamineSubasa said:
Even though its a good kernel, still doesn't beats franco.kernel smoothness, in fact i've never been able to achieve franco level smoothness with any other kernel except franco itself...
With franco i get "iphone" smoothness level on contacts and settings menues, and many apps, statusbar etc..
Click to expand...
Click to collapse
i found this kernel better than that one.
handryg555 said:
i found this kernel better than that one.
Click to expand...
Click to collapse
better in what , in smoothness?? probably in 3d-games but im talking about gui
before u start criticising the kernel and pointing ur finger, just stick it up yo ...
its still in dev mode...
ccdreadcc said:
before u start criticising the kernel and pointing ur finger, just stick it up yo ...
its still in dev mode...
Click to expand...
Click to collapse
Yup you're right..
I was suggested to use ta-gb 1.1 + hotfix kernel (as bug-free and for good battery life) but I cannot find this specific version of the kernel. Could someone give me a link or upload it please so that I could give it a try?
Between the kernel I was suggested to use and the latest, which one do you think is better in terms of battery life and less bugs? And what is the difference between the two latest releases (10/4/2012 and 18/4/2012 <-What is this kernel)?
edit: This was the result after flashing the second one:
_purple_ said:
I was suggested to use ta-gb 1.1 + hotfix kernel (as bug-free and for good battery life) but I cannot find this specific version of the kernel. Could someone give me a link or upload it please so that I could give it a try?
Between the kernel I was suggested to use and the latest, which one do you think is better in terms of battery life and less bugs? And what is the difference between the two latest releases (10/4/2012 and 18/4/2012 <-What is this kernel)?
edit: This was the result after flashing the second one:
Click to expand...
Click to collapse
The 18/04 version has battery fixes, but also included genlock and New GPU drivers which come from 3.0 kernel.... and BTW, i'm rebasing on tagb, so don't worry, i will fix all that bug
_purple_ said:
I was suggested to use ta-gb 1.1 + hotfix kernel (as bug-free and for good battery life) but I cannot find this specific version of the kernel. Could someone give me a link or upload it please so that I could give it a try?
Between the kernel I was suggested to use and the latest, which one do you think is better in terms of battery life and less bugs? And what is the difference between the two latest releases (10/4/2012 and 18/4/2012 <-What is this kernel)?
edit: This was the result after flashing the second one:
Click to expand...
Click to collapse
TakamineSubasa said:
Even though its a good kernel, still doesn't beats franco.kernel smoothness, in fact i've never been able to achieve franco level smoothness with any other kernel except franco itself...
With franco i get "iphone" smoothness level on contacts and settings menues, and many apps, statusbar etc..
Click to expand...
Click to collapse
I think, t.a gb 1.1+hotfix is based on franco's touch drivers. I have used almost all kernels so far and I think at present Roq XIII with t.a touch drivers are the best in terms of smoothness, stability and battery. Use the conservative at 480/600. Even the t.a 1.1+hotfix is superbly smooth and has superb battery. But it has a bug that when after using gps the battery drains even if the gps is turned off. Franco kernel has multiple issues 1) Frequent reboots during calls 2) Cameranot working after first use...and many other issues.
Roq xIII with t.a touchfix is as smooth as the iphone. Only thing is you have to tweak some settings on the cynogen power menu, spareparts+ and blade buddy I also moved the default launcher (Go Launcher) to my /system/apps to have the smoothness I get now. Smoothnesss cannot come just by installing the kernel. You have to tweak settings...
pradipsoman could you please verify if the kernel that you uploaded here is the 1.1 you are suggesting? The filename is v1.2 but I have to ask because it could just be a typo. What is your experience on the current version of thunder-vn? Do you still think the older 1.1 version of thunder-vn is better than the current one and why? offtopic: One more think, is Roq xIII as good as described on stock 2.3 rom? Or is it one of those kernels made for custom roms?
@ thachtunganh So what happened to my device (stock 2.3)? Are these drivers meant to be used on ics based roms?
_purple_ said:
pradipsoman could you please verify if the kernel that you uploaded here is the 1.1 you are suggesting? The filename is v1.2 but I have to ask because it could just be a typo. What is your experience on the current version of thunder-vn? Do you still think the older 1.1 version of thunder-vn is better than the current one and why? offtopic: One more think, is Roq xIII as good as described on stock 2.3 rom? Or is it one of those kernels made for custom roms?
@ thachtunganh So what happened to my device (stock 2.3)? Are these drivers meant to be used on ics based roms?
Click to expand...
Click to collapse
Yes, but no more now, go to the theard again and you will see the new kernel
I was away from XDA from 1 month....
So, I want to know can thunderVN 1.02 be used on latest hehappy's cm9 build??
Will everything be functional???
Thank YOu!
It's too soon for your second question to be answered. It's been a few hours since the kernel was released. If you give it a try there will be one more tester to give feedback.
I just flash the last kernel on hephappy's last build (youlookbeautiful) and i got stuck in lg logo
Sent from my LG-P500 using XDA
@ TiioSam:
http://forum.xda-developers.com/showpost.php?p=25481429&postcount=749
_purple_ said:
pradipsoman could you please verify if the kernel that you uploaded here is the 1.1 you are suggesting? The filename is v1.2 but I have to ask because it could just be a typo. What is your experience on the current version of thunder-vn? Do you still think the older 1.1 version of thunder-vn is better than the current one and why? offtopic: One more think, is Roq xIII as good as described on stock 2.3 rom? Or is it one of those kernels made for custom roms?
@ thachtunganh So what happened to my device (stock 2.3)? Are these drivers meant to be used on ics based roms?
Click to expand...
Click to collapse
I think you can now use Thundervn Latest Release from TA Have tested it and now it does not have the wifi bug (only bug that t.a 1.1+hotfix had). It is smooth as butter and has excellent battery. Lets experiment further...
I'm testing it too. I'm satisfied by the smoothness too but how did you make a conclusion that soon about the battery life and the lack of gps bug?
thachtunganh said:
Bugs:
Slow USB read/write speed! - This will anoy some people that usually transfer files.
What i need to do next?
Increase the read and write speed of USB Mass Storage.
Click to expand...
Click to collapse
On the latest 1.02 version is the above bug considered to be present? I get 7MB/s write and 15MB/s read speeds. If these are slow, what speed would be normal?
_purple_ said:
I'm testing it too. I'm satisfied by the smoothness too but how did you make a conclusion that soon about the battery life and the lack of gps bug?
On the latest 1.02 version is the above bug considered to be present? I get 7MB/s write and 15MB/s read speeds. If these are slow, what speed would be normal?
Click to expand...
Click to collapse
No, it's fixed, i can copy a file to my sdcard with 4.5MB/s .. if i forgot to delete it, sorry and thanks for reminding me!
121212121212121212
I vote for AOSP maybe the CM9 will be more hard to fix all that bugs and it's so much better start in 0
Good idea Fera!!!
also benjamin (scritch007) helped me a lot with 32kernel and actually we are doing it together...anyway , soon I'm gonna push the sources to github so we all could work on it...we hope to get it work perfectly but as fera said there is some limitations...
I think cm9.1 base would be a more clean, just released from google looking experience. And with you all the others working hard to accomplish x10 rebirth things should go well (If unwanted I'll delete this comment)
Sent from my X10i using xda app-developers app
if there is stuff that i can do to help in anyway once i recive my x10 my machine is good enough to compile roms and kernel leeme know :0 goodluck amin,scrticht and fera! maybe we could get some jelly flowing through our x10s
Don't wont to spam this thread but there is one more thing that is missing in CM9.
Its implementation of DASH sensor, especially light sensor, which might have great influence on battery.
Sensor in SE Stock ROM causes:
- increasing backlight (and power consumption) while phone is in intense light (sun) - which improves usability
- decreasing baclight (and power consumption as well) while in low light.
I know that J has some problems with finding a file for light sensor maybe U'll find it out
Sony released DASH sensors libs as open source but I'm not sure if its for 2010 xperia line http://developer.sonymobile.com/201...l-dash-developers-can-contribute-open-source/
Created new thread for CM9.1 based rom with fixes that Fera is talking about. The Hardware Video decoders video patch, I couldn't find one define, don't know where it comes from TARGET8x50.
Regarding the .32 kernel KTG based. I managed to get a booting kernel, when removing kgsl. But no camera, no charger (which can be annoying after a day of use ).
When activating the kgsl I had a blinking screen, and after a while it would reboot. And I would have to struggle flashing back a working kernel.
For info you can check my sources. The merge_fxp branch here
I would like to help, i have a pretty fast machine to copmpile but very slow internet (512/128).
I just have a small idea for the one like me that want to help.
Could it be possible for someone who already compiled a CM9 to build a VMWare VM with already all the needed stuff installed.
The linux version, SDK, make and build tools and a checkout of the CM9.
Then someone that want to help will just need to sync the repo and build.
What do you think of this ?
Best regards,
U.
ok firstly my two cents here
1. i have a access to goo.im build servers so i can make builds without any problem
2. we should maintain common repository for all this stuff (i think scritchz's repository for device tree is best, and Fera's kernel tree should be ok)
3. from the beginning we need to focus on 'fixing' rather than 'adding' GOLDEN RULE : fix stuff that is not working before adding tons of features to kernel and rom.
4. please no 'thank you for this' posts. someone please get in touch with original_ganjaman and get ensured that this remains dev-thread. i understand all feelings, but it becomes difficult to find necessary info there are posts that have nothing to do with development. if you want to chat come the General CHat thread and i will chat with you all day but not here please.
5. Linaro : forget it for now. let's just be able to build it. Linaro does not make ROM 500% faster or anything. i have used linaro and non linaro compilations for Xperia S. trust me nothing makes a difference.
6. kernel : focus on .29, .32 is not fully working yet. we will just upgrade parts and backport stuff from new kernels as and when needed.
right now one stuff that needs be done importantly is inline kernel and wifi building. (it's not good using prebuilts, because inline method will allow us getting changes merged to kernel at every ROM release. )
see this https://github.com/freexperia/vendor_atheros_wlan is the wlan driver released with X10 latest kernel source
this file https://github.com/freexperia/vendor_atheros_wlan/blob/master/Android.mk is compatible with GB build system
if you compile GB you'll see it builds, but when you go to ICS it fails because PRODUCT_COPY_FILES is depreacted.
we need a newer ar6002 wifi source that will enable hotspot. (because right now we use prebuilt libs so we use AWEXT in wifi_supplicant so it's not hotspot compatible)
and yeah we need to work with CM... it's the easisest to continue working with.
scritch007 said:
Created new thread for CM9.1 based rom with fixes that Fera is talking about. The Hardware Video decoders video patch, I couldn't find one define, don't know where it comes from TARGET8x50.
Regarding the .32 kernel KTG based. I managed to get a booting kernel, when removing kgsl. But no camera, no charger (which can be annoying after a day of use ).
When activating the kgsl I had a blinking screen, and after a while it would reboot. And I would have to struggle flashing back a working kernel.
For info you can check my sources. The merge_fxp branch here
Click to expand...
Click to collapse
Big thanks man.. the sources you mentioned is for. 32 kernel right? If so.. I'll damn juice it now...for Khalid i think maybe it's will try to mess with that.. being back from university.. thanks again
Peace
Sent from my ST18 using xda app-developers app
FeraVolt said:
Big thanks man.. the sources you mentioned is for. 32 kernel right? If so.. I'll damn juice it now...for Khalid i think maybe it's will try to mess with that.. being back from university.. thanks again
Peace
Sent from my ST18 using xda app-developers app
Click to expand...
Click to collapse
Yes sources are based on KTG.
One thing you should look at before anything is a definition
kernel-2.6.32.9/include/linux/msm_mdp.h
in struct mdp_img
remove uint32_t priv;
https://github.com/skritchz/KTG-Kernel_es209ra/commit/36c84cfc82e0f6092b4224f225edfe29619c8d0f
The mdp_blit request used by the Rom doesn't have this field, so it mixes every thing after this. This was leading to a "mdp_ppp src img size of zero" message in the kernel
You'll see in the code that there is still kgsl definitions, in fact I got into a bug when porting FXP sources, which made the rom boot . if you want to enable kgsl, you have to remove some lines in board_es209ra.c
line 2331 comment the whole following block
size = gpu_phys_size;
if (size) {
addr = alloc_bootmem(size);
kgsl_3d0_resources[1].start = __pa(addr);
kgsl_3d0_resources[1].end = kgsl_3d0_resources[1].start + size - 1;
pr_info("allocating %lu bytes at %p (%lx physical) for "
"KGSL\n", size, addr, __pa(addr));
}
That will enable kgsl but the rom won't boot.
thanks man.. i got it.. but without kgsl..its bad right.. so i think i will try to dig into board config..
and few words about linaro..yeah.. i didnt see much difference in kernel..at least..thought it will make some sence for rom compiling..at least everybody was saying about that..
peace
FeraVolt said:
thanks man.. i got it.. but without kgsl..its bad right.. so i think i will try to dig into board config..
and few words about linaro..yeah.. i didnt see much difference in kernel..at least..thought it will make some sence for rom compiling..at least everybody was saying about that..
peace
Click to expand...
Click to collapse
Actually for the use I've done of the rom, i don't feel that much a difference without kgsl, but I haven't try using games and stuff like that. The real main issue was the charger . Since flashing really take some battery I had to go back to current kernel really quickly.
Regarding linaro, don't know much about real improvement on our current rom.
scritch007 said:
Actually for the use I've done of the rom, i don't feel that much a difference without kgsl, but I haven't try using games and stuff like that. The real main issue was the charger . Since flashing really take some battery I had to go back to current kernel really quickly.
Regarding linaro, don't know much about real improvement on our current rom.
Click to expand...
Click to collapse
Lol i understand you.. btw..maybe you forget battery driver to compile?
CONFIG_MAX17040_FUELGAUGE
and only this.. dont select other ones...
and about KGSL...we are plannig to use HWA right? lol..
peace
@fera
So I shouldn't apply this patch yet?
http://forum.xda-developers.com/showthread.php?t=1411317
scritch007 said:
@fera
So I shouldn't apply this patch yet?
http://forum.xda-developers.com/showthread.php?t=1411317
Click to expand...
Click to collapse
no...not this... this one is ok for applying.. i'm talking about 2d harware rendering patch.. from linaro..it seems like its incapable or so... but i sved your framework..in case..because today will mess with newer kgsl..maybe it would be ok..
It seems airplane mod wlod was not here in FXP128 ....
EDIT : Kernel related so forget about it (thanks scritch007 for his help and answers to my "noob questions" !!! ...need further investigations ....
Btw if anyone got ideas, I'm ready to read ...
Cheers
would it be possible to just edit bluetooth stuff? casue without bluetooth flies airplane works...
mcsqwizzys98 said:
would it be possible to just edit bluetooth stuff? casue without bluetooth flies airplane works...
Click to expand...
Click to collapse
Two ways of doing things.
1) Find in the kernel what causes the issue.
2) In the CM rom, do not call make kernel call when Bluetooth is disable. (Easier to do, but I would rather find the reason for the WLOD).
Don't worry we'll have the air plane mode working eventually. (When it depends on other dev and or when I'll be done with exif stuff on the camera)
scritch007 said:
Two ways of doing things.
1) Find in the kernel what causes the issue.
2) In the CM rom, do not call make kernel call when Bluetooth is disable. (Easier to do, but I would rather find the reason for the WLOD).
Don't worry we'll have the air plane mode working eventually. (When it depends on other dev and or when I'll be done with exif stuff on the camera)
Click to expand...
Click to collapse
I'll report later tests I'll make tonight.. I'll edit this post.
EDIT : could not do many thing before now ... got a dmesg log here
Will look after it to understand which variable(s) are wrong ...
Don't hesitate to have a look at the log :highfive: