• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [BETA]Cyanogen!! Landed!!! :) Go get it![Updated 7/12/2011]

well you have to remember...that since the DX is now part of the normal CM update tree it automatically gets update by the bots even if there are no specific fixes for the DX....cvps is not the only guy making updates so its likely that very often the updates will not have much to do with the DX
Totally understand, it just strikes me weird that there are known issues that have been not addressed so far and it makes it hard to stay with a ROM with those types of issues.
...And, if it is actually a Generic type of situation, why do they list it as CDMA_Shadow? Why not CDMA_General to make it seem less DroidX specific?
Mostly observation, you understand, not trying to make waves or piss anyone off that works on this stuff.
 
Ive been wondering why the updates havent included at least the camera fix. Not that its a big deal to paste in a couple files but if this is the fix, why not include it in a nightly and be done with it? And what is the deal with the percentage battery usage? All ive seen today is x0%.
 
Ive been wondering why the updates havent included at least the camera fix. Not that its a big deal to paste in a couple files but if this is the fix, why not include it in a nightly and be done with it? And what is the deal with the percentage battery usage? All ive seen today is x0%.

Cyanogen is complied from AOSP. The camera fixes are proprietary Motorola drivers that are 'officially' unsupported by Cyanogen. That is why they can not use them; but we can flash them. The camera drivers need complied from source to be included into Cyanogen.

I hope I explained that well. :-/
 
I know our camera fix will never make it in CM7 as this is a Motorola file that is being used from Gingerbread. In order for it to make it in to the CM7 build is that it will have to be built from scratch.

Also from my understanding the way the nightly's work is your have the tree of base CM7 that is used and then there are X specifics that are added in to that. The only thing we will see in the change log are the base CM7 changes, anything that is X specific will not show. If you remember it was build 7 that had the GPS fix in it, however in the change log nothing shows.

I may be off base on this, but this is what I have seen and read from others.
 
Cyanogen is complied from AOSP. The camera fixes are proprietary Motorola drivers that are 'officially' unsupported by Cyanogen. That is why they can not use them; but we can flash them. The camera drivers need complied from source to be included into Cyanogen.

I hope I explained that well. :-/
See, now that makes sense finally. If that is the case, then a good market app, or the patch makes the issue a non-issue.
Not explaining why something doesn't work, or has been skipped over does NOT make sense. Just my $0.02, of course...
 
forewarning: This post explains why I'm getting rid of CM7 because everyone is entitled to his or her opinion. If you don't like these posts please scroll onward. :p

I've been on CM7 when it first launched for the DX a while ago. Been on it since. I was putting up with the subpar battery life. And the camcorder not working didn't bother me until I was driving through a wildfire area and wanted to capture it. But I kept with it because I hardly use it. Then tonight is when the camel's back broke. I was driving to my parents house about an hour and a half away. I charged my phone this morning and was working all day so didn't really have time to play with it much. I'm trying to find people to hang out with and my phone dies. And the car charger will not let it work. It will boot up then it would reboot. repeat. I just can't handle the subpar battery life when on .596 I could go almost 2 days without a charge. /coolstory.
 
forewarning: This post explains why I'm getting rid of CM7 because everyone is entitled to his or her opinion. If you don't like these posts please scroll onward. :p

I've been on CM7 when it first launched for the DX a while ago. Been on it since. I was putting up with the subpar battery life. And the camcorder not working didn't bother me until I was driving through a wildfire area and wanted to capture it. But I kept with it because I hardly use it. Then tonight is when the camel's back broke. I was driving to my parents house about an hour and a half away. I charged my phone this morning and was working all day so didn't really have time to play with it much. I'm trying to find people to hang out with and my phone dies. And the car charger will not let it work. It will boot up then it would reboot. repeat. I just can't handle the subpar battery life when on .596 I could go almost 2 days without a charge. /coolstory.

The battery life is my biggest issue as well. I've been trying to isolate the issue but nothing stands out in the log... :confused:
 
the battery is actually what just drove me back. I loved CM7 and the customization it provided, as well as the AOSP of it all. But I did absolutely nothing with my phone today, unplugged it, set next to my bed. Checked Twitter twice, sent one text message, no calls, no web, nothing, and after 4 hours it had dropped to 60%. I've been on CM7 since the very first day, and the battery has always bothered me. So tonight I said to hell with it. I actually am starting completely fresh. Reformatted my SD, and SBF'ed back to FroYo lol. When CM7 gets to an RC version, I'll get back on it, but until then, I'll probably go to Apex, or even back to ZombieStomped.
 
