Droid x slower with froyo? Disappointed?

[Piiman]

I saw it on the internet. It must be true.

What he said the internets never lie

 

[HauntedHallows]

how are you guys checking your DX speed scores is this an app or something?

 

[droidSPARX]

how are you guys checking your DX speed scores is this an app or something?

type quadrant on the market. The icon of the app are bar charts

 

[_Aardvark]

Maybe this Droid X is the same style that Apple used in their death grid video?

 

[mntbighker]

Isn't it likely that a test build probably has a lot of debug code in it to help with development. And any release would be faster because the debug code is pulled out? Also, I would think things will take time to be optimized to work most efficiently with 2.2.

 

[anaphora68]

Honestly, what difference does a quadrant score make? If the phone appears to run faster, that's all that matters.

You're not using the X for quantum computing, so it really shouldn't make a difference...just my two cents.

 

[AJ_EVO]

Well someone bought it, the pictures are from an ebay item so I think he'd get in a bit of trouble for selling a photoshopped item. As far as it being a test build its got to be pretty much final if it releases next week. Idk it doesn't make sense but still bothers me.

You don't even have an X, why does it bother you.

 

[enjoytheride823]

All of these responses and no one was sharp enough to suggest that these low quadrant scores are probably the result of the 2.2 install reseting battery performance settings, thus severely lowering benchmark scores? How many of you actually own a Droid X, lol?

 

[schimm]

All of these responses and no one was sharp enough to suggest that these low quadrant scores are probably the result of the 2.2 install reseting battery performance settings, thus severely lowering benchmark scores? How many of you actually own a Droid X, lol?

Perhaps if you were sharp enough you'd run the tests yourself to see what battery mode changes do to scores and report the results:

Performance: 1178
Smart: 1213
Battery Saver: 1177

The first time I ran it (smart mode) I scored an 843. That's probably what happened. The first score always runs short.

 

[_inKredible_]

This looks like a bunch of B.S. to me. How can people believe this? I've never seen these sites be right, im sure this is faked some how.

Whatever. What do you know? Stick to your stoopid Tiburon forum newb.


LOL. I thought I recognized your screen name. Good to see a familiar ummm.....face? Avatar? Screen name? Haven't been on NT in quite a while though. White TXT pwns you even on androidforums.net

 

[lexluthor]

I don't even understand why this thread is here. One random screenshot that may or may not be real and may or may not have used an accurate testing method.

Why are we even talking about this?

 

[Wolfedude88]

I don't even understand why this thread is here. One random screenshot that may or may not be real and may or may not have used an accurate testing method.

Why are we even talking about this?

Didn't you read this thread? This is the internet it is always right!!!

 

[Steven58]

HAAHAHHA! I love it! Keep up the fun!

 

[10splaya22]

Whatever. What do you know? Stick to your stoopid Tiburon forum newb.


LOL. I thought I recognized your screen name. Good to see a familiar ummm.....face? Avatar? Screen name? Haven't been on NT in quite a while though. White TXT pwns you even on androidforums.net

Don't worry i see ur white text. Haha. I definitely recognize ur avatar!

 

[soapinmouth]

You don't even have an X, why does it bother you.

yes i do????

 

[ekyle]

I thought I read that Froyo was designed differently, specifically to allow it to run faster. I wouldn't think that the X, of all devices, would run slower with Froyo... but there's only one way to find out.

 

[YellowGT0]

If its a dev build JIT could be turn off. Galaxy S's Froyo dev build has no JIT also, or very unoptimized.

 

[kwest12]

There is no "eFuse thing"...well, not one that makes any bit of difference. Encrypted bootloader? That's a different story.

I'm relatively certain that this is untrue: I was in the irc chat the night before they achieved root. They attempted to root a phone and wound up essentially bricking the phone. As advertised, it went to the boot menu and since there was no Moto signed ROM to present it with, the phone was basically useless. The discussion following that event was that this was indeed the eFuse at work, and while it doesn't brick the phone outright by literally irreparably injuring the hardware, it does indeed do what Moto said it would (which is brick the phone for all intensive purposes.... unless we can get a Moto guy to leak some files to us!). I know Birdman tweeted that it wasn't active, he was in the irc chat and was in agreement with all this.

All of these responses and no one was sharp enough to suggest that these low quadrant scores are probably the result of the 2.2 install reseting battery performance settings, thus severely lowering benchmark scores? How many of you actually own a Droid X, lol?

Typically it isn't recommended make a swing at everyone in a thread (even if that swing is a wild hay-maker that misses the intended target and comes back to smack you in the face) .... especially on your first post here.

 

[nathan312]

There is no "eFuse thing"...well, not one that makes any bit of difference. Encrypted bootloader? That's a different story.

That's what I meant...I couldn't think of the word encrypted bootloader for some damn reason. So I said eFuse as a quick reference...sorry

 

[ylexot]

