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

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

Your answer is unclear. The problem, I suppose, is that I really asked two questions, and I expect that the answer to each of these is the opposite of the answer to the other; and you gave one answer, “Basicly, if it came from a member of the MTDEV team then, no.”, and it is not clear which of the two questions goes with that answer.

The two questions, separated, are…

I get that Chairshot is the one who developed this GPS fix, and that he's also one of those working on this ROM, which suggests a very strong possibility that this fix may be incorporated into this ROM at some point. I haven't seen anything to indicate whether or not it already has, other than the statement on the other thread about it obviously hadn't been at that point because at that point, the latest version of the ROM had been released two days before this fix came out.

Sorry about that.

To answer them at the same time, it's same gps.config. I guess if you were running the older ROMs it would work. I would have to double check, but I think it would work on all ROMs. I don't think they changed that part of the design from FroYo to JB.

More github digs

Edit: In CM9 it's still a little different, and CM10 it's the one made by Issac.
 
Again, thanks for all the great work on this build. It has really made my Triumph usable.

One thing I have noticed and am not sure if it is related to any changes made here. When my camera uses the flash the pictures are almost always blurry. It seems the shutter is open longer than it should be. Is this something low level or is there an easy way to have the shutter open for a shorter time frame?

Thanks.

[add] One thing I should have said, too, is that on a bright day outside I am able to take pictures of my son half way through a swing and the baseball in the air. Obviously no flash for that one. But it seems to show the camera is capable of doing what I think it should do. It just seems that when the flash is on the shutter is open too long.[/add]
 
Can you tell if the blur is motion blur or Gaussian blur?
It'd be interested in seeing an example, if you can host one somewhere.

What crossed my mind, is that the cover over the lens and the flash is one single piece. I wonder if lint, dust or even moisture condensate, etc could be in there and be getting illuminated when the flash comes on.
 
I PM'ed you the location of two pictures (family pictures, hence the PM).

To me it seems like motion blur as the static objects in the image are not blurred. Unless there is lots of light (daytime baseball :-) ) and things seem fine.

[add] I suppose one way to test that would be to take a picture outside in the daylight and take a picture with the flash and without. If they are the same not as likely about light bouncing back from moisture/dust. If they are the same then not as likely. I'll see if I can try that when I get out from work.[/add]

Can you tell if the blur is motion blur or Gaussian blur?
It'd be interested in seeing an example, if you can host one somewhere.

What crossed my mind, is that the cover over the lens and the flash is one single piece. I wonder if lint, dust or even moisture condensate, etc could be in there and be getting illuminated when the flash comes on.
 
Looked at the pics and I see what you mean.
I'm at the brewery now, but I'll post my thoughts later.
hint: it won't be a solution ;)
 
It depends on what kernel you are playing with. If you have the one that gets flashed with the ROM, then I would recommend 64MHz - 1.4GHz with OnDemand and use SystemTuner to change the up kick to 85% and power save to 35 (maybe 350, my daughter is on the phone).

If you are running one of my "test kernels" then I would recommend going down to 21MHz on the low end and running it for like a week to tell me how it's going (shameless request for data)


what do you mean, upkick and powersave?
 
what do you mean, upkick and powersave?

Sorry, my daughter had the phone at the time.

On some governors you can control the way they behave.
screenshot-1349138840674.png
screenshot-1349138857283.png
You see whrere it says "Up-Threshold" and "Power-save bias"? That's what I ment.
 
Again, thanks for all the great work on this build. It has really made my Triumph usable.

One thing I have noticed and am not sure if it is related to any changes made here. When my camera uses the flash the pictures are almost always blurry. It seems the shutter is open longer than it should be. Is this something low level or is there an easy way to have the shutter open for a shorter time frame?

Thanks.

[add] One thing I should have said, too, is that on a bright day outside I am able to take pictures of my son half way through a swing and the baseball in the air. Obviously no flash for that one. But it seems to show the camera is capable of doing what I think it should do. It just seems that when the flash is on the shutter is open too long.[/add]

I wonder if you are right? I wonder if the "shutter" is held because of the low light and the flash kicks on washing out the picture on top of the longer time or something like that?
 
Right. That is what it feels like to me. Ummm... any ideas on how "we" can fix it?

I wonder if you are right? I wonder if the "shutter" is held because of the low light and the flash kicks on washing out the picture on top of the longer time or something like that?
 
I wonder if you are right? I wonder if the "shutter" is held because of the low light and the flash kicks on washing out the picture on top of the longer time or something like that?

