[Q] custom EVO ICS ROM speculation? - EVO 4G Q&A, Help & Troubleshooting

Anyone heard anything about when someone might cook up a ready to use ICS Rom for the EVO?
Sent from my PC36100 using Tapatalk

Only confirmed one I know of is Cyanogenmod 9 coming out in January.
Sent from my PC36100 using xda premium

Expect at least two months. And for official HTC roms ported to our devices even longer.
Sent from my PC36100 using Tapatalk

I'm really surprised to find that after searching the evo dev forum that it appears that there aren't any active porting projects. I'm curious to know why that is... the evo 4g seems like a pretty speedy phone that should fairly easily support ics without a problem.
I know that Cyanogen will probably release an ICS port at some point "when it's done" but cyanogen is well known for having extremely long testing cycles before releases (even beta ones) are made and both the ics sdk and sources are now available... the tools are there, i'm just really surprised that it seems nobody is using them.

cpgeek said:
I'm really surprised to find that after searching the evo dev forum that it appears that there aren't any active porting projects. I'm curious to know why that is...
Click to expand...
Click to collapse
Have a look here: http://forum.xda-developers.com/showthread.php?t=1328339
AFAIK, they've switched the base from the SDK dumps to source as soon as it was released.
I know that Cyanogen will probably release an ICS port at some point "when it's done" but cyanogen is well known for having extremely long testing cycles before releases (even beta ones) are made and both the ics sdk and sources are now available... the tools are there, i'm just really surprised that it seems nobody is using them.
Click to expand...
Click to collapse
Ports like this take months, as the source is not released with the drivers for all devices and the device drivers that are used in Gingerbread AOSP roms are not fully (if at all) compatible with the new OS version, not to mention the amount of testing that is involved to make sure everything is bug-free enough for any kind of beta release. ICS ports are in the works, just don't expect any sort of stable or mostly functional releases for a while...

Source Code just came out so time is needed to have anything stable for are Evo
I Am Legend

JUN10R831 said:
Source Code just came out so time is needed to have anything stable for are Evo
I Am Legend
Click to expand...
Click to collapse
Source dropped yes but not with the drivers for alot of phones including HTC phones so anything stable will be a few months. Most likely from cm

Related

Froyo + Sense ROM?

