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

Root [ROM] MTDEV-CM9 build 20130120 [BETA]

from the builds I have tried, it hasn't worked since the camera started working. not sure why, the graph works, but it doesn't show the app battery usage data.

I noticed this as well, but thought it was because I didn't wipe my battery in CWM (which I've never done, either...)
 
I noticed this as well, but thought it was because I didn't wipe my battery in CWM (which I've never done, either...)

I just looked at the Power profile and it's the base one. What it does is tell the system how much juice the parts use. With the base values it just doesn't crash the calling items. That will be an easy fix. Maybe I can call on the power of the community to see if they can help me refine it. I'll post back to tell y'all what I would need to see.

New tester coming up. This will be the same as the last, but with the udated powerprofile.xml.

Just flash fresh. I did the extract method and lost my Google account, so I flashed gapps again and have had crashes ever since.
 
Major problem on my end.
I don't know if its the build.prop messing up, or what's going on.
But basically, when I first install the ROM (I've reinstalled tons of times), I can download all apps to my hearts desire.
After a while, more and more apps say they're not compatible but I know that's a lie. Because I've tried downloading Pandora, Gmail (wasn't included in the GApps), and some other major ones that would always be compatible.

I will note, that I have changed my screen density with an app called LCD Density because I don't know how to manually change it. And after I use that app it seems to be what causes it, but after I revert back to the old DPI (a stomach churning 240) it still says not compatible.

So it's either a bug, or I need to stop using this app. And if I need to stop using this app, can someone here kindly teach me how to modify the screen density on my own so that this doesn't keep happening and I won't have to reinstall the latest tester build 4 times each night? (oh, it also happens on the stable release too)

Thank you all.
Also my last post was about last November, hadn't logged in since. Thanks to all these amazing MTDev's for this wonderful ICS ROM! You guys are the best!
 
Major problem on my end.
I don't know if its the build.prop messing up, or what's going on.
But basically, when I first install the ROM (I've reinstalled tons of times), I can download all apps to my hearts desire.
After a while, more and more apps say they're not compatible but I know that's a lie. Because I've tried downloading Pandora, Gmail (wasn't included in the GApps), and some other major ones that would always be compatible.

I will note, that I have changed my screen density with an app called LCD Density because I don't know how to manually change it. And after I use that app it seems to be what causes it, but after I revert back to the old DPI (a stomach churning 240) it still says not compatible.

So it's either a bug, or I need to stop using this app. And if I need to stop using this app, can someone here kindly teach me how to modify the screen density on my own so that this doesn't keep happening and I won't have to reinstall the latest tester build 4 times each night? (oh, it also happens on the stable release too)

Thank you all.
Also my last post was about last November, hadn't logged in since. Thanks to all these amazing MTDev's for this wonderful ICS ROM! You guys are the best!

Okay guys forget this, I reverted back to 240, wiped dalvik and cache and everything worked. Used ROM Toolbox to modify it myself using a Youtube video.
Looked up the LCD Density app and turns out the dev was just uber lazy and didn't want to fix the app after many complaints of devices getting bricked and stuff.

Sorry for the bother, G60!
 
haven't been on here for quite a while I noticed in the rom browser there are some new testers just wondering what's all new now? Have a mexican in a sombrero for your time :smokingsomb::smokingsomb::smokingsomb:
 