I think so.
I think that the exposure compensation on our camera doesn't seem to take into account the flash.
I have a camera app that has, as one of the flash settings, a constant on (torch) flash. This helps to frame a shot in low light, but the pictures are still blown out. The exposure compensation doesn't seem to adjust for the added light from the "flash".

It's not truley a "flash", as much as just added (weak) illumination.

With a traditional flash, the strobe is fast enough to freeze motion, even at seemingly too slow a shutter speed, as the flash comes on and back off much faster than the shutter (generally speaking).

in our case, the flash stays on for WAY longer than the shutter, so the ability to freeze motion really has no relation to the speed of the "flash", but relies only on shutter speed, which with the limitations of the speed (aperture, sensitivity) of our camera, plus our comparatively weak flash, is too slow to keep a moving object sharp.

I use my front camera constantly, for face recognition, and in low light situations, it's ridiculous how slow it is to ramp up sensitivity. This may contribute to the blown out highlights when using the flash, even still allowing blurred motion.

I won't hold my breath for a solution.
 
Newby here. Upgraded to the 0926 build yesterday. Everything working great, except incoming calls vibrate only. I've been through all the setting several times, rebooted, pulled the battery, etc., and nothing seems to help. Suggestions, other than reflash? Also, the phone would not synch Market/Play on initial reboot..is this a known problem? Privacy setting were/are correct. Thinking about going back to the August build - was working well...just a bit of a battery hog.

Thanks in advance for any help, and for all the great work and info. 6 weeks ago, had no idea how to root.
 
Newby here. Upgraded to the 0926 build yesterday. Everything working great, except incoming calls vibrate only. I've been through all the setting several times, rebooted, pulled the battery, etc., and nothing seems to help. Suggestions, other than reflash? Also, the phone would not synch Market/Play on initial reboot..is this a known problem? Privacy setting were/are correct. Thinking about going back to the August build - was working well...just a bit of a battery hog.

Thanks in advance for any help, and for all the great work and info. 6 weeks ago, had no idea how to root.

If you are concidering a restore of an old backup anyway, I would do a fresh flash of what you have. Sometimes things get messed up. It happens. I would just flahs and leave the othere apps until I knew the ROM was working.
 
I think so.
I think that the exposure compensation on our camera doesn't seem to take into account the flash.
I have a camera app that has, as one of the flash settings, a constant on (torch) flash. This helps to frame a shot in low light, but the pictures are still blown out. The exposure compensation doesn't seem to adjust for the added light from the "flash".

It's not truley a "flash", as much as just added (weak) illumination.

With a traditional flash, the strobe is fast enough to freeze motion, even at seemingly too slow a shutter speed, as the flash comes on and back off much faster than the shutter (generally speaking).

in our case, the flash stays on for WAY longer than the shutter, so the ability to freeze motion really has no relation to the speed of the "flash", but relies only on shutter speed, which with the limitations of the speed (aperture, sensitivity) of our camera, plus our comparatively weak flash, is too slow to keep a moving object sharp.

I use my front camera constantly, for face recognition, and in low light situations, it's ridiculous how slow it is to ramp up sensitivity. This may contribute to the blown out highlights when using the flash, even still allowing blurred motion.

I won't hold my breath for a solution.

I can take a look at the order the flash and camera capture are in. I doubt it, but if the flash is on and the camera is set to grab at a lower light, maybe I can reverse it and it work. Altho, what you said leaves me to beleive I may not be able to change anything. I do know our "flash" rate is very slow to respond. Just open the tourch app and play with the strobe to see what I mean.
 
If you don't mind trying that would be great.

My wife has the LG Optimus V and pictures in similar light are much better than what I get with my Triumph (though obviously not as good as a reasonable camera).

Keep me posted if you want me to test anything.

I can take a look at the order the flash and camera capture are in. I doubt it, but if the flash is on and the camera is set to grab at a lower light, maybe I can reverse it and it work. Altho, what you said leaves me to beleive I may not be able to change anything. I do know our "flash" rate is very slow to respond. Just open the tourch app and play with the strobe to see what I mean.
 
I think so.
I think that the exposure compensation on our camera doesn't seem to take into account the flash.
I have a camera app that has, as one of the flash settings, a constant on (torch) flash. This helps to frame a shot in low light, but the pictures are still blown out. The exposure compensation doesn't seem to adjust for the added light from the "flash".

