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!

why built from source just plain ROCKS

I was running BB .4 for 5 weeks, patiently waiting for .5 to come out. Got tired of waiting.
Tried Chevy SS 4.6 for 2 days. Laggy on my phone.
Then tried Sapphire on Saturday. The BEST, fastest, smoothest ROM I have ever tried!! I will not be going to BB .5. Sapphire has totally sold me.

I did the same thing tonight and I am totally sold. I haven't had a single LP redraw since I switched.
 
I have to agree, since I got comfy using a terminal emulator, I have been more into tweaks and such. I've been switching from CM> UD> Sapphire and back. Apparently I have too much time on my hands.
 
The major difference between source based and "hack" based roms are that source based roms are continually upgraded since theyre built from the AOSP (the devs include the new code whenever its released) while hack based roms rely on update leaks to upgrade their core OS file. Heres a good article written by CVPCS of the Sapphire team (officially called crystal clear roms) that discusses the differences between CCroms and Cyanogenmod, and the differences between source based vs. hack based.

Anyone with sapphire 1.0, have you used the volume rocker to change songs and have it spaz out and continuously change songs until the playlist ended? Its a great feature that I will be patiantly waiting to be fixed since it works with Pandora too.

Maybe I dont have it enabled but my volume rocker just increases/decreases the volume for me on slacker and mixzing, maybe it only works for the stock music app?

just disable the lock screen controls for now...

K, don't feel like typing much, so I'm just going to quote the wiki:

Occasionally when you longpress the volume up/down keys to skip through songs when the screen is off, it will begin to continually skip and never stop. This is a result of some problems in the multi-threaded code. I had thought that I had fixed this but apparently it still exists. The best way to stop it for now is to simply tap the volume button a few times in the direction you were skipping, as the “key released” messages will then be re-sent and clear out the event queue that causes this to happen.

I am currently working on trying to fix that, but hopefully you all can bear with me for now until it is fixed.

This features only works when the screen is off, so that is why you might not have noticed it, but once he fixes it I will be using the hell out of it all over again. And disabling the lock screen controls does not disable the volume rocker controls. Hopefully this will be a future addition for those who don't want to use it.

Grr, the code deal didn't work like I thought it would...
 
Once I got Sapphire tweaked right and removed several stock junk apps, it definitely flies. Honestly though, I got a little bored waiting for CM6 final to be released. I think they're going to do a parallel launch across multiple phones, with some phones having finished builds and others needing work still. Strictly my opinion though.

I may well flip back to CM6 when its released, but for now, Sapphire is outstanding. I have a feeling I could very well be ROM hopping between the two.
 
I like it as well (Sapphire).

I now that the CPU controls are not a replacement for setCPU, but a compliment.

However I'd like to see a thread on it (which I'll open in that forum), I know they are working on this, but, I have watched my boot animation fly, then slow down somewhat on boot.

Is that setCPU taking over and it throttling down during the boot process due to something I've set?

If I don't have setCPU set at boot, then it seems to me my profiles are not taking, etc. (I may be wrong).

CK, again, I turn to you on this, you have yours set fairly well.
 
I like it as well (Sapphire).

I now that the CPU controls are not a replacement for setCPU, but a compliment.

However I'd like to see a thread on it (which I'll open in that forum), I know they are working on this, but, I have watched my boot animation fly, then slow down somewhat on boot.

Is that setCPU taking over and it throttling down during the boot process due to something I've set?

If I don't have setCPU set at boot, then it seems to me my profiles are not taking, etc. (I may be wrong).

CK, again, I turn to you on this, you have yours set fairly well.
I went into Gem settings/performance and unchecked CPU frequency scaling to set at boot. Set up setCPU's profiles etc etc set it to set on boot then rebooted.

As a side note in gems settings performance I also set compcache on.


Sent from my Droid
 
internal cpu control

Just to clear things up the built in or internal Cpu scaling/governor controls
On any rom not just sapphire are not a compliment to setcpu they are in fact a replacement for setcpu
Granted a setcpu has profiles and the built in does not. The benefit of the built in feature is that it is not an APP and not so easy killed off by froyo’s task killer. You cant have to cpu controls running one will take over and the other will just run for nothing. If you want to use set cpu with Sapphire you must disable the cpu feature in gem settings. You get profiles with setcpu but you will get faster and more power friendly scaling with the internal gem governor.
Conservative is the best overall governor as it scales up or down in moderate jumps
Ondemand will give you a good run but it jumps to the highest open slot not always good for battery
Powersave sucks
Haven’t used userspace yet
I did notice that when changing the governor in gem settings it took a reboot to get it to change

I like it as well (Sapphire).

I now that the CPU controls are not a replacement for setCPU, but a compliment.

However I'd like to see a thread on it (which I'll open in that forum), I know they are working on this, but, I have watched my boot animation fly, then slow down somewhat on boot.

Is that setCPU taking over and it throttling down during the boot process due to something I've set?

If I don't have setCPU set at boot, then it seems to me my profiles are not taking, etc. (I may be wrong).

CK, again, I turn to you on this, you have yours set fairly well.
 
"Granted a setcpu has profiles and the built in does not."

Sounds like something to be added into 1.1 ?
 
"Granted a setcpu has profiles and the built in does not."

Sounds like something to be added into 1.1 ?

That would be a lot of work for cvpcs :)

I started to feel bad for the guy when he started to talk about the way he implemented the volume rocker music controls.
 
I assume you want the profiles
for battery conservation am i correct in my assumption.
if so i would suggest you try two apps
Ultimate juice and Juice plotter
these apps are great and will save you battery power
get 12 to 14 hrs on a single charge with moderate usage and 10 hrs with heavy usage. also try setting the internal CPU control to conservative. also
if you decide to try these apps tweak them a bit and give them a few days for the changes to take full affect it took three days for Ultimate Juice to really take control of the Droid but once it did man my battery life IS ROCKING



"Granted a setcpu has profiles and the built in does not."

Sounds like something to be added into 1.1 ?
 
Last edited:
And secondly profiles on set CPU will only save you a dismal amount of battery power as most of the power drain comes from two places the screen and the radios. ultimate juice can auto shutoff both of these and save huge amounts of battery power and then by not having setcpu running you save ram and CPU power as it takes both to run setcpu vs internal.

dancedroid
 
by not having setcpu running you save ram and CPU power as it takes both to run setcpu vs internal.

dancedroid

Android is so good at managing itself being OCD about things of this nature (setCPU) is truly a waste of time.

Widgets and such are a whole other story but setCPU is an AWESOME app/tool for overclockers that does NOT take up precious resources to the extent of degrading performance or draining battery quickly.
 
Back
Top