Finally the wildfire S is going to have official support for this, andthee devolopers of cyanogen are working on this.
Here is the notice:
It’s been nearly two months since we released the initial 7.2 RC1. Since then, the team has been working hard to identify and fix the issues reported to the bug tracker. We are nearing our release of CyanogenMod 7.2, based on Android 2.3.7 and will be releasing…….soon! You didn’t think you were getting an ETA did you?
Users may notice that some devices that received RC1 will not be graduated to a stable release. This is due to bugs we consider as showstoppers, but we feel there is no reason to hold up working devices for a few stragglers. The stragglers are not dropped, but will play catch-up to receive a 7.2-stable release.
What’s Next?
Many people have wondered what will become of CyanogenMod 7 now that Ice Cream Sandwich work has begun, and likewise, what happens to all the devices that won’t make it to CyanogenMod 9. We aren’t just leaving you behind.
The 7.x branch of CyanogenMod will stay open, available, and active beyond 7.2. We may switch to a more weekly drop of the infamous nightlies at some point, but they will continue as well.
In addition to that good news, we have a slew of new devices being merged into mainline thanks in part to our developer relations initiative and the greater Android community.
After CyanogenMod 7.2 is released, we will be merging in and welcoming aboard maintainers for the following devices (with more queued):
HTC Status (chacha)
HTC Wildfire S (marvel)
LG Optimus Chic (e720)
Motorola Photon (sunfire)
Samsung Galaxy 5 (i5500)
-CyanogenMod Team
Click to expand...
Click to collapse
Why didn't you just link to the blog post?
Thrawed said:
Why didn't you just link to the blog post?
Click to expand...
Click to collapse
because im not sure if is allowed to put links of other sites
Sexy!
Sent from my Wildfire S using xda premium
Related
HTC Releases Desire HD Source Code
For those of you with an HTC Desire HD, today is a good day for you! HTC has released the opensource bits of the Desire HD's source code on their developer website (see below for link). The most important parts of this release are the kernel and the drivers for the phone.
With the kernel and drivers code developers and tinkerers can start building custom ROMs for the device, making it go faster, the battery last longer, and who knows what other sorts of cool stuff! This won't happen over night, but now that the code is in the wild, it's just a matter of time.
And for you guys that would never, ever run a custom ROM on your phone, you've got good news, too! The more sets of eyes looking at the source code, the more likely it is that bugs will be found and fixed. This means that your devices will likely get more stable and bug-free the longer the community digs into the code.
http://pocketnow.com/android/htc-released-desire-hd-source-code
has anyone played around with the desire hd rom and got it working fully on the desire yet ?
Check the development section, there are already ports, only the camera doesn't work but other than that everything is perfect.
But with this Source Code we will maybe se more stable HD roms + working camera?
https://github.com/MiCode/
The project call patchrom，we can just make a build with the cm rom or our official sense rom.
I want to hava a try but i have not learned to do it.
There are so many miui fans still using inc.
So, any developer can try this out?
Tiny? Pons?
However, thanks for your cm10.1!
Due to me having to build on a build bot, then downloading a compiled ROM taking over 2 hours on my slow internet, I don't see me trying this right yet. Or at all. I'm not too fond of MIUI; I prefer CM, obviously. Plus I glanced at some of the code and, most (all?) of the README's are "This is a place holder, please fill in real text when you add stuff." for the past 3 years. I'm not too big of a fan of undocumented ROMs, and they don't even really have a basic readme. I also didn't see a readily available inc device tree, though admittedly I didn't look too hard, so this might have to be a port, than official compiling.
Galaxy S3 Rocking CleanRom 7
kyle1087 said:
Galaxy S3 Rocking CleanRom 7
Click to expand...
Click to collapse
This post is unrelated to the Inc.
Sent from my HTC One using Tapatalk 2
Even though Galaxy Nexus is no more officialy supported by Google and stuck at Android 4.3, KitKat Roms emerged quickly and evolve rapidly - thanks to our crazy devs!!! :victory: So how you all handling this? Still at 4.3... already jumped to a 4.4 rom?
I know it took a long way for 4.3 roms to reach that point where everything works near perfect and I think that Cataclysm or SlimBean are such examples. So, some will prefer the comfort of this instead of jumping into the unknown and start dealing with bugs and the trial and error procedure???
As I write this Android 4.4.2 is rolling to newer Nexus devices, my new Nexus 7 already running this and something tells me, since none of the factory images for 4.4.1 and 4.4.2 are officialy on google's page, that another update maybe coming soon. Since our phone is not officialy supported, devs will strugle merging new code to their sources and adapting it for gnex. How do you see this evolving?
To end this, it's been 2 years after the release of GNEX and our forum still is in the top 5 list. Quite impressive if you ask me. Tell that to Google... Galaxy Nexus is a legendary phone even though it's not the sharpest out there. And I am sure its "endurance" over time, will make it even more legendary!
PS: Working on a cool Zooper Skin. Will let u know when it's out!
It will continue, but the gnex population will gradually move on. The new incomers will not likely join at the rate the existing users leave to upgrade to a new device.
If it's any indication, Nexus One and Nexus S development are still continuing and they are older than the Galaxy Nexus. At some point when newer android versions get too resource intensive (KK tried to improve the memory management) then we will start seeing users preferring to stick with an older version.
I will continue with my Galaxy nexus and I'm still very happy with it especially so because of the talented developers here at XDA. I'm currently using the 4.4 KK rom : [ROM] [UNOFFICIAL] CyanogenMod 11 for the Samsung Galaxy Nexus with gapps 20131207. This ROM is now my daily driver and I won't be going back to 4.3 :good:
Thanks for this post, I'll subscribe!
myself, I've been thinking of sticking with Cataclysm for a while. But can I ask those who already use a 4.4 rom if they noticed any signifcant improvement on battery life or multitasking?
wrong thread. sorry
itasoulas said:
Even though Galaxy Nexus is no more officialy supported by Google and stuck at Android 4.3, KitKat Roms emerged quickly and evolve rapidly - thanks to our crazy devs!!! :victory: So how you all handling this? Still at 4.3... already jumped to a 4.4 rom?
I know it took a long way for 4.3 roms to reach that point where everything works near perfect and I think that Cataclysm or SlimBean are such examples. So, some will prefer the comfort of this instead of jumping into the unknown and start dealing with bugs and the trial and error procedure???
As I write this Android 4.4.2 is rolling to newer Nexus devices, my new Nexus 7 already running this and something tells me, since none of the factory images for 4.4.1 and 4.4.2 are officialy on google's page, that another update maybe coming soon. Since our phone is not officialy supported, devs will strugle merging new code to their sources and adapting it for gnex. How do you see this evolving?
To end this, it's been 2 years after the release of GNEX and our forum still is in the top 5 list. Quite impressive if you ask me. Tell that to Google... Galaxy Nexus is a legendary phone even though it's not the sharpest out there. And I am sure its "endurance" over time, will make it even more legendary!
PS: Working on a cool Zooper Skin. Will let u know when it's out!
Click to expand...
Click to collapse
I'm not one to sit by idly and wait for confirmation of a stable new Android version. When 4.4 was released I flashed it right away. Whats the fun in not "jumping into the unknown"?
I dont think small updates are that hard for developers to merge into our current builds. We are already on 4.4.1 and I'm sure that 4.4.2 will be on our devices soon as well.
KitKat has been running great on my device. I dont know of any issues we have now that havent been fixed yet.
jsgraphicart said:
I'm not one to sit by idly and wait for confirmation of a stable new Android version. Wn 4.4 was released I flashed it right away. Whats the fun in not "jumping into the unknown"?
I dont think small updates are that hard for developers to merge into our current builds. We are already on 4.4.1 and I'm sure that 4.4.2 will be on our devices soon as well.
KitKat has been running great on my device. I dont know of any issues we have now that havent been fixed yet.
Click to expand...
Click to collapse
Well...my GPS could be better. I'm seeing at best 30ft accuracy with about 8 satellites locked in with pretty low SNR values.
Im still on 4.3, Slimbean. Waiting for Slimkat to evolve just a litle bit more :good:
alpha-niner64 said:
Well...my GPS could be better. I'm seeing at best 30ft accuracy with about 8 satellites locked in with pretty low SNR values.
Click to expand...
Click to collapse
I haven't had any issues with GPS. It pinpoints pretty fast for me.
And by the way, cyanogenmod just updated us to 4.4.2.
I will be continuing to use my Galaxy Nexus until the 'Nexus 6', it can totally hold up to most of the competition. Currently using the last 4.4.1 Galaxy Nexus Maguro CM11 ROM with ASKP/Franco/Mpokang/Fancy/Stock kernel.
hello
I have ordered N1 32GB smartphone and waiting for shipment
I am wonder ... Can I easly install CM on regular version of oppo N1 ?
Yes, you can flash in stock recovery. Switching between them is very simple.
Sent from my N1 using Tapatalk
i cannot wait to get it
i understand that cm team will support this phone more than others by now?
nowy57 said:
i understand that cm team will support this phone more than others by now?
Click to expand...
Click to collapse
The CM team will be the ones running the show on their CM builds. Oppo will maintain ColorOS, but CM will do their own updates. So we should see a lot of official support and maintenance coming directly from the CM team straight to us.
Sent from my N1 using Tapatalk
so by now i am 101% sure it was good choice
Omni and CM have supported this phone better than most non-Nexus devices since before Cyanogen, Inc was formed, simply due to Oppo being so cooperative.
That is, for example, why Omni had 4.4 nightlies going almost two weeks before most people could even order the device.
Find5 and N1 are probably Omni's two best supported non-Nexus devices.
fcuk I really happy to have it !
Entropy512 said:
Find5 and N1 are probably Omni's two best supported non-Nexus devices.
Click to expand...
Click to collapse
I've been back and forth with Omni since it's been available. I'm enjoying it, but I keep going back to ColorOS for now. Omnirom has been great so far, and I love the amazing support.
Sent from my N1 using Tapatalk
NExus factory images live today. We are suppse to get it but end of this year or start of next. Is anyone out there planning on porting this maybe to both models of our phone? Im on Z008 Just curious
cell2011 said:
NExus factory images live today. We are suppse to get it but end of this year or start of next. Is anyone out there planning on porting this maybe to both models of our phone? Im on Z008 Just curious
Click to expand...
Click to collapse
If the source code isn't released we can't do anything. So it's probably not even the dev's fault as much as it is Google's.
All we can do is wait.
cell2011 said:
NExus factory images live today. We are suppse to get it but end of this year or start of next. Is anyone out there planning on porting this maybe to both models of our phone? Im on Z008 Just curious
Click to expand...
Click to collapse
Hate to be the bearer of bad news...
Ports assume the two devices (the base device, and the one to port to) are very similar (same chipset, et cetera). A good example (I used to use HTC) is the Sensation was a very good base for the MyTouch 4G Slide (they even shared the same battery design/size).
Unfortunately the Zenfone 2 and either of the new Nexus devices are worlds apart from each other. They don't share the same architecture, let alone chipset. We would be better off piggybacking off the work of the ASUS Fonepad 7 FE375CG (Z3560 Chipset) or the Asus Memo Pad 8 ME581CL (Z3580) - but in reality, in terms of updates - it's more likely we would be the base for those devices in a few months time.
Sorry.
---------- Post added at 20:36 ---------- Previous post was at 20:33 ----------
AkiroX said:
If the source code isn't released we can't do anything. So it's probably not even the dev's fault as much as it is Google's.
All we can do is wait.
Click to expand...
Click to collapse
That's right, all we can do is wait, then build from source once available.
Porting has it's place, but it can be a gong-show.
Source already available
We should wait for devs to build it ?
AL_IRAQI said:
Source already available
We should wait for devs to build it ?
Click to expand...
Click to collapse
AOSP is available, but now we have to wait to have CM13 in a manageable state. I don't imagine cpalmer and jrior001 will put on the brakes with CM12.1 to build straight from AOSP.
ROMe wasn't built in a day, and it will be months before CyanogenMod will be able to have the AOSP source modified for the new CM13 and reach the coveted milestone one.
Yap, waiting for you too @joel.maxuel for working on it
allasca said:
Yap, waiting for you too @joel.maxuel for working on it
Click to expand...
Click to collapse
Why am I being thrown under the bus? :silly:
In all seriousness, if CarbonROM continues to base their stuff off of CM (which I heard talk of that changing), this time around they may be once again months behind CM in terms of an official product (e.g, none of their devices have hit official status yet this round, or at least as of last night).
Not to speak ill of course, which is why I am curious of the route that does not involve basing off of CyanogenMod.
No guarantees with my involvement to 6.0, but I am interested in the job. I just can't predict what my life demands are going to be like in the spring (time seems tight right now, but I manage).
My short and medium term plans is to keep the 5.1 builds going, hopefully even after Carbon calls it quits for this branch to focus on the new one. The only possible things stopping me are:
Carbon leaves lp5.1.1 branch perfect, meaning I don't even have to do monthlies anymore (also means no future security issues)
CyanogenMod breaks their sources badly (has happened recently when Carbon couldn't keep up)
I get the official stock 6.0 image which ends up breaking modem usage - leaving me unable to properly downgrade to 5.1 to test
It feels like with this plan, someone is going to beat me to the punch by building a CarbonROM mm-6.0 ahead of me. Which is why at some point, I will (probably) be doing builds in parallel. But we shall see when we get there.
Just read this: http://arstechnica.com/gadgets/2015/10/android-6-0-marshmallow-thoroughly-reviewed/
Doesn't seem much for us CM12.1 users to get very excited about anyway. Material design not changed from Lollipop, Google Now launcher already updated with the changes, selectable app permissions already included in CM12.1 via Privacy Guard, fingerprint api and 4K display stuff irrelevant to our zenfones...
Personally, I think a stable CM12.1 (5.1.1) build is more important. In fact, the unofficial build we already have is stable and very nearly there, but I would rather see the last few kinks ironed out and official status before any time is put into 6.0
Most importantly, it should support 64bit for the z00a. Any news on this?
Sent from my iPhone using Tapatalk
The next month, asus update android 5.1 for zenfine 2, maybe 6.0 ? I don't know this,