Root Helping our MTDEV Team

[GrandTheftBJJ]

Hey guys (and gals), our MTDEV Team works hard to make this phone rock so lets try to return the favor. They spend a ton of time coding, building, breaking, swearing, fixing, and repeating. They are busy. I wanted to start a thread for them to post menial or not so menial requests of non-programming-savy root users like myself who still want to help out where possible.

This thread is now open to comments, concerns, and suggestions...

 

[dsmryder]

Best post ever! Basically I would like to see more attempts at diagnosis. I see the occasional post about something that I can't reproduce. If I can't do it on my phone, I can't track down a possible cause. There are other things that are quarks. We may not be able to fix a quark.

Any way, getting back to eating my lunch

 

[MikeRL]

Hey guys (and gals), our MTDEV Team works hard to make this phone rock so lets try to return the favor. They spend a ton of time coding, building, breaking, swearing, fixing, and repeating. They are busy. I wanted to start a thread for them to post menial or not so menial requests of non-programming-savy root users like myself who still want to help out where possible.

This thread is now open to comments, concerns, and suggestions...

This gives me an idea. Should we create a support thread for MTDEV-CM7 and MTDEV-CM9 as well? Once something cannot be fixed there, it could always be added as a bug. Might help organize things around here a bit. I think you have a great idea, but this could just move the cluttered questions, comments, and suggestions to a new place. Just an idea, and if you guys like it, we should create support threads for MTDEV-CM7 and MTDEV CM9, with feature requests for each as well. Only bug reports could go into the ROM's thread, or we could even create a separate thread for bug reports. What do you guys think?

 

[g60madman]

GrandTheftBJJ,

Nice post! It would have to agree with dsmryder. However it's the nature of a forum, while it's a slamming community there is a lot to chew off on and gobs and gobs of information every where. New and Veteran users usually don't take the time to search or read they just post because there is just so much to look at, and they want a quick answer. So I think you solve that you solve lot's of stuff, but then it wouldn't be a forum

 

[dsmryder]

This gives me an idea. Should we create a support thread for MTDEV-CM7 and MTDEV-CM9 as well? Once something cannot be fixed there, it could always be added as a bug. Might help organize things around here a bit. I think you have a great idea, but this could just move the cluttered questions, comments, and suggestions to a new place. Just an idea, and if you guys like it, we should create support threads for MTDEV-CM7 and MTDEV CM9, with feature requests for each as well. Only bug reports could go into the ROM's thread, or we could even create a separate thread for bug reports. What do you guys think?

Personally I don't care. I think I prefer to have the stuff related to the ROM in the ROM thread. I know I see a bunch of "HELP, CM7, yada yada" and it trurns out to be a known problem with no current solution. It may be more helpful to post it in another website LOL. At least that way it wouldn't be the same people who have looking into the issue before.

Of course I try to read every post before posting myself, but I'm guilty of asking before looking too. I've done it with the answer just a few posts above mine. Just like I've tried to help people just to find out that someone has answered (sometimes better) a couple of posts below mine.

 

[MikeRL]

Somehow I do doubt anyone is going to use this thread, unfortunately, simply out of convenience. But what you have done is still extremely courteous, kind, and thoughtful. Oh well. Not a big deal. I'll just keep answering any questions I can wherever I can. As long as I take some of the pressure off of you guys so that you can spend more time coding, and have some free time as well.

 

[GrandTheftBJJ]

Thanks for the input. After another look its probably best to just discuss problems in the specific thread for the ROM/Kernel/Mod. But from what I've seen its a lot of one-way conversation. People post problems and Devs fix them. I haven't seen a lot of requests from the Devs themselves which is what I was getting at.

 

[dsmryder]

Thanks for the input. After another look its probably best to just discuss problems in the specific thread for the ROM/Kernel/Mod. But from what I've seen its a lot of one-way conversation. People post problems and Devs fix them. I haven't seen a lot of requests from the Devs themselves which is what I was getting at.

You mean like the requests to do a screen brightness test, or test the bkernel, or my request for diagnostic information?

We ask questions, and don't always get answers. I know I was a total noob just a year ago. The difference on my end is I'm a diagostic automotive technician in real life. I'm used to isolating issues. So if I ask a question, I useally am looking for a way to diagnose it myself. Or at least how to find the tools to do so, like better battery stats and cpu spy. When whyzor was building his ROM I was running a stress test like every night to see what voltages are stable. That's how I know what MY phone can handle. I don't want to test the overclocking limits of my phone. When ponyoface (I think that was his name) was starting kernel work, he would boot the phone at the max (1.9GHz) clock rate. My phone would work just fine. And fast and smooth too.

Anyway, I'm ranting when I should be showering (stinky mechanic). Ask away, and if you want, do what we tell you for a test, even if it doesn't pertain to you.

Holla

 

[GrandTheftBJJ]

Yes, stuff like that is what I mean, but I guess I just overlooked the post(s).

 

[MikeRL]

Personally I don't care. I think I prefer to have the stuff related to the ROM in the ROM thread. I know I see a bunch of "HELP, CM7, yada yada" and it trurns out to be a known problem with no current solution. It may be more helpful to post it in another website LOL. At least that way it wouldn't be the same people who have looking into the issue before.

