Is this a patch to rc3? The file is small compared to the other ones
Sent from my DROIDX using XDA App
Sent from my DROIDX using XDA App
When I was on RC3 I just added the 10% battery add on as normal without anything extra and its working properly.
Google Servers Down?
After upgrading to the final release, I can't connect to the Google servers when adding my account...Anyone else having this problem?
After upgrading to the final release, I can't connect to the Google servers when adding my account...Anyone else having this problem?
Negative. Just flashed it and activated it. Did you wipe data/cache before and after installation?
hey Ang, when you say it is overclocked out of the box, is it relying on the overclock.ko stuff? (in other words, if i want to return it to non-overclocked, or O/C it differently, can i still use the droidx/2 overclock by jrummy?). my guess is yes, but figured i'd ask.
I don't believe that it means it comes stock overclocked, my Droid X/2 OC still shows the clock scaling settings is still set to stock for the device
I think what they mean by that is that there is a script you can run that comes installed with the ROM to overclock.
I think what they mean by that is that there is a script you can run that comes installed with the ROM to overclock.
I don't believe that it means it comes stock overclocked, my Droid X/2 OC still shows the clock scaling settings is still set to stock for the device
I think what they mean by that is that there is a script you can run that comes installed with the ROM to overclock.
yeah, i believe you are right, i just wanted to confirm.
on an unrelated note, after moving up to 2.1final, i seem to be having major rebooting issues... i'll diagnose and report back. (and these arent the fun quasi-reboots that don't go all the way back to M. these are full kernel panic.)
i am tentatively wondering if it is my clock state with droid x/2 -- ULV 1.1 on boot (never had a problem with it before) -- i need to go to bed for now. im going to change the clock state for now and see if it helps.
anyone else want to try 2.1final with 1.1 ULV? let me know how it goes? (might not want to do it on boot)
Last edited:
Zehkaiser, I'd suggest just backing up what you can and treating it like a new ROM installation, clearing the data and cache.
A
Angdroid
Guest
The build.prop was left default so the system version shows verizon. You guys can modify how you like. I believe it was the cause of some bugs.
The ROM is ready to OC out of the box. You an use recovery to flash the pre-made oc files from the fisson/addon floder or you can open up terminal and type overclock.
The stock framework is the 10% increments without the numbers. If you want numbers you can flash the framework file from the add on folder.
Decided not to go with 2.2.1 yet. I want to work with it some more and see what new features can be brought over to Vanilla Fission.
Myself and the team are taking the weekend off and we will have more info on Monday.
The ROM is ready to OC out of the box. You an use recovery to flash the pre-made oc files from the fisson/addon floder or you can open up terminal and type overclock.
The stock framework is the 10% increments without the numbers. If you want numbers you can flash the framework file from the add on folder.
Decided not to go with 2.2.1 yet. I want to work with it some more and see what new features can be brought over to Vanilla Fission.
Myself and the team are taking the weekend off and we will have more info on Monday.
so something funky must have happened when i upgraded to 2.1 final. my phone is uncontrollably rebooting now, and a nandroid back to a previous state didn't help. time for an sbf, let's hope it works.
That's strange. No rebooting here. All I did was nandroid back to 2.2 before flashing this rom. Strange though.
Sent from my DROIDX using XDA App
Sent from my DROIDX using XDA App
my guess? nothing whatsoever to do with the rom, just some sort of snafu. i'm in the middle of sbfing, then fully plan to reflash fission after i get it rooted again.
Similar threads
