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.7, back and better than ever

Mike, the dx version of froyo is built custom for the device. Froyo is 2.2, the x's version of froyo is currently 2.3.340. So yea your phone isnt messed up or anything, its telling you it has froyo, ect. my phone displays the same info
 
Thanks for clarifying. It just seemed odd that in the same info section "Android Version" where it once said 2.3.340 it nows says 2.2.1. ut if you all tell me thats completely normal I have zero issues with that.
 
... is it normal to have started with OTA 2.3.*** and after installing this having the about phone section list version 2.2.1?.
Thanks for clarifying. It just seemed odd that in the same info section "Android Version" where it once said 2.3.340 it nows says 2.2.1. ut if you all tell me thats completely normal I have zero issues with that.

Android version, vs. VZW/Moto update versions..

Moto/VZW update version 2.3.15 was android version 2.2
Likewise, 2.3.340 is 2.2.1, etc.

BTW, you can make that say anything you want just by editing the text file found at /system/build.prop.. So about phone will display whatever the ROM developer puts there. 2.2.1 is the android version that the ROM was primarily based on...

HTH
 
****been In libertyville, by the way of darkslide ******* looking into going back to where I started but see's things seem different here...some remodeling done reckon worth peep!
lol....the overclocking app seems interesting .
 
This is a completely stupid question, but there isn't any way to instal the BlurEmail.apk and BlurEmailEngine.apk onto this Rom is there? The ASOP version is pretty terrible for Exchange IMO. It just looks like crap and doesn't have HTML support.

I'm assuming it's a similar issue HDMI, and the different frameworks makes this impossible. And I know, I can just go install Blurry. But really, the only Blur thing I like/require is the email app.

The blur email app is integrated with almost a dozen other apps, as well as the framework. If you just install the email app, some features/functions won't work correctly, etc.
The integration is totally horrible.. which is one reason so many people want it gone...

There are also alternative exchange compat. options such as touchdown, etc. available.

Just wanted to chime in with my 2 cents.

Exchange email is such a pain. I work part time for one company, and full time for another. One uses exchange 2010, the other 2003. Both have security policies in place that my phone hates.

I've tried tons of email apps, and I can't get one solution to work with both. The 2010 works fine with blur email, and liberty's email app, but won't work with improved email or others off the market.

The 2003 only works with k-9 or touchdown. I think its a server issue as some people with D2's have it working. So I'm working with the admins to get it to function. So for now I'm running Apex so they can see that I'm on the "official" email they expect for my phone.

It does suck how motorola decided to tie everything together so closely in blur. I can see why, so they could offer "super integration", but it kinda kills the android experience a little bit.

[/rant]

to add to all of what's above.

We use a hosted exchange solution (2010) through Microsoft and it works fine on all phones. stock DX, rubiX DX, Pro, D2, D1.

We have seen issues in the past though stemming mostly from security policies on the server end.

When these devices initially rolled out there were problems with how blur interpreted those security policies and specifically how it handled polices that were simply not set. It tended to make assumptions if it wasn't told ON/OFF.

After a few updates to the devices though and MS changing some polices at our request we are stable.

The remaining "exchange problems" are simply that users are comparing them to how their old Blackberry worked instead of accepting it's a different device and learning how to use it. But you can't do anything about that.

We do have a few folks that use Touchdown simply because it does have features that are a bit closer to the blackberry experience. Specifically the ability to sort email. Why you need to sort when you can just search is beyond me but I stopped trying to figure out why end users dwell on small little things and forget that they have a phone thats newer, bigger, better, faster than what they had before.

For a brief period of time we did have a few stock DXs on Exchange 2003....there were problems. We were rolling the phones out in conjunction with a migration to 2010 hosted so we never really worked through those issues, just dealt with it for a few days until the move.
 
Is there a list of bugs for this rom anywhere. I just would like to know what I can assume is a rom bug or an individual issue.

Right now I have random reboots (infrequent) and touchscreen unresponsiveness (momentary and sometimes permanent )

Thanks!

Sent from my DROIDX using Tapatalk
 
Rubix 1.9.7 R-O-C-K-S !

Newbie and this is my first post….just wanted to say You Guys Rock !.
Rubix 1.9.7 has been SOLID ! for me.
This was my first root and ROM install. Used zroot and Droid X bootstrap then followed the Rubix “How to install” and also ran the scripts for gallery 3D and quickoffice. Piece of cake. Love IT ! Had one minor issue with not being able to hear incoming phone calls without first switching to speaker but a quick reboot fixed that (just a weird thing I guess). Everything I have testing works as it should. Love the ADW Launcher also. Was going to try other ROMs but after reading this forum….isn’t going to happen…I am happy with Rubix and plan to enjoying it along with any new releases that might come.
[FONT=&quot]My push to root was a result of the poor CorpSync in Blur (let’s be honest…it just didn’t work 75% of the time). We are running Exchange 2007 and while using Rubix 1.9.7 that has been spot on….no complaints from me.
:icon_ banana:[/FONT]
 
Is there a list of bugs for this rom anywhere. I just would like to know what I can assume is a rom bug or an individual issue.

Right now I have random reboots (infrequent) and touchscreen unresponsiveness (momentary and sometimes permanent )

Thanks!

Sent from my DROIDX using Tapatalk

are you running the latest OTA update?
I thought the random reboot thing was fixed in the framework with that OTA.

If you are I would just try wiping data/cache and re-installing.

I have been running without random reboots since 1.95. Actually, I had 1 but that's perfectly acceptable considering what happens on stock.
 
How can you ne OTA on the rom? I was on the latest OTA when I installed rubix, if that's what you mean.

Frankly, I have one random reboot in the three days since I installed it. A vast improvement over the 7 to 8 I would have had with the stock. So I'm not complaining at all, I was really just inquiring to see what are some common bugs I could expect. So far I have gathered that touchscreen unresponsiveness is quite common and usually temporary. I did have one instance where I was in a phone call and switched too speakerphone and upon switching to speakerphone the screen completely locked. Had to do a battery pull. But I have been on many calls and that has only happened once, so obviously totally acceptable.

Thanks!

Sent from my DROIDX using Tapatalk
 
How can you ne OTA on the rom? I was on the latest OTA when I installed rubix, if that's what you mean.

Frankly, I have one random reboot in the three days since I installed it. A vast improvement over the 7 to 8 I would have had with the stock. So I'm not complaining at all, I was really just inquiring to see what are some common bugs I could expect. So far I have gathered that touchscreen unresponsiveness is quite common and usually temporary. I did have one instance where I was in a phone call and switched too speakerphone and upon switching to speakerphone the screen completely locked. Had to do a battery pull. But I have been on many calls and that has only happened once, so obviously totally acceptable.

Thanks!

Sent from my DROIDX using Tapatalk

right you can't take OTA on a rom but 1.97 is built to work on 2.3.340 so in the event that you never upgraded you could have issues.

no sure on the touchscreen issues or speakerphone problem.
I haven't seen that.
 
Question. How do I get the camera functioning to its full resolution again? Is that a blur function?

Sent from my DROIDX using Tapatalk
 
Back
Top