[ROM][JB.16][CDMA] BloodRage v1.3 *Update* 9/9

rnh wrote:

CharmPeddler wrote:So far so GREAT!. installed late last night. I came from Rage 3.3 that has been SUPER laggy and glitchy (i dont think it was the ROMs fault), so i'm hoping that this one stays running great.

Question: I found the Power Toggle app and love the customization options, BUT how do i customize the power toggle that is already baked in to the shade?

You can remove the baked in toggles by flashing a battery zip.  There are two found under themes and mods in the black widow hd2 rom on droidrazr.com.
  To everyone else -1. how is the battery life compared to rage? Have any more battery tweaks been made in the rom? I've just installed bloodrage .
                            2. When using set cpu if the profile is set to screen on does that mean it isn't functioning when screen is off?

1. Thanks for the info!!
2. Pretty similar as of now but the next update should improve battery a bit more. Obviously if you oc battery life will suffer some.
As for set CPU you can create a separate profile for screen off that is to your liking/needs.

Just for the record an update per droidrzr.com post. I've re-started with wiping the slot and running this ROM exclusive to not adding any Nandroid Restore from another ROM, only using TIBU to restore User only apps. So far, working wonderfully. Looking forward to any improvement to battery life, although I do OC. What is a good "Screen OFF" profile to run in SetCPU?

lazer wrote:Just for the record an update per droidrzr.com post. I've re-started with wiping the slot and running this ROM exclusive to not adding any Nandroid Restore from another ROM, only using TIBU to restore User only apps. So far, working wonderfully. Looking forward to any improvement to battery life, although I do OC. What is a good "Screen OFF" profile to run in SetCPU?

I'm working on an update that should improve battery and smoothness even more. The oc does effect battery some. I personally set my screen off profile at 800 max 300 min. I am very happy you like the ROM and I think you will really like the update.

jl90x wrote:

lazer wrote:Just for the record an update per droidrzr.com post. I've re-started with wiping the slot and running this ROM exclusive to not adding any Nandroid Restore from another ROM, only using TIBU to restore User only apps. So far, working wonderfully. Looking forward to any improvement to battery life, although I do OC. What is a good "Screen OFF" profile to run in SetCPU?

I'm working on an update that should improve battery and smoothness even more. The oc does effect battery some. I personally set my screen off profile at 800 max 300 min. I am very happy you like the ROM and I think you will really like the update.

Great news! Just applied that screen off profile. Will the update require full wipes or just caches? Thanks  

Most likely just the caches. I gotta test that first though. I hope to have the update ready by this weekend.

Hrmmm, I've had two lock ups today where you can't wake the phone to come on but you can hear it on keypresses.

lazer wrote:Hrmmm, I've had two lock ups today where you can't wake the phone to come on but you can hear it on keypresses.

Try adjusting the max frequency to 1300. Its most likely an adverse reaction to oc. I haven't had any lockup issues in test versions or on the release version.

jl90x wrote:

lazer wrote:Hrmmm, I've had two lock ups today where you can't wake the phone to come on but you can hear it on keypresses.

Try adjusting the max frequency to 1300. Its most likely an adverse reaction to oc. I haven't had any lockup issues in test versions or on the release version.

Thanks, I assume you meant edit down that last line to 1300 in Smanager - save, reboot and fix in SetCPU which I just did. Thanks... We shall see  

lazer wrote:

jl90x wrote:

lazer wrote:Hrmmm, I've had two lock ups today where you can't wake the phone to come on but you can hear it on keypresses.

Try adjusting the max frequency to 1300. Its most likely an adverse reaction to oc. I haven't had any lockup issues in test versions or on the release version.

Thanks, I assume you meant edit down that last line to 1300 in Smanager - save, reboot and fix in SetCPU which I just did. Thanks... We shall see  

Exactly. I had that issue on ragerom. After messing with the oc it went away.

Well since lowering the frequency to 1300, I've now had another two lockups since then and this morning. The first one came during a phone call where it just locked up and dropped the call, luckily the person was able to call me back on my home phone connect box or I wouldn't have even realized in time the phone completely locked and dropped the call as I was still talking. :-/

2nd one came upon trying to wake my phone with the power button this morning whilst on charger. The LED was flashing for notifications, and I could sense the haptic feedback when trying to press various buttons for a screen response to no avail. Had to perform the 3 finger salute to get it back re-booted.

No idea what's going on. My phone doesn't seem to like certain ROMS and I don't think now it's an OC issue as I didn't have this problem occur on a previous ROM overclocked.

Well if you had run ragerom without issues previously there isn't enough difference yet for the ROM to be the issue. Which gov/ scheduler are you using? You may even have an app acting up try wiping cache and dalvik. If I remember correctly you had some issues with the overclocking on rage as well.

jl90x wrote:Well if you had run ragerom without issues previously there isn't enough difference yet for the ROM to be the issue. Which gov/ scheduler are you using? You may even have an app acting up try wiping cache and dalvik. If I remember correctly you had some issues with the overclocking on rage as well.

Yea I did on Rage even worse where the phone wouldn't boot back up without performing a "dirty flash". I'm using Hotplugx or whatever and sio. It could be an app, who knows, although I'm running with the same apps as my former ROM that was OC'd and the only issue I was having with it was not receiving PUSH gmails correctly and timely.  

Hotplugx has known issues! Try another gov. I use pegasusq. Sio is fine. I hope that's all it is.

jl90x wrote:Hotplugx has known issues! Try another gov. I use pegasusq. Sio is fine. I hope that's all it is.

Thanks, Just checked and I actually had hotplug as my main and then in my profiles I think it was hotplugx. Not sure how I screwd that up.  \

Changed everything to pegasusq in SetCPU, we shall see.

Cool! Hope is all it is. Also you said you were running blurry. How much space do you have allocated for each slot. You may have space issues.

jl90x wrote:Cool! Hope is all it is. Also you said you were running blurry. How much space do you have allocated for each slot. You may have space issues.

2gbs for each. I haven't had any "low memory" warnings or anything of the sorts which I did have a while back when mistakenly trying a few ROMS in 1Gb slots with all my apps.  

Well that could be OK depending on the amount of apps you install. Even though your not getting a warning space issues can show in weird ways.

jl90x wrote:Well that could be OK depending on the amount of apps you install. Even though your not getting  a warning space issues can show in weird ways.

According to TIBU, currently running 311 user & system apps.  

Holy shit!!! Lol!

Yea, I'm a bit of an "App-oholic"....  

Like me.....I have 297

I might have mis-spoken on my total number of apps. Thinking I read in TIBU the grand total counting ones I haven't restored because after doing a Dalvik wipe, I'm sitting on the boot screen with the count total @ 168.

I have less than 10 I didn't include in the ROM!!

Be prepared to get even bloodier .... bloodrage updated!!!!!

UPDATE IS LIVE!!!!!
THIS IS A MAJOR UNDER THE HOOD UPDATE SO PLEASE DO FOUR WIPES OR DO NOT REPORT BUGS!
GIVE THE SYSTEM TIME TO SETTLE IN BEFORE OC...USUALLY A COUPLE HOURS OR A FEW REBOOTS SHOULD DO IT.
THANK YOU ENJOY!!!