• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root GingerShedBread/GSB

what are your animatios set on? i believe i read somewhere that setting them to fast makes the tv sleep animation not work. or rather,not noticable.
 
paleodust said:
They are on default (all animations on).
Click to expand...

i thot there was a setting somewhere that let you pick how fast the animations ran,but now i cant find it! :mad: just the one that you mentioned-some,none,all.

also,mine has stopped working also :(
 
scotty85 said:
i thot there was a setting somewhere that let you pick how fast the animations ran,but now i cant find it! :mad: just the one that you mentioned-some,none,all.

also,mine has stopped working also :(
Click to expand...

Hmm... I wonder why it stopped working.

Has it stopped working for others, too?
 
paleodust said:
The power off animation stopped working for me even though it's still checked. Any ideas? Rebooting didn't help and neither did unchecking and re-checking the box.
Click to expand...

I believe it's a known issue.

I'm actually really amazed that so many people care about this particular feature. When I'm turning my phone off, I just want it to turn off and save battery for what's really important.

Anyway, I'd just wait - CM7 is still at early beta.
 
doogald said:
I believe it's a known issue.

I'm actually really amazed that so many people care about this particular feature. When I'm turning my phone off, I just want it to turn off and save battery for what's really important.

Anyway, I'd just wait - CM7 is still at early beta.
Click to expand...

Never gave a thought to it either. Turning all the animations off has definitely increased my battery life. v1.7 should be out soon. I think the other issue being addressed is the camera FC. I am amazed with the stability of this ROM so early on.
 
the old timey tv turn off is actually one of my favorite things about GB. but then,i am pretty easily amused,lol.

it is still working on my incredible,and my droid 1. big difference is i "refresh" them both every day with a new nightly. maybe when 1.7 comes out well have it back for awhile :D
 
doogald said:
Oh, also the ROM is overclocked by default to 587 MHz or something, since there is a small number of Erises that cannot handle 710 MHz. You can use your OC app of choice (SetCPU, CPU Boost Lite) to change this, or go into settings->CyanogenMod ROM settings->Performance and changing the CPU settings (and have them set on boot) there. As it says when you hit "Performance", you are supposed to restart the phone when you make changes in this category, though I would wait until that first sync is done.
Click to expand...

Just installed this ROM this afternoon and I'm pretty impressed so far...

It was/is pretty smooth and I suspected it was overclocked but didn't know what the O/C speed was. So, since you said setCPU was cool to install, I did :p.

Anyway, it looks like the default speed is 604MHz by the way.

Not for nuthin' ;), I also did a few little speed tests using my AVF app. Here are the results of calculating the SHA-1 checksums on the GSB.v1.6-CM7.0.0_RC1_STABLE.zip ROM (setCPU ondemand, fastest of three runs each speed):

Code: 
Clock Speed    SHA1 Time      Jar Verify Time
------------   ------------   ------------------
528 MHz        24.642 secs    1 min, 13.393 secs
604 MHz        23.184 secs    1 min,  8.286 secs
710 MHz        20.985 secs    1 min,  2.725 secs
748 MHz        20.575 secs    1 min,  0.173 secs

Couldn't go reliably higher than 748MHz since my phone froze-up at the end of the first SHA-1 scan at that speed :eek:. Also, note that I had hardly anything else installed / running at the time of these tests, so, they are pretty-much just my app and Android duking it out :cool:. Also, while the times are certainly better the higher you overclock, they are not shockingly so (nor do they directly correlate with the speed increases).

Bear in mind that I have not (yet) done these tests on a different ROM for comparisons which would give a better perspective for how much "faster" or "smoother" one ROM is compared to another. Also, I'm not making any claims that my AFV app will test all of the things that "smoothness" implies ;). Its just a test.

I'll probably re-run these same tests in xtrROM 5.0 since I "felt" that this ROM was "smoother" on initial install than GSB was.

Cheers!
 
CPU settings are built into CyanogenMod settings now under Performance.

Scary, would you mind running comps on smartass?
 
scary alien said:
Code: 
Clock Speed    SHA1 Time      Jar Verify Time
------------   ------------   ------------------

604 MHz        23.184 secs    1 min,  8.286 secs
710 MHz        20.985 secs    1 min,  2.725 secs

...while the times are certainly better the higher you overclock, they are not shockingly so (nor do they directly correlate with the speed increases).[/QUOTE]

The differential between 604 MHz and 710MHz is a ratio of 0.85 while that of their time to complete the given task is about 0.91, which seems to indicate about 7% increased efficiency going to 710 MHz.
Click to expand...
 
paleodust said:
CPU settings are built into CyanogenMod settings now under Performance.

Scary, would you mind running comps on smartass?
Click to expand...

Okay, I un-installed setCPU, set to the smartass governor in the Performance settings, and re-ran:

Code: 
Speed     SHA1 Time     Jar Verify Time      [COLOR="Blue"]Run with the smartass governor[/COLOR]
-------- ------------  ------------------    -----------   ------------------
528 MHz   24.642 secs   1 min, 13.393 secs   [COLOR="blue"]23.601 secs   1 min, 14.020 secs[/COLOR]
604 MHz   23.184 secs   1 min,  8.286 secs   [COLOR="blue"]22.321 secs   1 min,  6.830 secs[/COLOR]
710 MHz   20.985 secs   1 min,  2.725 secs   [COLOR="blue"]20.860 secs   1 min,  1.306 secs[/COLOR]
748 MHz   20.575 secs   1 min,  0.173 secs   [COLOR="blue"]20.308 secs   0 min, 59.230 secs[/COLOR]

Yeah, a smidge faster...don't have Excel installed on my laptop, otherwise I'd provide percentage increases, etc.

Also, just for grins (:D:D:D), I enabled JIT and re-ran the 748MHz tests and got 19.599 seconds for SHA1 and 1 min, 1.715 secs for the jar verify. I'm sure we could go on and on with different configurations...your mileage will vary.

Cheers!
 
I am loving this ROM so far...been using it about 3 days. Seems just as snappy and responsive a xtrROM 4.6 that I was using previously.
 
I have been on this rom for a few days(1.5) I love the fact that the dead call bug was fixed. I talk on the phone to my dad or wife at times for more than 20 min and would have dead call happen a few times. Everything works fine now, except when I am on speaker phone or bluetooth when my screen turns off it won't come on until I hit the end button. Now if you are on a call and have to use some other functions on the phone or go from speaker to ear phone you can't without hanging up on the person. I thought I read that their may be a fix on 1.6, but it was called something else. It sounded like my problem. Just wondering if anyone else could verify.
 
kobel1up said:
I have been on this rom for a few days(1.5) I love the fact that the dead call bug was fixed. I talk on the phone to my dad or wife at times for more than 20 min and would have dead call happen a few times. Everything works fine now, except when I am on speaker phone or bluetooth when my screen turns off it won't come on until I hit the end button. Now if you are on a call and have to use some other functions on the phone or go from speaker to ear phone you can't without hanging up on the person. I thought I read that their may be a fix on 1.6, but it was called something else. It sounded like my problem. Just wondering if anyone else could verify.
Click to expand...

press the vol up and then the send button.:) There may be a fix on 1.6 but that way has always worked for me. I'm still on 1.6 waiting for 1.7.:D
 
I tried vol up, and send, not together. I just checked the tackball wake, I hope that works. I did flash the 1.6, it seems as good as the 1.5. Shed has done a great job. I still wish a dev would play around with the aloyous snow, I know it's just a 2.1, but it was a nice rom.
 
kobel1up said:
I tried vol up, and send, not together. I just checked the tackball wake, I hope that works. I did flash the 1.6, it seems as good as the 1.5. Shed has done a great job. I still wish a dev would play around with the aloyous snow, I know it's just a 2.1, but it was a nice rom.
Click to expand...

You have to press vol up + send together to get the screen to turn on. I didn't know about the trackball... i'll have to see if that works.
 
You must log in or register to reply here.
Back
Top Bottom