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

Are there still issues with the contact ringtones on the new rubix? I know it was hit and miss on the last one.

I haven't had any luck with custom contact ringtones on this ROM either, but I don't know if it's the ROM, it may be the AOSP dialer, or a conflict with something else installed. I haven't tried any other ROMs, I've been so satisfied with Rubix that I haven't bothered trying any others. The fact that the framework is pretty much completely different in 1.9.5 kinda tells me it's a dialer or conflict issue. But maybe someone who runs another AOSP ROM can tell us if custom contact ringtones work for them.
 
Thanks DaveG1968. You may be correct with the AOSP because I'm running grummy now and it has the same issue. Apex seems to work fine though.
 
Last edited:
Thanks DaveG1968. You may be correct with the AOSP because I ran Rubix and it had the same issue. Apex seems to work fine though.

What dialer/phone app does Apex use? Do you know? Just curious, trying to see if there's some way we can make the custom ringtones work better with Rubix, and any info on ROMs that they work right on could potentially be helpful to drod and/or sephtin and/or whoever else in figuring the issue out. Of course, I have no idea how high on the list this particular issue is, it might be pretty low compared to getting other things working. And that's cool. I can get along without them. It'd be great if they worked, but it's not a deal breaker for me. Other than this particular issue Rubix runs awesome for me.
 
Hi,

I've been using RubiX since 1.6 and have loved it ever since. One of my only issues is the fact that there is no support for OTA updates, so I never know when the updates are ready until I check the forums here. Can you enable OTA updates in ROM manager for us?

Also, a word of advice for people who want the new RubiX 1.95, but are stuck on system version 2.3.15: flash .20, but don't flash .40. I've seen a few people (including myself) who have bricked their phones by doing this. It turns your phone from dancedroid into :motdroidvert: ... But if you play dumb with Verizon, you'll get a refurbished DX overnighted to you. But then again, with the new phone, you can flash the new version of RubiX without a problem. And then you can go back to being this :icon_ banana:

That's called fraud... and another reason our phones are continuously being locked down.

OTA Updates will be done in the future. I'm trying to enable a way to let you guys know directly, not through rom manager.

I'm sorry I miss-wrote what I meant to say and what I actually did. The problem was that I was doing too many things at once and at 1:30 or maybe later. I was creating my website, flashing SBFs, and some other things. My phone went straight to a bootloader with an error message (something like A5, 70, 00, 00, XX) and I couldn't get it to go anywhere else (besides the normal bootloader, but ADB doesn't work for me). I found a few other people with the issue, but no solution. So the next morning I called Verizon, told the guy that I'm having this issue and then he moved me to a higher level of tech support. I told the new guy the code and he said that they would just overnight a phone to me. So I meant tell them your issues and they might ship you a new phone. So I'm not sure, but I believe the issue was that I flashed .40 and then RubiX and forgot to wipe data/cache.
Wow I just reread what you replied to and that might have been the dumbest thing I've ever written.

But anyways, the auto update thing would be awesome if you can make it.
 
So, I've got an awkward problem with 1.9.5. anyone use the secondary bit of the swype keyboard? It seems like the colors for the labels are still black, so you can't really read the black text on black buttons. Anyone have a fix? :O
 
Yeah, I just noticed that. To clarify, it's the arrow keys and function button section. The arrow keys are fine, but the surrounding keys are black. To get to the arrow keys, swype from the Swype key to the SYM key.
 
Yeah, I just noticed that. To clarify, it's the arrow keys and function button section. The arrow keys are fine, but the surrounding keys are black. To get to the arrow keys, swype from the Swype key to the SYM key.

Cool, I'm glad I'm not the only one that has the problem. I think its just a png swapping patch, right? Or is the color of those labels dictated in some XML somewhere?
 
Thanks DaveG1968. You may be correct with the AOSP because I ran Rubix and it had the same issue. Apex seems to work fine though.

What dialer/phone app does Apex use? Do you know? Just curious, trying to see if there's some way we can make the custom ringtones work better with Rubix, and any info on ROMs that they work right on could potentially be helpful to drod and/or sephtin and/or whoever else in figuring the issue out. Of course, I have no idea how high on the list this particular issue is, it might be pretty low compared to getting other things working. And that's cool. I can get along without them. It'd be great if they worked, but it's not a deal breaker for me. Other than this particular issue Rubix runs awesome for me.

Apex is based on Blur Framework..
 
Hi,

I've been using RubiX since 1.6 and have loved it ever since. One of my only issues is the fact that there is no support for OTA updates, so I never know when the updates are ready until I check the forums here. Can you enable OTA updates in ROM manager for us?

Also, a word of advice for people who want the new RubiX 1.95, but are stuck on system version 2.3.15: flash .20, but don't flash .40. I've seen a few people (including myself) who have bricked their phones by doing this. It turns your phone from dancedroid into :motdroidvert: ... But if you play dumb with Verizon, you'll get a refurbished DX overnighted to you. But then again, with the new phone, you can flash the new version of RubiX without a problem. And then you can go back to being this :icon_ banana:

That's called fraud... and another reason our phones are continuously being locked down.

OTA Updates will be done in the future. I'm trying to enable a way to let you guys know directly, not through rom manager.

I'm sorry I miss-wrote what I meant to say and what I actually did. The problem was that I was doing too many things at once and at 1:30 or maybe later. I was creating my website, flashing SBFs, and some other things. My phone went straight to a bootloader with an error message (something like A5, 70, 00, 00, XX) and I couldn't get it to go anywhere else (besides the normal bootloader, but ADB doesn't work for me). I found a few other people with the issue, but no solution. So the next morning I called Verizon, told the guy that I'm having this issue and then he moved me to a higher level of tech support. I told the new guy the code and he said that they would just overnight a phone to me. So I meant tell them your issues and they might ship you a new phone. So I'm not sure, but I believe the issue was that I flashed .40 and then RubiX and forgot to wipe data/cache.
Wow I just reread what you replied to and that might have been the dumbest thing I've ever written.

But anyways, the auto update thing would be awesome if you can make it.

I'm still confident that it was a software error, and that could have been resolved by .sbf'ing to the correct .sbf. :P
 
Thanks DaveG1968. You may be correct with the AOSP because I ran Rubix and it had the same issue. Apex seems to work fine though.

What dialer/phone app does Apex use? Do you know? Just curious, trying to see if there's some way we can make the custom ringtones work better with Rubix, and any info on ROMs that they work right on could potentially be helpful to drod and/or sephtin and/or whoever else in figuring the issue out. Of course, I have no idea how high on the list this particular issue is, it might be pretty low compared to getting other things working. And that's cool. I can get along without them. It'd be great if they worked, but it's not a deal breaker for me. Other than this particular issue Rubix runs awesome for me.

Apex is blur based. Its probably a really easy fix if I were to try and pinpoint it, but since using apps like ringdroid from the market allow custom ringtones to work correctly, I'd like to get the rest of the kinks worked out first :)
 
Yeah, I just noticed that. To clarify, it's the arrow keys and function button section. The arrow keys are fine, but the surrounding keys are black. To get to the arrow keys, swype from the Swype key to the SYM key.

Cool, I'm glad I'm not the only one that has the problem. I think its just a png swapping patch, right? Or is the color of those labels dictated in some XML somewhere?

I honestly have no clue. I don't know much code besides Java and HTML (and I'm learning CSS for my website). And I'm only taking a Java class. But you can't expect more from a middle schooler. Or can you?

But I think it is a PNG Swap, but I've read that you need a PNG for each keyboard, not the individual keys.
 
Back
Top