Root [ROM] rubiX Focused 1.0 by drod2169

[sephtin]

So I've been trying to nail down some info on this Brightness glitch:

- Apparently, it seems to occur after an indeterminate amount of time with the screen off. I have yet to nail an exact time down.

- The screen always gets brighter regardless of what brightness the screen is initially set to. Under no circumstances was I able to find a setting that would trigger a "screen dimming" glitch.

- When the glitch occurs, neither my widgets nor the actual Display menu reflect the change.

- There have been occasions where I've been on a phone call for a significant amount of time, only to find that the glitch had occurred (screen got brighter) when I hung up. I do not have the phone set to lock the screen during a phone call. To me, this indicates that it has less to do with the lock screen, and more to do with something that gets triggered when the screen goes off. I could be wrong about this though, so please don't completely discount a problem with the lock screen.

Have you (or Drod) found any further info on this? I love this ROM for it's incredible speed and efficiency, but having my screen constantly jump up from 25% to 50% is destroying my battery life. If it helps, I came from a "clean" 2.2 Full SBF. Maybe this glitch only affects people who used the SBF to upgrade to the official 2.2?

Well, it's a long shot, but...
Focused 1.x Battery issues- Please Read -- sephtin.com

On droidforums, a handful of people have been working on this issue, and a couple believe they've "solved" the "bad battery" issue...
Screen brightness is a ginormous battery drain.. maybe that fix affects this?

I have not had bad battery really.. mine's been awesome. :S All I can do is reference the last .. 10 or so pages perhaps of the 1.6 thread on droidforums, where there is a pretty large discussion on battery life?

Hope this helps!

 

[dabomb224]

Thanks, I will give this a try. I am in a strange category, where I received phenomenal battery life on Focused 0.5 with the 2.2 leak, but now that I'm on Focused 1.6 with the 2.2 ota, my 4-5 hours of screen on time has been cut in half. I truly hope that it is only due to the brightness issue, as I'd hate to lose the clean cut 1.6 to go back to 0.5.

 

[Flying_Hellfish]

Thanks, I will give this a try. I am in a strange category, where I received phenomenal battery life on Focused 0.5 with the 2.2 leak, but now that I'm on Focused 1.6 with the 2.2 ota, my 4-5 hours of screen on time has been cut in half. I truly hope that it is only due to the brightness issue, as I'd hate to lose the clean cut 1.6 to go back to 0.5.

I was on 1.6 all day yesterday and in the first hour my battery dropped 30%. I restarted the phone and it was more stable but still not the battery life I was seeing on the OTA or other ROMs

 

[sephtin]

I was on 1.6 all day yesterday and in the first hour my battery dropped 30%. I restarted the phone and it was more stable but still not the battery life I was seeing on the OTA or other ROMs

See, and that's really weird! I have had much better battery life on Focused than I had with stock, or other ROMs I've tried...

Try the above for battery life, and let us know if it works or not for you....

 

[Flying_Hellfish]

See, and that's really weird! I have had much better battery life on Focused than I had with stock, or other ROMs I've tried...

Try the above for battery life, and let us know if it works or not for you....

that is almost to a T what I did for my install. Except I used a backup I have of OTA 2.2 rooted with bootstrap installed right after I ran the SBF the last time.

The only thing on that list I didn't do was the dalvik cache. Oh, and did a restore via titanium of my apps/data (not system settings) before logging into google at all. I really hope that it isn't titanium. reconfiguring all my apps isn't worth my time right now.

 

[dabomb224]

I did the same as you, except I only restored Apps, not Data. Restoring Apps only is supposed to be safe, right?

 

[sephtin]

I did the same as you, except I only restored Apps, not Data. Restoring Apps only is supposed to be safe, right?

Should be... Some apps install some weird stuff... I don't know how titanium backup handles that.
Example, If I check my mounts, angrybird appears to have added a new mount point... I think it did this by editing fstab (system file), but not really sure. :S To be honest, I don't know how a backup program would back this up, and I don't know how restoring the app without this change would affect the app, or what other issues it could cause.

So.. in theory, sure, backup programs are great. In reality, the less restoring you do, the less issues that will be caused by restoring *shrug*

 

[Flying_Hellfish]

Most of the problems I have seen with people restoring from TB are when they restore system settings into a ROM that may not support those settings then it causes strange issues. Not restoring my angry birds data might kill me. lol

If I get some time this weekend maybe I will try it from scratch but we will see.

 

[androy]

The only app that I restore both app and data is Angry Birds, using TB. I've installed the same Angry Birds data on Apex, Fission, rubiX Blury, and rubiX Focused.. I've had no problems at all with it.

I use TB and install just the app for the rest of my backups.. I usually use the app's backup feature(if it has one) to install settings. So far, I've had no issues.

 

[sephtin]

Most of the problems I have seen with people restoring from TB are when they restore system settings into a ROM that may not support those settings then it causes strange issues. Not restoring my angry birds data might kill me. lol

