Root [ROM] MTDEV-CM7 build 2013-03-03

[g60madman]

So, I'm getting the Triumph in 2 days. Upgrading from OV, what are the actual issues with this rom as of right now? I've seen things were changed in yesterdays update.

-Is there still the flicker in watching videos in portait?
-Is there still a clicking noise while recording video?
-I can careless about the deep sleep issue, because I have that problem on the rom I'm using now.
-HDMI does not bother me.

Please update me on the most recent build please. Thank you!

Yes those are all the same issues as of right now.

 

[jameyhowell73]

If I dl YouTube from market it does not open, just gives me error fc. If I visit yt in opera it will not play vids. Also the market seems outdated as music does not show up. I love CM7 and so far this is the only problem I have. I downloaded mxplayer but maybe I'm not using it right??

 

[dsmryder]

If I dl YouTube from market it does not open, just gives me error fc. If I visit yt in opera it will not play vids. Also the market seems outdated as music does not show up. I love CM7 and so far this is the only problem I have. I downloaded mxplayer but maybe I'm not using it right??

sounds like a bad flash. Double check the checksum of what you downloaded, then reflash after wiping.

 

[thangfish]

Chairshot, this 10-15 build seems really good so far!

---

I have been having a kind of weird BT failure involving the voice dialer for a long time.
I had thought it may have been my hands free BT device in my truck going flaky (and it still might be) but it has changed a little on this particular build so now I'm not so sure.

I don't remember this happening on the TG builds... Maybe it started with Whyzors but I just can't remember.

Voice dialer works fine the first time after connect, but if it gets the number wrong and I kill it by hitting the CALL button on the BT device or the hang up button on the dialer screen, it won't ever work again until I reconnect BT.

It never says "speak now" through the BT speaker (it does say it on screen) and just sits there waiting for voice input until it times out... It goes deaf and mute. Also no audio is transmitted if a call comes in while in this condition.

I think it works fine if the call is completed and ends normally.

On this build, after the above action, voice dialer will come up and I hear it say "speak now" but instantly errors and aborts. Will work normally after a disconnect/connect.

So, in summary, it's still sorta broke, but acts differently, like it's half fixed.

Like I said, this has been going on for quite a while, so it would be hard to say when or why it started.

I don't know of this info is helpful at all, but thought it significant enough to mention.

I'm going to test further. I've never tried voice dialer with my BT stereo head set... Think I'll try that.

 

[Chairshot215]

There are a few other things I am looking at that may help. It looks like Whyzors fix for allowing BT and Wifi to work together without locking the cpu at max was commenting out all the permissions for bluetooth in the init.rc. In the last build I added in a few new BT permissions but had not uncommented the older permissions. Have been looking to see if A, there is another way of going about it. Looking allot at the update script which is kind of unfamiliar territory but wondering if something is off there. Also I'm going to start one at a time putting back each permission commented out by Whyzor because it looks like commenting them all out may have been unnecessary. Just a little time consuming as it will take more then a few test builds to figure out what permissions are causing the issue.I don't know for sure but Whyzor may have done them all to save allot of time because it appears at least 2 so far can stay.

 

[thangfish]

A couple more details that may help with your journey through permission land.

Verified that voice dialer continues to operate after multiple calls, as long as they are terminated normally by either side.

subsequent calls connect, but BT is off. A quick touch of the BT button on the call screen immediately works, to direct the audio through the BT device.

 

[jameyhowell73]

sounds like a bad flash. Double check the checksum of what you downloaded, then reflash after wiping.

BIG newbie question here... so that means re-setting up all of what I've done in the last couple weeks on homescreen, downloading apps again, etc.... that right? If so, any other way to get this fixed? Just curious. Thanks!

Also, what am I looking for to double check the "checksum" ? Super newb here, sorry about that.

 

[jamesd1085]

Im having major issues with wifi after adding my build.prop tweaks and swapping droidsansfallback font...will show connected to my wifi but in reality it has no connection...would it help with troubleshooting if i posted all my changes...i have used the same ones on all the different roms i frequent

 

[thangfish]

Im having major issues with wifi after adding my build.prop tweaks and swapping droidsansfallback font...will show connected to my wifi but in reality it has no connection...would it help with troubleshooting if i posted all my changes...i have used the same ones on all the different roms i frequent

I haven't had that wifi issue with the 10.15 build.. Thought it was fixed.

Check your build.prop for:
video.accelerate.hw

If you see that line, try removing it, or commenting it out and see if that helps.

 

[jamesd1085]

It is there but was there from the start...i added quite a few lines to my build.prop but i have used the same ones on every rom i have ever used...i have also used all of them in past versions of mtdev cm7 without issue

 

[activeservo]

I just want to report a but I am having. I am running the 9/26 release with the CM9 theme. I'm not sure if it is the cm9 theme or the rom but when I try to log into the amazon app store or stumble upon it always says the username/password is incorrect. It's like the keyboard it typing a wrong entry. It is great for texting though. This rom is great and fast!

 

[jamesd1085]

I dont know if it is still an ongoing issue but i know in many of the older cm7 versions the keyboard had a habit of putting a space after you finish typing and press enter which may or may not register as incorrect entry

 

[thangfish]

It is there but was there from the start...i added quite a few lines to my build.prop but i have used the same ones on every rom i have ever used...i have also used all of them in past versions of mtdev cm7 without issue

I wasn't blaming you for adding it.
Just put a # in front of that line and reboot and see if that fixes it.

 

[jamesd1085]

