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

Root [Merit] [ROM] METRO v2.0.777--777 Kernel + TouchNav, all versions, all setups [ROM]

stayboogy

stayboogy

Android Expert
METRO v2.0.777
with
777Mhz Overclocked Kernel
and
TouchNav System Recovery Utility




FEATURES

TouchNav System Recovery Utility (both ext and vfat versions)
777Mhz Overclocked Kernel with ext4 and swap support
rooted
Blue Steel Themed
init.d scripting
custom cpu management--never go below 777mhz--user customizeable
dalvik-cache relocated to /dev
optimized for space
minimal ram usage
best, custom, system apps


Install one and done!!!


And all of this in only one update package file!!!
And it installs on any setup--any model, any version, any recovery!!!




Disclaimer: I am not responsible for any damage that may or may not result from the use of this rom or kernel. You are responsible for what happens to your device. USE AT YOUR OWN RISK.


NOTE: MAKE A BACKUP BEFORE YOU INSTALL THE ROM


NOTE: YOU CANNOT INSTALL THE ROM AND THEN JUST INSTALL ANOTHER BOOT.IMG. IF YOU DO SO, YOUR WIFI WILL NOT WORK BECAUSE ITS DRIVER HAS TO BE BUILT WITH THE KERNEL. IF YOU WANT A VERSION WITHOUT THE KERNEL, USE v2.0




DOWNLOADS
(remember to rename to update.zip if installing on stock recovery)

*wipe your data before you install. you can try to just delete your dalvik-cache, but if rom fails to boot then wipe all userdata and install again*

**first boot will hang at ZTE logo for nearly a minute sometimes. this is normal**

***all boots will be long because of the dalvik relocation and rebuild and because it is deodexed***
METRO v2.0.777 with TouchNav System Recovery Utility (ext)

METRO v2.0.777 with TouchNav System Recovery Utility (vfat)

THEME ONLY HERE


​
 

Attachments

  • recovery.png
    recovery.png
    3.1 KB · Views: 189
  • boot.png
    boot.png
    4.1 KB · Views: 175
  • main.png
    main.png
    48.4 KB · Views: 182
  • droid@screen-2.png
    droid@screen-2.png
    11.4 KB · Views: 174
  • droid@screen-3.png
    droid@screen-3.png
    31.2 KB · Views: 182
  • about.png
    about.png
    16.4 KB · Views: 165
  • min.png
    min.png
    6.2 KB · Views: 150
  • max.png
    max.png
    6.2 KB · Views: 142
I'll reinstall and give it another try. Also there seems to be something eating up the battery...could be a bad install.
 
tjarvis said:
I'll reinstall and give it another try. Also there seems to be something eating up the battery...could be a bad install.
Click to expand...

Stayboogy's roms are overclocked to 777Mhz. 177Mhz higher than the normal clock settings for our devices. It's also set to performance mode by default, which doesn't allow the CPU to drop below 777Mhz, Such as an "ondemand" governor will allow you to do.

I personally use SetCPU with Profiles enabled. The only time my CPU uses 777Mhz is when I am using applications that a otherwise sluggish without over clocking. Otherwise it switches to a "ondemand" governor with max CPU of 600Mhz. I also have it setup to underclock the CPU when the screen is off. Saves even more battery life.

I get anywhere from 7hr-9hrs of battery life, and I use my phone constantly. Without using SetCPU I got 5hrs average using Stayboogy's overclocked kernel.
 
tjarvis said:
I'll reinstall and give it another try. Also there seems to be something eating up the battery...could be a bad install.
Click to expand...

no, your battery issues are because you are 1) keeping so many applications running even when they are not being used by using the included task manager/killer, and 2) because the battery will always drain faster immediately after the install of a new rom until the battery is recalibrated

OVERCLOCKING HAS NOTHING TO DO WITH IT AT ALL

in fact, if you do some reading, you will find that it eats up more battery juice to keep the freq changing instead of leaving it at one speed, even overclocked

my cpu is at 777 all the time, never changes, and my battery never drains any more noticeably than ever before
 
stayboogy said:
no, your battery issues are because you are 1) keeping so many applications running even when they are not being used by using the included task manager/killer, and 2) because the battery will always drain faster immediately after the install of a new rom until the battery is recalibrated

OVERCLOCKING HAS NOTHING TO DO WITH IT AT ALL

in fact, if you do some reading, you will find that it eats up more battery juice to keep the freq changing instead of leaving it at one speed, even overclocked

my cpu is at 777 all the time, never changes, and my battery never drains any more noticeably than ever before
Click to expand...

In all honesty, there's a lot of information out there about the Android OS that's completely wrong. For example, using a task killer isn't a good idea at all. Most applications automatically re-open after being killed, using more CPU to restart that application. Task Killers are bad unless you know for sure an application is poorly coded and is acting up. I use Watchdog and haven't turned back to a task killer.
http://www.howtogeek.com/127388/htg-explains-why-you-shouldnt-use-a-task-killer-on-android/

Also in reply to your constant clock changing comment, You are right, If it's setup wrong. However, If I rarely need 777Mhz, Keeping it at 600Mhz unless it's needed does save battery life. I've tested this for weeks. Regardless, Overclocking consumes more battery. Proven fact, More voltage + Battery runs hotter = Faster battery drain.
 