If I get some time this weekend maybe I will try it from scratch but we will see.

Lol.. I know, right?
Ya.. so bad example. :S But you get the idea... that's just one of many...

 

[sephtin]

The only app that I restore both app and data is Angry Birds, using TB. I've installed the same Angry Birds data on Apex, Fission, rubiX Blury, and rubiX Focused.. I've had no problems at all with it.

I use TB and install just the app for the rest of my backups.. I usually use the app's backup feature(if it has one) to install settings. So far, I've had no issues.

And this is the story with most.. no issues at all.
Then, there are the stories of people who have issue after issue, that can be traced back to restoring from Titanium.. *shrug* Though, I totally agree that these are almost always attributed to someone restoring settings/system.
Funny, but when the thread, or post starts, it's always the fault of the ROM... It's just good that people know it *can* cause issues... *shrug*

 

[Flying_Hellfish]

And this is the story with most.. no issues at all.
Then, there are the stories of people who have issue after issue, that can be traced back to restoring from Titanium.. *shrug* Though, I totally agree that these are almost always attributed to someone restoring settings/system.
Funny, but when the thread, or post starts, it's always the fault of the ROM... It's just good that people know it *can* cause issues... *shrug*

I'm not blaming the ROM in any way.

System settings to me are like trying to migrate from one version of windows to another and keep the exact same look/feel. The thing is it is nearly impossible and I know it can cause problems so I don't even back them up to be honest.

I will give rubix another shot. I tend to flash my phone every 4-5 days at this point so I will be back to it before too long. I just don't have the time during the week to manually install everything right now.

 

[Coolguy71261]

I liked the app launch screen plus out of no where. I was getting stcores as highas 2000+ went. To 1.6 hated it now on 1.0

 

[dabomb224]

a

 

[ekyle]

Awesome. Thanks for the great support.

By the way, is there a fix for the UID 1001 sensor issue? On every ROM except Fission 1.2 UID 1001 continues to run (spare parts=>sensor usage) after making a call. Not sure if the effect on battery life was huge, but I went from 25 hrs + easily to about 20 hrs.

In fission, the "dialer" sensor stops after the call ends. Since drod also worked on fission, I'm hoping there's a fix!

Did you ever resolve the issue with UID 1001 over utilizing the sensor?

 

[WalmartSecurity]

Did you ever resolve the issue with UID 1001 over utilizing the sensor?

Well not a fix, but I switched from Apex to rubiX Focused 1.6 and I haven't had a problem with it up till 1.9.0.

I'm going to try out fission 2.4.2 (just upgraded up to 2.3.340) and I'll let you know how that goes.

 

[ekyle]

Well not a fix, but I switched from Apex to rubiX Focused 1.6 and I haven't had a problem with it up till 1.9.0.

I'm going to try out fission 2.4.2 (just upgraded up to 2.3.340) and I'll let you know how that goes.

I think it has omething to do with the dialer. I tried to install dialed one and rename the blur phone apk but I didn't get any service ater that so that didn't work...

 

[sephtin]

I think it has omething to do with the dialer. I tried to install dialed one and rename the blur phone apk but I didn't get any service ater that so that didn't work...

Dialer one isn't a complete replacement for the dialer.. it's a front-end dialer actually.

The sensor issue has to do with a slight framework change, and should be resolved in the next version of Focused. Drod mentioned that perhaps by the end of the month, 1.9.5 should be released.

 

[ekyle]

Dialer one isn't a complete replacement for the dialer.. it's a front-end dialer actually.

The sensor issue has to do with a slight framework change, and should be resolved in the next version of Focused. Drod mentioned that perhaps by the end of the month, 1.9.5 should be released.

I'm new to custom ROMs. Is Focused another ROM? I'm using ApeX right now.

EDIT: derp. Just read the title of the post. Obviously a custom ROM. what is the differnce between that and ApeX?

 

[sephtin]

I'm new to custom ROMs. Is Focused another ROM? I'm using ApeX right now.

EDIT: derp. Just read the title of the post. Obviously a custom ROM. what is the differnce between that and ApeX?

Every ROM has lots of little differences. The BIGGEST difference between Apex, and Focused, is that Apex uses the stock MotoBlur framework at it's core (which allows some of the blur components to continue to function correctly).
Focused on the other hand, uses a framework that was derived mostly from the Moto SDK, which is nearly completely blur-less. 1.9.5 takes it a step further than previous versions, even less Moto components.

Apex and Focused both replace lots of the apps with AOSP versions, and others...

If you take a nandroid of what you have, it's pretty painless to try another ROM and get back to what you have if you decide to go back! (Nandroid backups are your friend!!!)

More info on Focused (and other works by drod2169) here:
Drod2169 - X - Droid Forum - Verizon Droid & the Motorola Droid Forum

Latest version here:
rubiX Focused 1.9.5 - Droid Forum - Verizon Droid & the Motorola Droid Forum

Merry Christmas/Happy Holidays (whichever is applicable).