rubiX Focused 1.9.0 Leak/Non-Leak

[sephtin]

hey guys,
so ima total noob but all i want is a simple black bar mod. i have flyx v0.1 final, which i believe is blurless. my brother said he flashed a different rom, so i think i will need to do that, but where do i start? rubix seems to have the most support, but which do i choose? focused or blurry? i dont really care to have all the blur applications, but whatever is similar to flyx. and when i flash a new rom, what are my black theme options that are fully compatible with rubix?

also, i have to have LCD density changer. i wont go back to the smaller pixel density

Focused is built from a completely different framework than FlyX (FlyX was based on the original 2.3.9 leak of 2.2 I believe). One (of a few) side affects of this, is that LCD Density changes WILL cause additional reboots on the current Focused framework. If you need to change it, you'll want to start with a Blur based rom, so you get the MotoBlur framework (similar to FlyX).. which means if you care to try Drod2169's rubiX ROM, then Blurry it is.

Think the latest version is 1.6.3.. should be in the drod2169 section...

 

[sephtin]

It doesn't even matter to me to be on .340. Just wanted to see what all the hype is about. Lol. Im fine just where im at. Now when developers start making roms and themes for .340 I would like to upgrade. Till then my phone runs beautifully. Im happy with the leak that im on and I have a full sbf to go with it

Sent from my DROIDX using DroidForums App

Any ROM that has a version for the .320 Leak, should work fine with .340...

 

[sephtin]

Camera stopped working with 1.9

When I try to open the app, it only briefly opens then closes.

try clearing data/cache for it
Menu> Settings> Applications> Manage Applications> all tab> Camera
force stop, clear cache, clear data
Then try it again.

If it still has issues, when did it stop working.. any changes just before it that might be the cause?

 

[teh_g]

Time to download the 2.2 sbf and hope for the best. I am glad I can install rubiX again right away . Wish me luck fellow DX owners...

 

[sephtin]

Anyone have any issue with the auto brightness? I just installed this ROM yestereday and noticed that toggling the brightness between auto and full really doesn't make much of a difference (in a dark lit area). I would think in a dark place the difference would be quite noticeable. I've seen a post or two on older versions of the ROM using an auto brightness hack/patch does anyone know if that will work on 1.9 or if there's another patch available? Thanks!

The brightness patch was from a completely different framework, and replaces a file that wouldn't be compatible with current versions of Focused.
That file is however replaced by any theme installed.. which theme are you using, if any?

Also, to clarify... manual, has a lower limit, and an upper limit, and auto just automatically selects what it should be set to within these upper and lower limits...
When it's dark out (walking the dog after nightfall for me), and I change the setting between Auto, 1/4, 1/2, and full... it seems auto picks somewhere between 1/4 and 1/2 brightness... which is probably fine, but I always just manually toggle to the 1/4 setting.. I'm using switchpro toggle, but should be the same as using ANY toggle widget...

Are you using a widget, or the actual brightness settings screen?

 

[rion_j]

It doesn't even matter to me to be on .340. Just wanted to see what all the hype is about. Lol. Im fine just where im at. Now when developers start making roms and themes for .340 I would like to upgrade. Till then my phone runs beautifully. Im happy with the leak that im on and I have a full sbf to go with it

Sent from my DROIDX using DroidForums App

Any ROM that has a version for the .320 Leak, should work fine with .340...

Sephtin, thanks for your feedback on this. You did however say "should work"....has this been tested? I'd like to put this rom on .340.

 

[brockeverly]

New problem which is kind of interesting. I cannot stream any videos from any source, always get an error that the video cannot be played. I have also lost the ability to stream music via rhapsody and some other internet radio apps. Even when I try to run quadrant it errors out and stops when it gets to video. Anyone have this happen? I'm running the leak version. Thanks!

 

[sephtin]

It doesn't even matter to me to be on .340. Just wanted to see what all the hype is about. Lol. Im fine just where im at. Now when developers start making roms and themes for .340 I would like to upgrade. Till then my phone runs beautifully. Im happy with the leak that im on and I have a full sbf to go with it

Sent from my DROIDX using DroidForums App

Any ROM that has a version for the .320 Leak, should work fine with .340...

Sephtin, thanks for your feedback on this. You did however say "should work"....has this been tested? I'd like to put this rom on .340.