Is there a stable Froyo with Sense out there, one based on the Evo's ROM cause I did flash a rom by avalaunch. But it was based on the desire. I didn't like that and it didn't seem as fluid. So my question is... Is there a Froyo with Sense ROM out there thats stable and based on the Evo? and if there is what features are not working (if any) thank you
So far, all the FroYo roms are missing ( at the very least ) the back camera & 4G. However DamageControl & Cyanogen should have working ROM's within the next few days. Cyanogen will be AOSP, but i think DC might be Sense UI.
I initially thought I'd want an AOSP rom but after trying them I much prefer Sense, mainly for the widgets. Lets hope DC has sense! Wouldnt that be a slap in the face to HTC devs who need until December to complete it.. and DC does it with 2 devs in their spare time?
OneStepAhead said:
I initially thought I'd want an AOSP rom but after trying them I much prefer Sense, mainly for the widgets. Lets hope DC has sense! Wouldnt that be a slap in the face to HTC devs who need until December to complete it.. and DC does it with 2 devs in their spare time?
Click to expand...
Click to collapse
Htc devs are in no rush and it's not due to be released in December but BY December meaning any time until then
Is there any time frame for when DC development will come out with froyo with sense ROM. I currently am running DC 3.2.3. If they release it will it be listed in DCupdater?
From what I understand Google will not let anyone release 2.2 until N1 has it for a while. HTC has no control over it. It is google's way of keeping the N1 atop of the phone ladder. The same will happen with the next version. Its google's game, we have to play by their rules.
eskomo said:
From what I understand Google will not let anyone release 2.2 until N1 has it for a while. HTC has no control over it. It is google's way of keeping the N1 atop of the phone ladder. The same will happen with the next version. Its google's game, we have to play by their rules.
Click to expand...
Click to collapse
I don't think that's true... The source code is released so anyone can compile it whenever. That's the whole point of it being open.
Where did you hear that?
hved999 said:
Is there any time frame for when DC development will come out with froyo with sense ROM. I currently am running DC 3.2.3. If they release it will it be listed in DCupdater?
Click to expand...
Click to collapse
I've been stalking the DC thread for the past few days & it looks like they're starting to wrap things up. They didn't give an exact ETA, but based off the few comments they have made, i'd guess within the next few days ( i would love it for this weekend ), but i guess we'll just have to wait & see .
eskomo said:
From what I understand Google will not let anyone release 2.2 until N1 has it for a while. HTC has no control over it. It is google's way of keeping the N1 atop of the phone ladder. The same will happen with the next version. Its google's game, we have to play by their rules.
Click to expand...
Click to collapse
Well, not entirely. When Google is finished testing on their "standard" hardware (in this case, the Nexus One) they will designate a final version. Then, HTC needs to get hold of this final version and add support for any unique hardware or software that their devices have. Think of it like release candidates and RTM versions of Windows. PC manufacturers get hold of the release candidates and test versions so that they can develop drivers and make sure their devices all work with the new OS. Then they get the final version, tweak what needs to be tweaked, run it through bug testing, and then pass it along.
In this case, HTC has to get the final version, make sure all of their apps and drivers work, make sure it works on their phones, and then pass it to Sprint for *more* testing to make sure it plays nice with the network and performs well.
Veritas06 said:
I've been stalking the DC thread for the past few days & it looks like they're starting to wrap things up. They didn't give an exact ETA, but based off the few comments they have made, i'd guess within the next few days ( i would love it for this weekend ), but i guess we'll just have to wait & see .
Click to expand...
Click to collapse
I am aware that for many ROMs the camera doesn't work. Will it be working DC's ROM? And will it have sense? Is there any speculations of certain features not working? sorry these questions but since you have been "stalking" their thread you would know this stuff more than other (atleast I guess).
hved999 said:
I am aware that for many ROMs the camera doesn't work. Will it be working DC's ROM? And will it have sense? Is there any speculations of certain features not working? sorry these questions but since you have been "stalking" their thread you would know this stuff more than other (atleast I guess).
Click to expand...
Click to collapse
According to a Tweet from Damageless himself last night "finishing porting cameras to Android 2.2... getting close."
Also the ROM will include Sense w/ the option to disable if desired.
-kp
kperry1911 said:
According to a Tweet from Damageless himself last night "finishing porting cameras to Android 2.2... getting close."
Also the ROM will include Sense w/ the option to disable if desired.
-kp
Click to expand...
Click to collapse
Thank you very much. Is there a approximate release date for the ROM?

Inc no longer receiving 2.3, according to HTC Rep?

