What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

rubiX Focused 1.9.5

I'm having a small issue..I re-installed because of poor battery life, wipe data/ cache, but when my phone boots up it wont re-install apps like usual via sync...

You can always check if Market is bringing apps back, by looking at MyApps in the market. They should say "Downloading" next to all of them if they're attempting to restore.

If that's not happening.. you could try to boot back to recovery, wipe data/cache one more time, and try a reinstall.. it ***should*** work. :S

Wait, I just noticed the install instructions don't say to wipe cache, only data wipe...

It says wipe data/factory reset because that option in cwm wipes cache as well
 
Battery Life Observation

I am currently running Rubix 1.9.5 with Linear Theme

I turn data off at night before I go to sleep to save battery. Back when I was running 1.9.0 I would be able to do this and still be at 100% when I woke up. Now with my current setup I wake up at 90%. I know it's not too big of a deal but it does tell me my battery life is worse with current setup. I'm going to SBF, wipe data/cache/davlik/battery stats and run 1.9.5 stock to test if it's the theme.

Unless anyone has any theories as to why this is the case, I'll be back to report the results in the New Year.
 
I don't have all of the information either.. but here's what I understand was he issue, and why steps were taken to get to where things are at now.

There WAS a bug.. in that if the timer for pin lock was set differently than the screen timeout, then there was a huge delay before the pinlock would come up (someone correct me if I misunderstood exactly what the issue was....).

Anyway, that issue affected EVERYONE (not just the minority that use pin-lock), and lots of people complained... Since there isn't an easy fix for that issue, the timer was removed to resolve it.

Hope that clears it up. If you're not happy with that change, feel free to contact Drod/Kejar with your concerns.

I guess I just never experienced that bug...though I did jump from 1.6 to 1.9.5 so maybe it was in 1.9.0...??

I LOVE the rom and appreciate all the hard work....just sucks having too put in my pin all the time. I wouldn't even have a pin if my job didn't require it for the Exchange connection. I'll give it a week or so to see if I get used to it.
 
I don't have all of the information either.. but here's what I understand was he issue, and why steps were taken to get to where things are at now.

There WAS a bug.. in that if the timer for pin lock was set differently than the screen timeout, then there was a huge delay before the pinlock would come up (someone correct me if I misunderstood exactly what the issue was....).

Anyway, that issue affected EVERYONE (not just the minority that use pin-lock), and lots of people complained... Since there isn't an easy fix for that issue, the timer was removed to resolve it.

Hope that clears it up. If you're not happy with that change, feel free to contact Drod/Kejar with your concerns.

I guess I just never experienced that bug...though I did jump from 1.6 to 1.9.5 so maybe it was in 1.9.0...??

I LOVE the rom and appreciate all the hard work....just sucks having too put in my pin all the time. I wouldn't even have a pin if my job didn't require it for the Exchange connection. I'll give it a week or so to see if I get used to it.

I was on the previous version of Focused, and before that I was on Blurry. As someone whose company has an Exchange security policy that requires a pin, I had no issues at all in that space on those releases. My pin timeout was set to 10 minutes and my screen timeout was 1 minute. If I manually turned off the screen (which I usually do), I could freely turn it back on and only have to slide-unlock it. But if I didn't touch it for 10 minutes, I would have to enter the pin. But this version is as you describe; pin lockout every time screen is turned off.

I looked around for a method to just defeat the passcode requirement but it seems a bit difficult to do.
 
Last edited:
I am currently running Rubix 1.9.5 with Linear Theme

I turn data off at night before I go to sleep to save battery. Back when I was running 1.9.0 I would be able to do this and still be at 100% when I woke up. Now with my current setup I wake up at 90%. I know it's not too big of a deal but it does tell me my battery life is worse with current setup. I'm going to SBF, wipe data/cache/davlik/battery stats and run 1.9.5 stock to test if it's the theme.

Unless anyone has any theories as to why this is the case, I'll be back to report the results in the New Year.

I really dont understand why people dont just charge their phone at night....I do, always have...leave the phone on and wake up to 100% charge every morning :)
 
I am currently running Rubix 1.9.5 with Linear Theme

I turn data off at night before I go to sleep to save battery. Back when I was running 1.9.0 I would be able to do this and still be at 100% when I woke up. Now with my current setup I wake up at 90%. I know it's not too big of a deal but it does tell me my battery life is worse with current setup. I'm going to SBF, wipe data/cache/davlik/battery stats and run 1.9.5 stock to test if it's the theme.

Unless anyone has any theories as to why this is the case, I'll be back to report the results in the New Year.

I really dont understand why people dont just charge their phone at night....I do, always have...leave the phone on and wake up to 100% charge every morning :)

Yeah, I have 2 chargers at home, one in the car, and one at work. I can be plugged in most of the time I'm using my phone. The only times I don't plug in when I CAN are the times I'm testing battery life for Drod :)
 
I am currently running Rubix 1.9.5 with Linear Theme

I turn data off at night before I go to sleep to save battery. Back when I was running 1.9.0 I would be able to do this and still be at 100% when I woke up. Now with my current setup I wake up at 90%. I know it's not too big of a deal but it does tell me my battery life is worse with current setup. I'm going to SBF, wipe data/cache/davlik/battery stats and run 1.9.5 stock to test if it's the theme.

Unless anyone has any theories as to why this is the case, I'll be back to report the results in the New Year.

