Most common causes:
LCD Density changes (almost certain reboots)
Overclocking/undervolting
Theme
Restore from backup
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [ROM] rubiX Focused 1.0 by drod2169
- Thread starter mezdup
- Start date
-
- Tags
- motorola droid x
Most common causes:
LCD Density changes (almost certain reboots)
Overclocking/undervolting
Theme
Restore from backup
soapinmouth
Android Enthusiast
I have no theme, am not overclocked or undervolt (stock), and I did not restore from any backups.....on the other hand, it reboots when I unlock the phone most the time, so the lcd auto brightness could possibly do it.
Flying_Hellfish
Android Enthusiast
I think the unlock 1/2 reboot error is in a bunch of ROMs right now. I think some people even have that issue on stock 2.2
soapinmouth
Android Enthusiast
Rubix 1.6 is out try that one
Airmaxx23
Android Expert
You can look in the build.prop file (using root explorer) to be sure that the stagefright settings are set to false, it sounds like the app isn't actually changing the settings. With the Droid X you can kind of tell what range a linpack or quadrant score should be (roughly) based on the other score. A 1800 quadrant should get a linpack around 18.00, and 15.99 should be getting around 1600ish quadrant score. The stagefright mod will add about 600-800 points.
Just curious, what was the reasoning behind switching from the Launcher used in Focused 1.0 to ADW Launcher?
Also, I noticed that coming from 0.5 to 1.0, I lost the ability to set custom ringtones for different contacts, as well as the ability to always send specific contacts straight to voicemail. I assume that this is because these were Blur features. Are there any alternatives to Blur that would allow me to get these back? (I assume that putting back only those features would be a bit difficult)
EDIT: Is Focused 1.6 the continuation of Fission? I noticed that the Fission team had mentioned that their ROM would eventually become Rubix. If so, does that mean that this is completely AOSP (not even a hint of Blur)?
Also, I noticed that coming from 0.5 to 1.0, I lost the ability to set custom ringtones for different contacts, as well as the ability to always send specific contacts straight to voicemail. I assume that this is because these were Blur features. Are there any alternatives to Blur that would allow me to get these back? (I assume that putting back only those features would be a bit difficult)
EDIT: Is Focused 1.6 the continuation of Fission? I noticed that the Fission team had mentioned that their ROM would eventually become Rubix. If so, does that mean that this is completely AOSP (not even a hint of Blur)?
I'll try to answer. Drod could probably answer better than I can.. but *shrug*
--Launcher choice:
Focused 0.5 had ADW, iirc. Drod prefers it, it's not blur, and it's not much "heavier" than Launcher2 (stock in Focused 1.0).. still miles lighter/less laggy/sluggish than something like Launcher Pro.
--Custom ringtones is an issue with the framework of Focused 1.x, and Fission. No known fix yet, workaround is to use a ringtone application like RingDroid to set custom ringtones... I HAVE heard that if a contact has multiple numbers assigned, it sometimes/often won't work if the contact calls from a number that isn't primary. Either way, it's a known issue.. here's an unofficial list of issues I put together:
UNOFFICIAL Known Issues
Ok, restored my stock 2.2 nandroid and installed Rubix 1.6. So far, I'm loving the speed (although for some reason, I'm not a fan of ADW... too much choice maybe?).
One question I had came up while playing around with the built in JRummy overclock script in Terminal Emulator (which was a very nice touch BTW). Specifically, I was wondering if my Undervolt/Overclock settings automatically get set at boot (upon my next reboot), or do I need to select a special option for that. Currently, I only went into the terminal and selected ULV and the "stock" frequencies (although I recall stock being 300000, not 350000).
EDIT: I have also been experiencing the "Brightness Glitch", where my screen brightness jumps way up on its own at random intervals. Ironically, I left Apex and installed this primarily to escape this glitch (which I was experiencing on Apex as well).
Maybe the fact that I was experiencing this problem with both ROMs indicates a problem with a common modification?
One question I had came up while playing around with the built in JRummy overclock script in Terminal Emulator (which was a very nice touch BTW). Specifically, I was wondering if my Undervolt/Overclock settings automatically get set at boot (upon my next reboot), or do I need to select a special option for that. Currently, I only went into the terminal and selected ULV and the "stock" frequencies (although I recall stock being 300000, not 350000).
EDIT: I have also been experiencing the "Brightness Glitch", where my screen brightness jumps way up on its own at random intervals. Ironically, I left Apex and installed this primarily to escape this glitch (which I was experiencing on Apex as well).
Maybe the fact that I was experiencing this problem with both ROMs indicates a problem with a common modification?
akdoyle
Newbie
I am new to rubiX rom.....is there any way to link contacts together, for some reason there is double contacts for some people....one for the google contact and another as a facebook contact, is there any way to merge them together like on the stock phone? I love this ROM so far, but this is very annoying....any help or suggestions would be greatly appreciated!!
__________________
__________________
Can't link, but can join:
Open a contact, edit it, Menu> join. (Think from memory.. something like that...
akdoyle
Newbie
chrlswltrs
Extreme Android User
Flying_Hellfish
Android Enthusiast
So, I decided to give this a go last night. As with every install I have a few steps I go through to get it the way I want it and I always calibrate the compass but it is FC on me every time I open it. Anyone else with this issue or have a fix?
imronburgundy
Android Enthusiast
Are there any themes for this rom or do most normal themes work on it?
There's an awesome theme that you can google called Black Juice for rubiX 1.6. It takes several elements of neXTheme and improves on them, with a blue circle battery indicator and some new Settings menu icons. Plus, there's that awesome, multi-colored Rubix Cube that drops down with the notification bar.
Very cool.
Very cool.
Themes replace framework files, and any apps that have been themed with a themed version of whatever app the theme was based on...
So, if a theme was based on a Blur ROM or install.. then you get that framework/apps back on your phone... Which can cause all kinds of problems for any ROM that's not based on the stock (blur) framework... like fission/Focused.
List of themes (probably slightly incomplete... but *shrug* starting place)...
The Themes for 1.0 will work, but MAY remove the 10% battery increments:
[ROM] Zero Blur! Zero Lag! rubiX Focused 1.0 - Droid Forum - Verizon Droid & the Motorola Droid Forum
Themes for 1.6:
rubiX Focused 1.6 - Droid Forum - Verizon Droid & the Motorola Droid Forum
Unofficial list of known issues for Focused 1.6:
UNOFFICIAL Known Issues – Focused 1.6 — sephtin.com
In particular, you're interested in:
Flying_Hellfish
Android Enthusiast
I'm getting the 1/2 reboot issue on Rubix just like on ApeX. I guess I shouldn't be surprised since people are saying they get it on stock OTA as well.
Ya, If getting tons of reboots, only other suggestion, is make sure that you haven't changed the LCD Density setting via mod or whatever. It has also been shown to cause reboot issues with Focused/Fission.
Flying_Hellfish
Android Enthusiast
I have not changed the pixel density at all. Oh well
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?
- 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?