Totally understand, it just strikes me weird that there are known issues that have been not addressed so far and it makes it hard to stay with a ROM with those types of issues.
...And, if it is actually a Generic type of situation, why do they list it as CDMA_Shadow? Why not CDMA_General to make it seem less DroidX specific?
Mostly observation, you understand, not trying to make waves or piss anyone off that works on this stuff.

You're not entirely understanding how these builds get compiled.

So, they have this source tree, right? There are all kinds of modular parts to CM7, or any ROM. But because CM7 is built for lots of phones, not every phone uses every part, and some parts are specific to certain phones - for instance, all of the CM7 phones use the ADW launcher APK. And the settings file. And.. well, you get it. But only the DX uses the DX drivers. It has a special build.prop. And the DX doesn't use files that might relate to, say, a front facing camera.

Rather than recompiling everything in tidy little packages for each phone, you use a system wherein each phone has their parts selected and those parts are compiled into each phone's build automatically. That includes the changelog.

The consequence of this, is all of these builds really have nothing to do with the Droid X, even though the changelog marks stuff. They're part of the whole CM7 source tree, so other developers are fixing stuff for other phones, they just happen to be files the DX uses too. Actually, some of the stuff does relate to the DX, but you're looking at it as "why are you fixing minor crap when major crap exists?" whereas the developer is saying, "droid X what? I don't know squat about that, this fix was something I noticed on my Nexus One."

Make sense? The devs for CM are working on all kinds of phones, and some of the CM7 builds are super stable and full featured. So when you see changes, it's only because there were changes to files the DX happens to use in its own branch of the source tree, and they may or may not have a visible or important effect.
 
Hmmm while my battery life has not been great i recently sbf and started all over not with the moster zip but the actual file, and have yet to theme it and are noticing a big advance in battery life compared to what it was.
 
You're not entirely understanding how these builds get compiled.

So, they have this source tree, right? There are all kinds of modular parts to CM7, or any ROM. But because CM7 is built for lots of phones, not every phone uses every part, and some parts are specific to certain phones - for instance, all of the CM7 phones use the ADW launcher APK. And the settings file. And.. well, you get it. But only the DX uses the DX drivers. It has a special build.prop. And the DX doesn't use files that might relate to, say, a front facing camera.

Rather than recompiling everything in tidy little packages for each phone, you use a system wherein each phone has their parts selected and those parts are compiled into each phone's build automatically. That includes the changelog.

The consequence of this, is all of these builds really have nothing to do with the Droid X, even though the changelog marks stuff. They're part of the whole CM7 source tree, so other developers are fixing stuff for other phones, they just happen to be files the DX uses too. Actually, some of the stuff does relate to the DX, but you're looking at it as "why are you fixing minor crap when major crap exists?" whereas the developer is saying, "droid X what? I don't know squat about that, this fix was something I noticed on my Nexus One."

Make sense? The devs for CM are working on all kinds of phones, and some of the CM7 builds are super stable and full featured. So when you see changes, it's only because there were changes to files the DX happens to use in its own branch of the source tree, and they may or may not have a visible or important effect.

Where are the CM7 developers for the Dx? Isn't anyone working on our phone?
 
Where are the CM7 developers for the Dx? Isn't anyone working on our phone?

As glorious and star-studded as it sounds developing software for one model of phone, for free, with minimal recognition, I suspect devs aren't lining up out the door to have a crack at it. I believe cvpcs is the only dev dedicated to the X right now.

You're asking people to work for free. Be patient. Or use one of the ROMs that are already complete based on Moto's framework.
 
13 hrs so far with pretty heavy netflix and a bit of tethering through the day, not the best battery ever but sufficient for me at least. I dont really expect the phone to last much more than this. Thats why i have a car charger.
 
I use root call blocker too. That must be it! Damn, I love that app too. Hope the issue can get sorted. Have you contacted the dev of that app!

There's an update for root call blocker today. Maybe it'll fix the data lose problem we've had.

Update: No the update did not fix the data lose issue with this app. reboot = no data connection
 
Hmmm while my battery life has not been great i recently sbf and started all over not with the moster zip but the actual file, and have yet to theme it and are noticing a big advance in battery life compared to what it was.

This. I went this method as opposed to the all in one p3droid method and battery life seems to be better. I updated to the nightly 0.9 and it's been working good.
 
I use root call blocker too. That must be it! Damn, I love that app too. Hope the issue can get sorted. Have you contacted the dev of that app!

There's an update for root call blocker today. Maybe it'll fix the data lose problem we've had.

Update: No the update did not fix the data lose issue with this app. reboot = no data connection