I really dont understand why people dont just charge their phone at night....I do, always have...leave the phone on and wake up to 100% charge every morning :)

Yeah, I have 2 chargers at home, one in the car, and one at work. I can be plugged in most of the time I'm using my phone. The only times I don't plug in when I CAN are the times I'm testing battery life for Drod :)

Lol, I normally only charge at night....and periodically when Im driving in the car.

Using this ROM, my setup...LV overclock and an extended battery....I can go all day without charging. And I use the phone quite a bit during the day, running 2 companies.....it gets used.
 
I really dont understand why people dont just charge their phone at night....I do, always have...leave the phone on and wake up to 100% charge every morning :)

Yeah, I have 2 chargers at home, one in the car, and one at work. I can be plugged in most of the time I'm using my phone. The only times I don't plug in when I CAN are the times I'm testing battery life for Drod :)

Lol, I normally only charge at night....and periodically when Im driving in the car.

Using this ROM, my setup...LV overclock and an extended battery....I can go all day without charging. And I use the phone quite a bit during the day, running 2 companies.....it gets used.

Yeah I've tested mine with the extended battery to last anywhere from 20 to 30 hours depending on usage. I'm running with stock voltage and clock though. Haven't seen a need to adjust it with that performance. I also need the updated overclock module for use with 2.2.1. I encountered problems with the old one where the clock speed would stay pegged at 1 GHz when in use and not adjust at all, so just went with nothing.
 
I really dont understand why people dont just charge their phone at night....I do, always have...leave the phone on and wake up to 100% charge every morning :)

Yeah, I have 2 chargers at home, one in the car, and one at work. I can be plugged in most of the time I'm using my phone. The only times I don't plug in when I CAN are the times I'm testing battery life for Drod :)

Lol, I normally only charge at night....and periodically when Im driving in the car.

Using this ROM, my setup...LV overclock and an extended battery....I can go all day without charging. And I use the phone quite a bit during the day, running 2 companies.....it gets used.

So many answers....

1) The point of my post was to provide feedback to the dev(s) on the Rom's battery performance.

2) I really don't have battery issues because I do have chargers in my car, at work and at home. But in the rare cases I don't drive to go out on the weekends and I end up sleeping somewhere besides my house, I would be SOL and in those cases battery performance is important.

2) I charge my phone to a full charge before I go to sleep, then turn off data and take it off the charger because I am concerned with heat issues and the wear and tear overheating can cause. I constantly stream music in my car with the phone on the charger and the phone gets super hot so I would rather let it chill out at night. I'd like to extend the life of my phone for as long as I can because I don't plan on moving to 4G until data plans become reasonably priced.

Thanks for the feedback though.
 
Honestly dude, if there is an issue your having with battery performance, its probably isolated.

Cause alot of people here including myself are having EXCELLENT battery performance on this ROM.

And really, I have always charged my phone at night....all night....every night.....and NEVER EVER had a battery go bad, or hurt a phone.
 
Honestly dude, if there is an issue your having with battery performance, its probably isolated.

Cause alot of people here including myself are having EXCELLENT battery performance on this ROM.

And really, I have always charged my phone at night....all night....every night.....and NEVER EVER had a battery go bad, or hurt a phone.

It's obviously not an isolated issue because several posts on this thread have been about battery life issues, some of them even worse than the situation I've experienced. I'm not complaining I love the ROM I'm providing feedback which is what the forum is for.

In my experience, I have burned up a battery on my old HTC Titan and I used to keep that thing on a charger all the time. I know the tech in the X is way more advanced but I'd rather be safe. I'm trying to preserve my phone as long as I can like 2 years or so.
 
I understand that....however, usually if its an issue with the actual ROM, then everyone would have the same issue.

If its an issue with the download, install, or setup...then thats when you normally see it from random people (meaning not everything, not calling you random ;) )

But anythings possible. Sux to have issues.
 
Last edited:
I have a recurrence of a fairly awful problem that I must be alone in experiencing. I posted a while back about my DX having a bootloader error after 1.95 and trying to nandroid backup. I went to VZW and they had no clue and didn't have the capability or intelligence to reflash the software so I received a refurb unit by mail yesterday.

The new unit was already on .340/2.2.1 so I rooted with z4root, loaded clockwork, loaded Rubix 1.95 and then restored most of my stuff via google and mybackup pro (just apks and data, no system).

Everything was fine until this morning when I went back to clockwork and re-bootstrapped recovery (I always do this before I go into clockwork recovery or ROM manager), and had clockworkmod reboot into recovery. I am now back stuck at the M logo. However, this time I can get into the normal recovery mood (Home/Power/Search etc.) In the normal recovery I tried a cache clear with a reboot - nothing; then I tried a wipe data/factory reset with a reboot - still stuck at the M logo.

I am guessing I have to SBF but I am now unsure what files to use for the SBF - I think there are .340 system only files somewhere and I am praying that will work. Does anyone know where those SBF files are and whether they might work or have any other suggestions??

Clearly there is some reproducible corruption of the bootloader (?) with the Clockworkmod recovery bootstrap that I have now unfortunately duplicated on two different DXs but I am guessing I am the only one experiencing this since nobody could even flash a theme after the ROM without going into recovery...
 
So, I'm trying to run the scripts in the OP, but for some reason, none of them exist... I cant restore quickoffice, ect ect. I checked, and data/rubix doesnt exist on my phone. Any idea what could have happened?
 
Back
Top