From Droid Life on Twitter:
Droid Life
I must stay, not surprised if it's true. The time it was "supposed" to happen came and went, with no word. I bet they do the same thing with the 2.3 release that they did with the HTC Desire, put it out there on their development site and state that it's for "advanced users". Good thing we had the leak a little while back, and amazing developers who spend endless hours tweaking and adding things to make it usable!
Hopefully this is a mistake. Otherwise, it would be nice if they could release the source code so that those who actually care (xda devs, etc) can deliver the goods. However that's wishful thinking.
Sent from my Droid Incredible using the XDA app.
i could have told you that in march when it EOL'd HTC still sells and supports the device, and alot of verizon stores have accessories for the phone on clearence as in, under 4 bucks sitting in a cardboard box in the back clearence, (IE. they want to get rid of them)
so, yeah, i could have told you that already, and we probably will see a source code release, they released the source code for GB on the samsung galaxy s phones, and i think either MIUI or cyanogenmod already has 2.3.4 on the fascinate, with the right kernel.
And here too:
http://www.androidpolice.com/2011/0...bringing-gingerbread-to-the-droid-incredible/
I never really cared about a gingerbread ota, I just want that sense .35 kernel source.
Sent from my ADR6300 using XDA App
i said it before, and i will say it again, ROOT YOUR PHONES IF YOU WANT MORE OUT OF IT!.
there are some non-tech users, yes, but those of us that are power users, like the idea of having a good phone, i'm close to ordering an extended battery (just going to mod the siliconecase i have now with a pocket knife, no need to speed 15 bucks on somthing you can do yourself )
Kiboe said:
i could have told you that in march when it EOL'd HTC still sells and supports the device, and alot of verizon stores have accessories for the phone on clearence as in, under 4 bucks sitting in a cardboard box in the back clearence, (IE. they want to get rid of them)
so, yeah, i could have told you that already, and we probably will see a source code release, they released the source code for GB on the samsung galaxy s phones, and i think either MIUI or cyanogenmod already has 2.3.4 on the fascinate, with the right kernel.
Click to expand...
Click to collapse
I don't think we'll be seeing source code. AFAIK, they're only obligated to opensource within 30 days of officially releasing it.
snq- managed to reverse engineer the desire's gb kernel when it was leaked, and created a closed-source kernel with governers and oc/uv as modules. So it's possible to have a custom kernel, but I know for a fact that I don't possess the skill required to do that. We'd have to talk to the resident kernel hackers about that.
tcberg2010 said:
I never really cared about a gingerbread ota, I just want that sense .35 kernel source.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Yeah, kernel source would be nice.
wdfowty said:
I don't think we'll be seeing source code. AFAIK, they're only obligated to opensource within 30 days of officially releasing it.
snq- managed to reverse engineer the desire's gb kernel when it was leaked, and created a closed-source kernel with governers and oc/uv as modules. So it's possible to have a custom kernel, but I know for a fact that I don't possess the skill required to do that. We'd have to talk to the resident kernel hackers about that.
Click to expand...
Click to collapse
what device does -snq own?
Kiboe said:
i said it before, and i will say it again, ROOT YOUR PHONES IF YOU WANT MORE OUT OF IT!.
there are some non-tech users, yes, but those of us that are power users, like the idea of having a good phone, i'm close to ordering an extended battery (just going to mod the siliconecase i have now with a pocket knife, no need to speed 15 bucks on somthing you can do yourself )
Click to expand...
Click to collapse
Agreed, time to root to take advantage of this phone if you haven't. Not only can you run Gingerbread, but get better battery life and better overall feel.
I saw the reverse engineered HTC Desire kernel, as since my g/f has one on USCC now. I couldn't figure out how it was done, other than reverse engineered...impressive.
Maybe we'd get lucky and some developer would do the same, as I think it'd make the 2.3 Sense ROMs run better...
I am so thankful for our devs/modders/themers who put in the time!
JoelZ9614 said:
what device does -snq own?
Click to expand...
Click to collapse
I've seen him a lot in the Desire forums, and Xoom too...but not sure what device he owns for sure (maybe both, if not more?).
bollocks!
/10char
The biggest problem we will have, if HTC doesn't release the update, is that they will not HAVE to release the Gingerbread kernel source. That means no OC or other great tweaks to the kernel.
I just want a tun.ko module for the gingerbread kernels so that I can use VPN again with the new Sense 3.0 ROMS! Come on, we atleast need the source!
I'd be way more upset about not getting gingerbread if it wasn't already available with the aosp roms.
Sure it sucks not getting the code to modify sense kernels, but honestly, with the dev community around here, that's not a huge loss.
Sent from my ADR6300 using XDA App
Lets start nagging them about ICS
Maybe there's a way to get HTC to start putting leaks on their dev center site so that the community can play with them too. Is there a way to mod one of the other GB kernels source codes to fit the Inc?
http://htcdev.com/devcenter/downloads
kzoodroid said:
Maybe there's a way to get HTC to start putting leaks on their dev center site so that the community can play with them too. Is there a way to mod one of the other GB kernels source codes to fit the Inc?
http://htcdev.com/devcenter/downloads
Click to expand...
Click to collapse
Actually yes. Having a kernel dev that has the knowledge or is willing to that for us....
seems that chad is the only active kernel dev left in this forum. i found a site that had pretty detailed instructions on how to set up a linux box to build kernels and it doesn't look all that difficult. my only problem is linux, i kind of suck at it, though i've played with it off and on for the last 6 years. right now i don't have a linux box but in december i'm getting a new laptop and will turn the old one into a dedicated linux box so maybe i'll look at it then. i also plan to move to the iphone, i know you don't have to say it i drank the kool-aid, but this will free up my inc for me to do more experimentation with.
We will have to wait and see! THe new HTC Vigor is looking promising.
^noob

[Q] Source