That sucks.

Have you emailed the dev by chance?
 
Yeah my first day and battery life sucks so far. Will give it a few days but if it does not clear up, will be going back to Liberty until this thing is more stable.

One thing that annoys me is that when you turn the phone off to charge it, the phone just turns back on to charge. Annoying as hell. Why is this not fixed?

Lack of camcorder is lame. I need an app that will work for now so if anyone has any ideas, let me know.

Thanks.
 
Yeah my first day and battery life sucks so far. Will give it a few days but if it does not clear up, will be going back to Liberty until this thing is more stable.

One thing that annoys me is that when you turn the phone off to charge it, the phone just turns back on to charge. Annoying as hell. Why is this not fixed?

Lack of camcorder is lame. I need an app that will work for now so if anyone has any ideas, let me know.

Thanks.

Definitely give it a few days for the phone/battery to settle down and you should get a lot better battery life.
 
You're not entirely understanding how these builds get compiled.

So, they have this source tree, right? There are all kinds of modular parts to CM7, or any ROM. But because CM7 is built for lots of phones, not every phone uses every part, and some parts are specific to certain phones - for instance, all of the CM7 phones use the ADW launcher APK. And the settings file. And.. well, you get it. But only the DX uses the DX drivers. It has a special build.prop. And the DX doesn't use files that might relate to, say, a front facing camera.

Rather than recompiling everything in tidy little packages for each phone, you use a system wherein each phone has their parts selected and those parts are compiled into each phone's build automatically. That includes the changelog.

The consequence of this, is all of these builds really have nothing to do with the Droid X, even though the changelog marks stuff. They're part of the whole CM7 source tree, so other developers are fixing stuff for other phones, they just happen to be files the DX uses too. Actually, some of the stuff does relate to the DX, but you're looking at it as "why are you fixing minor crap when major crap exists?" whereas the developer is saying, "droid X what? I don't know squat about that, this fix was something I noticed on my Nexus One."

Make sense? The devs for CM are working on all kinds of phones, and some of the CM7 builds are super stable and full featured. So when you see changes, it's only because there were changes to files the DX happens to use in its own branch of the source tree, and they may or may not have a visible or important effect.

perfectly explained IMO

Where are the CM7 developers for the Dx? Isn't anyone working on our phone?

they are out there...you've got to give them time...remember the DX is still completely new to the world of CM...

Yeah my first day and battery life sucks so far. Will give it a few days but if it does not clear up, will be going back to Liberty until this thing is more stable.
there is nothing unstable about CM7 on the X...there are things that don't work...but the software itself is quite stable...


One thing that annoys me is that when you turn the phone off to charge it, the phone just turns back on to charge. Annoying as hell. Why is this not fixed?
its a Motorola feature...built in by the OEMS....its not really something to "fix" its a feature that cvps will have to try and add if he chooses to do so...

Lack of camcorder is lame. I need an app that will work for now so if anyone has any ideas, let me know.
that should have been something you were completely aware of...if its really a necessity then you probably shouldn't have flashed CM...

Any idea on how to prevent the phone from booting up when trying to charge it?
impossible as of right now
 
ppl will always cry over the lil stuff that dont work and faill to appreciate and show it for all the stuff that does work. I see this daily maintaining CM-Ascend. The community is lucky to have what we have. And for the few I seen complaining about CM74DX not being on the lastest RC1 or 7.1 for that matter, CM4DX is 7.1 as 7.1 is 2.3.4 and 7.0 is 2.3.3. For cvpcs to jump to RC1 he needs to get what he is working with fully functionally, ifs thats even possible w/ the locked bootloader and lack of hardware src code. RC1 changes things up a bit and can be almost like starting over.
 
ppl will always cry over the lil stuff that dont work and faill to appreciate and show it for all the stuff that does work. I see this daily maintaining CM-Ascend. The community is lucky to have what we have. And for the few I seen complaining about CM74DX not being on the lastest RC1 or 7.1 for that matter, CM4DX is 7.1 as 7.1 is 2.3.4 and 7.0 is 2.3.3. For cvpcs to jump to RC1 he needs to get what he is working with fully functionally, ifs thats even possible w/ the locked bootloader and lack of hardware src code. RC1 changes things up a bit and can be almost like starting over.

Right. The only thing we are behind on is the kernel.

I think it is funny, in an annoying way, that people get all uppity about 1% battery increments like it's the only thing missing.

While I wish/hope the real bugs get fixed soon, cvpcs has done a stellar job so far, so a little break from his hobby of helping us is well deserved.
 
Back
Top Bottom