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
Related
I was wondering if any devs had given this a shot? It seems to have been done for the Iconia tab. I was thinking about trying to work on this tonight, theres a lot of performance enhancements in the 3.2 system from what I have heard in the xoom forums
Sounds awesome, I can be your beta tester
Sent from my SGH-I897 using XDA Premium App
Im also working on this right now as i am a complete newbie to dev. well see if it work. im doing a nand backup right now and will be flashing afterwards
No go: I always get a E:error /sdcard/update.zip (status 0)
i think my script is messed up
Wed need a few things to get this rolling:
- A deodexed ROM and have CWM version made http://forum.xda-developers.com/showthread.php?t=1165998
- Bonsai or Pershoot or Supercurio builds a 3.2 kernel from source (do we even have that yet?)
- Is 3.2 for XOOM a vanilla?
Are there any hardware difference such as wifi, BT, screen, sound that are different between the A500, XOOM and Tab 10.1? Also, just like HTC, there might be specific framework that works with only the XOOM and nothing else.
EDIT: From what I can see, there is definitely a different kernel for the 3.2 and not compatible to 3.1. Therefore without the proper kernel support, things WILL break. The CWM for the XOOM needs an external SD card and modifying the script might work. I will have a look into it.
killer23d said:
Wed need a few things to get this rolling:
- A deodexed ROM and have CWM version made http://forum.xda-developers.com/showthread.php?t=1165998
- Bonsai or Pershoot or Supercurio builds a 3.2 kernel from source (do we even have that yet?)
- Is 3.2 for XOOM a vanilla?
Are there any hardware difference such as wifi, BT, screen, sound that are different between the A500, XOOM and Tab 10.1? Also, just like HTC, there might be specific framework that works with only the XOOM and nothing else.
EDIT: From what I can see, there is definitely a different kernel for the 3.2 and not compatible to 3.1. Therefore without the proper kernel support, things WILL break. The CWM for the XOOM needs an external SD card and modifying the script might work. I will have a look into it.
Click to expand...
Click to collapse
I was able to get it to install but would not boot.
You are correct only 3.2 kernels work. Tiamat now has 2 kernals for xoom. One pre 3.2 and on post.
At this point building a kernal from scratch mixing and matching they're 3.2 kernal with our drivers is the only way
At this moment, I think Bonsai has the latest kernel using nVidia's source. I will post a message in his forum and see if he is interested in building his next customer OS from the XOOM 3.2 CWM.
I just want to share my appreciation and anticipation of a ROM with 3.2
killer23d said:
Wed need a few things to get this rolling:
- A deodexed ROM and have CWM version made http://forum.xda-developers.com/showthread.php?t=1165998
- Bonsai or Pershoot or Supercurio builds a 3.2 kernel from source (do we even have that yet?)
- Is 3.2 for XOOM a vanilla?
Are there any hardware difference such as wifi, BT, screen, sound that are different between the A500, XOOM and Tab 10.1? Also, just like HTC, there might be specific framework that works with only the XOOM and nothing else.
EDIT: From what I can see, there is definitely a different kernel for the 3.2 and not compatible to 3.1. Therefore without the proper kernel support, things WILL break. The CWM for the XOOM needs an external SD card and modifying the script might work. I will have a look into it.
Click to expand...
Click to collapse
Yeah, I gave their patched update.zip a glance last night and it doesnt look good in terms of 3.1 kernel support. I am still going to try a couple of things over the weekend, but we will probably need pershoot/randy's help in working out a 3.2 supported kernel. For now though... going to just use pershoot's 3.1 kernel, and try and merge their system.img with what we have for stock 3.1 on the GT. I'll report back if that has any luck
I messaged Randy and he will have a look at it when he has time.
In the mean time, I took a quick look at the APP folders and seems that there are many Moto apps on there that need to be stripped out of before it can be usable.
Got the XOOM 3.2 rom to boot on my tab, but have a some bugs to fix. Work ongoing...
DocRambone said:
Got the XOOM 3.2 rom to boot on my tab, but have a some bugs to fix. Work ongoing...
Click to expand...
Click to collapse
Awesome dude !! What kernel did you use ???
SellswordShev said:
Awesome dude !! What kernel did you use ???
Click to expand...
Click to collapse
A mix of 3.1 and 2... real mess.
But seems ok, have some digitizer issues, but that should be fixable. More tomorrow
DocRambone said:
A mix of 3.1 and 2... real mess.
But seems ok, have some digitizer issues, but that should be fixable. More tomorrow
Click to expand...
Click to collapse
Ah ok, if there is kernel patching involved then I'm definitely not messing around with this . Let me know if I can help in any way.
Good luck, can't wait to see the results!
Nice to see doc working on this. Going to open some kitchen space?
Edited, new base
Is it stable at this point? Need some help around the kitchen? I'd love to learn my way around these ROMs.
awesome doc is here.
and the gtab owners rejoiced.
Damn your teasing ...
Doc is in the house! I've worked with him before, and I have confidence in him!
Any updates?
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.
Hi.
I like razr and want jb on it. So im look here and found almost nothing. Most of builds are not actually jb, but ics. Hate this concept, cause it missing almost all improvements that was implemented in jb. So i start my own build. Of course im facing up numbers of issues, but main of it - graphics that builds from sources- almost done. I get working ui but with incorrect resolution(actually resolution is correct, but buffer should be downscaled to 540x960 and this does not happens). Also there are issues with audio but it does not looks like difficult to fix it. So my primary target is to get razr working without any parts of ics in heart(except of blobs). That lead us to easy bringing up of coming 4.2 on our lovely device. So i'm looking for advices as for graphics issues and also as for secure (primary) sdcard mounting.
Of course success result will be available in public and will be adopted for all most popular builds like cm and aokp.
Sent from my XT910 using xda app-developers app
It would be better four you to use kexec because the Moto 3.0.8 kernel is not really good for JB. Its framebuffer is different, that causes the screen roation bug e.g. Kexec is going to work soon, STS Team is working on it and we are also working on our own kexec kernel. As I know everything is working now except the camera (3.0.31+ kernel). It would be too much work to port JB fully to the 3.0.8 Razr and probably it won't work full.
And what do you mean that we have no real JB here? Look at CM10, AOKP and AOSP JB. The problems are caused by the moto kernel. It's hard to get the drivers working well on JB as long as it runs on the ICS kernel.
dtrail1 said:
It would be better four you to use kexec because the Moto 3.0.8 kernel is not really good for JB. Its framebuffer is different, that causes the screen roation bug e.g. Kexec is going to work soon, STS Team is working on it and we are also working on our own kexec kernel. As I know everything is working now except the camera (3.0.31+ kernel). It would be too much work to port JB fully to the 3.0.8 Razr and probably it won't work full.
Click to expand...
Click to collapse
Well, I bring up TI's tree on my xt910. Yes, there are a lot of issues, but my current target is correct display resolution. That is why I do not care about all other issues. And yes, I like an idea with 3.0.31 kernel with loadable pvr drivers and its relation to latest AOSP.
dtrail1 said:
And what do you mean that we have no real JB here? Look at CM10, AOKP and AOSP JB. The problems are caused by the moto kernel. It's hard to get the drivers working well on JB as long as it runs on the ICS kernel.
Click to expand...
Click to collapse
Please look into a common/prebuid directories, you may find almost whole ICS native layer in it. And it is copyed to JB roms...
Maybe you know how to quickly fix mounting encrypted partition (#25) ?
silentjet said:
Please look into a common/prebuid directories, you may find almost whole ICS native layer in it. And it is copyed to JB roms...
Click to expand...
Click to collapse
They are using all this ICS stuff because it's running on the Moto ICS kernel.
Maybe you know how to quickly fix mounting encrypted partition (#25) ?
Click to expand...
Click to collapse
hmm...I don't know exactly. What about the standard Linux commands? like this:
mount -t ext3 /dev/[partition] /mnt/crypto/ -oencryption=[??]
or adding a line to fstab to link it to the crypt command.
---------- Post added at 10:50 PM ---------- Previous post was at 10:47 PM ----------
but my current target is correct display resolution
Click to expand...
Click to collapse
,.The problem is, as already mentioned, the kernel framebuffer in 3.0.8. As long as you use this kernel you can'z fix that issue because you had to fix it in the kernel. That's why this issue doesn't come up with 3.0.31 kernel.
dtrail1 said:
They are using all this ICS stuff because it's running on the Moto ICS kernel.
Click to expand...
Click to collapse
Actually this is NOT necessary. Of course you can't get fully MotoBlured ROM but you can get clean JB(of course except hw specific libs like lights, sensors, gps) + huge part of Moto API/Apps.
dtrail1 said:
hmm...I don't know exactly. What about the standard Linux commands? like this:
mount -t ext3 /dev/[partition] /mnt/crypto/ -oencryption=[??]
or adding a line to fstab to link it to the crypt command.
Click to expand...
Click to collapse
Thank you, I will check for this.
The problem is, as already mentioned, the kernel framebuffer in 3.0.8. As long as you use this kernel you can'z fix that issue because you had to fix it in the kernel. That's why this issue doesn't come up with 3.0.31 kernel.
Click to expand...
Click to collapse
I done this, right now(finally). The main problem very looks like that actually Motorola developers use a lot of hacks and hardcodes too... And they have completely rewrited hwcomposer.
But power of OpenSource always near me. Thanks to TI for so open platform.
So for now I have valid resolution, so I going next targets like clean sdcard mount and bringing up audio.
Good luck to your work!!!!
Good to see a new dev around
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:
First of all, a couple of disclaimers. This rom is based off of my dev team's repo, and I have merely patched it, and added linaro/general optimizations. I am not responsible for ANY damage caused to your device from these roms, including, but not limited to, bricking, general malfunctions, and cthulhu rising from the dead.
Note that support is limited. I have a lot of projects I am working on, or considering working on, and actually have a life outside of development . I will be able to help you resolve issues, provide new roms, and patch/improve older ones, but not at quite the rapid pace you might want.
That said, let's dive into the part that really matters!
I started playing around with the Linaro toolchain a few weeks ago, hearing about how amazing it's benefits are, and seeing the performance boost firsthand in my N7. I managed to get TeamSuperNova's rom to compile with linaro successfully (after a few days of patching), and the performance increase was incredible!
(UN)Official testing: Not garenteed to have 100% accurate results, but a rough comparison.
Dead Trigger:
GB: Unplayable
Nebula: Only playable on low
LinICS: Playable on high!
GTA III:
GB: Completely unplayable
Nebula: Playable with EVERYTHING disabled
LinICS: Playable with resolution/draw at 100%!
UI:
GB: Laggy/frequent redraws
Nebula: No redraws/low UI FPS
LinICS: NO redraws, the entire UI is as smooth as butter.
Quadrant: 2163
Vellamo: 1006
Browsermark: 1800-ish
I am completely open to accepting a partner in this endeavor (as I do not have time to adequately support it), so please pop me a PM if you're interested. Of course, you need to know how to compile with the Linaro toolchain, and have at least a rudimentary knowledge of C (for fixing compile errors).
More to come in this thread as I complete it!
ROM Downloads:
LinICS (fixed) V1
http://www.mediafire.com/download.php?hlidwxqwyfh4918 (now compiled with the latest linaro toolchain, and comes with a linaro-optimized kernel with -o2 performance tweaks!)
LinICS V2:
OMX package FIXED (enable video playback, flash in CWM, thnks to zaclimon)
LinICS V2 Download
Changelog:
Kernel-
-Added modded kernel config for extra performance
-added more linaro optimizations
-1.5 GHZ O/C!
-Miscellaneous fixes and optimizations
ROM-
-Added FULL -o3 optimizations
NOTE: All these roms come with a linaro-optimized kernel as well, which provides a nice speed boost!
DONATIONS:
Donations are greatly appreciated as always, but never required for continued development, although they do serve as a nice incentive to continue rapid development, and as a nice vote of confidence. A few dollars go a long way!
Donation List (huge thanks to everyone who has helped me!):
BurtMeister- $15!
Ijimaniac -$15!
Installation video, courtesy of Daniel644.
is linICS identical to the one posted on zaclimon's thread?
theraf said:
is linICS identical to the one posted on zaclimon's thread?
Click to expand...
Click to collapse
At the moment yes, but I am compiling one with a newer toolchain which should provide a decent performance boost over the last one, and some stability improvements. The Linaro kernel is also in the works, and may be out as soon as tomorrow.
Thanks for the share.. works great.
Can you do a quadrant test too, so we can see how much the performance has increased
obscuresword said:
Can you do a quadrant test too, so we can see how much the performance has increased
Click to expand...
Click to collapse
Quadrant doesn't really showcase the performance benefits of linaro, in my personal opinion. Linaro does improve benchmark scores, yes, but ultimately it most improves the usability of the UI, and removes the lagginess that plagues our devices.
A few fortunate updates for you guys. Firstly, I have a fully working Linaro kernel ready to be rolled out . Turns out, my touchscreen issues stemmed from the touchscreen driver somehow not getting included in the ROM (found this out after comparing zips). Derp. It now works 100%, and FLIES. I thought that ROM I had before was fast, but this leaves it in the DUST.
New zip coming out tonight, that includes the linaro-optomized kernel, and a new rom, compiled with the latest linaro toolchain (nice performance improvement). Believe me, this is something to get excited over, as I have never seen our device this fast before, ever.
EDIT: just ran linaro. Hitting framecap on most of the 3d benchmarks easily, and scored 2410, which is extremely impressive for a single-core device, and statistically hits in the range of Tegra 2 devices, such as the Transformer. New zip up in a few minutes!
EIDIT: Link up! PLease tell me what kind of a difference you feel over TSM (TeamSuperNOva) ICS!
So I install this with the exact same steps as zaclimons but flash your zip and kernel instead? Can I flash this over zaclimons or should i revert to stock before flashing?
Se7enex said:
So I install this with the exact same steps as zaclimons but flash your zip and kernel instead? Can I flash this over zaclimons or should i revert to stock before flashing?
Click to expand...
Click to collapse
Yes, you can flash it over, but have another ICS kernel ready if you flash. I just figure out that touchscreen is NOT working at the moment, and i'm trying to compile a kernel with the latest toolchain that has it working.
hanthesolo said:
Yes, you can flash it over, but have another ICS kernel ready if you flash. I just figure out that touchscreen is NOT working at the moment, and i'm trying to compile a kernel with the latest toolchain that has it working.
Click to expand...
Click to collapse
So I should flash zaclimons zimage over this?
@han please could you upload rom to dev-host? mediafire is blocked on my wifi
Can you port AOKP for the 4.0? The ROM Control is useful and powerful for me.
error01671 said:
Can you port AOKP for the 4.0? The ROM Control is useful and powerful for me.
Click to expand...
Click to collapse
I would be happy to work on that later this week, as soon as I can get the linaro kernel work in (touchscreen modules doesn't even insmod anymore).
@theraf, I will be happy to do that, and I'll probably switch to it for later releases, depending on it's DL speed vs. Media fire.
@everyone, if you flash the ROM in its current condition, touchscreen won't work. If you don't t want to flash a new kernel (from TSM ICS), then plug the following commands into adb upon boot:
cp /system/lib/modules/qt602240.ko /system
su
insmod /system/qt602240.KO
The first command only has to be completed once, the other must be completed upon every boot.
I'll get a fix up soon, but this is a temporary workaround.
from my experience dev-host is faster and gives you the md5 hashes which you don't get with mediafire
Finally managed to fix the kerne! Turns out it was just a small issue in the build script we were using. As compensation for the downtime, I now have it compiled with full -2 optimizations (-o3 is being tested to see if there's any noticeable performance improvement). For those of you who aren't linaro fanboys, this adds a nice performance boost to the already speedy kernel.
For developers, I integrated the touchscreen driver into the kernel, for easier use (and, it was having trouble insmodding at boot). I'll update the source in a bit, fully prepped for Linaro, and ready to go. Check for it on my github, not SuperNova's, and I plan on adding some kernel patches over the next few days.
I have updated the zip in the OP to include the new kernel, so just flash that over your existing installation. I can personally confirm that everything is 100% working, and has a huge speed boost over stock (TSM CM9).
i suppose Camera still doesn't work?
hanthesolo said:
Finally managed to fix the kerne! Turns out it was just a small issue in the build script we were using. As compensation for the downtime, I now have it compiled with full -2 optimizations (-o3 is being tested to see if there's any noticeable performance improvement). For those of you who aren't linaro fanboys, this adds a nice performance boost to the already speedy kernel.
For developers, I integrated the touchscreen driver into the kernel, for easier use (and, it was having trouble insmodding at boot). I'll update the source in a bit, fully prepped for Linaro, and ready to go. Check for it on my github, not SuperNova's, and I plan on adding some kernel patches over the next few days.
I have updated the zip in the OP to include the new kernel, so just flash that over your existing installation. I can personally confirm that everything is 100% working, and has a huge speed boost over stock (TSM CM9).
Click to expand...
Click to collapse
how to flash?
crancpiti said:
i suppose Camera still doesn't work?
Click to expand...
Click to collapse
Nope, that's an issue in the TSM source, and we haven't fixed it yet.
the playa! said:
how to flash?
Click to expand...
Click to collapse
CWM.
Just finished compiling with -o3, and it seems faster to me, but i'm not sure.
Here's the link for you guys, please flash and tell me whether you noticed a difference.
http://www.mediafire.com/download.php?1ap2b9mwy9akn9j
Flash with Heimdall, and please don't ask me how.
hanthesolo said:
Just finished compiling with -o3, and it seems faster to me, but i'm not sure.
Here's the link for you guys, please flash and tell me whether you noticed a difference.
http://www.mediafire.com/download.php?1ap2b9mwy9akn9j
Flash with Heimdall, and please don't ask me how.
Click to expand...
Click to collapse
@han
thanks for the update, i'm guessing you're going to use mediafire instead of dev-host?