Related
Question 1
My Droid 3 is really slow compared to my T-Mobile G2. The Droid 3 has a dual-core 1 ghz cpu, while the T-Mobile G2's single-core is clocked at 800 mhz. I doubt that the T-Mobile G2's cpu is superior.
So what is causing my Droid 3 to underperform?
Question 2
There is a little hole between the USB port and the HDMI out. I don't know if this is my imagination or not, but I saw this hole light up yellow (only once, since I received Droid 3 2 months ago). Is this the charging LED? Why doesn't it light up? Am I imagining things?
Question 3
Did anyone notice that their Droid 3 got even slower after the latest official update a few weeks ago?
"question 1"
my motorola droid is overclocked to 1.2ghz and in benchmarks only scores a 1500
my droid 3 scores a 2500
check what is using up your ram perhaps? are you using the stock moto blur launcher?
also have you ran the script to rename all your bloatware as .bak? big improvement less crap running in the background
Hmmm, can someone recommend me the benchmarking app that most reviewers use? I always wanted to know what they use to benchmark and compare but I never got to finding out the app name.
Also please, someone answer my LED question.
quadrant standard edition/global quadrant rank
The LED is a charging light. When the phone is OFF and your charger (or data cable) is plugged in, the light goes white. (Only after applying the OTA)
Also talking about the OTA, I find my phone slightly faster, and definately more stable.
I had a Droid x at 1.6 ghz and a cliq previously. As well as a D inc 2. The droid 3 is vastly superior in EVERY way. If your phone is that slow, I recommend you either Factory reset and/or sbf and clear cache/dalvik after rooting and bootloadering then run another factory reset.
Sent from my DROID3 using XDA App
poetryrocksalot said:
Question 1
My Droid 3 is really slow compared to my T-Mobile G2. The Droid 3 has a dual-core 1 ghz cpu, while the T-Mobile G2's single-core is clocked at 800 mhz. I doubt that the T-Mobile G2's cpu is superior.
So what is causing my Droid 3 to underperform?
Click to expand...
Click to collapse
I came from a Desire Z too, and frankly I can't call the D3 an upgrade.
The DZ had a better screen, a better form factor an hugely better battery, a better reception, a way faster modem and a better CPU.
D3 wins just on the volume level, and in the keyboard layout side.
Not enough.
The Droid X was bad (not having owned one but a friend had one that perma froze often). And well the Cliq is just crap. So I can see why the Droid 3 is vastly superior to one of you (can't quote you because I am using mobile app).
I still like my D3 more than the G2 though. It's just relatively slow...by a small margin. But that shouldn't be like that with dual core and clock rating. I also agree the battery is crap.
But the reception really....I mean really depends on where you are cause my G2 was always running on 2G.....G2 had its flaws too, like: battery popping out when phone dropped, screen opens and closes by accident too easily, and I feel like 3.7 inch screens aren't enough. I actually enjoy watching Netflix on the D3. The D3 keyboard isn't just better, it's probably the best yet. It rivals the keyboards on Touch Pro2 and Nokia E90.
Sent from my DROID3 using XDA App
poetryrocksalot said:
But the reception really....I mean really depends on where you are cause my G2 was always running on 2G.....G2 had its flaws too, like
Click to expand...
Click to collapse
LIkely the D3 does better on CDMA networks. Here where luckily CDMA is absent, the D3 does worse than the DZ, which in turn did worse than the milestone 1
It's just relatively slow...by a small margin.
Click to expand...
Click to collapse
Teorhetically the new OMAP should UMILIATE the G2's qualcomm CPU, the real world says differently, I don't know if the culprits are the amateur motorola coders, or the CPU itself, probably a combination of the two.
poetryrocksalot said:
(can't quote you because I am using mobile app).
Click to expand...
Click to collapse
Yes you can, press the post you wish to quote and a menu will pop up.
Raa_1 said:
The LED is a charging light. When the phone is OFF and your charger (or data cable) is plugged in, the light goes white. (Only after applying the OTA)
Also talking about the OTA, I find my phone slightly faster, and definately more stable.
Click to expand...
Click to collapse
That LED has been discussed on the motorola forum. They say it works as follows:
If the phone is off and the battery has <5% charge, when you plug in your phone you'll get the LED showing it is charging so you know the phone has a "sign of life".
https://supportforums.motorola.com/message/467971#467971
Regarding quoting with the XDA app, I realized I could quote but I avoid double posting and quoting 2 guys in one response is too annoying for me.
I am pretty sure it's the coders fault. I suspect the moto bloat is the culprit behind this, but I am a stock ROM kind of guy. I avoid flashing vustom ROMs because I hate finding the right one only to realize that the devs constantly update the ROMs and that some bugs need to be fixed.
With stock, the update process is simple and automatic.
Sent from my DROID3 using XDA App
I have experienced a large increase in battery and home screen speed after the latest update. In terms of battery, I think all the gains are in the power consumed by the cell radio while on standby or with screen off, so moderate to low users will probably see the most gains - someone who is constantly on their phone will not.
Notice I said homescreen speed, not overall speed. What I believe happened is that Motorola moved the home screen from the cache to a system app. Before the update, the home screen would constantly get kicked out of the cache in RAM (you can view this in the memory manager, select your free memory at the bottom to view cached items - pre OTA the homescreen would be there unless you were low in which case it got flushed, while post-OTA you never see your homescreen there). However, what this does it reduces the amount of RAM available to a given app when it is open, since the homescreen is kept in RAM to keep the system snappy, so individual app performance may suffer when you have a lot open and the are constantly switching in and out of RAM.
I have stock motoblur - have people on new OTA seen improvements from using ADW or LP+? Have people seen free RAM increases when freezing bloat? Given that the homescreen has moved to system memory, I am not sure using a launcher will help anymore, and I am not sure how much bloatware is actually running in the background and taking up RAM versus simply taking up space on the phone.
Of course, I am a noob, so I could be completely wrong...it's a bit conjecture. I do feel like this phone wold be so much better if Moto matched HTC and put in 768 of RAM, or even blessed it with 1GB like the Bionic or Atrix.
Would it be possible to have the new Moto X features like the always listening google now without draining the battery?
And the flip for camera and with the same camera apk?
And the notification on screen with message info and everything?
Basicly I love all the new features Moto X could bring to a phone but the phone it self isn't as good as the HTC one
Sent from my HTC One using xda app-developers app
The always Google Now feature is provided by a low energy and slow processor -which One doesn't have so no about that. The notification thing is only possible on AMOLED screen, One is a SLCD.
Sent from my All Metal HTC One
The always on Google Now certainly drains battery. Even normal GNow drains battery by a decent amount, which is why I disabled it.
BartuG said:
The always Google Now feature is provided by a low energy and slow processor -which One doesn't have so no about that. The notification thing is only possible on AMOLED screen, One is a SLCD.
Sent from my All Metal HTC One
Click to expand...
Click to collapse
This. Same with the screwdriver for camera thing.
The Motorola X wouldn't be so expensive if the features that it had could be implemented via software.
Google: X8 mobile computing system.
Moto X has customized low powered core for this
strange quirk with active notifications.
1) notifications light up using select few pixels (GOOD)
2) notifications fade out and go away completely (GOOD)
3) all pixels light up very dim for a second (KINDA ODD)
You have to have the lights off in your room for you to notice it really.
Check it out...
Mine doesn't do that in a pitch black room.
Sent from my XT1053 using XDA Premium 4 mobile app
matt87n said:
strange quirk with active notifications.
1) notifications light up using select few pixels (GOOD)
2) notifications fade out and go away completely (GOOD)
3) all pixels light up very dim for a second (KINDA ODD)
You have to have the lights off in your room for you to notice it really.
Check it out...
Click to expand...
Click to collapse
you have the beginnings of the universe!
nah, you should get that replaced.
i forgot to mention im still running 4.2 in Canada..
Rhiannon224 said:
Mine doesn't do that in a pitch black room.
Sent from my XT1053 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
its super super dim and hard to catch if u dont OCD over things like i do.. lol
call motorola, they might be able to get your a replacement, if you havent rooted and unlocked bootloader
oh man, seriously nobody else has this going on? its such a small bug and seems fixable.. i dont wanna send back my motooo!
gonna try n reset the phone to see what happens.. my expectations are near nil though.. anyone else with this strange issue?
Just tried in a pitch black room. Saw nothing after the active display time faded out.
The whole screen flickers gray right? I'm on a Rogers X. Mine does that.
Sent from my XT1053 using Tapatalk
Just for giggles, I checked out my phone and two coworkers phones and none of them do it. Two AT&T, one Verizon.
Yeah, I don't think that's normal. The whole reason Active Notifications doesn't annihilate your battery life is because only the pixels that need power, get power. That's how AMOLED works. You can turn off each individual pixel. Which is why you don't see something like Active Notifications on phones with an IPS panel such as the Nexus 5. IPS works by lighting a giant backlight, and the pixels act something like shutters, opening and closing as needed. Of course it's more technical than that, but in layman's terms, that's how you can think of it.
So yeah. Something's up. Those pixels should not be lighting up on an AMOLED display. If it were an IPS, that would be normal.
Two Rogers phones here, neither do that.(I am running 4.4 though)
My VZW MM doesn't do that. Seems strage, as it's a big selling point for the phone that it only lights the pixels you need.
i have the same problem, im on 4.2.2, i will take it to motorola
Hayaku said:
The whole screen flickers gray right? I'm on a Rogers X. Mine does that.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
YA! a Rogers phone running 4.2 still.. i did a reset but it didnt help
Johmama said:
Yeah, I don't think that's normal. The whole reason Active Notifications doesn't annihilate your battery life is because only the pixels that need power, get power. That's how AMOLED works. You can turn off each individual pixel. Which is why you don't see something like Active Notifications on phones with an IPS panel such as the Nexus 5. IPS works by lighting a giant backlight, and the pixels act something like shutters, opening and closing as needed. Of course it's more technical than that, but in layman's terms, that's how you can think of it.
So yeah. Something's up. Those pixels should not be lighting up on an AMOLED display. If it were an IPS, that would be normal.
Click to expand...
Click to collapse
thanks for the explanation! cant wait for OLEDs to be ubiquitous.. wonder what comes after OLED, or is it the final frontier for active matrix
Since its a problem that only I would notice, and only in the darkest of rooms, I Dont want to go thru the hassle of explaining to the poor guys at the Rogers store why I want to exchange the phone. I'm wondering whether it may be a software related thing... What's the best way to reset the software besides deleting all data.. Is there a way to get down deeper and scrub it clean?
Sent from my XT1058 using Tapatalk
matt87n said:
Since its a problem that only I would notice, and only in the darkest of rooms, I Dont want to go thru the hassle of explaining to the poor guys at the Rogers store why I want to exchange the phone. I'm wondering whether it may be a software related thing... What's the best way to reset the software besides deleting all data.. Is there a way to get down deeper and scrub it clean?
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
Well, it's most likely just a software bug in the Rogers 4.2 rom. As the others who are not on Rogers do not have this issue, your best bet is probably to upgrade to the T-Mobile 4.4 ROM, which is what I'm running (I'm also with Rogers).
EDIT: Just noticed someone had said that they had Rogers phones that didn't have the issue... I say proceed with caution. You can try reflashing the Rogers stock firmware from the internet, see if that clears it up?
I've had 4 Moto X's. They all did this. It doesn't impact battery enough for me to worry about it. It may be the backlight or something though I admit I know very little about how SAMOLED works.
I think is happening is that there's some code in there that's telling the transistors to discharge throughout the matrix instead (which explains why the whole screen is dim for a second) which helps with reducing the amount of wear on individual parts of the screen (the notification icons itself). If someone can compare the ActiveNotification between 4.2.2 and 4.4, that would be nice.
As the subject. Is that my impression or something well known? Is there an app/setting to make it more natural?
Thanks!!!
PS. I'm on stock kit Kat.
Sent from my XT1053 using XDA Premium 4 mobile app
Looks fine if you ask me.
I'd rather have it more saturated than have it looked washed out.
Its different compared to GS4 or iPhone but not bad. Considering I regularly get 3± hours screen time on a 24+ hour cycle I have no complaints.
Sent from my XT1060 using Tapatalk
Compared to my S2, the screen colours and black are amazing. Hard to even look at my s2 now.
But.... Some can find fault in anything somehow. Lol
Sent from my Moto X cell phone telephone.....
The screens and saturation levels do vary a little phone to phone. I have played with 3 Moto X's quite a bit now and each have been different. My first one isn't over saturated at all, the screen on it has a little more yellow to it. The other two have more of a blue tint and show more saturation. The whites do look better on the second two but the first is easier to look at in the dark.
I don't think there is any way to adjust it or even change the DNIe mode like Samsung allows. People wrote custom kernels for the Nexus 4 to allow color adjustment but there aren't nearly as many devs working on the Moto X, so you're probably stuck with what you get. I don't imagine that they do any factory calibration to speak of, so of course it will vary greatly between panels.
Unfortunately, oversaturated is the new properly calibrated. The problem is that it has a better off-the-shelf look when people who are clueless are comparing models in the store--hold a Moto X or GS4 up next to an iPhone or Nexus 5 and the colors "pop" more, which seems to be more appealing to the average consumer than the more muted appearance of a display with proper sRGB calibration.
Cool. Thanks guys. In on a xperia z1 and the display is amazing. So using the motox is very different. But yep I should be used to. Another thing I noticed is that is way less bright under the sun. Again I think is just a calibration thing since we if you switch to manual you can increase it much more than the way our light sensor detect it.
Sent from my C6903 using XDA Premium 4 mobile app
DAddYE said:
Cool. Thanks guys. In on a xperia z1 and the display is amazing. So using the motox is very different. But yep I should be used to. Another thing I noticed is that is way less bright under the sun. Again I think is just a calibration thing since we if you switch to manual you can increase it much more than the way our light sensor detect it.
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can try the app Lux to control auto brightness and Screen Adjuster to try to correct the colors.
I was wondering if anyone had tried one of the active notification app alternatives to Moto Display. I'm curious as to how performance stacks up and the effect a third party app would have on battery compared to our native one. I've used peek before and it's cleaner, easier to use, more customizable, etc. Etc. ( I can also calibrate it to turn the display on when I pull my phone up, instead of every damn time it jiggles ).
So anyone given any a try?
G4 Man2 said:
I was wondering if anyone had tried one of the active notification app alternatives to Moto Display. I'm curious as to how performance stacks up and the effect a third party app would have on battery compared to our native one. I've used peek before and it's cleaner, easier to use, more customizable, etc. Etc. ( I can also calibrate it to turn the display on when I pull my phone up, instead of every damn time it jiggles ).
So anyone given any a try?
Click to expand...
Click to collapse
I used AcDisplay on my Note 3 and saw no negative battery stats from it, about the same as using the regular lockscreen. Haven't thought to try it on the X.
jdubya42 said:
I used AcDisplay on my Note 3 and saw no negative battery stats from it, about the same as using the regular lockscreen. Haven't thought to try it on the X.
Click to expand...
Click to collapse
I loved acdisplay on my note 2. Moto display needs customization
Sent from my XT1095 using XDA Free mobile app
I've started to use Peek instead of Moto Display, the battery life is a ton better since the sensors don't stay on constantly and the customization is great