[Q] Source - Epic 4G Q&A, Help & Troubleshooting

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.....

Related

2.3.3 sense kernels!

i know most of the devs said in order to have custom kernels for the new sense leak we have to wait for the official release or source to drop. i guess my question is, why not take the current shipped kernel and tweak it a bit and add sbc mod to it for the time being?
is this even possible and if so is anyone like toast/netarch working on this?
at this point i think it was said that the current kernel was very incomplete so devs are waiting for htc to drop the KERNAL source code
fixxxer2008 said:
i know most of the devs said in order to have custom kernels for the new sense leak we have to wait for the official release or source to drop. i guess my question is, why not take the current shipped kernel and tweak it a bit and add sbc mod to it for the time being?
is this even possible and if so is anyone like toast/netarch working on this?
Click to expand...
Click to collapse
Mainly, the 2.2 kernel is based on 2.6.32, while the 2.3 kernel included with the last leak was based on 2.6.35. Two different trees totally. With no source for the newer kernel yet, it's almost impossible to do anything... at least easily.
It's easier to just wait for HTC to drop their source for the .35 kernel they are going to use, then the devs can go to town on it fixing what's broken as usual.
I'm not a kernel expert, so there may be things I left out or assumed.
3 months later and still no source code
jbrawley1 said:
3 months later and still no source code
Click to expand...
Click to collapse
3 months? Its only been a little over a month since the official 2.3 update
We're comin from a pure power source.
HTC has released the source code in a month or less in the past for the Evo.
Unfortunately, I don't expect that to happen this time because several of the bugs with the current 2.3.3 release seem kernel related to me. So my guess is we won't see source until after they release the next update. I just can't see them releasing source for something that is so screwed up, but that is pure speculation on my part.
Yeah, if there is already so much talk of another update, then that would make sense. Plus, according to HTC they have 90-120 days to release the source code.
I thought it was 30 days. I know toast wants kernel source for evo 4g and evo shift. Hopefully HTC realizes its been over a month. I don't think it matters if 2.3.3 has bugs, since it was officially released I think they are required to post kerenel source of what they used for 2.3.3
Maybe we should give a reminder to @HTC on twitter
Sent from my PC36100 using XDA Premium App
deviouskater said:
I don't think it matters if 2.3.3 has bugs, since it was officially released I think they are required to post kerenel source of what they used for 2.3.3
Click to expand...
Click to collapse
I don't think their is any requirement for them to release source until they get it working. For example, I can almost guarantee we will never see source for the 4.22.651.2 update, and as I said before, it wouldn't surprise me if we got another update and never see source for the current 4.24.651.1 update either. I can think of several good reasons why they wouldn't release source with known problems.
Every time I back out of an app and have to wait for sense to reload, or whenever I try to switch to an app that was supposed to be running in the background and it has to reload and start over, it is obvious that this kernel has serious issues. I would bet HTC is working on it now to figure out what those issues are.

[Q] Why dont we have GB Sense Kernels?

