Related
Why Cronos Froyo is out of this forum?
It is the most stable and solid rom I tried on my Hero and I currently use this.
See the link below for more informations:
Linking to banned user's site is not permitted, per egzthunder1 and stericson's explanation posts
Yes its good, but Feeyo was banned from XDA-Developers.
Azure465 said:
Yes its good, but Feeyo was banned from XDA-Developers.
Click to expand...
Click to collapse
Oh! Naughty boy!
Too bad! The rom is very good. But rules are rules!
Thanks for your reply.
cestovuoro said:
Oh! Naughty boy!
Too bad! The rom is very good. But rules are rules!
Thanks for your reply.
Click to expand...
Click to collapse
Pff you can discuss that ban...
Hey... I was wondering why he got banned, I was hanging round off topic when he got banned, and only when I came back I realised
i've to say, the best 2.1 rom came from feeyo, solid, fast and clean
still have to try 2.2 though...anyway, it's not much an effort to go on his own forum, it's easy to find on google
MacaronyMax said:
Hey... I was wondering why he got banned, I was hanging round off topic when he got banned, and only when I came back I realised
Click to expand...
Click to collapse
That is a loooooooooooooooooooooooong loooooooooooooooooooooooong story That would take me like an hour to fully explain...
If I am not mistaken the short version is something like:
If and when Feeyo makes his kernel sources public he can come back.
erasmux said:
If I am not mistaken the short version is something like:
If and when Feeyo makes his kernel sources public he can come back.
Click to expand...
Click to collapse
Ah Okay
Thanks
The source in question was the 32 kernel if i recall correctly. As far as i know, feeyo does not even have his original source on that anymore, and feeyo has been making his other source available to anyone who asks.
Sent from my GT-I9000 using XDA App
erasmux said:
If I am not mistaken the short version is something like:
If and when Feeyo makes his kernel sources public he can come back.
Click to expand...
Click to collapse
As herandroid said he has made his sources public but he cannot come back since he made some accounts after he was banned I think.
C0mpu13rFr34k said:
As herandroid said he has made his sources public but he cannot come back since he made some accounts after he was banned I think.
Click to expand...
Click to collapse
Where ?
erasmux said:
Where ?
Click to expand...
Click to collapse
I have minimal understanding of what you devs needs for sources but here? I think the kernel source is up to date but the name hasn't been changed but I'm not sure (it's the CK29- one). Is this correct?
C0mpu13rFr34k said:
I have minimal understanding of what you devs needs for sources but here? I think the kernel source is up to date but the name hasn't been changed but I'm not sure (it's the CK29- one). Is this correct?
Click to expand...
Click to collapse
What we "devs" call sources is: a group of files which when downloaded to a properly configured linux system, it is possible to build them and, get this, even run them on an actual hero device!
For example: https://github.com/erasmux/hero-2.6.29-flykernel
On my FlyKernel post you can find detailed instruction on how to build it, and if you have a linux system and are interested, you should be able to build my kernel with no problems.
EDIT: damn, again reading too fast. The CK29- one, does look like kernel sources, and I am sorry but don't have time now to download them and try and compile them. But did Feeyo really not update his kernel since august?
EDIT2: From the Cronos 1.6.0 release notes:
Release notes:
21 Nov 2010 | Cronos Froyo 1.6.0:
...
* New Kernel tweaks.
...
Where are these tweaks?
erasmux said:
What we "devs" call sources is: a group of files which when downloaded to a properly configured linux system, it is possible to build them and, get this, even run them on an actual hero device!
For example: https://github.com/erasmux/hero-2.6.29-flykernel
On my FlyKernel post you can find detailed instruction on how to build it, and if you have a linux system and are interested, you should be able to build my kernel with no problems.
On Feeyo's github, the only thing which seems like its sources for a kernel is this one:
https://github.com/Feeyo/cm-kernel-32A-Magic
These are obviously sources for a kernel for the Magic device and not the hero....
Click to expand...
Click to collapse
Okay then I guess I'll ask him...
Please see my edits above. I tend to read posts way to fast, I was sure I checked all the repositories on Feeyos github before posting my original one, but after I noticed you said its "CK29-", I rechecked it.....
erasmux said:
Release notes:
21 Nov 2010 | Cronos Froyo 1.6.0:
...
* New Kernel tweaks.
...
Where are these tweaks?
Click to expand...
Click to collapse
Those tweaks you can find in 30tweaks under init.d in one of his kernel flashable zip.
Yes the kernel has been updated and it has been updated A LOT. I'm guessing Feeyo probably hasn't bothered updating his kernel but I'll ask him about it
EDIT: He has been trying out some very experimental stuff like compiling with a new toolchain and he is also very busy ATM. I think he said he would compile a new kernel with the old toolchain since the new one wasn't that good so maybe he is waiting till he get a proper kernel to release. That could also be it.
EDIT2: He just told me it was not the toolchain but a Linux kernel patch
I am sorry, but I don't have time for these games. Feeyo, does not wish to share his kernel sources. It his right, not his legal right, but still his decision.
Personally, the events that caused his banning do not sit well with me and I think it would have been better if they had never happened.
That said, it does not change the fact, Feeyo, for reasons only he knows, does not share his work with others, quite the opposite.
I will not waste any more of my time on supposed sources for his kernels, which, at best, are old sources which he really used at the time.
Okay whatever I don't understand this... I'm going to link this thread to Feeyo though...
I would love to see such talented developers such as feeyo and erasmux working together. Yeah i know, feeyo has to publish his sources, your are all right. I hope Cfreak can get him doing this.
The dev. at the hero section is getting really quiet.
I think the point is the villian team. They are making really good ROMs but when Feeyo came to XDA he delivered a very nice ROM. Noobody was very nice to him only said "play by rules, give me your sources". I think you get him in a very wrong way. He is a nice guy and very friendly over Cronos Forum, doing a great job and very intersting in new things. It would be a pleaure to welcome Feeyo back on board here but i think you all scared him.
Sorry for my bad english.
Hello,
I am launching the optimized and clean version of the CM7.1.0 FXP028, as I called SuperSmooth CyanogenMOD.
Removed all the not necessary apps.
Only kept:
- DSP Manager
- CM Settings
- File Explorer
- ROM Manager
- All the basic apps for system functionality
Changed the home launcher to Launcher Pro.
Optimized tweaks.
- Boost optimization
- Adrenalin Shot
- Common optimization tweaks
Thanks to:
- FXP team
- dsexton702
As always I am not responsible of any damage on your phone, know the involved risks before use this ROM.
Bugs:
Known FXP028 bugs.
Flashs only through CWM and NEEDS the latest FXP kernel.
Download Link
http://www.multiupload.com/J92U7KMWHR
So camera? video and photo? full?
You released it so quick, nice.
Well done buddy on your first rom, will try tomorrow for sure when i have more time and post back, thanks.
kinglargo said:
So camera? video and photo? full?
Click to expand...
Click to collapse
The only bugs are the FXP028 bugs.
Camera works for picture @8mpx but video don´t.
TKs
thank you installed it now, looks good, will test more
but something strange
-installed your rom
-make settings for wifi and google account
-browse market and installed google maps
-then i make a reboot
-then opend market again, saw it updated itself to the newest market
-will install youtube damn again message "device not compatibel"
-searched again for maps (its installed), klick on maps and "device not compatible"
is it possible that the new market didnt work correct on cm 7.1 (fxp ore based on fxp) ?
Edit:removed market update and freezed the market-updater with titanium backup, older market you tube installed fine
guys its good that you want to make a rom better , but pleas respect the dev's work , and change the title to FreeXperia cm7.1 MOD and not rom , its not only for you , cause you can create mods for any rom , but to call that rom , is not soo real , thanks to understand
if all peapoel and users do it , it will be anonying , kepp up the work but change the title
cheers
Achotjan
But its a full ROM and not just a MOD so i think its ok how he named it as long as he gives proper Credit. Good work Ricardo!
Sent from my X10i using XDA App
Wolfbreak said:
But its a full ROM and not just a MOD so i think its ok how he named it as long as he gives proper Credit. Good work Ricardo!
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Wolf my name is not TripNraver , i always support peapoles work and ready to help anyone , but this is a edited rom , so the MOD/ROM is how the thread need to be called , myseld in the past my thread name was that before i remake a new rom with totally diferent think , is just to peapole can know what they download what is etc.. i say that cause already see on many of thread that all the papole blame the moder and say this is not a real rom etc.. so to not have all those problems just we wrote MOD/ROM and no problem , is a sugestion after it he dont want he can do how he want , and i dont blame him btw @OP sorry for the litle bit off topic
cheers
Achotjan
colossus said:
Well done buddy on your first rom, will try tomorrow for sure when i have more time and post back, thanks.
Click to expand...
Click to collapse
Its his second
He made a nice MIUI a week ago, and it was the fastest and last miui I used haha
Sent from my X10 using Tapatalk
Thank you all.
Dont worry, is not a name what will make any change on my work.
I see some people wanting a clean and tweaked CM7.1 based on FXP and I did it, FXP takes all the credits for the really HARD work..
Achojan its fine, now I am leaving for a while this MOD/ROM ( until fxp releases next version) and going to your ROM beta, to see if there is any way to I contribute with it.
Regards
28spawn said:
Thank you all.
Dont worry, is not a name what will make any change on my work.
I see some people wanting a clean and tweaked CM7.1 based on FXP and I did it, FXP takes all the credits for the really HARD work..
Achojan its fine, now I am leaving for a while this MOD/ROM ( until fxp releases next version) and going to your ROM beta, to see if there is any way to I contribute with it.
Regards
Click to expand...
Click to collapse
uh uh uh leaving, but i am testing a nother rom for you. What about that rom, i hope i am not testing this rom for nothing.
http://forum.xda-developers.com/showthread.php?t=1280743
Dear all,
I will release my first ROM, that will be a Super Oxygen based on FXP028.
The main objective is to be a superclean and demon fast rom
For now I need some testers to help me out.
After the testing period I provide more information.
Interessed in testing just send me a P.M.
Thank you!
Test period started =)!
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
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:
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