I have a question, while everyone says that to get cm7 we need to wait for official gb. I understand that but we got official froyo didn't we? how come we don't have cm6 if it was official froyo and i would think it came with source within 30 days?
By all means, dont take this as a rant, i was just curious.
The people working on cm6 didn't see any point in finishing the project even with source because gb and new source was supposedly around the corner. 6 months later, we still don't have gb, and imo may never, and cm6 is final. The real cyanogen team doesn't support 6 anymore afaik.
Sent from my SPH-D700 using XDA App
austin420 said:
The people working on cm6 didn't see any point in finishing the project even with source because gb and new source was supposedly around the corner. 6 months later, we still don't have gb, and imo may never, and cm6 is final. The real cyanogen team doesn't support 6 anymore afaik.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
No I asked this same question the other day and a CyanogenMod dev said it was because we never got driver sources :/ supposedly were getting them with gb but if not its gonna be hit or miss every step of the way since building aosp roms w/o source is like navigating a maze in the dark.......
theduce102 said:
No I asked this same question the other day and a CyanogenMod dev said it was because we never got driver sources :/ supposedly were getting them with gb but if not its gonna be hit or miss every step of the way since building aosp roms w/o source is like navigating a maze in the dark.......
Click to expand...
Click to collapse
i thought they had to release source within 30 days? or is the driver source not part of that?
if they didn't release the driver source with official froyo release then they probably wont for gb, then its say bye bye to official cm -.-
kwazytazz said:
i thought they had to release source within 30 days? or is the driver source not part of that?
if they didn't release the driver source with official froyo release then they probably wont for gb, then its say bye bye to official cm -.-
Click to expand...
Click to collapse
Let's clear a something up.
Official Cyanogenmod is 100% possible WITHOUT source code/drivers/etc. it just is not a practical endeavor to begin the arduous process of writing drivers and an AOSP kernel from scratch when there is a very real chance of source code being released in the near future.
kwazytazz said:
i thought they had to release source within 30 days? or is the driver source not part of that?
if they didn't release the driver source with official froyo release then they probably wont for gb, then its say bye bye to official cm -.-
Click to expand...
Click to collapse
Yeah its not impossible dude, just like 063_XBOX said..... I thought my metaphor explained it pretty well .... its possible to navigate your way out of a maze in the dark.... it'll just be a pain in the ass running into walls the whole way through..... "if we don't get any source with gb, Id think we would have nightly builds within 2-3 months assuming everyone pitched in and we had our best devs on the job..... " everything in the quotes is speculation and my personal guess so take it with a grain of salt or not at all.....
Ninja Edit: and as for source being released within 30 days of rom release, that's only for the kernel (and maybe rom?, I don't think roms have source??? I could be wrong)...... but drivers are closed source, which means they aren't required by license to give out.....
theduce102 said:
No I asked this same question the other day and a CyanogenMod dev said it was because we never got driver sources :/
Click to expand...
Click to collapse
I didn't think we ever had a sanctioned cyanogen mod dev working on the epic. Just other devs working on a port.
Sent from my SPH-D700 using XDA App
austin420 said:
I didn't think we ever had a sanctioned cyanogen mod dev working on the epic. Just other devs working on a port.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Naw we have had quite a few devs working on it but one of them just so happened to answer me....
But when I say CM dev I mean someone who actually contributed to the projects and made some progress in getting something to work in one of the builds.....

[INFO] Good News Abound - The state of DEV

