[Android Software/Hacking General [Developers Only]] lowpro3210:
HTC Evo Shift (speedy)

Using Recovery CWM / and TWRP on occasion (was told dreads recovery isn't compatible)

Initially when the dev was starting off fresh making the script, I was running Jellybean 4.12 with Jellybelly Omega v1.1 http://xdaforums.com/showthread.php?t=2024749

I PM'd the dev of the Jellybelly ROM "bilgerryan" just to make sure the ROM he built would be compatible with EO's script and he said yes, he was saying nothing BUT good things about EO and his work "There aren't any tweaks that would interfere. Flash away. Exit_Only's tweaks are great" :good:

The ROM IS deodexed and was told by EO that using deodexed ROMs could cause issues though (I was experiencing longer than normal boot times (roughly 2-3x longer than normal) while the script was installed). Unfortunately I don't recall what version I was using (I think DI 3.0, maybe), it was an earlier release which installed fine, though I was still experiencing HUGE battery drainage within time even when the phone was in standby. Upon using other versions I would get the good old boot loop issue (but made a NANDROID so no biggie). I didn't try every new test that was released, just a couple..again, unfortunately I don't recall the test #s I was trying at the time :(

I purchased a new battery from Anker just to double check and make sure the battery wasn't bad since it was 2+ years old and I did abuse it quite often; so I got a new battery and eliminated that. I have tried other JB ROMs compatible with my device such as Evervolv (stable and the nightly builds), Provision, and Carbon. I experienced the same issue of above with each ROM (I believe they are all deodexed). And out of the ones I tried, IMO I enjoyed JellyBelly the most and had the least amount of issues with. I am aware the evo shift is a bit of an old phone (but LOVE the qwerty keyboard and can't upgrade thanks to sh!tty sh!tty bang bang Sprint; not until next year) and is running a 1core snap dragon CPU processor which is hard to believe it can even run JB (but that processor can be overclocked like CRAZY).

Since then I made the change back to GB 2.35 running NewRUNNY ROM which I've NEVER seen so many customization tools ever in a ROM before. That ROM too is deodexed. There is an option in the NewRUNNY control panel to odex the framework and system, so I can gave that a whirl..upon it doing a force close for every app (which it states it will do), the phone boots. I tried install the latest official build of EO's DI and got stuck at splash; I installed the sqlite for my version and cleared cache and dalvik too.

AFTER flashing from JB back to GB, I came across a odexing program to odex your framework and system. https://www.xda-developers.com/android/odex-your-rom-directly-from-the-device/ (page doesn't seem to load for me today, the page was loading up fine for me yesterday unless there are multiple apps to do so and I just grabbed the wrong link) another link http://classic.cx/android/dexo-universal-odex-tool/ . In anyone's opinion, would it be worth going back to JB 4.12 using JellyBelly omega v1.1 (fav out of all available JB ROMs) and trying to odex the deodexed ROM to see if it would work that way?

I read the OP over and over in regards to requirements and I do meet them all. That's why I emailed the dev of the JellyBelly ROM just to verify his ROM would work with EO's script and again, he said yes.

I did notice a lot of the people who are using this script, have samsung devices? Is that script made specifically for samsung phones only :( because it never mentions anywhere in the OP/requirements about Samsung phones (it's listed under "Android development" so figured I would try his script. I have been crackflashing NON stop for 2 weeks now and finally realized I maaay have a problem :eek:

IF this script is compatible with other phones which I'm praying it is; it would be super groovy if someone could please help me to get EOs flawless script working on my device because battery life SUX! On a 2nd thought, is there ANY way how I could have a flawed phone causing battery issues?

I used -stephen (stericson) busybox app https://play.google.com/store/apps/details?id=stericson.busybox to make sure I have the latest version of BB which I do.

At this particular time, I frankly could care less whether I am on GB or JB using WHATEVER ROM, as long as I could get EOs script to work with my phone will work. I am baffled as to how he can make a script to get such amazing battery life when the manufacturers of the phone can't even do the same :laugh:

I am aware there are apps on googleplay that in return can provide some of the same ideas I suppose such as saving battery life; but how can an app save battery life while it's constantly running the background unlike EO's script which is why I dont use any other battery saving apps except for greenify.

I use SuperSU which is working fine.

I am MORE than willing to contribute and make a donation since EO does this on his spare time and from what it seems, EVERYONE is BLOWN away with what their phones are capable of doing and the unbelievable battery life everyone is achieving. EO does NOT need to share his work with us but yet does and helps SOOOO many people out. I am more than grateful of having amazing devs such as himself here on XDA to help the community out with bettering their phones.

Could someone maybe take a quick glance at the Jellybelly Omega v1.1 ROM I prefer to use http://d-h.st/5fx and see if the kernel (made by strapped365) and ROM are good for using? I know the dev of the ROM said yes, but want to see if anything else is causing issues.

Appreciate whatever help is coming and thank you for the time.

P.S. I know it's an app, but what is your impression on "greenified" https://play.google.com/store/apps/details?id=com.beyondem.greenified not to be confused with greenify