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

Speaking of gallery, Im having an issue with viewing the gallery reboots the phone, otherwise everything works great. Any ideas?
 
Installed 1.6 at 60% battery. When it was done I was at 80%. Wasn't on the charger. What gives lol?

Sent from my DROIDX using DroidForums App

That info is cached, so it can sometimes be wonky when changing stuff, restoring, etc. When the status of your battery changes significantly enough, it should straighten itself out...
 
Speaking of gallery, Im having an issue with viewing the gallery reboots the phone, otherwise everything works great. Any ideas?

Hmm. If you turn off the OC, do you still get the reboot? :P

Yeah, but its not everytime, dunno....I am also having issues with odd folders showing up in the gallery and major lag in the gallery :(

Everything works great except gallery, anyway to wipe and reinstall just it? I was running a non-compatible theme at one time and I think that was causing a little issue but since I installed 1.6 Im themeless.
 
Hey sephtin, thanks for posting the updated 1.6 info on your site, and the links to the unofficial patches. I've tried a few times to install the Blur Gallery patch, but no matter what I do, the app doesn't appear in my app drawer. The mediagallery.apk is definitely in system/apps, and it has the correct permissions. Any thoughts would be greatly appreciated.


Blur Gallery will not work with this. The gallery from fission is as close as it gets.

In other news, I made a big breakthrough on HDMI last night, I CAN confirm it's not working, even with real HDMI. Give me a few days guys, and I should have it fixed, whether my own custom way, real hdmi, in gallery, or all of the above :)

Thanks drod2169. I flashed this [http://www.sephtin.com/rubiX/DX_Gallery(BlurGalleryFromFission).zip] in Bootstrap, but I still only have the 3D version of the gallery in my app drawer. It's a minor issue, and I understand it's unsupported and certainly not a priority for you, but the 3D Gallery really drives me nuts.

Thanks,
J
 
When I try to edit my contact info in contacts, I get a force close (doesn't happen if I try to edit any other contact). Why might that be?

Also, is there a way to get the dark swype keyboard theme for this?

Love your work, thanks!


Sent from my DROIDX using DroidForums App
 
Hey sephtin, thanks for posting the updated 1.6 info on your site, and the links to the unofficial patches. I've tried a few times to install the Blur Gallery patch, but no matter what I do, the app doesn't appear in my app drawer. The mediagallery.apk is definitely in system/apps, and it has the correct permissions. Any thoughts would be greatly appreciated.


Blur Gallery will not work with this. The gallery from fission is as close as it gets.

In other news, I made a big breakthrough on HDMI last night, I CAN confirm it's not working, even with real HDMI. Give me a few days guys, and I should have it fixed, whether my own custom way, real hdmi, in gallery, or all of the above :)

Thanks drod2169. I flashed this [http://www.sephtin.com/rubiX/DX_Gallery(BlurGalleryFromFission).zip] in Bootstrap, but I still only have the 3D version of the gallery in my app drawer. It's a minor issue, and I understand it's unsupported and certainly not a priority for you, but the 3D Gallery really drives me nuts.

Thanks,
J

I've been trying to test this.. but working on my black bar mod, I .. got a little creative, and had to .sbf to fix. :P.. and unfortunately I haven't had time to finish loading back to the ROM... heh. Know more soon....
 
Ok so I'm debating on updating to v1.6 (currently running RubiX v1.0) but I can do without the overclocking because honestly my phone runs just fine...but what benefit does modifying the voltage do?

I've been happy with using SetCPU to underclock my phone when the screen is off, when the battery gets toasty & when the juice runs low.
 
Ok so I'm debating on updating to v1.6 (currently running RubiX v1.0) but I can do without the overclocking because honestly my phone runs just fine...but what benefit does modifying the voltage do?

I've been happy with using SetCPU to underclock my phone when the screen is off, when the battery gets toasty & when the juice runs low.

Voltage is directly relevant to how much battery is used. Lower voltage = better battery life.
 
Ok so I'm debating on updating to v1.6 (currently running RubiX v1.0) but I can do without the overclocking because honestly my phone runs just fine...but what benefit does modifying the voltage do?

I've been happy with using SetCPU to underclock my phone when the screen is off, when the battery gets toasty & when the juice runs low.

Voltage is directly relevant to how much battery is used. Lower voltage = better battery life.

What about overall performance of the battery though? If you just undervolt it can you get away with not overclocking it?

Pardon my n00bness...I've never gotten into overclocking in general (even on my desktop), just never saw a reason. :)
 
Ok so I'm debating on updating to v1.6 (currently running RubiX v1.0) but I can do without the overclocking because honestly my phone runs just fine...but what benefit does modifying the voltage do?

I've been happy with using SetCPU to underclock my phone when the screen is off, when the battery gets toasty & when the juice runs low.

Voltage is directly relevant to how much battery is used. Lower voltage = better battery life.

What about overall performance of the battery though? If you just undervolt it can you get away with not overclocking it?

Pardon my n00bness...I've never gotten into overclocking in general (even on my desktop), just never saw a reason. :)

You are going to get 1000 MHz regardless of whether that is at 48V or 68V... Running it with a lower voltage, if your phone can handle it, will do only one thing: increase battery life/reduce battery consumption.
 
Ok so I'm debating on updating to v1.6 (currently running RubiX v1.0) but I can do without the overclocking because honestly my phone runs just fine...but what benefit does modifying the voltage do?

I've been happy with using SetCPU to underclock my phone when the screen is off, when the battery gets toasty & when the juice runs low.

Voltage is directly relevant to how much battery is used. Lower voltage = better battery life.

What about overall performance of the battery though? If you just undervolt it can you get away with not overclocking it?

Pardon my n00bness...I've never gotten into overclocking in general (even on my desktop), just never saw a reason. :)

Overclocking has to do with 2 elements... clock speed, and voltage (There's a lot more to it than that, but.. keeping it simple here).
A processor comes from the manufacturer with a speed and voltage that they've tested as stable... but each chip is a little different. When you raise the voltage, it increases the stability of the processor, but will drain the battery faster, and also cause increased temps.

Some chips can run at the default speed at a much lower voltage than others... this is undervolting, and can be used to increase battery life, often without impacting performance.

Some, when raising the voltage slightly, can run at faster clock speeds. This is often done to slightly improve performance. It's unlikely that you'll "feel" the performance increase, but it shows up in performance monitoring apps, so makes people feel warm and fuzzy, and that they're running faster. (It also has other side effects, like making the device feel warmer (and possibly fuzzier.. ;))...

Not knocking those that want to OC their device.. just saying that it's a preference thing, AND that there ARE risks... including when you raise the clock speed, and/or voltage, it will increase the heat output.. as well as the variance in temps (hot to cold and back, over and over again), which can lead to earlier failure of the chip, etc.
Likewise, undervolting can cause stability issues.. if the voltage isn't enough for the particular chip that you have...

So to better answer your question... undervolting, and overclocking are 2 different things. When you undervolt, you are attempting to lower the voltage to increase battery life, without changing performance. This **can** lead to stability issues, if the chip isn't getting enough voltage to function properly.
Overclocking is raising the clock speed (and most of the time, the voltage along with it) for performance purposes.

Hope this is helpful!
 
Is set cpu the problem

I have a noob question. Ive been using set cpu for about 3 weeks now and noticed with the new roms that are out ive had a lot of FCs, so this morning i switched to overclock widget and im running 1380 at 70vsel and my phone is smoking, i have Rubix 1.6. which i installed last night and had a lot of FCs, but now since i took off set cpu hadnt had any and getting consistent 1800-1900s on quadrant and my X is not getting hot to touch like it was at first with set cpu, i have jrummy16 overclock, also tried milestone overclock both running well. Could set cpu be the cause of a lot of problems we are having. dancedroid
 
Voltage is directly relevant to how much battery is used. Lower voltage = better battery life.

What about overall performance of the battery though? If you just undervolt it can you get away with not overclocking it?

Pardon my n00bness...I've never gotten into overclocking in general (even on my desktop), just never saw a reason. :)

You are going to get 1000 MHz regardless of whether that is at 48V or 68V... Running it with a lower voltage, if your phone can handle it, will do only one thing: increase battery life/reduce battery consumption.

Gotcha, guess that mean I'll have to update then :)

So versus having to read through 25+ pages of posts, what seems to be the best/most stable settings? Would you need to set a voltage for each speed setting? i.e. the 300, 600, 800 and 1000mhz

...and can I still use setCPU? The underclock feature when the screen is off works wonders :)
 
Back
Top