I thought I'd clear some things up.
If I'm wrong please don't flame me, I'm only doing my best to subdue the general discontent in [sgh-t989]/[android development]...
Steve Kondik, also known as the creator of the godfather of all ROMS (cyanogenmod) personally owns one of our t989s (source:twitter). That, combined with the fact that this is a FLAGSHIP t-mo device probably means that our phone will be supported from the day that 9.0.0 drops.
Now, let me tell you what this means.
As you all know, for a device get non-kang CM9 our hardware must be fully supported. Camera, GPS, bluetooth, egl drivers all must work.
When a huge scale ROM like CM9 is cooked for so many devices I understand it goes something like this
[AOSP modified by Cyanogenmod(teamdouce)] +
[Android Kernel, also modified by Cyanogenmod]+
[Device tree]+
[A virgin sacrifice]=
CYANOGENMOD
Now the interesting bit, is that as soon as the device tree (Eg. Specific driver modifications for GPS, Camera, GPU) includes our device the device tree can be used to power OTHER AOSP ROMS like Miui
I know that gingerbread MIUI already makes use of the CM7 device tree, so in all likelihood they will use the CM9 device tree as well!!!
So in conclusion.
-Because CM9 has a high likelihood of dropping on our devices as soon as it comes out (most likely within the next 30 days)
-Because other AOSP-Based roms depend on the cyanogenmod device tree
-WE WILL HAVE A LOT OF FLASHING OPTIONS SOON
-Probably including CM9 AND MIUI v4 <<<<--------THAT **** CRAY
Thanks for your time, hope it helped
Don't forget the thanks button feels good when you push it.
there are a lot of other devices with cm9 alpha and we are still not an officially supported device. Still unofficially being worked on
I for one is not counting on it, frankly...
No matter how beautifully you phrase things, WE GOT NOTHING YET.
Sent from my SGH-T989 using XDA App
[A virgin sacrifice] =
SO FREK'IN EXCITED!!!!!
thanks for the info bro looking forward to it
jessejames111981 said:
there are a lot of other devices with cm9 alpha and we are still not an officially supported device. Still unofficially being worked on
Click to expand...
Click to collapse
the thing is, many of those are KANGed as in not officially supported by CM team
of the few that officially are supported is Nexus S i9020 and SGS i9000
even the "classic" SGS2 i9100 is not fully supported by CM yet, there's more bugs than... well it's not usable as a daily driver
that was just before the end of last year
they might have improved it a bit by now
even the Nexus S version of CM9 is still very buggy, that's why i have the stock official ICS4 instead on my Nexus S
Please please use words like
"death of an era." Instead of virgin sacrifice. I don't believe in that
Sent from my SGH-T989 using xda premium
iwasblown said:
Please please use words like
"death of an era." Instead of virgin sacrifice. I don't believe in that
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I don't believe in idiots, can you make them all go away?
It takes time for this stuff guys. Anyone remember how long it took to jump from donut to eclair to get a stable rom? And look how few devices there were that actually ran android. This whole "if its not done in 2 weeks then its never happening" thing is a bit unfair. Let the devs dev and those who do not can wait for them quietly.
Why this statement?
From a glaxay better than yours.
tl;dr
I am basing my entire post on the fact that Steve Kondik has our device and should theoretically be working on it.
Click to expand...
Click to collapse
Steve Kondik aka Mr. Cyanogen also works for Samsung. I am sure he gets ALL Samsung devices...
corwest said:
It takes time for this stuff guys. Anyone remember how long it took to jump from donut to eclair to get a stable rom? And look how few devices there were that actually ran android. This whole "if its not done in 2 weeks then its never happening" thing is a bit unfair. Let the devs dev and those who do not can wait for them quietly.
Click to expand...
Click to collapse
It only takes 2 weeks to modify the stock rom or cm7/9.
Its the expectation that is built when people act like quantity is all that matters. There are basically only 2 people making roms; Samsung and CM team, everyone else just waits on these 2 so that they could tweak and modify one of those 2. The funniest part is that the use of the word "kanging" is thrown around among these other people.
housecat93 said:
I thought I'd clear some things up.
If I'm wrong please don't flame me, I'm only doing my best to subdue the general discontent in [sgh-t989]/[android development]...
Steve Kondik, also known as the creator of the godfather of all ROMS (cyanogenmod) personally owns one of our t989s (source:twitter). That, combined with the fact that this is a FLAGSHIP t-mo device probably means that our phone will be supported from the day that 9.0.0 drops.
Now, let me tell you what this means.
As you all know, for a device get non-kang CM9 our hardware must be fully supported. Camera, GPS, bluetooth, egl drivers all must work.
When a huge scale ROM like CM9 is cooked for so many devices I understand it goes something like this
[AOSP modified by Cyanogenmod(teamdouce)] +
[Android Kernel, also modified by Cyanogenmod]+
[Device tree]+
[A virgin sacrifice]=
CYANOGENMOD
Now the interesting bit, is that as soon as the device tree (Eg. Specific driver modifications for GPS, Camera, GPU) includes our device the device tree can be used to power OTHER AOSP ROMS like Miui
I know that gingerbread MIUI already makes use of the CM7 device tree, so in all likelihood they will use the CM9 device tree as well!!!
So in conclusion.
-Because CM9 has a high likelihood of dropping on our devices as soon as it comes out (most likely within the next 30 days)
-Because other AOSP-Based roms depend on the cyanogenmod device tree
-WE WILL HAVE A LOT OF FLASHING OPTIONS SOON
-Probably including CM9 AND MIUI v4 <<<<--------THAT **** CRAY
Thanks for your time, hope it helped
Don't forget the thanks button feels good when you push it.
Click to expand...
Click to collapse
I'd like to believe, I really would. And I hope this does come to fruition. However, even if it doesn't, the few ROMS we do have are pretty good, and our phone still outperforms almost anything else available right now, so I'll still be happy.
I do have one request, though. Can we figure out a way to make CM based ROMS happen without a virgin sacrifice? There are so many other things in life that require those, that they are starting to become scarce
The fact that lots of other phones have alphas and repositories available to even make kangs does not fare well for our device.
Sent from my HTC_Amaze_4G using xda premium
guys chillax..slayher already has it booting..and that's news from december
good to know, thanks
Great phone, needs more dev time and hopefully that comes along with it when ics hits.
We got shafted early with the nexus release so close to the T989 and a dev that promised things but ran away.
New year brings new hope. Great respect for the devs that care about our phone.
Sent from my SGH-T989 using XDA App
Let's hope the mods don't ban what little devs we have left...
Sent from my HTC_Amaze_4G using xda premium
AznDud333 said:
guys chillax..slayher already has it booting..and that's news from december
Click to expand...
Click to collapse
I don't follow, what do you mean by booting?
synergeticink said:
I don't follow, what do you mean by booting?
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Booting