I know what you meant...but the line was there through quite a few reboots and wifi didnt stop working until i added my extras...i just dont know which one or ones broke wifi...i removed them all wiped caches and rebooted still no wifi...i went back to sharp for now...might reflash a fresh copy and add lines one at a time to se what breaks it...or who knows could be a fluke

 

[b_randon14]

I have had a couple build.prop entries mess things up such as the jni checks, verify bytecodr, some of the II tweaks, etc. So I keep build.prop tweaks very minimal!

 

[nyioo7]

So, I've been playing around with CM7 latest release today. It is more solid feel than previous releases. So much smoother and scrolling feels like stock ROM.

Here are some bugs I found:
-Gallery causes reboot on certain files, especially *.png format, when I tried to zoom in and move around.
-Screen Locker doesn't change right away unless reboot the system.
-Auto brightness seems very low on default.
-Volume is a bit lower than stock but doesn't cause it to go lower after notification sound. This is only noticeable when I hook up the phone to the car stereo.
-Video recording doesn't record the voice when earphone is plugged in. For some reason, I don't have the clicking noise. I've tested in many position to cause auto focus.
EDIT: Just encountered a weird bug. Whenever I press the browser address bar, when the keyboard comes out, browser disappear. If I press "back", the browser comes back but the screen gets locked.

Other than that, it is the best release so far and I'm sure the next one will be better. Oh. I've tested wifi with both visible and invisible access points. Both works well and stable connection for me.

I have some suggestion I thought might be a bit useful or maybe silly.
-Video flicker in portrait mode. So, why not lock the video playback to landscape mode only like stock 2.2 ROM. That will save you guys a lot of time.
-Since this is not the final version yet, you should add formatting system/data/cache partitions in updater-script to make it fresh install. Fresh install seems to eliminate some bugs and ROM is very stable.
-If that can't be done, this is just a fun idea. Why not reroute the IP of Update option in Settings to MTDEV file upload server and release updates from there to auto download the update.zip? That would keep us updated and MTDEV will rule over Motorola.

Anyways, I'll keep messing with the ROM to see if I can find anymore bugs or improvements.

 

[piper_]

yes, this is a damn good rom

good job

 

[thangfish]

EDIT: Just encountered a weird bug. Whenever I press the browser address bar, when the keyboard comes out, browser disappear. If I press "back", the browser comes back but the screen gets locked.

Are you using any particular Theme Chooser theme?

 

[sikk66]

The 10/15 build seems to be running great for me. I had reported the weird issues with Groove IP in the test build that Charishot had put up before this build was released. I think it may have just been a bad flash or something causing this, since I saw him mention that this was pretty much the same as his test build.
This one is running smooth and no problems.
Thanks again Chairshot and the rest of the MTDEV team. You guys are doing an amazing job!

 

[tridge]

2 issues:

1. Pressing the dial button from recent calls or contacts has a lag of 3-6 seconds before the 'dialing' screen pops up. I had this issue with the last update and this update. I have done a full wipe / factory reset between updates.

2. Wi-Fi keeps re-enabling itself every 10-20 minutes! I've turned it off via power widget and settings... No luck, tried a cache wipe also.

 

[nyioo7]

Are you using any particular Theme Chooser theme?

I am using system theme that came with CM7. I also installed MTDEV ICS theme. It seems as though, browser is ok after fresh install but after a while of using, it happens again. Clearing data and cache seems to fix it only for the first use. Then it happens again. Oh. I am also using Swype beta. I switched back to Android Keyboard and still the same.

EDIT: Ok. So, I just flashed over on the currently working CM7 with Browser bug and it fixed it. The keyboard pops up faster and browser doesn't go away or lock the screen.

 

[dsmryder]

2 issues:

1. Pressing the dial button from recent calls or contacts has a lag of 3-6 seconds before the 'dialing' screen pops up. I had this issue with the last update and this update. I have done a full wipe / factory reset between updates.

2. Wi-Fi keeps re-enabling itself every 10-20 minutes! I've turned it off via power widget and settings... No luck, tried a cache wipe also.

There are apps that will turn on the wifi. Might not be your problem, but you can look art what can turn it on. Maybe pull a log cat?

As far as the call delay, look at the build.prop. There is a line in there to set the delay that looks like
ro.call.delay=1000
If you set it to a lower number the delay will reduce. But 1000 means one second.

 

[Bull Shark]

is anyone else getting the volume lowering problem with notifications still or is it just me? I thought it was fixed a few builds ago, but the last two updates I did, it is back to doing it again. Did a full wipe both times.

 

[djboi2011]

is anyone else getting the volume lowering problem with notifications still or is it just me? I thought it was fixed a few builds ago, but the last two updates I did, it is back to doing it again. Did a full wipe both times.

i still get it

 

[dsmryder]

BIG newbie question here... so that means re-setting up all of what I've done in the last couple weeks on homescreen, downloading apps again, etc.... that right? If so, any other way to get this fixed? Just curious. Thanks!

Also, what am I looking for to double check the "checksum" ? Super newb here, sorry about that.

OK, so sorry about the delayed responce.
To answer your first question, yes. You would have to do everything agian. I would do a nandriod backup first, just in case it didn't work. That way you could return to where you left off.

To check your MD5 checksum, it would depend on what OS you are using. Under linux and Android you could open up a terminal and type

md5sum /(the path to the directory that holds the ROM file/(ROM file)

and it will spit out a big alfa-numeric string that should match what is on the MTDEV website. If it doesn't, then you need to redownload first.
Under Windows, there are programs that will do it for you. I just don't use them. I normally do it from the phone it self.