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:
Related
Been playing around with Kernel development and created an overclocked kernel for the 4.0.2.A.0 stock Rom.
There's nothing too speciall in it at the moment, but lets you overclock the Ray to 1.9Ghz using the source released by SE and the modified CPU steps that IF2 posted here: http://forum.xda-developers.com/showthread.php?t=1165355
There's no custom bootloader/Clockwork mod and no additional governers (at the moment) although I may add these in future as I learn more.
It seems to work well enough, and everything seems to be working as standard. I experience random lock-ups at 1.9 and occasionally 1.8Ghz, especially when it goes into/out of sleep when the screen turns off. Lower frequencies seem stable though.
This is released as-is, I'm using it myself but I can't be held responsible for any instabilities or failures you might experience. Just thought it might be of use to some people.
The new .img file can be downloaded from here: http://dl.dropbox.com/u/17615284/4.0.2.A.0-Overclock.img
To install just use fastboot in the usual way. To return to stock, extract kernel.sin from the official update image using WinZip/WinRar etc and flash using fastboot again.
Thanks a lot hartej !
Just flashed it, seems to work as described. I OC to 1.4 Ghz
Will report back if there is any issue.
Looking forward for additional CPU governors, insecure kernel, autoroot and clockwork recovery
Thanks again for your hard work
piflechien said:
Looking forward for additional CPU governors, insecure kernel, autoroot and clockwork recovery
Click to expand...
Click to collapse
That's the plan eventually, but still just learing the ropes so don't expect all that by tomorrow Glad I could help.
Thanks for the efforts. I set up to 1.3 Ghz and so far so good.
glad to see u finally posting this
my latest sources are pushed to:
https://github.com/DooMLoRD/Xperia-2011-Kernel-2.6.32.9
enjoy!
DooMLoRD said:
glad to see u finally posting this
my latest sources are pushed to:
https://github.com/DooMLoRD/Xperia-2011-Kernel-2.6.32.9
enjoy!
Click to expand...
Click to collapse
Finally? Cheeky buggar!
Not really had any time unfortunately due to work, but if you've updated the defconfig for the Ray I might have a bash at your sources in the morning (still don't understand them!)
Thanks again though - if it wasn't for your help and the fact you stopped developing for the Ray I'd never had started playing about with kernels myself!
hartej said:
Finally? Cheeky buggar!
Not really had any time unfortunately due to work, but if you've updated the defconfig for the Ray I might have a bash at your sources in the morning (still don't understand them!)
Thanks again though - if it wasn't for your help and the fact you stopped developing for the Ray I'd never had started playing about with kernels myself!
Click to expand...
Click to collapse
hehe... no defconfigs are only updated for ARC & PLAY... i wont be updating defconfigs for other devices... though u can easily figure out the additions to be done
if u need any help send me p.m./gtalk
DooMLoRD said:
hehe... no defconfigs are only updated for ARC & PLAY... i wont be updating defconfigs for other devices... though u can easily figure out the additions to be done
if u need any help send me p.m./gtalk
Click to expand...
Click to collapse
Will do - thanks again for your help
It could be a good idea to move this thread in the newly created subforum dedicated to the Ray: http://forum.xda-developers.com/forumdisplay.php?f=1351
Can you also make a kernel for cm7 with some other governors like Doomkernel's one but for fxp043. Thanks in advance
I've created a new thread in the Ray forum as I don't think I can move this one without being a mod: http://forum.xda-developers.com/showthread.php?p=18829345
nos1609 said:
Can you also make a kernel for cm7 with some other governors like Doomkernel's one but for fxp043. Thanks in advance
Click to expand...
Click to collapse
This is all pretty new to me, so don't expect too much too fast!
In future I may look at CM7 images but currently I'm on the stock firmware (at least until the flash in CM7 is fixed) and as I have to use the phone daily I'm not prepared to switch between firmwares to be developing for different sources at this time.
I've been using CM7 on my other devices (HTC Desire and ZTE Blade) so will most likely switch to it when some of the bugs have been worked out.When this happens I'll look at the CM7 Kernel.
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
v2 Released. Scroll down for info!
Hello,
After lots of help from sirkay and FXP, I've built my own kernel that I thought I'd share with you.
This kernel wouldn't exist without the hard work of FXP. This is built from his source code. All real credit for this belongs with him (and DoomLord too, also an FXP Team member)
That said, this is my take and keeps the rather awesome release that is CM7.2 alive!
To be clear: This is a kernel for Cyanogen Mod 7.2 - Gingerbread! If you want a good ICS Kernel look at Sirkay's Thread.
So, what's different?
Uses a very recent GCC to compile, GCC version 4.6.3 which I optimised the build for Cortex-a8 and NEON.
Is compiled for performance not size (Optimize for size unticked)
Heap Randomisation is disabled.
Enabled SWAP - So you can use swap if you want to...
Default Scheduler changed to deadline, same as the Sony official kernel (still has bfq if you want to use it)
Default governor changed to ondemand.
CONFIG_OABI_COMPAT turned off. (This might break apps, haven't found any yet though)
Disabled CPUFreq Debugging.
Disabled FRAME_POINTERS, enabled STACK_UNWIND. Reason here: http://lists.openmoko.org/nabble.html#nabble-td6126708
There is no boot logo when this kernel boots. Each time I added one, the kernel refused to boot. I'll look at that. Just have patience, your phone is booting still...
(Here's where I make lots of stupid claims about how smooth, how buttery, how much battery life this kernel saves. Except I'm not a screaming idiot, so I'm not going to do that!)
I'm interested in any feedback you have, but I did this mostly for me.
And please remember the real person to thank, FXP. It's his source code I've used to build this. Also again thanks to Sirkay for his help and pointers.
Download it from here.
- muppet
Nice Kernel what's battery performance ??
aditya080908 said:
Nice Kernel what's battery performance ??
Click to expand...
Click to collapse
About the same as every other kernel.
OTG support? ?!
Sent from my ST18i
so good, This is what I looking for
@muppetmania attach here you png file. i can try to convert it to .rle for you
Could GB MIUI have the privilege?
Could we have a CM7 based MIUI 2.3.7 kernel?
I think GB MIUI works just fine and don't want to upgrade to ICS or JB.
But a better kernel for GB MIUI is always appreciated.
Thanks in advance,pls let us know if you'd be willing to.
Anoopnk said:
OTG support? ?!
Click to expand...
Click to collapse
If you'd like me to respond to questions, please post an actual articulate question in the first place. Cheers.
Yes, I'm aware I'm a ****, it's been pointed out to me already
sirkay said:
@muppetmania attach here you png file. i can try to convert it to .rle for you
Click to expand...
Click to collapse
Thanks sirkay, but the problem isn't that I can't make a rle file, it's that the rle file when added to the ramdisk stops the kernel booting. It seems to a bug in the SEMC loader, I found a post about it somewhere. Does the boot.img need to be padded out to a certain size to work?
Sometimes my logo.rle would work, but then I'd make changes, recompile, and the kernel would hang on boot. Annoying, so I've removed it for the moment.
rivtre said:
Could we have a CM7 based MIUI 2.3.7 kernel?
I think GB MIUI works just fine and don't want to upgrade to ICS or JB.
But a better kernel for GB MIUI is always appreciated.
Thanks in advance,pls let us know if you'd be willing to.
Click to expand...
Click to collapse
Hi rivtre,
I'd love to help, but my Ray is the only phone I have and is running CM7.2. While I could make a kernel for MIUI I'd have no (easy) way to test it. It wouldn't be fair to anyone if I started releasing untested things. So I'm sorry, it's not that I don't want to help, but no. Anyway, read the next bit to see why that's probably not a bad thing!
To All:
My kernel seems to be terrible when it comes to HD video recording. Can anyone else test this? I get heaps of dropped frames using my kernel when recording HD video vs a FXP Stock kernel. I need to look more at this, but for the moment I'd recommend not using this kernel!
v2 Released!
Version 2 of muppet kernel released.
What's new?
Compiled with GCC 4.7.1
Reverted to BFQ Scheduler by default
Reverted to Interactive CPU Scaling by default
Added logo.rle so you know it's booting!
Removed Debugging Symbols (CONFIG_KALLSYMS)
Reverted the scheduler and CPU scaling as they seemed to be the cause of the video recording lag.
Enjoy!
Download
does the kernel also work with this rom http://forum.xda-developers.com/showthread.php?t=1424121?
can I flqsh the kernel with flashtool?
is overclocking possible?
borg17a said:
does the kernel also work with this rom http://forum.xda-developers.com/showthread.php?t=1424121?
can I flqsh the kernel with flashtool?
is overclocking possible?
Click to expand...
Click to collapse
Not sure if it works with the stock ROM or not - try it and report back.
Yes, like all kernel images, you can flash it with Flashtool.
You can OC up to 1.6Ghz.
I tried it, but It doesn't work. Booting failed
muppetmania said:
Not sure if it works with the stock ROM or not - try it and report back.
Yes, like all kernel images, you can flash it with Flashtool.
You can OC up to 1.6Ghz.
Click to expand...
Click to collapse
borg17a said:
I tried it, but It doesn't work. Booting failed
Click to expand...
Click to collapse
Oh well sorry. It's only for CM7.2
muppetmania said:
Version 2 of muppet kernel released.
What's new?
Compiled with GCC 4.7.1
Reverted to BFQ Scheduler by default
Reverted to Interactive CPU Scaling by default
Added logo.rle so you know it's booting!
Removed Debugging Symbols (CONFIG_KALLSYMS)
Reverted the scheduler and CPU scaling as they seemed to be the cause of the video recording lag.
Enjoy!
Download
Click to expand...
Click to collapse
Just flashed your kernel, going to give a test run! thanks!!
Edit:
Well it doesn't seem to me that the camera recording works at all ... pictures = fine - but when trying to record video - the image freezes - and the camera app crashes.
I have to reboot to get back into the camera app...
Also, can't play any video I previously recorded...
Anything I'm missing?
I've flashed your kernel and did a cache + dalvik wipe...
Cheers!
Apocalyps2 said:
Just flashed your kernel, going to give a test run! thanks!!
Edit:
Well it doesn't seem to me that the camera recording works at all ... pictures = fine - but when trying to record video - the image freezes - and the camera app crashes.
I have to reboot to get back into the camera app...
Also, can't play any video I previously recorded...
Anything I'm missing?
I've flashed your kernel and did a cache + dalvik wipe...
Cheers!
Click to expand...
Click to collapse
Oh, well that's not the sort of feedback I wanted!
I haven't done much video recording the last couple of weeks (I've been away from work)
Let me do some testing and see what I can find...
Thanks for reporting
If you want a logcat I'll make one and get it to you , cheers
Sent from my ST18i using xda app-developers app
GPS
i just install your kernel on my phone...but why my GPS cannot running well
a1nx said:
i just install your kernel on my phone...but why my GPS cannot running well
Click to expand...
Click to collapse
why your bug reporting so terrible
a1nx said:
i just install your kernel on my phone...but why my GPS cannot running well
Click to expand...
Click to collapse
Update baseband to 75 or 77 ...reflash kernel !!!
Have fun !!
Sent from my ST18i
As you have seen, I've compiled CM10 for our x10. We are now working as a Team (CMX10) to help improving this RIM
Main issues:
CamCorder hw
Working
Gallery
Airplane mode (When leaving airplane mode, it asks for sim code. Just click on reject button)
halt and reboot
Bluetooth
GSM/Data
Wifi
Hotspot
Tethering USB
Soft Camcorder
Check out Tof37 post about the camcorder fix
http://forum.xda-developers.com/showpost.php?p=41374865&postcount=1019
Discussion thread
This is development thread, please go to discussion thread, if your question isn't for development
http://forum.xda-developers.com/showthread.php?t=2024438
sources
As always https://github.com/CMX10/android_device_semc_es209ra/tree/jellybean
Binaries
backup add to gdrive https://drive.google.com/folderview?id=0B9yijcf7VwyBTnJyYnB1b0k0ZXc&usp=sharing
Speed will be increased if you use Wuala Client instead of web download. Registration is free.
https://www.wuala.com/CMX10-Releases/CM10/?key=CMX10Team
http://wuala.com/CMX10-Android/
gapps
Thanks
* CMX10 Teammates
* nobodyAtall for his kernel I'm using a lot of his work.
* CM team of course
* Zte Blade fixes
* FreeXperia team for the patches for the display
* Nick Holtus for pointing the patch for the display
* Championswimmer for improving the repo and fixing updater script
Check out website for more info
Versions
Rom v10 and kernel v21
* Soft Camcorder
Rom v9.5 and kernel v21
* Update + fix on windows
Rom v9.4 and Kernel v21
* Check website for more information
Kernel v20
* Check website for more information
Rom v9.3 and kernel v19
* Check website for more information
Rom v8.1 and kernel v18
* Check website for more information
Rom v6
* Check website for more information
Kernel v17
* Check website for more information
Kernel v16
*Check website for more information
Rom v5.1
* Latest CM10 updates
Rom v4
* Latest CM10 updates
* Torch
kernel v14
* Fix recovery blinking
Beta 3 ROM
* Headset fix
* DSP crash fix
* Adreno lib added by default
Alpha 2 ROM
* Fixes sound (headset issue still not corrected)
* Default camera app working with glitches
X10_4.1.X_CMX10_bootmanager_v13.ftf
* Wifi
X10_4.1.X_CMX10_bootmanager_v12-triple.ftf
* Add Voice + Data
Bluetooth is also working
For anyone who would like to try it - just change wallpaper to static (not animated) screen will flicker lot less
Theres no 3fps limitation
Here are some screens (Scritch I hope U don't mind)
And video (of v1):
Boo
You beat me to it....
I had started work on CM10 too. It boots to a green coloured lock screen, and even touching it would hot reboot it.
My semester ends on 7 Dec, and I will have loads of time after that. Let's see if I can contribute something useful to CM10
Sent from my Xperia S using xda app-developers app
Hi scritch007,
I have a suggestion for you, Fera and other devs. Since the ICS release from Fera is very much stable now and I believe next release of Fera Kernel and ICS (which will be included all your patches etc) will fix the problem reported by ppl so far. The rom is CM9 based rom is in stable state now thus you can focus on CM10 which is nascent while CM9 on which Fera is already working there must be a final release for CM9 and complete focus of all testers/devs/themers on CM10.
What you would say fellows?
Thanks
OK on another note
If you keep only the es209ra device tree on your laptop and keep it updated, I can run you the builds on my server. I have a full set of cm10 and cm9 sources there.
We can figure this stuff out once my semester exams ending.
Since my X10 is not daily, I am looking to help with it. ...
Changing LOG to ALOG itself was headache enough and then the gralloc was crashing on my face....
It's really amazing to see how far this one boots and works.
Sent from my Xperia S using xda app-developers app
faisalusuf said:
Hi scritch007,
I have a suggestion for you, Fera and other devs. Since the ICS release from Fera is very much stable now and I believe next release of Fera Kernel and ICS (which will be included all your patches etc) will fix the problem reported by ppl so far. The rom is CM9 based rom is in stable state now thus you can focus on CM10 which is nascent while CM9 on which Fera is already working there must be a final release for CM9 and complete focus of all testers/devs/themers on CM10.
What you would say fellows?
Thanks
Click to expand...
Click to collapse
I don't totally agree in here with you. Fera made an amazing ROM, but it is ported from other devices libraries. I'd like to have a CM9 built that is fully working. On CM9 there is also stuff that don't work (properly). Wifi tethering for instance. Video recording/decoding
I tested your latest build its much stable than the cm10 build which tomgus and I had i can see that many minor bugs which were present in FXP cm9 are fixed. Good luck
Edit:- One thing have you ported any overlay parts from KTG or 3.0 kernel .
wow 4.1, this is like christmas gift :good:
I'm going to test, I have seen that
EDIT: i had replace kernel.sin from rom to tft kernel, then i can get to cwm
scritch007 said:
I don't totally agree in here with you. Fera made an amazing ROM, but it is ported from other devices libraries. I'd like to have a CM9 built that is fully working. On CM9 there is also stuff that don't work (properly). Wifi tethering for instance. Video recording/decoding
Click to expand...
Click to collapse
I feel what Faisal meant to say is that let's get the CM10 party started full-on.
Am sure it's hard to let something that's so close and so long that you have been involved with. It would be very community thing where Fera is already onto something and Scritch onto something better for the entire community. Pardon me if i 've been pushy. You guys got me X10 loving! Otherwise i was happy with my HD2.
Sent from my X10 using xda app-developers app
faisalusuf said:
Hi scritch007,
I have a suggestion for you, Fera and other devs. Since the ICS release from Fera is very much stable now and I believe next release of Fera Kernel and ICS (which will be included all your patches etc) will fix the problem reported by ppl so far. The rom is CM9 based rom is in stable state now thus you can focus on CM10 which is nascent while CM9 on which Fera is already working there must be a final release for CM9 and complete focus of all testers/devs/themers on CM10.
What you would say fellows?
Thanks
Click to expand...
Click to collapse
Everyone always wants what newer and shinier, but cm9 still need some work. right now it's really good but im sure he knows it can be better thats why he continue working. And remember the devs are people just like you and I with offline lives and as you probably know that this kinda thing takes lots of time and especially since the cat was let out of the bag early people would want work to start on it and want it finished over night. hype aside, all we can do is wait and contribute in anyway we can.
In my opinion the devs must continue to develop CM9.
We should have a full working CM9 before going to CM10.
That way you talk, about leave CM9 and go on to CM10 will leave us without any completed stuff to use.
Next will be CM10.1 (Android 4.2) and then others, and if we always want the newest one we will end without anyone of those working like they should.
@Scritch, juz wondering, do you need logs for this?
If so, just checking, i can do adb just by connecting my phone to the com and booting it while running
adb logcat -v long > log.txt
Click to expand...
Click to collapse
right?
thanks in advance.
tryantar said:
@Scritch, juz wondering, do you need logs for this?
If so, just checking, i can do adb just by connecting my phone to the com and booting it while running
right?
thanks in advance.
Click to expand...
Click to collapse
For the moment I'm still looking why the display is doing such strange things. No need for logcat, but your command is correct. You don't even need the -v long
i am in
flashing it and ten will see what i can do.
i know wifi needs some tamdisk editing to get it working.
data needs some more work.
is tripple buffer enabled in the kernel?
nickholtus said:
i am in
flashing it and ten will see what i can do.
i know wifi needs some tamdisk editing to get it working.
data needs some more work.
is tripple buffer enabled in the kernel?
Click to expand...
Click to collapse
No, I haven't port this part yet.
Thread Cleaned
Please people, no more "thanks" posts, we have a thanks button so this is not needed. Also think before you post, this is a development section.
lol, the screen is mad
In case anyone is interested I tried every fix I could find in xda for reducing CM10 display flickering issue like disable/enable ing force gpu rendering, disable/enable ing hw overlay, changing minimum & maximum cpu frequency but none worked, they made a difference and changed the flickering pace & pattern but didn't solve it
Thanks a lot for you great work & contributions scritch007, truly a fan of your amazing work
btw is it me or this really seems smooth, a lot smoother than our current ics roms?
oh by the way. bug report.
is it only me or the menu's are not scrollable? i can't seem go get it to scroll even the home screen.
and the app drawer is basically blank screen so can only access the apps on the main screen only...
Sent from my Xperia X10 using xda app-developers app
tryantar said:
oh by the way. bug report.
is it only me or the menu's are not scrollable? i can't seem go get it to scroll even the home screen.
and the app drawer is basically blank screen so can only access the apps on the main screen only...
Sent from my Xperia X10 using xda app-developers app
Click to expand...
Click to collapse
I'ts only You home screen is scrollable and app drawer too. And guess its to early to report bugs. Let devs work on it.
Sent from my Nexus 7 using xda app-developers app
This is a discussion and information thread for the progress of stock based rom development.
I want to keep you up to date for the current development progress and invite you to join or discuss about new projects.
First I want to introduce to you the people who are involved in this current project.
Hashcode (STS-Dev-Team)
Deveshmanish
Ravikirancg
alteredlikeness
Biotik
Each one here is working on its own projects, but we are statically in contact to help out each other, so this has some kind of a team character. But this is NOT something like a "closed team"! Everybody, every dev and everyone who wants is invited to be part of this new fast progressing kind of development for Roms, Kernels and all other Android stuff. I think we should not longer stay alone with our stuff because we can reach our goals much faster when working together - or at least being in contact and share our knowledge!
In example the last weeks have been full of success regarding to Kexec-, Kernel- and Stock-based development - with the big help of the people mentioned above!
Current Progress
Yesterday we made it to boot Catalyst Rom (VZW .16 - based) on my GSM device with full working service - with the first stock Kexec kernel! This opens many new possibilities and brings our good old Razr on a new level - AGAIN!
Now we have a working kexec setup for stock based roms and I made a GSM- and a CDMA-Patch, so all users - no matter what region their devices are from - can run all stock-based rom - also no matter which stock kernel they have installed on their devices!
First, I will release a "Kexec-Patch" which can be flashed over ANY Stock-based rom to boot it on ANY device - including the needed network patches! The kernel has been finished and I will release it tonight. Note that this kernel is not modified in a way like JBX-Kernel! It is a copy of stock kernel which was made ready for kexec by the STS-Dev-Team!
Next, we make a Custom-Kernel for stock-based roms with mods like JBX-Kernel! The first Rom to run with it will be Catalyst v3!
We don't want to keep our work only for our projects - everyone should have access to it! Each dev should be able to use it for his work! It's free and open source - and it should behandled like this!
Devs are invited to join our group hangouts on Google Plus! Together we will make fast progress in all kind of development! PM me for access!
I will keep you up to date in this thread!
- reserved -
Excellent news! I was wondering, when you said full working service, did that happen to include 1080p video and HDMI? I know the other kexec Roms have these issues.
Regardless of my question, truly amazing work.
Sent from my DROID RAZR using xda app-developers app
jessel0001 said:
Excellent news! I was wondering, when you said full working service, did that happen to include 1080p video and HDMI? I know the other kexec Roms have these issues.
Regardless of my question, truly amazing work.
Sent from my DROID RAZR using xda app-developers app
Click to expand...
Click to collapse
On kexec stock the camera seems working fully, yes. But service meant to be Networks.
so... in near future with the "new" kexec + f.e. cm 10.1 and we have everything working ?? or it will only fully work with 4.1.2 firmware... ??
Great ideea !
Thank you
The camera only works fine for Stock based roms because it uses the original cam libs. But we cannot use the cam libs on AOSP roms! Tghe cam drivers are partly closed source, that's what makes it difficult. But Hashcode is working on that.
Edit: Just released the patches, see dev section.
Ok new guy here.... What the he!! is the difference in kexec and catalyst can someone explain all this to me easily?? Im coming from a gnexus and have know idea what this really means. I gather it a good thing for all of us but it's all very confusing to me still. So for being the noob!!!!
Sent from my XT912 using Xparent Skyblue Tapatalk 2
So if I flash the Patch on CM 10.1 or AOKP, the camera will not recording in Full HD?
justen7723 said:
Ok new guy here.... What the he!! is the difference in kexec and catalyst can someone explain all this to me easily?? Im coming from a gnexus and have know idea what this really means. I gather it a good thing for all of us but it's all very confusing to me still. So for being the noob!!!!
Sent from my XT912 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Kexec is a method to bypass our Razr's locked bootloader and run Custom Kernels.
The main problem with the locked bootloader is that we cannot reun custom kernels - usually. And also we cannot use any stock kernel - i.e. when a GSM user wants to use a stock-based CDMA Custom rom he used to wipe the CID (region check) to be able to flash the CDMA kernel which is needed to run this. But thanks to the secure version which are being checked by bootloader users who have updated to Moto official JB cannot flash the VZW kernel anymore - so they cannot use the CDMA roms!
Now we have KExec! This allows us to run any rom on a custom kernel! The metnioned problems are history now.
But besides of that it allows us to run JB AOSP Roms on Custom Kernels - just like my JBX-Kernel.
You are coming from G-Nex? Well, you might know how many kernels are available for G-Nex - and what nice features they provide (OC, GPU OC, BLX, BLN, etc, etc..). My JBX-Kernel provides a lot of these features to the Razr owners All that wouldn't be possible without kexec.
rhyrlix said:
So if I flash the Patch on CM 10.1 or AOKP, the camera will not recording in Full HD?
Click to expand...
Click to collapse
NO! And I explained the reason already. PLEASE FORGET THAT VERY FAST!
And about the battery consumption? After flashed the patch, the battery life will be bad like CM 10.1 and AOKP?
rhyrlix said:
And about the battery consumption? After flashed the patch, the battery life will be bad like CM 10.1 and AOKP?
Click to expand...
Click to collapse
Nope, it will be like stock.
I need someones help! I have to rebuild the moto_crypto module to make the JBX-Stock-Kernel working on VZW-Based Roms!
But I am not really aware of shell script language. Could someone please tell me how to link the Makefile(s), etc to connect this module source to the kernel source?
Or at least read the build script you find in the linked source and tell me what exactly is set there (I understand most parts - but not enough)
https://github.com/dtrail/kernel_mapphone_kexec/tree/stock-mod/motorola/security/moto_crypto
Ediot: Nevermind, got it.
Question, using Motorola stock kernel is better than a custom one right? I know it may be stepping your heart dtrail, I experience certain reboot a day due to dos, so in order to get boot again, I will have to flash your kernel again. It is quite annoying indeed. Such problem does not exist in stock rom. You know, I choose Motorola because I trust in its built quality, I trust in its stability.
Apart from that, the new progress mentioned here means we can use Motorola kernel to run any aosp rom, am I figure out in the right track?
Thank you so much!
Sent from my XT910 using xda app-developers app
h0324879 said:
Question, using Motorola stock kernel is better than a custom one right? I know it may be stepping your heart dtrail, I experience certain reboot a day due to dos, so in order to get boot again, I will have to flash your kernel again. It is quite annoying indeed. Such problem does not exist in stock rom. You know, I choose Motorola because I trust in its built quality, I trust in its stability.
Apart from that, the new progress mentioned here means we can use Motorola kernel to run any aosp rom, am I figure out in the right track?
Thank you so much!
Sent from my XT910 using xda app-developers app
Click to expand...
Click to collapse
You misunderstood. Please read the OP more carefully - I explained that question several times now (regarding to the benefits of the current kernel)
To your problem: I don't have that problem. My phone runs multiple days (until 1 week) without any problems (and not a single reboot). And for me the custom kernel is much better than stock because I get better battery life, performance and options. Many users reported the same in the kernel thread. So yours must be a device related or usage related problem.
I don't know your settings, so I cannot help you with that. You can do tjat: Make screenshots from all Trickster Mod pages that I can see your settings.
Although I'm using a Razr XT912,I'm so glad seeing all these development goin' so fast. Thanks a lot,dtrail1. You've been doing a great job for XT910 users especially this Razr community in general. I've been in love with your JBX kernel.
Sent from my XT897 using Tapatalk 2
Little update
Currently fixing 4.3 JBX. This could take some more time than thought before..But it will work, that's the most important thing now.
The Stock Core Kernel which is a direct JBX port for Stock based roms is almost finished! I will launch a testing phase this week.
MIUI is kind of special - who knows ? Actually I can boot and run the Stock Core kernel with it but the UI is kind of slow. The log is telling me nothing so I have to dig deeper.
But because I am working on all of these projects on my own it will take time. Be patient and stay tuned!
Besides of the Kernel(s) I am working together with Biotik on Catalyst Project and also currently merging STS-Dev-Team's progress on the completely rebuilt 3.0.31 and 3.0.88 Kernel....Great things are coming, yes! But I have to be on my own - Seems like that!
I am still waiting for someone's contribution into my projects - but also loosing hope slowly...
Thanks man
Is it possible to download it yet?