Of course I try to read every post before posting myself, but I'm guilty of asking before looking too. I've done it with the answer just a few posts above mine. Just like I've tried to help people just to find out that someone has answered (sometimes better) a couple of posts below mine.

When I said requests, I meant feature requests from users. But I guess I helped jog your memory into something even more important! What an ironic coincidence LOL! By the way, any specific testing any of the devs want done, let me know if I can assist.

 

[dsmryder]

When I said requests, I meant feature requests from users. But I guess I helped jog your memory into something even more important! What an ironic coincidence LOL! By the way, any specific testing any of the devs want done, let me know if I can assist.

Do you have the soft button flicker? If so, could you mess around with the button brightness table on you phone and see if it goes away? That's one I have asked about in the MTDEV CM7 thread and g60 style thread. LOL

 

[GrandTheftBJJ]

To do list for tomorrow:
-Check bKernel (might as well check theOC as well)
-Compare MIUI and MTDEV-CM7 Screen brightnesses
-Look for bugs / diagnostics
-Try to get buttons to flicker and/or stop flicker

*I shall have much to report

 

[dsmryder]

To do list for tomorrow:
-Check bKernel (might as well check theOC as well)
-Compare MIUI and MTDEV-CM7 Screen brightnesses
-Look for bugs / diagnostics
-Try to get buttons to flicker and/or stop flicker

*I shall have much to report

Why thank you. And if you want, could you find out what partition is the "hidden" partition for the stock ROM and get me the size and help me figure out if I can steal it and move the space to the /system partition?

I think any testing, like the other kernels, would need a couple of days to really know the differences. I do appreciate the sentament, though.

 

[MikeRL]

Do you have the soft button flicker? If so, could you mess around with the button brightness table on you phone and see if it goes away? That's one I have asked about in the MTDEV CM7 thread and g60 style thread. LOL

When you say flicker, how bad do you mean flicker? Sometimes the keys may not light up properly or stay lit long enough (I need to look into it), but do you mean flickering like crazy, a strobe, or just early turning off?

 

[dsmryder]

When you say flicker, how bad do you mean flicker? Sometimes the keys may not light up properly or stay lit long enough (I need to look into it), but do you mean flickering like crazy, a strobe, or just early turning off?

I don't know, it doesn't happen on my phone. I can't get the purple who were talking about it to report back LOL. I did have ones guy, but he was on another ROM. I would like to help, I just can't confirm what is going on. Maybe I spend too much time on these forums and don't realize that other people don't.

 

[GrandTheftBJJ]

I usually keep my brightness at ~20-25% to save battery and haven't really noticed any soft-key flicker. When I turned brightness all the way down I did notice some flickering of the buttons. When set to auto-brightness or turning brightness to 100% there seemed to be no noticeable flickering. I took "flickering" to mean like light bulb tweaking on crack. If the keys weren't lighting at all, then here is the next part.

Did some testing with Incredicontrol to see if maybe the voltages were to blame. Governor was set to "powersave" so the CPU would stay put at the min (245mhz), and the i/o was left at "sio". I decreased all outputs equally down about 200 mv before the system rebooted, did not notice any flicker on the way down. I repeated the test with the governor as "performance" to lock the CPU at the max (1024), again left the i/o as "sio" and took the voltages down 150mv before crash/reboot. Sure enough the soft-keys kept flashing on and off as the voltages were ratcheted down. So a dying battery could be the cause of some of the flicker if someone has a heavy overclock and brightness turned way up.

After the system reboot(s) I did notice that my soft-keys didn't light up right away, but I went into settings a toggled "auto brightness" on, then back off, and things were back to normal.

*and now time for bed

 

[Cataulin]

whats the chance we can port super wipe to our Triumphs? I had it for my WFs and it would help with install time greatly.......

 

[GrandTheftBJJ]

I tried to find an app to test the lumen output of an android screen, but no such luck on the market. There is this, but it is for using your phone to test the brightness of a light, in a room for example, not the phone's screen itself. So the best I could do was take a few pictures with a digital camera in a dark room to compare the two. Quality control is crap and I wish I had some hard numbers to compare, but I guess its up to subjective user feel.

For the dark room test, my camera settings stayed the same (it is a Panasonic Lumix 14mp by the way), lights off in the room, flash off on the camera, and pics were taken from ~1foot above the phone and ~2feet above the phone with this app used to make the phone screen a "flashlight." I also included pics of my app drawer, same background (black) and launcher (Go Launcher EX) were used in the pics. The flashlight app automatically turns screen brightness to 100% and I manually set screen brightness to 100% for the app drawer pics.

MIUI Samples:

CM7.2 Samples:

Prior to the test I personally did not notice a difference in screen brightness between MIUI 2.4.20v3 and MTDEV-CM7.2. Though, as mentioned in the "Flicker Test" post I usually keep screen brightness turned pretty low anyway. After the test I would say that the results are inconclusive due to the lack of quantifiable measurements. MIUI may be a bit brighter, but for what its worth I'd say the screen brightness on MTDEV-CM7.2 is just fine as is.