• 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

I got in touch with VM who said there were no outages or issues in my area.

My MT continues to flicker to 1x sometimes, although not as much today as it did yesterday.
 
You could try testing it with this version

MTDEV-CM7-20130119.zip

I honestly have not gotten much feedback yet but it uses a different init.triumph.rc and a few different file changes for BT not implemented in the 12-28 build. G60 tested the changes for me one time with the bt & wifi as I do not own a Bluetooth headset but honestly is the only feedback I have received.

Hey chairshot? What should I be looking for. I have this loaded on the DEV (no service) phone. Should I put this on the my main phone (full service, used through out the day)?
 
I have had nothing but problems these past few days (I thought my issues with Titanium Backup were annoying).

A lot of the time I keep seeing I am at 1x instead of 3G. Toggling airplane mode sometimes fixed it, sometimes didn't, and the same for a reboot.

I tried forcing 3G through Settings -> Wireless and Networks -> Mobile Networks -> CDMA Network Preference -> EvDo only. A couple of days ago this used to force 3G on, but now it simply makes the phone act as if I have put it in airplane mode again. All of the signals bars go away, and the small "x" appears above them. I cannot make or receive calls or access anything via the data connection when EvDo is forced on in this way.

I toggled back to CDMA / EvDo and my phone can make and receive calls and texts again, but it's stuck at 1x about 90% of the time now.

At first I thought it might be the ROM (unlikely, since nobody else had reported it, but possible I guess) so I tried flashing the 10-15 CM7, only to experience the exact same issue.

Now I am left thinking it's one of two things:

(1) Either Sprint maintenance on my local tower, or a localised outage.

(2) The radio in my phone is on its way out.

I've been thinking about either an EVO 4G or maybe even a Nexus 4 recently, but was hoping to get a few more months out of my Triumph (it's a few months past the one year warranty). I'm at a loss as to else I can try.

I'm seeing this issue too, as is my dad who has Sprint, so my assumption is it has something to do with the "network improvements"
 
so it's in five languages ?

Yeah, android apps are mostly Java with the layouts and "data" in .xml. The OS is in C and C++ mostly. On top of that there are scripts and whatnot written for bash or whatever, maybe not python. I see a script and lump it into my "script" group. The building script we use is in python, though. I could be done in a bunch of different languages, but that's what they went with.
 
I'm seeing this issue too, as is my dad who has Sprint, so my assumption is it has something to do with the "network improvements"
Well that certainly adds fuel to the fire.

I'm near Dallas, TX, so nowhere near you. This does not seem to be a regional issue...

Anyone else seeing a lot of 1x instead of 3G?

It seems there are also people complaining of the same issue over at their Facebook page: http://www.facebook.com/virginmobileusa
 
Well that certainly adds fuel to the fire.

I'm near Dallas, TX, so nowhere near you. This does not seem to be a regional issue...

Anyone else seeing a lot of 1x instead of 3G?

It seems there are also people complaining of the same issue over at their Facebook page: http://www.facebook.com/virginmobileusa

thats all i get i very rarely see 3g...vm says its where i am..gave me 4 replacement phones and no change same..i belive its software related
 
thats all i get i very rarely see 3g...vm says its where i am..gave me 4 replacement phones and no change same..i belive its software related

If it was software related then more people would have issues. When I'm in Orlando I get terrible 3g service. Outside Orlando, my area mostly, I get 3g all day long. Even with GPS running.
 
Hey guys. Sorry for the lack of progress recently. I am working on reporting and debugging a critical bug I've ran into on Ubuntu. It happens to me on 12.10 and 13.04 development branch. Let's just say it is a hard crash and it's not obvious to debug, and it happens a lot. So I went on IRC and chatted with some knowledgeable Ubuntu devs. I know what to do to debug now, but it may be a while till the desktop works properly. I cannot devote much time to MTDEV until the debugging is finished, the bug report perfected, and I draw developer attention. I should be able to do this by Monday, though. Besides, how am I supposed to code on a machine that crashes all the time? I will return shortly. Sucks having to rely on Windows 8. But I have some good news. Not only am I learning C formally along with visual studio, I am learning Android and github as well. On Linux. Visual Studio 2012 in the next update is getting github integration. Microsoft done something good for once in quite a while. I do have a laptop, but I must fix this computer so this computer is actually usable.
 
Seems to be a decent amount of downloads for the MTDEV-CM7-20130119 build. If anyone finds any improvement over the 12/28 build let me know and ill update the OP.
 
Hey guys. I don't know if you guys already realized this bug but when you take picture with front facing camera on CM7 latest release, it turns into green screen when shutter opens and camera becomes zoomed in. Picture is taken fine but camera becomes malfunction. The only way to fix it is to go back to back camera or restart the camera app. After several pictures taken with front facing camera, camera hardware crash and error message pops up saying cannot connect to camera. Only way to fix that is to restart the phone.
 
