Hello,
What are the differences in the builds of FreeXperia (https://sites.google.com/site/projectfreexperia/) and the builds from CyanogenMod.com?
Do they use different libs?
Sent with my Xiaomi MI2 with Tapatalk Pro
Well, obviously FXP is the unofficial version that got released before the official nightlies started to roll out. The cool thing with FXP is that they are collaborating with Sony, and their Free Xperia Project Cyanogenmod builds are the result of that collaboration. They can get drivers, blobs etc. much faster and easier than most other devs out there, so FXP is an awesome project.
Official CM is what you're used to. The nightlies are updated more often than FXP's build, so bugs get fixed much much quicker.
You should probably go with official CM. I can't really see why you should flash an "old" build (FXP)
Sent from my C6833 using Tapatalk
Related
Cyanogen has released for our belived phone wt19i...codename coconut...cm 7.2.0...2.3.7...nightly build...the question is,have anybody ever try it?
Sent from my WT19i using xda premium
CyanogenMod haven't released CM7 on their website yet for Live
yes neroyoung is right CM yet not available for WT19.
Waiting eagerly
Please update this tread when support is available.
On the cyanogenmod forums are 13 nightly builds posted...
How much time does normally pass between a first nightly build and a stable release?
Anyone got any idea how stable this build is?
cm_coconut_full-13.zip
any news on that?
Its out
I have used aka tested it. Its cool fast.
Problem
The dual speaker is not working which can be fixed using a flash file
http://forum.xda-developers.com/showthread.php?t=1600762&page=4 check here for the file
The brightness is too much I think 100% I think it will spoil the display.
No hepatic feedback on soft keys.
Battery back up I have not tried
Anyone can comment on battery..?
Go to Development section, there are 2 topics, CyanogenMod 7.2 and CyanogenMod 9 for 2011 Xperia series, including Live with Walkman.
These are the CM ROMs, that are also on the official webpage. FreeXperia Team is responsible for building these to 2011 Xperia phones. You can find more info in these topics.
Cm9 stable
Yes! I've tried the new rom. It's smooth and fast. NO doubt. But comes with few bugs which can be resolved easily.
1. Wifi doesn't work.
2. Accelerometer lag
3. Stereo Speakers working but no xLoud ( Only for sony live with walkman).
I've fixed all these bugs and create d a backup image. Contact me and i'll send you the link.[/FONT]
You guys are aware right that Erik Hardesty a.k.a. dalingrin is wokring on ICS for touchpad and has promised (citation needed) to deliver before CM9? Now, I want to know if he indeed delivers, then will his work to taken to make the CM9 build faster and then will he be included in the official CM team. I am asking this because I have a Moto Defy and before CM7, Quarx, Epsylon and others compiled it and I think they are now in the CM team. Just curious on how it works.
He is already a part of the CM team, he is the CM maintainer for the Nook Color.
That's news.. well for me! But if there is someone else in his place who is ot in the CM team then what happens?
abhi.eternal said:
That's news.. well for me! But if there is someone else in his place who is ot in the CM team then what happens?
Click to expand...
Click to collapse
Then its not a CM9 build. Basically the CM team are a bunch of developers on different devices. In the case of ICS each developer will build their versions and it will be pushed and integrated into the CM9 list when CM9 is ready to launch. However, in the case where a CM team member's build is ready to be tested before CM9 is ready then they will most likely post them as a under a different title because its not integrated as a CM9 device yet.
In the case that another developer releases an AOSP ROM into the wild then he can do whatever he wants with it and it has nothing to do with the Cyanogenmod team whatsoever.
Samsung Galaxy S Captivate ICS CM9, Glitch Kernel | HP TouchPad CM7 Xron Beta 2.9.1
@iamsamsamiam: I get your point but if that is the case then how come Quarx and Epsylon (for Motorola Defy) are in the official CM team now (I think they are [citation needed!]). If you are not aware, CM7 had no love for Defy for a very long time and that gap was filled by Quarx at first. Afterwards, when we had a almost complete working rom based on CM7, these devs were included in the official list. I just want to know is this how it happens?
abhi.eternal said:
@iamsamsamiam: I get your point but if that is the case then how come Quarx and Epsylon (for Motorola Defy) are in the official CM team now (I think they are [citation needed!]). If you are not aware, CM7 had no love for Defy for a very long time and that gap was filled by Quarx at first. Afterwards, when we had a almost complete working rom based on CM7, these devs were included in the official list. I just want to know is this how it happens?
Click to expand...
Click to collapse
And there are still a ton of devices out there without any Cyanogenmod ROM at all. I guess its more like a developer who wants to code for a particular device and wants to put a CM flavour to the ROM and gets permissions from the CM team to use it and builds a CM ROM and I guess they would become part of the team as a de facto point since they continue to support their build. Remember there are a ton of other ROM developers out there that don't use a CM base and does things their own way.
Cyanogenmod isn't always going to be the "best" ROM out there for every device, but they're trying to support many devices out there. The devices that get support are reflected upon the community and the more popular the phone the larger the community. And developers come out of said communities and maybe one of those developers wants to make it into a CM build.
Samsung Galaxy S Captivate ICS CM9, Glitch Kernel | HP TouchPad CM7 Xron Beta 2.9.1
That made sense!
This rom is effectively the CM7.2 version of FXP140. I don't believe any changes have been committed to the es209ra sources since FXP130, but it does include the all the latest 7.2 commits made in the 2 months or so since FXP130 was released.
Background:
The USSD exploit was published last week and the Cyanogen dialer is vulnerable. I don't know if there's a USSD factory reset code for the X10 but frankly, I don't want to find out.
The exploit was patched in the CM sources recently and since FXP is no longer releasing 7.2 builds I thought I'd try and build the latest CM version from source for use on my X10 (rather than install some extra app just as a work around)
I was most surprised to get it compiled correctly first time, and I've been running it on my phone today without problems. I figured there are people here who don't have the time or inclination to compile the sources and might find this rom useful.
Installation
It's exactly the same as FXP 7.2 roms, so just follow this.
Colossus FXP install guide
You'll need the standard FXP 130 kernel, or a kernel that's compatible with FXP 130. The Kernel.sin file is included in the rom and you can make an FTF from that with Flashtool if you don't already have a suitable kernel to install.
Download link
http://www.mediafire.com/?6zkni41daaaieq7
Disclaimer: I'm not a developer and haven't made any changes, this is just a clean build of the very latest latest CM7.2 sources from Github: https://github.com/CyanogenMod/
will test.
REPOSTED!
Me test, too.
And I did, idk what kernel should I use, so it's a bit laggy for me. and Play store with Gmail isn't working. but everything else works good.
Sent from my SO-01C using xda app-developers app
will try it
working ok. if i could add the camera from cm7 M&M.. would be better. A lot of free ram, good 3d performance with Cosmic Kernel Mod.
I'm not sure which camera app M&M use, the APK should work as long as it's not the semc one (since M&M is based on stock rom/zmod).
what's USSD ?
USSD codes are special dialling codes that can be used to make a phone perform special functions (e.g. show the IMEI, access the secret menu on a sony stock rom).
See the link I posted originally for more details on the bug:
http://dylanreeve.posterous.com/remote-ussd-attack
It's most serious on Samsung phones as they have a USSD code that performs a factory reset without prompting.
Hi,
i use in my Roms CM-cam.apk
Greets maik
Gesendet von meinem GT-I9100 mit Tapatalk 2
Originally Posted by CYANOGENMOD
in facebook
CM 10.1 Status Update
So we continue to work through the merger of 4.2 code and our CM enhancements. A branch in our github repos called mr1-staging has been created to facilitate the merger and is the target for core CM items (not features).
mr1-staging is not meant to be compile-able, its only purpose is to be a staging grounds for our core work. Chances are, it is useless for independent builders.
CM 10.0 (4.1.2) code is in jellybean-stable, if you are working on a bug-fix for the last stable release, patches should be submitted against that branch. If/when we do another 4.1.2 release (ie CM 10.0.x), it will originate from code in this branch.
Once staging is done in mr1-staging, we will push all that code to a 'CM10.1' branch, and eventually back to our primary 'jellybean' branch. This process is in place to make sure that we effectively move forward from CM 10.0 code, instead of starting over as was seen with the jump from Gingerbread to ICS. Patches from gerrit will be accepted towards CM 10.1, but for now, please have patience while we work through mr1-staging.
While the 4.2 updates are on a smaller scale, they do present some changes that will need to be considered and will effect our implementation of features. Just to name them briefly: Telephony Split, Multi-User, Quick Settings, and Lock-Screen Widgets. These items will be a strong focus when the initial CM10.1 branch is created.
On the feature front, David van Tonder (dvtonder) decided to make his weekend productive, and has already worked on the code for the majority of our MMS enhancements: Emoji support, sms split, gestures and templates, quick messaging. Notably MMS auto retrieve is not being forward ported as Google fixed that themselves. As stated above, patches will hit gerrit review after this staging process is completed.
As always, a timeline isn't and won't be available. We will continue to provide updates as we have them.
Click to expand...
Click to collapse
Let's wait for further announcements
thanks but no CM10.1 for Neo and Neo V
mido_fedo said:
thanks but no CM10.1 for Neo and Neo V
Click to expand...
Click to collapse
CM 10 is available for Neo/Neov ..but its not the stable release ..they are close to making a stable release .. So I guess we might get 10.1 too
Abhiheart said:
CM 10 is available for Neo/Neov ..but its not the stable release ..they are close to making a stable release .. So I guess we might get 10.1 too
Click to expand...
Click to collapse
Even if we get a stable Cm 10 ,it would be worth it and I think Fxp would do that!
As for Cm 10.1,it's been answered already ,it's not just worth the efforts n hassles!
Sent from my MT11i using xda premium
---------- Post added at 09:42 AM ---------- Previous post was at 09:41 AM ----------
FXP said:
HY All
We said it already several pages back CM10 is last release for 2011 devices
Those devices use an old kernel (2.6.32) and old blobs for camera (ICS)
So even making those work with cm10 (jellybean) was an real pain
To update kernel to 3.0 we will require 6+ months (not worth for an 2 year old SOC) limited in hardware and memory
Even if we take this effort this device will not be able to handle next version of android after 4.2 because it simply lacks RAM
Even for Jellybean we had to use legacy camera to be able to use camera in an proper way (with broken panorama)
What's the benefit of having latest android if your device is not able to use new features?
We will continue fixing cm10 and releasing weekly updates with latest JB progress
Jerpelea
FreeXperiaTeam
Click to expand...
Click to collapse
Sent from my MT11i using xda premium
What does it take for a ROM to move from unofficial to official or is that not how it works? For example, I run cm11 official because its official. I would like to run cm12 but it says unofficial.
Sent from my LG-VS985 using XDA Free mobile app
Someone can correct me if I'm wrong.. But... Unofficial is usually when someone compiles the build themselves and share. They sometimes add commits that have not been merged into official builds. Sometimes add add-ons that may not be supported in official builds. Sometimes a dev team may not have a maintainer for a specific official build. Most times unofficial builds aren't always as dependant as official. Sometimes they can be better.
As for CM 12. It went official last night. They are nightly builds, but they are official now. The thread is in the original development section. You can go to the CM site and it shows all the official 11 builds and then starting with 1/6 it is now on official 12 nightly. Hope that helps. ?
Just to clarify. The official CM11 thread is where to go for more info right now. Sure they will probably start a new one soon, but the link still takes you to CM and the latest build is the CM 12 from today 1/6. http://download.cyanogenmod.org/?device=vs985&type=nightly