• 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

Good news! Isolating the rapid battery drain problem following the CM7 ROM flash to being caused by the Enhanced Email app left me a little disappointed because this app has been great for overriding my company network server security. I decided to install the application again and the problem has gone away. I can show you the improvement from the screen shots below, thanks to the suggestion on this forum to use CPU Spy. I went from drain rate to 18% level in 3 hours to only 87% after uninstall and reinstall. The only thing I can tell you is I used Titanium Backup to restore the app+data feature when I first installed the ROM. I would have never known this could cause a problem because there was no error encountered.
 

Attachments

  • screenshot-1352374061524.png
    screenshot-1352374061524.png
    170.6 KB · Views: 179
  • screenshot-1352461084126.png
    screenshot-1352461084126.png
    178.3 KB · Views: 119
nwaves said:
Reboot in recovery, wipe cache and dalvik, then boot back into CM7, set the keyboard input you want, make sure you can use it then reboot the phone and see if the setting sticks.
Click to expand...

I did the dalvik wipe followed by partition wipe cache. I then did a system reboot. When I went into settings and looked under language and settings the only keyboard visible was android. I went to Amazon Apps where I obtained the app and did an open witch made it visible again. I selected it and even used it before doing a reboot. Same problem occurred where it didn't remain selected. I the decided to do an unistall and went back to Amazon and it indicated that I only had an open option which didn't work. Now I no longer have it available. I guess I should have left well enough alone!
 
marathondon said:
I did the dalvik wipe followed by partition wipe cache. I then did a system reboot. When I went into settings and looked under language and settings the only keyboard visible was android. I went to Amazon Apps where I obtained the app and did an open witch made it visible again. I selected it and even used it before doing a reboot. Same problem occurred where it didn't remain selected. I the decided to do an unistall and went back to Amazon and it indicated that I only had an open option which didn't work. Now I no longer have it available. I guess I should have left well enough alone!
Click to expand...

I forgot that I had done a Titanium Backup so I did a restore and it appears to be working correctly! Thanks for your direction it gives me practice with these ROM tools which I am a noobie at using.
 
marathondon said:
Good news! Isolating the rapid battery drain problem following the CM7 ROM flash to being caused by the Enhanced Email app left me a little disappointed because this app has been great for overriding my company network server security. I decided to install the application again and the problem has gone away. I can show you the improvement from the screen shots below, thanks to the suggestion on this forum to use CPU Spy. I went from drain rate to 18% level in 3 hours to only 87% after uninstall and reinstall. The only thing I can tell you is I used Titanium Backup to restore the app+data feature when I first installed the ROM. I would have never known this could cause a problem because there was no error encountered.
Click to expand...

Based on your screenshots it looks like you're using the stock frequencies. I would suggest changing the min freq to 122 MHz. You could even as low as 61 MHz which seems to work well on most phones but it causes random reboots on mine :( It will help lower the battery drain when your phone doesn't go in deep sleep.
 
nwaves said:
Based on your screenshots it looks like you're using the stock frequencies. I would suggest changing the min freq to 122 MHz. You could even as low as 61 MHz which seems to work well on most phones but it causes random reboots on mine :( It will help lower the battery drain when your phone doesn't go in deep sleep.
Click to expand...

I can tell you that I am running 24 min/ 1.5g max and have yet to have a random reboot that I couldn't attribute to a bad flash or test run. I can say that running in an underclocked manner does save a few drops of juice. I can also tell you that using the wrong governor will lock the processor to a low clock speed and will get stuck for a long while. I use onDemand as it's simple and if the processor is loaded, then it must need to kick up.

And because I don't use my phone enough, I have an average of 86% at ilde, 7% at 24MHz.
 
Popped back to cm7 until cm9 gets the camera going...

I like the quick access to screen brightness on status bar so I always opt for that. I noticed that on cm7 I'll increase bright, then after screen goes black and I turn back on, screen is not so bright again... there a way to fix that ?

Thanks for all the hard work and long hours into making my MT what it is today. So many don't know what they could have with this phone, it's like night and day from stock pos system... THANK YOU
 