I'm relatively certain that this is untrue: I was in the irc chat the night before they achieved root. They attempted to root a phone and wound up essentially bricking the phone. As advertised, it went to the boot menu and since there was no Moto signed ROM to present it with, the phone was basically useless. The discussion following that event was that this was indeed the eFuse at work, and while it doesn't brick the phone outright by literally irreparably injuring the hardware, it does indeed do what Moto said it would (which is brick the phone for all intensive purposes.... unless we can get a Moto guy to leak some files to us!). I know Birdman tweeted that it wasn't active, he was in the irc chat and was in agreement with all this.

That is NOT eFuse. An eFuse tripping would result in a bricking that could only be reversed with special hardware to reset the eFuse. That is encrypted bootloader. Not a signed ROM? Not going to run. Put a signed ROM on and then it will work. Just because you don't have a signed ROM does not mean that the eFuse is tripped.

 

[kwest12]

That is NOT eFuse. An eFuse tripping would result in a bricking that could only be reversed with special hardware to reset the eFuse. That is encrypted bootloader. Not a signed ROM? Not going to run. Put a signed ROM on and then it will work. Just because you don't have a signed ROM does not mean that the eFuse is tripped.

Go into the Everything Root Forum and take a look at the OP in the Encrypted Boot Loader and eFuse thread (actually, I'll save you time, it's me). The point is, I know what the encrypted boot loader is, and I know what the eFuse is (spent quite a lot of time reading about each). As Motorola stated in their press release, the eFuse functionality in the DX is NOT to outright brick the phone (aka you can't even turn it on). The eFuse will function by tripping the system into the boot loader and lock it there until certain conditions are met. Right now this causes issues for us b/c the boot loader is signed by Motorola. If you don't believe me or want a more detailed explanation head over to the AllDroid forums: most of the guys responsible for the hacking progress to date are hanging out there.

I don't think a lot of people understand how incredibly lucky we were to gain root at all. When Birdman tweeted that the boot loader wasn't active, what he meant was that it wouldn't completely kill the phone like we originally thought: it gave some hope b/c even tho it trips to the phone to the boot loader, it still leaves the phone on and while the phone is on there is always the potential to hack it.


I apologize for leading taking this thread off topic so let me bring it back on.

My take on the Froyo situation is as follows:
The Motorola Milestone recently received the equivalent of a 2.2 skin: it sounds like they found a way to do some "double boot" or something crazy and load it to sit on top of the 2.1 kernal. The problem is that since it isn't a 2.2 kernal, certain features refuse to work (GPS or Wifi if memory serves me correctly) and it certainly won't see the speed improvements that regular 2.2 should. I am betting that either someone figure out how to do this (or some version of this) on the DX.

If not that, then the absence of the JIT compiler in a dev version of Froyo is another plausible explanation.

The bottom line is this: it is NOT plausible that the final version of Froyo (aka speed demon) will do anything but make the DX much, much faster.

 

[Piiman]

Go into the Everything Root Forum and take a look at the OP in the Encrypted Boot Loader and eFuse thread (actually, I'll save you time, it's me). The point is, I know what the encrypted boot loader is, and I know what the eFuse is (spent quite a lot of time reading about each). As Motorola stated in their press release, the eFuse functionality in the DX is NOT to outright brick the phone (aka you can't even turn it on). The eFuse will function by tripping the system into the boot loader and lock it there until certain conditions are met. Right now this causes issues for us b/c the boot loader is signed by Motorola. If you don't believe me or want a more detailed explanation head over to the AllDroid forums: most of the guys responsible for the hacking progress to date are hanging out there.

I don't think a lot of people understand how incredibly lucky we were to gain root at all. When Birdman tweeted that the boot loader wasn't active, what he meant was that it wouldn't completely kill the phone like we originally thought: it gave some hope b/c even tho it trips to the phone to the boot loader, it still leaves the phone on and while the phone is on there is always the potential to hack it.


I apologize for leading taking this thread off topic so let me bring it back on.

My take on the Froyo situation is as follows:
The Motorola Milestone recently received the equivalent of a 2.2 skin: it sounds like they found a way to do some "double boot" or something crazy and load it to sit on top of the 2.1 kernal. The problem is that since it isn't a 2.2 kernal, certain features refuse to work (GPS or Wifi if memory serves me correctly) and it certainly won't see the speed improvements that regular 2.2 should. I am betting that either someone figure out how to do this (or some version of this) on the DX.

If not that, then the absence of the JIT compiler in a dev version of Froyo is another plausible explanation.

The bottom line is this: it is NOT plausible that the final version of Froyo (aka speed demon) will do anything but make the DX much, much faster.

according to motorola the efuse makes the phone boot to recovery , not the bootloader, until a good rom is reinstalled. So until they get a good rom that phone is bricked.

 

[kwest12]

according to motorola the efuse makes the phone boot to recovery , not the bootloader, until a good rom is reinstalled. So until they get a good rom that phone is bricked.

lol I knew someone was gonna catch that slip up. I kept saying boot loader and I meant recovery. Good catch..............you bastard.... jk lol

 

[ckochinsky125]

Wait until you get 2.2 on your own X before you get your panties in a wad. No sense in making a judgement off screenshots we don't even know the credibility of.

Agree froyo is supposed to have the JLT(or whatever compilier) that is supposed to increase speeds greatly i wouldnt put too much belief into this