CM9 Stable

Looks like the G2 (Desire-Z) will not be getting CM9 stable as I have been keeping an eye on this list since last week's launch:
http://get.cm/?type=stable
Does anyone in this dev thread know why? I know there are unofficial RCs and the nightlies, but I avoid them and only go for stable. I was hoping it would get ICS stable but it appears 7.2 Gingerbread will be this device's final stable ROM.
Any insight would be greatly appreciated!
sf_smith said:
Looks like the G2 (Desire-Z) will not be getting CM9 stable as I have been keeping an eye on this list since last week's launch:
http://get.cm/?type=stable
Does anyone in this dev thread know why? I know there are unofficial RCs and the nightlies, but I avoid them and only go for stable. I was hoping it would get ICS stable but it appears 7.2 Gingerbread will be this device's final stable ROM.
Any insight would be greatly appreciated!
Click to expand...
Click to collapse
We don't have the needed drivers/source code HTC backed out on us. Aside from that though Mimicry is VERY stable I'd recommend flashing it!
Many roms past GB are very stable now. From Sense 4.0, to ICS, to even JB nightlies are reportedly smooth.
I use this ICS as a daily driver and it's very stable (AOKP): http://forum.xda-developers.com/showthread.php?t=1642443
JB nightlies: http://forum.xda-developers.com/showthread.php?t=1605016 Weren't stable when I tried them, but I hear they're really good now. Might try later this week.
It all has to do with drivers being released or something from Qualcomm: http://forum.xda-developers.com/showthread.php?t=1822694
I don't know if it's true. The thread doesn't provide much information, maybe someone can clarify.
Are the drivers really released and being incorporated into roms? People are saying they are already being used in those JB nightlies.
As for not being out officially by CM... I don't even think they started working on it.
sf_smith said:
Looks like the G2 (Desire-Z) will not be getting CM9 stable as I have been keeping an eye on this list since last week's launch:
http://get.cm/?type=stable
Does anyone in this dev thread know why? I know there are unofficial RCs and the nightlies, but I avoid them and only go for stable. I was hoping it would get ICS stable but it appears 7.2 Gingerbread will be this device's final stable ROM.
Any insight would be greatly appreciated!
Click to expand...
Click to collapse
There are no official CM9 roms for the vision. The unofficial roms (Andromadus & the one by jerl92) are the closest thing, but they are only based on Cm9, not released by or associated with the actual Cyanogenmod team. The reason there even is a CM9 based rom is thanks to Andromadus.
That said, Mimicry will have a new version out this week based on the repo for CM9 stable. The non-device specific code anyway, the other branches are of course unofficial and not supplied by the CyanogenMod team.
Sent from my HTC Vision using xda premium
---------- Post added at 03:57 PM ---------- Previous post was at 03:54 PM ----------
.ili.music.ili. said:
Are the drivers really released and being incorporated into roms? People are saying they are already being used in those JB nightlies.
As for not being out officially by CM... I don't even think they started working on it.
Click to expand...
Click to collapse
Yes, the qualcomm drivers have always been incorporated into Andromadus roms as soon as they're available. Since the other roms are based on Andromadus (AOKP, jerl92's), they also incorporate the new drivers.
Sent from my HTC Vision using xda premium
eeeeey, and I thought that CM9 stable for Desire Z is already out, bad luck
I hate to be that guy, but while development related, I'm pretty sure this belongs in the Q&A or General Discussion section. Catch knowledge!
You guys are missing drivers to?? We're also missing them!! Dang HTC :banghead::banghead::banghead:
Sent from my HTC_Amaze_4G using Xparent Green Tapatalk 2
The word around the Cyanogenmod Google+ site is that its coming but that it will take some time given that the drivers need to basically be written from scratch. This is a list of devices that are being droppped from any further releases of CM past CM7. The vision is not included on the list so you could say there is a glimmer of hope but I guess you have to take it with a grain of salt.
https://plus.google.com/117962666888533781522/posts/MRnnvs3oFUF
DON_58 said:
The word around the Cyanogenmod Google+ site is that its coming but that it will take some time given that the drivers need to basically be written from scratch. This is a list of devices that are being droppped from any further releases of CM past CM7. The vision is not included on the list so you could say there is a glimmer of hope but I guess you have to take it with a grain of salt.
https://plus.google.com/117962666888533781522/posts/MRnnvs3oFUF
Click to expand...
Click to collapse
There was a post by one of the developers stating that it will be coming. Everyone just needs to be patient.
Sent from planet Vegeta.
DON_58 said:
The word around the Cyanogenmod Google+ site is that its coming but that it will take some time given that the drivers need to basically be written from scratch. This is a list of devices that are being droppped from any further releases of CM past CM7. The vision is not included on the list so you could say there is a glimmer of hope but I guess you have to take it with a grain of salt.
https://plus.google.com/117962666888533781522/posts/MRnnvs3oFUF
Click to expand...
Click to collapse
Only mentions of the DesireZ/G2 in that posting is in the comment section, they're probably talking bout semi-newer devices. I still think we have a better chance of getting it 'fully' working under the Andramadus team's effort (still cM9 but probably the best it's going to be for our devices). ie: if drivers are written from scratch, it most likely won't be done by the CM team, but will probably be incorporated into their project when done.
kbeezie said:
Only mentions of the DesireZ/G2 in that posting is in the comment section, they're probably talking bout semi-newer devices. I still think we have a better chance of getting it 'fully' working under the Andramadus team's effort (still cM9 but probably the best it's going to be for our devices). ie: if drivers are written from scratch, it most likely won't be done by the CM team, but will probably be incorporated into their project when done.
Click to expand...
Click to collapse
Thats the point. Its not listed among those which are being discontinued and most of those devices are over 2 years old. Don't get me wrong I'm not trying to take anything away from the Andramadus team. I'll probably end up giving mimicry a run soon. I'm just trying to point out that the door hasnt been officially shut yet on this device as far as an official cm9 build goes.
DON_58 said:
Thats the point. Its not listed among those which are being discontinued and most of those devices are over 2 years old. Don't get me wrong I'm not trying to take anything away from the Andramadus team. I'll probably end up giving mimicry a run soon. I'm just trying to point out that the door hasnt been officially shut yet on this device as far as an official cm9 build goes.
Click to expand...
Click to collapse
Though here's something to think of: There is only one, I repeat one HTC device that is officially supported by Cyanogenmod 9. IF newer HTC devices aren't getting it, I doubt even more that a 2+ year old device would.
kbeezie said:
Though here's something to think of: There is only one, I repeat one HTC device that is officially supported by Cyanogenmod 9. IF newer HTC devices aren't getting it, I doubt even more that a 2+ year old device would.
Click to expand...
Click to collapse
I doubt the One S/One X aren't going to get CM9 Actually, I could complain about CM turning into SamsungMod, but I don't really give a damn. Just look through the supported device list yourselves, folks...

Categories

Resources