-
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
- Thread starter Chairshot215
- Start date
-
- Tags
- motorola triumph
thangfish
Android Expert
If you manually edited egl.cfg, don't forget you have to put permissions back to rwrr.
sikk66
Member
I did this and my graphics were VERY choppy until I fixed the permissions.
I tested it and I can confirm that the flashable zip does work.
The Disable CPU Rendering mod doesn't appear to have any impact on my handset's performance or its battery life.
I'm running UV + light OC at 1.3 GHz, using SmartAssV2 + Anticipatory I/O Manager and getting about 3 days+ of battery life normally. After performing the mod, it seems to be on track for another 3 days+ of battery life.
It's hard figuring out why people are reporting so many improvements. Maybe I'm doing it wrong?
I'm running UV + light OC at 1.3 GHz, using SmartAssV2 + Anticipatory I/O Manager and getting about 3 days+ of battery life normally. After performing the mod, it seems to be on track for another 3 days+ of battery life.
It's hard figuring out why people are reporting so many improvements. Maybe I'm doing it wrong?
b_randon14
Android Expert
Just to post some updates I'm on the 23 build and I'm still gavng the call mute then drop issue and my wifi is really messed up. If it will turn on, it will connect but can't ever resolve with the DNS server so no internet connection and sometimes it will turn on then right back off.
Possible, but I saw no change either.
Just to double-check, I flashed the VM670 zip and then went into Solid Explorer to check if the egl.cfg and build.prop files were edited. They weren't. I went ahead and manually edited both of them. However, Thangfish, considering that you used the manual method, it's likely this particular mod just doesn't do anything noticeable. :-(
thangfish
Android Expert
It's all good man. I always figure that if one person posts with concerns, there's at least 20 more lurking with the exact same concern, that didn't post. That's why I love this forum.
We all learn everyday... well if it's a good day, anyway!
PS,
I'm old... got a problem with that?
Bob Blaylock
Well-Known Member
I am also on the 23 build and I haven't experienced any of the issues you listed. But I sometimes wonder if the "wipe data/factory reset" function works the way it should (I am on CWM v5.0.2.6). I know that I have "wipe data/factory reset" and cleared cache then install a new rom and find that some of my settings have carried over from my previous flash.
I don't have any answers... just wondering if others have had lingering data? And if so could it explain the problems you are seeing?
It seems that 5.0.2.6 carries over data, 5.0.2.7 is the one I have had the least issues with, 5.5.0.4 and up seem to work fine but only make backups as ext4 so with some ROMs you have to change the names to ext3 and the names of the files in the md5 also, to get it to work properly. Hope this explains things for you guys.
dsmryder
Android Expert
rebel69ization
Well-Known Member
This 9/26 is sweet, overclocking settings, what would you suggest?, gov?
thangfish
Android Expert
Probably just a VM thing.
btw, since I've seen comments/questions similar to yours about prl..
Your prl file can not be changed by flashing a ROM. It's a separate process.
thangfish
Android Expert
since there is really no evidence that a prl swap can help us (because VM doesn't allow roaming anyway) the stock one is fine.
I found it entertaining to play around with anyway, so far be it from me to discourage you from it!
dsmryder
Android Expert
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)
- lowered voltage kernel with 21MHz to 1.9GHz enabled
- Lower voltage kernel. Simular to the other one, just might cause a bootloop. I would like feedback on this one anyway, if you don't mind.
b_randon14
Android Expert
Hey guys I'm in the process of prepping both kernel repos in the MT dev organization so I can patch them up to 2.6.32.59 so within a few days I should have em pushed up to the MT dev github!
Bob Blaylock
Well-Known Member
At this point, is there any benefit to flashing this (“Vastly improve GPS for all ROMs”
Basicly, if it came from a member of the MTDEV team then, no. As Chairshot215 works his way through the device files and configurations he is going to find stuff that will work through other ROMs.
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…
- At this point, is there any benefit to flashing this (“Vastly improve GPS for all ROMs” over this ROM?
…and…
- Has it or something better been incorporated into this ROM by now?
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.