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

Root XTRrom 3.03 observation

I had this same issue when i flashed to this rom last night. Someone on here suggested i reflashed with a wipe first. So that is waht i did, wipe then reflashed the rom and then the other 2 add ons and all is well. No FC as of yet in Accounts and Sync.

I did not turn on jit or LWP or apps2sd just FYI

Ok, so here is what I did ...

I cleared everything out, and reflashed the rom. Accounts and Sync worked again. I restored all my apps and data with Titanium Backup, Accounts and Sync still worked. Set all my screens back up and set up email, Accounts and Sync still worked. I was going to make a Nand backup at this point, but decided to update the 10 apps that the market had updates for. Finished that and boom, Accounts and Sync forced closed again. Started over and made backups as I went. This time though, I updated each app one by one, hoping I would catch the app that screwed up my Accounts and Sync. Now they are all updated and Accounts and Sync still works. I am at a loss. I just finished making another Nand backup with it working and all my apps up-to-date. Hopefully it wont happen again.
 
quick question, after i wipe data, by reflashing do you mean the original ROM then customizing desktop again or restoring the NAND backup?


Typicall re-flashing would mean flashing the original ROM and then you would have to customize everything again unless saved with Titanium Backup.

Restoring a Nand Backup will bring you to the exact spot where you made the backup. If you had a problem when you made the backup, you will still have it after a restore.
 
So what is the conclusion. Should you overclock on XTR?

Run it one way for at least three days, Hercules. Then switch to the other way. My guess is that you'll not see much difference at all in real performance of an xtrROM with it overclocked; not enough to keep it that way.

Those three days should wash out your usage habits, configuration and tweaks.

As far as the actual settings for the three days of overclocked CPU, I'd recommend conservative 710 with 245 for sleep, both on demand: 710/528, 245/245 (710/710 always worked well too, but I keep my recommendations leaning just a bit conservative ;)).
 
Run it one way for at least three days, Hercules. Then switch to the other way. My guess is that you'll not see much difference at all in real performance of an xtrROM with it overclocked; not enough to keep it that way.

Those three days should wash out your usage habits, configuration and tweaks.

As far as the actual settings for the three days of overclocked CPU, I'd recommend conservative 710 with 245 for sleep, both on demand: 710/528, 245/245 (710/710 always worked well too, but I keep my recommendations leaning just a bit conservative ;)).

Frisco, do you have your xtrROM clocked at 710/710?
 
Speed of the processes, moving from menu to menu, app loading, keyboard quick responsiveness, etc are all very good in xtrROMs I've run. No overclocking needed.

I did run 2.1.1 and then 3.0.3 at 710 for a while, but could detect no differences except for a slightly warmer battery cover.
 
This is one of the main reasons I've kept xtrROM in my device for so long now, always going back to it as my default after testing betas or Froyos.

I've found only one that comes close to xtrROM's performance and that is Aloysius.

Aloysius is my favorite.
 
Speed of the processes, moving from menu to menu, app loading, keyboard quick responsiveness, etc are all very good in xtrROMs I've run. No overclocking needed.

I did run 2.1.1 and then 3.0.3 at 710 for a while, but could detect no differences except for a slightly warmer battery cover.

Do you underclock? What about JIT?
 
Just curious: why not underclock with profiles while the phone's display is off/temp is hot/battery is low, etc.?

I have sleep profiles set in the Froyo ROMs, but not in xtrROM.. it's just that I've seen no need to do that; things are very smooth and fast, with no loss of battery, etc after a lot of experimentation with profiles, etc.
 
I have sleep profiles set in the Froyo ROMs, but not in xtrROM.. it's just that I've seen no need to do that; things are very smooth and fast, with no loss of battery, etc after a lot of experimentation with profiles, etc.

Not to push a point, but if you ever consider navigating with the Maps, with the display on, you may want to consider a temp profile. After a half hour in XTR my Eris was so hot I could barely hold it (and the car was air conditioned) before I did the profile.
 
Not to push a point, but if you ever consider navigating with the Maps, with the display on, you may want to consider a temp profile. After a half hour in XTR my Eris was so hot I could barely hold it (and the car was air conditioned) before I did the profile.

My map use has never been for more than a few minutes, and even then rarely.

The heaviest use my device gets is in the phone itself, messaging and web browsing. I'm not a multimedia user with the device at all, as I have other things for music and my computers for videos (why watch a video on such a tiny screen as a phone?), although occasionally I get something in a message that I need to see, such as pics of my grandkids sent to me or when a family member is traveling.
 
You don't? How come? :confused:

I believe above he said because he doesn't want to hinder battery life, tax his processor all the time, and just because it's so fast LOL. :)

I just downloaded this rom b/c I have been rom hopping for quite some time. My default was Suave Smush. I was trying out the "stable" 2.2's but they just seemed so slow to me. I put this XTR on and MAN is this thing fast. I haven't even overclocked at all and it still feels faster than any other rom I have used.

I had a guy at work with an EVO ask me what I was getting MFLOPS and I told him I don't care. In my experience, the higher the MFLOPS I have gotten, the laggier the phone has been lol. I just want a fast phone and this rom is the winner so far.
 
I have SetCPU at 528/528 with no profiles.
.

Frisco, if I'm reading this correctly you've got this set so that your CPU won't ever get a 'break'. Wouldn't it make more sense to set it at 528/240-ish to let the CPU slow down when not in use (ie: phone asleep). I don't think the ROM is in danger of being overtaxed or anything, but you might get an extra 15 minutes of battery life. :)
 
Frisco, if I'm reading this correctly you've got this set so that your CPU won't ever get a 'break'. Wouldn't it make more sense to set it at 528/240-ish to let the CPU slow down when not in use (ie: phone asleep). I don't think the ROM is in danger of being overtaxed or anything, but you might get an extra 15 minutes of battery life. :)

With just about every variable I've experienced going into this rooting thing, and with the variables I've seen posted, such as overclocking, battery saving measures, ROMs, etc, I've leaned heavily on personal experience with the Eris that I own.

When it occurred to me that overclocking xtrROMs was not necessary, I decided to test all of the profiles and main settings at or below 528.

My findings over time puzzled me for a bit because I honestly have not been able to detect any difference in battery life, speed or boot up with 528/528 with one exception: with SetCPU at a very low sleep profile setting, 190 I think, it seemed to take an annoying second to wake up and show me the screen, so I ditched the sleep profile and began watching battery levels with days of use and, as I say, have not noticed a darned thing in the way of increased drain.
 
I wasn't so much suggesting a sleep profile, as a lower down-side setting on your main (and only) profile. Just to allow the CPU to slow down in the event that it doesn't have much to do.
However, I bow to your greater wisdom and knowledge. :)
 
Well, in my explanation there I inadvertently blended the sleep profile findings and logic with that of the main 528/528 setting.. sorry.
 
I've never noticed any sort of speed difference with JIT on vs off when used on a 2.1 ROM. It does make a difference in linpack but honestly the number it gives doesn't seem to be related to actual phone usage.

I do notice a difference in xtrROM when overclocking. The extra speed does help but it's really only noticeable to me when multitasking (decent difference in responsiveness for me when I have music in the background) or using certain apps.
 
I've never noticed any sort of speed difference with JIT on vs off when used on a 2.1 ROM.

I did not notice anything at first, either.

Then I decided to run 3.0.3 with JIT for the whole day, then disabled the next day; both work days and a lot of messaging and calls and downloading graphs with the browser.

It was not dramatic, but it was noticeable, so I deemed it a step in the right direction, especially having decided overclocking was not necessary.
 
Back
Top Bottom