It's not truley a "flash", as much as just added (weak) illumination.

With a traditional flash, the strobe is fast enough to freeze motion, even at seemingly too slow a shutter speed, as the flash comes on and back off much faster than the shutter (generally speaking).

in our case, the flash stays on for WAY longer than the shutter, so the ability to freeze motion really has no relation to the speed of the "flash", but relies only on shutter speed, which with the limitations of the speed (aperture, sensitivity) of our camera, plus our comparatively weak flash, is too slow to keep a moving object sharp.

I use my front camera constantly, for face recognition, and in low light situations, it's ridiculous how slow it is to ramp up sensitivity. This may contribute to the blown out highlights when using the flash, even still allowing blurred motion.

I won't hold my breath for a solution.

Ok, if I can read jave correctly, the order of events is:
  • Focus
  • (with flash enabled) iluminate and get white balance, set iso
  • flash and take the picture
I don't know if there's something I can do here. We do have hardware limitations and may be affected be the libraries we're playing around with.

I did find some other tid bits. I can adjust the post view delay. Right now it's set to 1.2 seconds. I hope to come back and make a menu setting for that. And there's a screen delay that was set for 1 second. I'm playing around with that to see what it does.
 
Ok, if I can read jave correctly, the order of events is:
  • Focus
  • (with flash enabled) iluminate and get white balance, set iso
  • flash and take the picture

Is there an obvious way to change how it sets iso?
I wonder if that can be used to fool the camera into using a shorter shutter speed, without darkening the shot too much.
 
Is there an obvious way to change how it sets iso?
I wonder if that can be used to fool the camera into using a shorter shutter speed, without darkening the shot too much.

I'm just getting started in programming, but if I can find an example of a manual iso setting, then I can probably bring it in.
 
Ive been running an older version of this ROM (Id say around 7/26/12-8/01/12) and was having problems, but didnt complain because I figured they were fixed in the update. I reflashed a few days ago and the problems are still persisting:

-When I go into the gallery app and zoom in on a picture, the phone will often freeze for a few seconds, sometimes even minutes, and sometimes the phone will actually reboot
-When I take pictures with the camera, occasionally it will say my battery is at 0% and the phone will shut down. It will say this regardless of what my actual battery percentage is.
-I cant seem to format the SD card but Im pretty sure thats intentional, right?
 
Ive been running an older version of this ROM (Id say around 7/26/12-8/01/12) and was having problems, but didnt complain because I figured they were fixed in the update. I reflashed a few days ago and the problems are still persisting:

-When I go into the gallery app and zoom in on a picture, the phone will often freeze for a few seconds, sometimes even minutes, and sometimes the phone will actually reboot
-When I take pictures with the camera, occasionally it will say my battery is at 0% and the phone will shut down. It will say this regardless of what my actual battery percentage is.
-I cant seem to format the SD card but Im pretty sure thats intentional, right?

WOW that is not right at all. I would recommend backing up your SDCARD and then format it in CWM and then reinstall the ROM and make sure to do a full wipe / dalvik and see what happens. If it's OK restore your SD and see if it happens again.
 
I've been having an issue where when turn off usb storage my phone doesnt mount the sd card again until I reboot and the usb icon stays in the status bar.

Is anyone else having this issue?
 
WOW that is not right at all. I would recommend backing up your SDCARD and then format it in CWM and then reinstall the ROM and make sure to do a full wipe / dalvik and see what happens. If it's OK restore your SD and see if it happens again.

I already did this as a precaution before I posted and the error still remained. Perhaps in an issue with my particular phone?
I just took a bunch of pictures at 32% battery when it gave me a low battery notice and turned off the phone. I started it back up and it said the battery was at 0% and then it turned off again. I plugged the charger in, turned it on, and then it said I had 32% battery. I have no idea whats going on, but I took it off the charger to see how long it will last and make sure my battery isnt being read incorrectly.
 
I already did this as a precaution before I posted and the error still remained. Perhaps in an issue with my particular phone?
I just took a bunch of pictures at 32% battery when it gave me a low battery notice and turned off the phone. I started it back up and it said the battery was at 0% and then it turned off again. I plugged the charger in, turned it on, and then it said I had 32% battery. I have no idea whats going on, but I took it off the charger to see how long it will last and make sure my battery isnt being read incorrectly.

Install the stock ROM from b_randon14 and see if it's doing the the same thing.

Stock_ROM_SplashImage_b_randon14.zip
 
Back
Top Bottom