jameyhowell73 said:
Popped back to cm7 until cm9 gets the camera going...

I like the quick access to screen brightness on status bar so I always opt for that. I noticed that on cm7 I'll increase bright, then after screen goes black and I turn back on, screen is not so bright again... there a way to fix that ?

Thanks for all the hard work and long hours into making my MT what it is today. So many don't know what they could have with this phone, it's like night and day from stock pos system... THANK YOU
Click to expand...

I'm not sure what you mean. You have the widget set for various brightness levels and the seeing won't stick after the screen cycles off then on?
 
Well I'm using the status bar for dimming/brightening the screen (which works great) BUT if I brighten the screen and then let the screen go dark(put into pocket) and then turn the screen back on, the screen goes back to dim lit... then I have to brighten it up again.

I like that you can use the status bar to slide up and down for screen brightness but on cm9 once I set it to either dim or slid it to bright, once I put phone down and pick it up a few mins later, screen is lit to what I left it at....
 
dsmryder said:
Did you see my test build? It was just for this, thouh it may of had an issue or two. I just wonder because I didn't get any feedback on it from any of the 22+ people who downloaded it.
Click to expand...

I've been using the 1025 test build for 4 days now. The only improvement I noticed is that Wifi is now reliably connecting when screen comes back up. I didn't notice any other changes. ROM is rock stable just like the 1015 build. Still having a hard time getting the phone in deep sleep mode, Event4-165 process is keeping a wakelock most of the time. I emailed Sven@BBS to find out what event4-165 is, I'll let you guys know if I hear back from him.
@dsmryder did you change anything else besides the Wifi in this build?

P.S. Looks like I spoke a bit too early about not having any issues. Just noticed Wifi off doesn't stick anymore, it turns itself on. Pretty sure a cache and dalvik wipe will fix it for a while. Oh and I wasn't able to get the video to work on Skype no matter what. It worked well in 1015 build. Could just be a fluke, I'll try again later on today and let you know if it works this time.
 
nwaves said:
I've been using the 1025 test build for 4 days now. The only improvement I noticed is that Wifi is now reliably connecting when screen comes back up. I didn't notice any other changes. ROM is rock stable just like the 1015 build. Still having a hard time getting the phone in deep sleep mode, Event4-165 process is keeping a wakelock most of the time. I emailed Sven@BBS to find out what event4-165 is, I'll let you guys know if I hear back from him.
@dsmryder did you change anything else besides the Wifi in this build?

P.S. Looks like I spoke a bit too early about not having any issues. Just noticed Wifi off doesn't stick anymore, it turns itself on. Pretty sure a cache and dalvik wipe will fix it for a while. Oh and I wasn't able to get the video to work on Skype no matter what. It worked well in 1015 build. Could just be a fluke, I'll try again later on today and let you know if it works this time.
Click to expand...

From waht I understand, wake locks are set by the kernel. Basicly if you see a wake lock, you need to see what the kernel has to say about it. That doesn't mean that it isn't the same accross most other kernels (they come from the same code mostly).
 
My understanding (and I might be wrong) is that a wake lock is a process that's keeping the kernel locked and preventing it from going in deep sleep mode. Thing is that I don't know how to find out which process is causing this or what process these events 164 or 165 or 166 are, so that I know which app is the causing the issue. If 164, 165, 166 are the PIDs then
164 is geomagneticd
165 is orientationd
166 is proximityd
But i'm not sure if that's the case.
 
marathondon said:
The only thing I can tell you is I used Titanium Backup to restore the app+data feature when I first installed the ROM. I would have never known this could cause a problem because there was no error encountered.
Click to expand...

Yeah I use Titanium all the time but for the most part just the app and not data. Is not always apparent. Way back when I first started flashing Roms had some issues with wifi I fought with until finding out it was caused by restoring a corrupted contacts data backup. Wouldn't have thought contacts data could have effected wifi. I now will only restore data if I'm like really into a game or something.
 
