rubiX Focused 1.9.5

[Casen]

If you downloaded the ROM, you do. In the .zip file, it's in the /data/rubiX/app dir.

ADW, Maps, Swype, and youtube are in that folder.... I downloaded the rom from the very first link on front page.

Anyways, I gotta go for a few. Ill check back later

MyNet.apk isn't? (that's the 3g hotspot)

If it's not in that folder after installing, then it was installed correctly

Well, it wasnt in that folder, but I did download the TBH 3g hotspot. I installed the .zip in bootstrap, and still no 3g...

Then I just went in root explorer, opened up the TBH 3ghotspot.zip, extracted, put the mynet.apk in /system/app , set permissions, rebooted, and now have 3g hotspot... weird.

 

[jacksradio]

in the themed version while setting an event using calendar...i noticed the "to from" selection boxes were black text on black boxes...very hard to read.

 

[Happystranger]

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...

 

[sephtin]

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

 

[sephtin]

in the themed version while setting an event using calendar...i noticed the "to from" selection boxes were black text on black boxes...very hard to read.

Good Find.
I had a version of my barmod for Focused 1.6 (or was it 1.8.6.. I can't remember).. that had black notifications, and the black buttons, etc. with white text.
What I found, was that there are TONS and TONS of .apk's that don't accept the default colorscheme/font colors from the framework.

Rather than try to theme a few hundred market apps and try to keep them updated, I caved in, and made them grey. :S

It DOES look nice, but there are some disadvantages to black notifications (etc.) on Android.. that I'm afraid is always going to be a limitation...

 

[Happystranger]

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...

 

[sephtin]

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...

Hmm... Well, I can say that from experience, wiping cache is just a important as wiping data, and I highly recommend you wipe it as well...

Doesn't gain you anything by not wiping it..... And it does solve a few issues that we know of when switching between frameworks...

Sent from my DROIDX using DroidForums App

 

[superleon]

I don't know if it is a bug of rubix 1.9.5.
When I try to dial the ##7764726 and press send the phone starts to dial that number instead. I have to go to the original rom and did it as above to enter the Programming Menu.

 

[Droid74]

Either RubiX or Linear for RubiX is not playing well with launcher pro plus. Every time I try and change the wallpaper it forces closed. I have tried clearing LPP data and cache and no change. I have reflashed both as well. Any ideas? (im leaning towards Linear being the culprit)

Edit: The od thing is that reflashing RubiX and Linear didnt work but restoring a back up did...something went wacko. Oh well fixed anyways.

 

[btesoroni]

I'm just wondering... why is everyone using 3g hotspot? Why not use Wireless Tethering, its free.

 

[wooddale]

I duno maybe you can get 3G for free on different Roms

 

[Strikeir13]

Hey seph or drod, was it ever confirmed that the scripts worked? I know when I installed my 1.9.5 (wiping data/cache/dalvik cache/batt stats), the auto app restore script didn't work (I had used the backup script to create the rubix folder on the SD card, they just never restored...).

 

[trogdorjack]

In 1.9.5, I can no longer distinguish between "Screen Timeout" and "Screen Unlock Timer"... This is an irritation because my corporate exchange policy requires a PIN code after 10 minutes of inactivity.

In previous ROMs, I would set the "Screen Timeout" to 30 seconds but would only be asked to re-enter the PIN if 10min of inactivity had lapsed.

In 1.9.5, once the screen turns off at the 30sec timer, I have to re-enter the PIN. And, actually, even if I turn off the screen 2 seconds after I unlock it, I still have to re-enter the PIN.

Am I overlooking a setting somewhere? How do I set the display to turn off at 30 seconds while setting the PIN re-entry period to 10 minutes?

One of the "bugs" people "pointed out" was having to wait to re enter their pins and patterns. Timer was removed.

Please excuse my ignorance if this has been discussed more but I don't understand why this was considered a bug and removed. If you wanted to re enter your pin/pattern every time you unlocked your phone then you just had to set the timer to 0.

As someone who doesn't want to enter my pin every time, not having a timer is kind of a "bug". Its a HUGE hassle at work when I am constantly checking my phone. Could we get a patch that would re enable the timer...so that those of us who want the timer can have it while the everyone else can do without...that way everyone is happy.

 

[sephtin]

Hey seph or drod, was it ever confirmed that the scripts worked? I know when I installed my 1.9.5 (wiping data/cache/dalvik cache/batt stats), the auto app restore script didn't work (I had used the backup script to create the rubix folder on the SD card, they just never restored...).

I helped with the backup script, and tested it, and know it works great.
Drod said he had someone test the restore, and they reported that it worked.. ??

 

[sephtin]

In 1.9.5, I can no longer distinguish between "Screen Timeout" and "Screen Unlock Timer"... This is an irritation because my corporate exchange policy requires a PIN code after 10 minutes of inactivity.

In previous ROMs, I would set the "Screen Timeout" to 30 seconds but would only be asked to re-enter the PIN if 10min of inactivity had lapsed.

In 1.9.5, once the screen turns off at the 30sec timer, I have to re-enter the PIN. And, actually, even if I turn off the screen 2 seconds after I unlock it, I still have to re-enter the PIN.

Am I overlooking a setting somewhere? How do I set the display to turn off at 30 seconds while setting the PIN re-entry period to 10 minutes?

One of the "bugs" people "pointed out" was having to wait to re enter their pins and patterns. Timer was removed.

Please excuse my ignorance if this has been discussed more but I don't understand why this was considered a bug and removed. If you wanted to re enter your pin/pattern every time you unlocked your phone then you just had to set the timer to 0.

As someone who doesn't want to enter my pin every time, not having a timer is kind of a "bug". Its a HUGE hassle at work when I am constantly checking my phone. Could we get a patch that would re enable the timer...so that those of us who want the timer can have it while the everyone else can do without...that way everyone is happy.

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.