So... i know that there aren't any devs working on modifying the kernels from the 2.3 Sense Leak, but this is something I dont really understand.
Netarchy and crew (among many others) had kernels pushed out for the EVO WAAAAYYY before they released any source info. and even when we moved to 2.2, there were kernels ready soon after.
Obviously, the brightness fix is in a ton of working 2.2 kernels. Why cant we pull that out and put it in another kernel? Maybe add SBC and/or some battery tweaks?
I know that devs dont want to have to start over if there is a major difference in the Kernels from beta to release, but what would be the major change? Wouldnt the 2.3 be a good place to start messing around, and then make small adjustments when the full kernel is released? You could easily get a leg up on other devs and incorporate it into the TONS of 2.3 Roms that are out there now.
Im ignorant as hell when it comes to kernels and compiling, but speaking on a tiny modicum of common sense, there should be a way to prod and poke this kernel into submission.
ignore me if in being dumb. I just felt like i had to ask this.
EDIT:
Id like to keep this a conversation between people who want this and people who know. Please dont add your 2cnts in to say the same things we have all heard (we need source, cant do it, no reverse engineering, blah blah)
If you are a dev and can give some REAL PROPER insight, we would love to hear it. even if its to tell us to stuff it LOL.
rawdikrik said:
So... i know that there aren't any devs working on modifying the kernels from the 2.3 Sense Leak, but this is something I dont really understand.
Netarchy and crew (among many others) had kernels pushed out for the EVO WAAAAYYY before they released any source info. and even when we moved to 2.2, there were kernels ready soon after.
Obviously, the brightness fix is in a ton of working 2.2 kernels. Why cant we pull that out and put it in another kernel? Maybe add SBC and/or some battery tweaks?
I know that devs dont want to have to start over if there is a major difference in the Kernels from beta to release, but what would be the major change? Wouldnt the 2.3 be a good place to start messing around, and then make small adjustments when the full kernel is released? You could easily get a leg up on other devs and incorporate it into the TONS of 2.3 Roms that are out there now.
Im ignorant as hell when it comes to kernels and compiling, but speaking on a tiny modicum of common sense, there should be a way to prod and poke this kernel into submission.
ignore me if in being dumb. I just felt like i had to ask this.
Click to expand...
Click to collapse
Unfortunately, there is nothing that can be done until HTC releases source code for the kernel, or until HTC releases a new, working kernel. The kernel that is out now, that causes the brightness issue, is basically an incomplete kernel, from a leaked rom. Something that is fully working, and more stable is needed.
k2buckley said:
Unfortunately, there is nothing that can be done until HTC releases source code for the kernel, or until HTC releases a new, working kernel. The kernel that is out now, that causes the brightness issue, is basically an incomplete kernel, from a leaked rom. Something that is fully working, and more stable is needed.
Click to expand...
Click to collapse
I appreciate you saying that... but it doesnt explain why we had kernels for 2.1 and 2.2 before any source was released. I would like to hear from the devs directly.
Thanks for chiming in though.
From the little and probably wrong information I'm making up, you can't decompile kernels from a Rom, you need source to download from, then apply your mods and then can compile a fixed kernel
Edit: complete speculation, if it is in fact true i will modify post to reflect my all knowing powers
NewZJ said:
From the little and probably wrong information I'm making up, you can't decompile kernels from a Rom, you need source to download from, then apply your mods and then can compile a fixed kernel
Click to expand...
Click to collapse
Thank you... but this is what I am trying to avoid. Id like to remove the misinformation and get a real set of reasons and information. We can all speculate. I want a real answer... and im sure im not the only one.
rawdikrik said:
Thank you... but this is what I am trying to avoid. Id like to remove the misinformation and get a real set of reasons and information. We can all speculate. I want a real answer... and im sure im not the only one.
Click to expand...
Click to collapse
Can't make kernels unless they are 1.) reverse-engineered 2.) or HTC releases the source code for a specific device.
Too time consuming. And by the time, it goes through a psuedo-SDLC, HTC would have probably already released the newest one and devs here already working on a custom kernel.
Hope that answers your question
I believe net said he would work on one as soon as the source is released....I think I read it in his thread
Sent from my PC36100 using XDA App
pinky059 said:
Can't make kernels unless they are 1.) reverse-engineered 2.) or HTC releases the source code for a specific device.
Too time consuming. And by the time, it goes through a psuedo-SDLC, HTC would have probably already released the newest one and devs here already working on a custom kernel.
Hope that answers your question
Click to expand...
Click to collapse
So in other words the reasons that they arent bothering is because they dont want to invest the time when it could become obsolete before it is even released?
mutant13 said:
I believe net said he would work on one as soon as the source is released....I think I read it in his thread
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I dont see that happening any time soon.
Not only that, but i think i remember NET working on one before any source came out for 2.2 and 2.1, especially to fix the FPS cap.
I think that he didnt want to touch it because it is beta and can change between now and an official 2.3 release, like most devs have stated.
rawdikrik said:
I appreciate you saying that... but it doesnt explain why we had kernels for 2.1 and 2.2 before any source was released. I would like to hear from the devs directly.
Thanks for chiming in though.
Click to expand...
Click to collapse
Not a problem. I don't have an answer for you about kernels being released for 2.1 and 2.2 before source was released, other than that you're most likely mistaken about that. Based on what I've been told by devs, and what I've seen devs say (netarchy said he'd work on this kernel as soon as source was released, and that there was nothing that could be done prior to source being released....he said it in his kernel thread), it is nearly impossible to mod/tweak a kernel without the source code. Without source code, it would need to be reverse engineered. By the time that was to happen, a new kernel would already be released most likely.
That's all I got on that issue. So basically, no custom kernels without kernel source.
k2buckley said:
Not a problem. I don't have an answer for you about kernels being released for 2.1 and 2.2 before source was released, other than that you're most likely mistaken about that. Based on what I've been told by devs, and what I've seen devs say (netarchy said he'd work on this kernel as soon as source was released, and that there was nothing that could be done prior to source being released....he said it in his kernel thread), it is nearly impossible to mod/tweak a kernel without the source code. Without source code, it would need to be reverse engineered. By the time that was to happen, a new kernel would already be released most likely.
That's all I got on that issue. So basically, no custom kernels without kernel source.
Click to expand...
Click to collapse
I may very well be COMPLETELY WRONG. LOL. Im not against that. I am right now doing my homework to confirm what ive been thinking.
EDIT: After doing some homework, it looks like Net and Toast were making changes to the stock 2.1 kernel before any source was released. This i remember because the 2.2 Kernels that they first made broke the camera, which wasnt fixed until the source was released. I remember waiting with my hand over f5 til HTC released the source.
They we working hard on using Kernels from other devices and tryign to get the FPS cap removed along with getting the HDMI working.
All i did was go over this ANCIENT thread
http://forum.xda-developers.com/showthread.php?t=719763&highlight=source
rawdikrik said:
I may very well be COMPLETELY WRONG. LOL. Im not against that. I am right now doing my homework to confirm what ive been thinking.
EDIT: After doing some homework, it looks like Net and Toast were making changes to the stock 2.1 kernel before any source was released. This i remember because the 2.2 Kernels that they first made broke the camera, which wasnt fixed until the source was released. I remember waiting with my hand over f5 til HTC released the source.
They we working hard on using Kernels from other devices and tryign to get the FPS cap removed along with getting the HDMI working.
All i did was go over this ANCIENT thread
http://forum.xda-developers.com/showthread.php?t=719763&highlight=source
Click to expand...
Click to collapse
Well, maybe there are certain things that can be worked on without source, but I believe for this type of problem (brightness issue), source is needed. Probably similar to how you said that the 2.2 kerneles broke the camera at first, and couldn't be fixed until source was released. This is the same type of deal. Hopefully Sprint will release an OTA within 30-60 days. I wouldn't get my hopes up for anything before that, unfortunately.
k2buckley said:
Well, maybe there are certain things that can be worked on without source, but I believe for this type of problem (brightness issue), source is needed. Probably similar to how you said that the 2.2 kerneles broke the camera at first, and couldn't be fixed until source was released. This is the same type of deal. Hopefully Sprint will release an OTA within 30-60 days. I wouldn't get my hopes up for anything before that, unfortunately.
Click to expand...
Click to collapse
The word around the grapevine is that sprint isn't releasing the OTA until after the release of the evo 3d (marketing scheme, you know how it is).
AbsolutZeroGI said:
The word around the grapevine is that sprint isn't releasing the OTA until after the release of the evo 3d (marketing scheme, you know how it is).
Click to expand...
Click to collapse
I heard that too. That wont be til June/July and then they have another 60days of waiting time they usually take to release source.
and that is IF They do the upgrade, since usually they only want a single upgrade in the life cycle of a product. They will most likely REALLY think about it, to not risk stealing sales from the newer phones coming out over the summer.
AbsolutZeroGI said:
The word around the grapevine is that sprint isn't releasing the OTA until after the release of the evo 3d (marketing scheme, you know how it is).
Click to expand...
Click to collapse
Correct. I predict the 3D to drop within 30-60 days from now though. Then shortly after that, the OTA will probably roll out. As rawdikrik said, source will probably come a month or two after the OTA. The good thing though, is that if/when an OTA is released, it will have a working kernel in it. So even without source being released, a working kernel will be in circulation at that point, which will most likely resolve the brightness issue.
Evo 3D is supposedly hitting June so I'm going to say July just to give it some breathing room. If OTA hits around August maybe September, then its another 30-45 days to release source. So were talking around September-October ish for complete source. This is all speculation but sprint/HTC operate that way. My guess is september for a fully working kernel for GB based on the source code. Stupid marketing scheme to get us to buy the evo 3D.
Sent from my PC36100 using XDA Premium App
I'm so going to buy the EVO 3d
not sure how i feel about the 3d gimmick...
Can we keep this on topic though? THanks guys... Im just waiting to hear something from the big dogs.
Keep in mind it's entirely possible that we will see another leaked kernal long before the OTA is out, this one fully functional. This is especially true if(as many of you seem to suspect) this "leak" was actually no leak at all but an intentional way to let the Chefs and Power Users test their new ROM for them and get feedback on it.
Not sure if you (the Op) have ever tried programming... But (in perspective of the difficulty), basically this would be like me writing a "Hello World" app in Java or C++, and it having an extra space in between the words that bothered you. You would have to cipher through hundreds of lines of code in a hexidecimal editor trying to find the "call" to the display API, and then find which variable or constant it was using for the text output, and change it.
Then you would have to re-compile, and hope it worked without breaking anything else already in place. If you broke something, it's INCREDIBLY hard to debug without real source code.

Ice Cream INCOMING!

http://groups.google.com/group/android-building/browse_thread/thread/4f85d9242667a85f?pli=1
Now let's hope for the best and support our devs!
so its better to unlock bootloader phone for CM9 that coming?
Anyone know how long it takes for someone like cyanogenmod to implement it or how long it will take someone to make a port to the play?
TDMaster said:
so its better to unlock bootloader phone for CM9 that coming?
Click to expand...
Click to collapse
CyanogenMod based on ICS will presumably be CM8. And it wouldn't hurt to unlock your bootloader now for CM7. Many report it works just fine on the GSM side of things.
ff7fan4eva said:
Anyone know how long it takes for someone like cyanogenmod to implement it or how long it will take someone to make a port to the play?
Click to expand...
Click to collapse
It will take a while. Don't hold your breath for the Cyanogen team to get this in soon. There is a lot of work that goes into making a Cyanogen port from the source of the AOSP. It has to be merged, approved, tweaked, approved, tested, approved, and then you might see some fruits of the labor.
As far as a raw AOSP build, you might be holding your breath there too, on account of the fact that no one yet has build a Gingerbread AOSP build to the play.
I am SO stoked right now. Skyrim, and ICS source..It's been a good few days
Mills00013 said:
CyanogenMod based on ICS will presumably be CM8. And it wouldn't hurt to unlock your bootloader now for CM7. Many report it works just fine on the GSM side of things.
It will take a while. Don't hold your breath for the Cyanogen team to get this in soon. There is a lot of work that goes into making a Cyanogen port from the source of the AOSP. It has to be merged, approved, tweaked, approved, tested, approved, and then you might see some fruits of the labor.
As far as a raw AOSP build, you might be holding your breath there too, on account of the fact that no one yet has build a Gingerbread AOSP build to the play.
Click to expand...
Click to collapse
CM7 - Gingerbread, G = 7th letter.. Cm8 would be honeycomb but it's closed source so presumably it will be cm9. Could be wrong tho
Sent from my R800i using XDA App
Cyanogenmod 9 has already been confirmed to be ICS.
Cyanogenmod 8 will be Honeycomb if the sources ever get released.
Naaah CyanogenMod8 is reserved for honeycomb but it will never be release. Why should they? ICS Source come out soon and they will include a teblet version to wich looks a lot like honeycomb. So there is no reson for anybody to work on honycomb.
Sent from my R800i using XDA App
Ignore this
I am trying to got ics working.
But actually i haven't luck
nickholtus said:
I am trying to got ics working.
But actually i haven't luck
Click to expand...
Click to collapse
Do you still try it with the sddk or are you working with the source code? Bocouse woring with the sdk does not have much sense when the sourcecode is alredy out.
I will build ics with the source code.
but i am in a learning phase
Best wishes. It's great to see new people daring to step up and learn for the benefit of the community.

[Q] custom EVO ICS ROM speculation?

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

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