Focused has been reported to be working on .340. Best I have for ya.
The differences between .320 and .340 are so minimal.. I can't imagine it not working.. but I also haven't seen the changes in the /system/lib dir from .320 to .340 (I've not yet upgraded to it from my 2.1 bootloader.. heh I've never taken an OTA at all.. Honestly, hate to give it up, it's been SO SOLID.. *sigh*... oh well.
Today or tomorrow I'll play with it, and if there are differences between .320 and .340 in /system/lib, a patch will follow by either drod or myself.

Edit: If it makes you feel any better.. I'll be doing just that "putting this ROM on .340" today or tomorrow..
Haven't seen any .340 specific errors yet, as long as you're running the leak version of 1.9.0, should be fine.

 

[mcp770]

I'm running on 340 perfectly with Rubix 1.90.

 

[Marius1]

340 works great with 1.90 so far.

Sent from my DROIDX using Tapatalk

 

[17akota]

New problem which is kind of interesting. I cannot stream any videos from any source, always get an error that the video cannot be played. I have also lost the ability to stream music via rhapsody and some other internet radio apps. Even when I try to run quadrant it errors out and stops when it gets to video. Anyone have this happen? I'm running the leak version. Thanks!

i think to solve your problem you have to go into your build.prop and change the line that says media.stagefright.enable-player=true. change it to =false. that should fix it.

 

[jstrick5]

Anyone have any issue with the auto brightness? I just installed this ROM yestereday and noticed that toggling the brightness between auto and full really doesn't make much of a difference (in a dark lit area). I would think in a dark place the difference would be quite noticeable. I've seen a post or two on older versions of the ROM using an auto brightness hack/patch does anyone know if that will work on 1.9 or if there's another patch available? Thanks!

The brightness patch was from a completely different framework, and replaces a file that wouldn't be compatible with current versions of Focused.
That file is however replaced by any theme installed.. which theme are you using, if any?

Also, to clarify... manual, has a lower limit, and an upper limit, and auto just automatically selects what it should be set to within these upper and lower limits...
When it's dark out (walking the dog after nightfall for me), and I change the setting between Auto, 1/4, 1/2, and full... it seems auto picks somewhere between 1/4 and 1/2 brightness... which is probably fine, but I always just manually toggle to the 1/4 setting.. I'm using switchpro toggle, but should be the same as using ANY toggle widget...

Are you using a widget, or the actual brightness settings screen?

Sephtin -

Thanks for the reply and the clarification on that older patch. I'm actually using your black notification bar theme (very nice btw). I use the Power widget built into stock android and usually keep it on the auto setting. If I toggle between full and auto there's very little change in a dark room... or in any situation really. I would think there would be a much more drastic difference as the 1/4 setting would be plenty in the situations I've tried.

I thought when I was running the stock ROM the change was more drastic or maybe it's just my mind playing tricks on me and what I really need is a tweaked version or app that defaults the auto level slightly lower than is standard.

 

[sephtin]

Anyone have any issue with the auto brightness? I just installed this ROM yestereday and noticed that toggling the brightness between auto and full really doesn't make much of a difference (in a dark lit area). I would think in a dark place the difference would be quite noticeable. I've seen a post or two on older versions of the ROM using an auto brightness hack/patch does anyone know if that will work on 1.9 or if there's another patch available? Thanks!

The brightness patch was from a completely different framework, and replaces a file that wouldn't be compatible with current versions of Focused.
That file is however replaced by any theme installed.. which theme are you using, if any?

Also, to clarify... manual, has a lower limit, and an upper limit, and auto just automatically selects what it should be set to within these upper and lower limits...
When it's dark out (walking the dog after nightfall for me), and I change the setting between Auto, 1/4, 1/2, and full... it seems auto picks somewhere between 1/4 and 1/2 brightness... which is probably fine, but I always just manually toggle to the 1/4 setting.. I'm using switchpro toggle, but should be the same as using ANY toggle widget...

Are you using a widget, or the actual brightness settings screen?

Sephtin -

Thanks for the reply and the clarification on that older patch. I'm actually using your black notification bar theme (very nice btw). I use the Power widget built into stock android and usually keep it on the auto setting. If I toggle between full and auto there's very little change in a dark room... or in any situation really. I would think there would be a much more drastic difference as the 1/4 setting would be plenty in the situations I've tried.

I thought when I was running the stock ROM the change was more drastic or maybe it's just my mind playing tricks on me and what I really need is a tweaked version or app that defaults the auto level slightly lower than is standard.

Ya, not sure! I don't use powercontrol, I use switch pro... I'll test when I get a few mins with the included powercontrol widget.. see if it acts differently than switchpro... :S

Edit: Tested with PowerControl widget, with same results.
Interesting however.. that the widgets and brightness screens never were in sync. When I changed a setting on one screen, the others were never in sync.

Just for fun.. try this.
Go to settings> display> brightness, and turn off auto, and set the slider all the way to low.. then power off the phone, and power it back on (don't reboot..).

See if auto acts any differently. It shouldn't, but I just wonder if it got out of sync or something? :S
(honestly, I'm kinda scratching my head here, mine just works...).

And, do you by chance have any other apps that might affect screen or display? Have you changed LCDDensity, or .. anything else you might be able to think of that could affect this? :S

 

[teh_g]

Used the sbf to get back to stock 2.2, used the update.zip, rooted, and I am now on rubiX 1.9 with the .320 kernel.

 

[devortex]

Used the sbf to get back to stock 2.2, used the update.zip, rooted, and I am now on rubiX 1.9 with the .320 kernel.

Technically your on the .340 kernel which is most likely identical to the .320 kernel besides the build date.

The reason your system info shows .320 is because 1.9.0 build.prop has that value set.

Doesn't matter, just wanted to clarify.