Hey guys. I don't know if you guys already realized this bug but when you take picture with front facing camera on CM7 latest release, it turns into green screen when shutter opens and camera becomes zoomed in. Picture is taken fine but camera becomes malfunction. The only way to fix it is to go back to back camera or restart the camera app. After several pictures taken with front facing camera, camera hardware crash and error message pops up saying cannot connect to camera. Only way to fix that is to restart the phone.

I'm on a 12-30 build and I took several pictures with the fromt camera after taking a bunch of pictures with the back camera. This is with an uptime of 108 hours. What build are you running?
 
I'm on a 12-30 build and I took several pictures with the fromt camera after taking a bunch of pictures with the back camera. This is with an uptime of 108 hours. What build are you running?

I'm running 12.28 build on the front page. Is there newer version than that? I didn't know.
 
I'm running 12.28 build on the front page. Is there newer version than that? I didn't know.

My 12-30 is 12-28, it's just I build it at home. That's why the date is different. And there are some test builds that chairshot releases. You would have to look through the posts to see them.
 
My 12-30 is 12-28, it's just I build it at home. That's why the date is different. And there are some test builds that chairshot releases. You would have to look through the posts to see them.

Tested the link that Chairshot posted in above thread and still the same. It might be my camera is messing up. The quality is greatly reduced. There's a lot of pixels in the pictures. It used to be clear before. I know it is only 0.3 MP but now, it's worse. I'll find a way to take a picture of my phone and post. Maybe some driver error or maybe the hardware error.
 
Tested the link that Chairshot posted in above thread and still the same. It might be my camera is messing up. The quality is greatly reduced. There's a lot of pixels in the pictures. It used to be clear before. I know it is only 0.3 MP but now, it's worse. I'll find a way to take a picture of my phone and post. Maybe some driver error or maybe the hardware error.

are you using a this party camera app?
 
So I got
1
this bluetooth adapter as a gift and it streams music perfectly to my sound system from my Nexus 7. However, when I try to stream music from my Triumph (2012-12-28 MTDEV CM7 build) the audio quality/range is horrible if I am more than two feet away from the bluetooth receiver.
I am wondering if anyone else on this build has any issues streaming bluetooth, or if it is just a combination of the receiver's hardware and the Triumph not working well together. Based on the cost of the bluetooth adapter, I would normally just attribute the poor quality to that device, but it works great on the Nexus 7. Any advice would be appreciated.
 
So I got
1
this bluetooth adapter as a gift and it streams music perfectly to my sound system from my Nexus 7. However, when I try to stream music from my Triumph (2012-12-28 MTDEV CM7 build) the audio quality/range is horrible if I am more than two feet away from the bluetooth receiver.
I am wondering if anyone else on this build has any issues streaming bluetooth, or if it is just a combination of the receiver's hardware and the Triumph not working well together. Based on the cost of the bluetooth adapter, I would normally just attribute the poor quality to that device, but it works great on the Nexus 7. Any advice would be appreciated.


not an expert but if i were to take a stab at this, id say it could be 1 of 2 things

1. The bluetooth in the nexus has better antenna power/range giving you a much better connection at a greater distance

2. The bluetooth in the Triumph and the adapter may be different versions of bluetooth, i just had a pc/game controller issue where bluetooth versions were the culprit, bluetooth started with version 1.0 i believe and recently it went to 2.0 then 2.1 and while they say its 100% backwards compatible they sometimes have issues with one another


The pc/game controller issue i mentioned was a PS3 controller which runs bluetooth 2.0 and my adapter which is supposed to be dual band 2.0 and 2.1, turns out its just backwards compatible 2.1, gave me hours upon hours of trouble before i actually got it working correctly even tho the adapter says backwards compatible with 2.0 and 1.0 sometimes electronics dont play nice with one another lol
 
My 12-30 is 12-28, it's just I build it at home. That's why the date is different. And there are some test builds that chairshot releases. You would have to look through the posts to see them.


Yeah the 1-19-13 build posted a bit back for testing is using a different set of permissions and files for BT. One thing I have verified is it at least transfers the build from my laptop to my Triumph a hell of allot faster then the 12 - 28 build.
 
Yeah the 1-19-13 build posted a bit back for testing is using a different set of permissions and files for BT. One thing I have verified is it at least transfers the build from my laptop to my Triumph a hell of allot faster then the 12 - 28 build.

Hey Chairshot. So, my problem with the camera is possibly only my phone? Could it be hardware problem?
 
Back
Top Bottom