redfield88 said:
In all honesty, there's a lot of information out there about the Android OS that's completely wrong. For example, using a task killer isn't a good idea at all. Most applications automatically re-open after being killed, using more CPU to restart that application. Task Killers = Bad unless you know for sure an application is poorly coded and is acting up. I use Watchdog and haven't turned back to a task killer.
HTG Explains: Why You Shouldn
Click to expand...
 
stayboogy said:
it's just a fact that changing cpu freq uses more battery power than keeping it at one freq, regardless how frequently the change takes place--that's what i meant

also, there's nothing wrong with tasks killers. and many apps do not restart after being killed if you are using a good app killer like the one i've supplied

the only ones that restart are system apps and services--but there are ways around this too. i have google play installed on my device right now, but it's never running and when i kill it, it doesn't restart. most people cannot say the same thing, and it has to do with how you are killing your apps

when apps run in the ram they eat up the battery, period. the more that are running continuously and transferring data continuously, the more the battery drains.

also background data will kill a battery fast as well

you've been testing for weeks, i've been using and testing for months lol :D

and agreed, useless and incorrect android information abounds, even by people here and other forums who think they know what's up

that's the main reason why when i disagree with someone it's because i actually know what i'm talking about the majority of the time (but i'm not perfect or all-knowing) and i'm not reading a stupid post by someone who's completely oblivious to what's really going that google found for me in a simple search lol

more than 60% of all information i've ever read has been DEAD WRONG

even more so when it comes to scripting--like how dumb and useless busybox is in everyone's scripts
Click to expand...
Android is made to fill up as much of the RAM as it can defined by the minfree values. It also releases applications from RAM depending on how active you are using the app. Using a task killer to flush the RAM takes a bit of CPU each time you do it. Android is an "event" operating system. Depending on what you're doing with your phone, depends on is running. Sure you can go through all the events to stop an application from automatically starting to save on RAM. However, Android OS will just fill the RAM up with other applications. Basically a never ending fight, all that task killing is using more battery than just leaving them in the RAM. Certain applications, let's pick on facebook for a moment, use an intense amount of CPU and RAM at any given time. So using a task killer on these sort of applications isn't a "bad" idea at first glance, unless the application just automatically restarts after it's been killed, which facebook does. So you just used CPU to kill the application, and even more CPU because the application decided to restart itself. Not every user out there knows they can remove these events to stop an application from restarting and are simply wasting their time using a task killer.

I do agree though, apps staying in RAM are using battery. I prefer to the lesser of two evils though. Killing an application and having it restarted is just counter productive and technically uses more battery consumption.

You're a very smart dev stayboogy. You're the only reason I've stayed active on this forum. I appreciate all the work you do for us.
 
redfield88 said:
Android is made to fill up as much of the RAM as it can defined by the minfree values. It also releases applications from RAM depending on how active you are using the app. Using a task killer to flush the RAM takes a bit of CPU each time you do it. Android is an "event" operating system. Depending on what you're doing with your phone, depends on is running. Sure you can go through all the events to stop an application from automatically starting to save on RAM. However, Android OS will just fill the RAM up with other applications. Basically a never ending fight, all that task killing is using more battery than just leaving them in the RAM. Certain applications, let's pick on facebook for a moment, use an intense amount of CPU and RAM at any given time. So using a task killer on these sort of applications isn't a "bad" idea at first glance, unless the application just automatically restarts after it's been killed, which facebook does. So you just used CPU to kill the application, and even more CPU because the application decided to restart itself. Not every user out there knows they can remove these events to stop an application from restarting and are simply wasting their time using a task killer.

I do agree though, apps staying in RAM are using battery. I prefer to the lesser of two evils though. Killing an application and having it restarted is just counter productive and technically uses more battery consumption.

You're a very smart dev stayboogy. You're the only reason I've stayed active on this forum. I appreciate all the work you do for us.
Click to expand...

thanks for the kind words.

i use my task killer and maybe once a day, maybe one task will restart itself--usually my email client--and that's it. at any typical moment on any day, i have 250-300mb free ram. so it's not getting filled up by the system. my phone's uptime is over 36 hours right now (2 hours on a fresh charge, but not rebooted in over 36h) and i have 275mb free ram.
 
I have flashed several roms over the course of the past year or so, trying to find that one rom that fits my style of use. I would have to say that I've always wandered back to Metro everytime. Thank you stayboogy for this rom, I can say it is a true favorite. Now I did read the warning about kernel switching, but I chose to use Anthony's kernel to see the overall effect on the rom. I thought, "Loss of wifi? Pfft, I don't use it enough to rely on it."

I have to say that I was impressed that the wifi was the only driver to fail, and I'm still evaluating how the rom is handling the new kernel. What I'm wondering is, in order to get the driver back up and running, can I get away with taking a shortcut and just find a copy of the driver to replace the rom's? Or are we talking about a driver rebuild to resolve compatability issues within the rom? On a side note, is there an app you prefer to have used on this rom to keep the ram use low? I would use the autostarts app that came with it, but I am worried about bootlooping the phone because one app is relying on another. Any suggestions?
 
Edit:

Question removed. I've figured out my problem. I should have installed the stock ROM first, then this one on top of it.
 
You must log in or register to reply here.
Back
Top Bottom