nwaves said:
My understanding (and I might be wrong) is that a wake lock is a process that's keeping the kernel locked and preventing it from going in deep sleep mode.
Click to expand...
You're right about that part. the kernel or the app itself can call a wake lock. Like the wifi wake lock that tickerguy added. It was because of a lockup condition that he couldn't resolve because of a lack of code (we might be able to fix that with hex-ray one day) Apps can call a wake lock too, think of MMS. It would suck if you turned off your screen and the text didn't go through.
Thing is that I don't know how to find out which process is causing this or what process these events 164 or 165 or 166 are, so that I know which app is the causing the issue. If 164, 165, 166 are the PIDs then
164 is geomagneticd
165 is orientationd
166 is proximityd
But i'm not sure if that's the case.
Click to expand...

Maybe. Like I said, I think. I remember reading things in the code that makes me think I'm right.
 
Is there a setting that will make the mic work on pair of iphone earbuds? I'm pretty sure that on the lame old stock rom that these head phones worked, anyway, thought I'd ask since I like the phones. Thanks for all the hard work! ;) I'll have more to donate soon too!
 
jameyhowell73 said:
Is there a setting that will make the mic work on pair of iphone earbuds? I'm pretty sure that on the lame old stock rom that these head phones worked, anyway, thought I'd ask since I like the phones. Thanks for all the hard work! ;) I'll have more to donate soon too!
Click to expand...

From what I have read, Android devices lack hardware support (a chip) to use the Mic on IPhone ear phones.
 
Have another test build to post, do you guys think it would be best to start a different thread or just add a section in the op for beta potentially unstable builds?
 
Chairshot215 said:
Have another test build to post, do you guys think it would be best to start a different thread or just add a section in the op for beta potentially unstable builds?
Click to expand...

I think you should keep it all in one area personally. If it's a beta build change the top name to beta and just add the new builds. If people want older stable builds they are all online :)
 
I agree with g60. Perhaps you should update the title, and put your beta builds in the first post with changelogs as well. It would be a good idea if all the MTDEV ROMs had a concise formatting with regards to finding the download and changelog. Or you could rename this thread stable, release a stable build, and make an experimental build thread.
 
I have resolved my personal WiFi issues. It was my router. One problem I have is I am crazy busy. But as luck would have it, my wife was using the laptop (something I was going to use to try to diagnose my situation) and she kept complaining about the internet going out. I would reset the router, the problem would be solved for a while, then the call from down the hall would return "Where did my internet go?". When she took her shower, I found an updated fermware for my router and I haven't had a problem sence
 
Pretty tired so for now just added a small section below downloads for beta builds along with the change-log post. Will need to work something out with G60 so I don't need to bug him about updating the Rom Browser all the time. What is different about the latest beta build is first removed the Stock HW Sensor libs & updated to Sharp 2.3.5 libs, almost forgot about that one. For starters it just seemed like a good idea based on we are and have been using the Sharp 2.3.5 sensord Bin files for the last few builds. Also just to test any other noticeable improvements or possible fixes such as the prolonged black screen after a premature disconnect bug. Second is using hex-ray picked out a few files we don't have that had been listed to be used by some of the other proprietary files we add in. Basically just to see if having these files makes any difference. For the most part I only checked wifi & BT related files. Lastly is the entire GPS configuration has been revamped restoring all the Sharp 2.3.5 / Andro-id libs we had actually used in the first few MTDEV releases along with some additional libraries and a modified version of G60's new CM9 board.congif. Would not work in CM7 as is and took a little finagling and just a few builds to get working.
 
OK, chairchot, we have to snag the USB connection backround from your starship ROM. That thing is b e a utiful.

Way too many projects. Time for bed.(that probably means I'll think of a ton of stuff that I'll do instead of sleeping.
 
well ive tried both Test Roms the most recent i have flashed twice. It has been some what smooth on features but its given me reboots from out of nowhere. had an odd Wifi problem this morning but fixed it with rebooting. i like it but its a test rom it has potential to be beast !!!
 
You must log in or register to reply here.
Back
Top Bottom