haven't been on here for quite a while I noticed in the rom browser there are some new testers just wondering what's all new now? Have a mexican in a sombrero for your time :smokingsomb::smokingsomb::smokingsomb:
I am also wondering what's new? Specifically, what's changed from the 20130320 tester (which is what I'm currently running) and the most recent 20130415 build?
 
I am also wondering what's new? Specifically, what's changed from the 20130320 tester (which is what I'm currently running) and the most recent 20130415 build?

4/15 is essentially the same as the 3/20 build, changed to the ICS release branch of Cyanogen. Hopefully, it is more stable code. Not much feedback yet, which hopefully means it's running well for everyone :)

I forgot to mention why I made this tester.

What I did was changed to the ics-release branch of the Cyanogen code.

From then to now it has been me chasing my tail.
Basically it was just me trying to move to what I hope is more stable code. I don't know how many people remember how irritating it was when CM7 was starting out and CyanogenMod would update and kill our build. I'm not even sure if I ended up changing any of the code by switching branches. I do have one section I need to checkout because it killed the build. It's next on my list.

Anyway, this build should be the same as the last. I just can't test the cell radio parts on my DEV phone.

The difference between the 4/14 and 4/15 build is just the battery stats; in the 4/14, we noticed that the graph would show, but it wouldn't list what was using power and how much. Should be fixed in the 4/15.
 
So what features are/aren't working on this ROM right now? I do consider back camera, WiFi, and GPS/Maps essentials. I'm having enough stability issues on the version of CM7 I'm currently using that a rebuild may be a good idea anyway, so if this one has the features I need working, I'm very likely to give it a try. :D
 
So what features are/aren't working on this ROM right now? I do consider back camera, WiFi, and GPS/Maps essentials. I'm having enough stability issues on the version of CM7 I'm currently using that a rebuild may be a good idea anyway, so if this one has the features I need working, I'm very likely to give it a try. :D
The 3-20 build that I was using had back camera but no FFC.It also couldn't do video calling.The GPS would lock on thru the tower or Wi-Fi on maps but took forever to get thru navigation.I took a 12 hr trip to Michigan for Shuto Con and once I had the GPS locked in at my house thru Google Navigation it worked flawlessly.But when I exited out of navigation it was HELL getting GPS back so I had to use maps to get the directions without the turn by turn assist.Wi-fi was also working on it as for tethering Wi-Fi I didn't check.I had no issues with it at all just dumped it cause BSydz got video to work on Skype with his PA CM9.
 
4/15 is essentially the same as the 3/20 build, changed to the ICS release branch of Cyanogen. Hopefully, it is more stable code. Not much feedback yet, which hopefully means it's running well for everyone :)


The difference between the 4/14 and 4/15 build is just the battery stats; in the 4/14, we noticed that the graph would show, but it wouldn't list what was using power and how much. Should be fixed in the 4/15.

She got it right. I have been busy with the birth of my son (yeah buddy). Some of the issues with using an unsupported phone on a ROM build is they make changes that break things on our phone. This was a rear problem with the CM7 ROMs at first, until CM9 took off. Then they released the "release" branch of CM7 and things went much smoother. That's why I did it for CM9. It should stop the stupid things that happed when I sync with CyanogenMod and cant build or boot.

After I figure out what BSydz did I'll probably make a new release. Like tamasaurus said, since no one said anything, I presume that all is the same. Or that everyone went to BSydz' PA ICS.:D
 
I think I have found some issues in the camera app. One is I can't change the resolution or most of the settings. Another is after I played with the camera app I went to actionsnap and it wouldn't work at all. Just hung there. I'm going to try flashing one of the other older ROMs and see if it persists.

Holla if you see the same.
 
I've tried using this ROM, which is actually really great. However, it doesn't get any kind of signal. Not 3G, not 1X, not even a non data signal. Whenever I try to enter into the "Mobile Networks" section of the settings the settings force closes. I really like this build but it just won't get a signal. I know it's not my phone b/c I've used an older version of CM9 (non-MTDEV) and I get decent signal. Even MTDEV's CM7 gets signal. I've tried toggling airplane mode but that doesn't work either. Any help would be appreciated, thanks.
 
I've tried using this ROM, which is actually really great. However, it doesn't get any kind of signal. Not 3G, not 1X, not even a non data signal. Whenever I try to enter into the "Mobile Networks" section of the settings the settings force closes. I really like this build but it just won't get a signal. I know it's not my phone b/c I've used an older version of CM9 (non-MTDEV) and I get decent signal. Even MTDEV's CM7 gets signal. I've tried toggling airplane mode but that doesn't work either. Any help would be appreciated, thanks.

Kind of weird. Did you check the checksum? I'm running this on my DEV phone which doesn't have service. On that I am able to get into settings. And I'm presuming that you are using the one I posted in April around the 15th.
 
Kind of weird. Did you check the checksum? I'm running this on my DEV phone which doesn't have service. On that I am able to get into settings. And I'm presuming that you are using the one I posted in April around the 15th.

How do I check the checksum? I'm not too bright when it comes to this stuff. And do you mean that I'm using the one you posted around April 15th? I assume you mean the version/build. The build date on mine says "Mon Feb 18 19:54:26 EST 2013"
 
How do I check the checksum? I'm not too bright when it comes to this stuff. And do you mean that I'm using the one you posted around April 15th? I assume you mean the version/build. The build date on mine says "Mon Feb 18 19:54:26 EST 2013"

The way I do it is to long press the file name in ES File Explorer, go to properties and then checksum and compare it with what is posted with download link.

My suggestion would be to do a full wipe, and reinstall.
 
The way I do it is to long press the file name in ES File Explorer, go to properties and then checksum and compare it with what is posted with download link.

My suggestion would be to do a full wipe, and reinstall.

Start with the 20130415 build in the Testers folder. And not to reload any other apps until you verify it works. After that do it slowly.

And on the release of non tester ROMs, I don't have a schedule. Or much time for that matter. My last repo sync killed my ability to build and I'm working on what went wrong.

I think that after I get it going I will do like g60 did with the CM7 ROM and just upload a working set and not rely on CyanogenMod.
 
There will be a new site on it's way. When I get it set up it will be updated on my signature and on the OP of this thread. Other links for CM7 and the like may get updated. I'll work with the OPs and try to get them to update the sites as necessary.
 
There will be a new sire on it's way. When I get it set up it will be updated on my signature and on the OP of this thread. Other links for CM7 and the like may get updated. I'll work with the OPs and try to get them to update the sites as necessary.

If I may as, what's the point of updating CM7 and not adding full attention to CM9/CM10?
 
Back
Top Bottom