my P-sensor is faulty
when I make a call sometimes it turns the screen off without me putting it near my ears. Is it hardware related or ROM related?
I tested it on cm 7.2 and cm 9 and it happens specially after a restart.
Even if you don't put it near your ear, the screen will turn off automatically to save power. However, if after removing it from your ear it doesn't turn the screen on, slightly untighten the white screw behind the sensor (under the back door) and it will be fine.
how come it does that though? I saw the chinese video about the screw thing. Is this another engineering flaw in motorola's design?
I had a milestone 1 and the headset jack got broken/loose. had to put some paper in it be able to work
this will be my last motorola! time to save up
thanks Auris
by the way upon seeing your signature, is the 5/26 build of cm9 the best so far?
chachoi said:
by the way upon seeing your signature, is the 5/26 build of cm9 the best so far?
Click to expand...
Click to collapse
I am on 06-07... Just hadn't updated my signature.
tried untightening the screw and it works alright now,
I've had problems of the screen not turning on after a call, had to do a battery pull. Damn Motorola
thanks Auris
is it stable? I'll download it now. Then flash the cm9 kernel right? I'm using cm9 kanged by Fuzz
does the 06 07 2012 have the latest add ons like theme chooser?
Yes, it is stable and yes, it has theme choser.
Related
I rooted and put Damage's rom on my phone a few weeks ago when the 2.1 leak came out. When I was on 1.5 and I would watch a movie from my sd card, all the lights on the phone would go out (except the charging light if plugged in). It wouldn't matter if it was light out or in a dark room, the bottom panel lights would all turn off.
I noticed in damage's rom, they stay on when watching videos. This is slightly annoying to my wife at night when she wants to sleep. That light is so bright it lights up the entire room. I just flashed Fresh 2.0d just to try it out and decided to check the lights when watching video there, and it's the same thing.
Is there a way to fix that?
HA!
at last! a reason the light sensitive leds can be considered a BUG.
this just made my day.
thank you.
and no theres no fix
Lol, I actually miss the "broken" trackball light, I'd just as soon disable it all together if I knew how.
So you are saying the way it was on 1.5 was considered broken and now it's not?
Is there a way to break it again? LOL
CodeMonk said:
So you are saying the way it was on 1.5 was considered broken and now it's not?
Is there a way to break it again? LOL
Click to expand...
Click to collapse
its all a matter of opinion. anyone who knows me knows i made love to my trackball led for so long on 1.5 that when i switched to 2.1 i went into withdrawls.
id advice nandroiding to 1.5 everysingletimeyouwanttowatchamovie (j/k)
live with until the evo
bigger screen, and hey! no trackball!
oh, yeah, and a FN KICKSTAND
Ok for a real answer to the trackball.. We dont have source to the .29 kernels that the 2.1 roms use. Trackball and camera are 2 main things no one knows much about. The only fully working trackball (in every way, like in movies) will be on the 1.5 roms as of now. Until sprint releases its update, or releases the .29 kernel.
Or if some dev like toast wanted to spend every moment back porting the trackball to the .27 kernel. Which for most of the people here, it would be a waste.
Just flashed a new ROM and noticed there is a line about a little higher than halfway that seems to tear even when I move the screen slightly. Is this a hardware issue or a ROM issue? Never noticed before. Should I unroot and send to sprint? Its really noticable.
fmedina2 said:
Just flashed a new ROM and noticed there is a line about a little higher than halfway that seems to tear even when I move the screen slightly. Is this a hardware issue or a ROM issue? Never noticed before. Should I unroot and send to sprint? Its really noticable.
Click to expand...
Click to collapse
What kernel does it show when you go to settings > about phone? That's most likely the cause
Running netarchys universal 4.1.9.1. with myns new twopointtwo rom. It went away now, but was pretty bad at that one point. Seems to come and go.
fmedina2 said:
Running netarchys universal 4.1.9.1. with myns new twopointtwo rom. It went away now, but was pretty bad at that one point. Seems to come and go.
Click to expand...
Click to collapse
You may want to find his thread in the dev section and try another version of it. It usually stays on the first page or two.
What about this version is causing this effect? I have ran this kernel before with no problems. Is this for sure a software issue and not a hardware?
It's only when you turn the phone on after a ROM flash, or reboot. Just turn the screen off, and then back on, and it fixes it...
ImmortalLuD said:
It's only when you turn the phone on after a ROM flash, or reboot. Just turn the screen off, and then back on, and it fixes it...
Click to expand...
Click to collapse
I am having the same problem. I find that different kernels clear it up. I also suspect that on some kernels it happens as the phone heats up.... hmmmm....
First of all, I know that I have read about this problem in other threads but I cannot find it; I think it was associated with custom ROMs but I'm not entirely sure.
I have two problems with my sound right now:
popping
Every time the tables boots up the speakers pop. No a big deal and it might be just because they get activated and the current causes the pop. But every time a sound is made? That is annoying!
humming/screeching/buzzing
Now this is the scariest problem. The sound that comes from "within" the tablet, i.e. behind the screen and not the actual speakers. It does not always appear but seems to be linked to apps trying to use sound. It almost sounds like a hard drive spinning irregularly or a distant old dial-up modem (weird analogy, I know). I don't know what's causing it but in my opinion it's not a good sign.
Again, if anyone here remembers where it has been discussed already I will take the blow as long as I can find out if the problem(s) have been solved somewhere.
Thanks y'all!
1. Everyone's device does that. It's just the way the device wakes the speakers before playing a sound as you say. Would hope Asus could do something about that in the future.
2. It sounds like you are hearing the screen's backlight frequency. Not everyone will hear this (as we lose the ability to hear certain frequencies as we get older), but again it happens with everyones device, and is normal with any screen using a backlight.
Do you have a custom rom on it?
Oyeve said:
Do you have a custom rom on it?
Click to expand...
Click to collapse
Yes, I do. I use the PRIME! 1.4 ROM and the blades-clemsyn overclock kernel. It has been an issue since the 3.1 upgrade I think. Never had it stock though so I cannot comment on issues with the stock ROM, unfortunately.
stuntdouble said:
2. It sounds like you are hearing the screen's backlight frequency. Not everyone will hear this (as we lose the ability to hear certain frequencies as we get older), but again it happens with everyones device, and is normal with any screen using a backlight.
Click to expand...
Click to collapse
What makes this theory a bit wobbly is that the sound isn't always there. It seems to be application-specific. I would expect a backlight frequency (like a fluorescence bulb?) to be audible whenever the backlight is on and not during one application running but not the other.
Process of elimination.
Roll back to stock and see if the problem occurs. If so, sounds like you’re going to have to return it for an exchange.
smellmyfingers said:
Process of elimination.
Roll back to stock and see if the problem occurs. If so, sounds like you’re going to have to return it for an exchange.
Click to expand...
Click to collapse
The scientific way, I like your idea
Do you also know if there has been a use for the SBK to enable root for the stock ROM?
funnycreature said:
What makes this theory a bit wobbly is that the sound isn't always there. It seems to be application-specific. I would expect a backlight frequency (like a fluorescence bulb?) to be audible whenever the backlight is on and not during one application running but not the other.
Click to expand...
Click to collapse
Each app will tell your device to process the images onscreen in different ways, whether thats the refresh rate, resolution or just pixel density, so you would still get different frequencies from different apps all the time. Anyway I'm not saying that's 100% the reason, it's just a possibilty based on what you were describing.
stuntdouble said:
Each app will tell your device to process the images onscreen in different ways, whether thats the refresh rate, resolution or just pixel density, so you would still get different frequencies from different apps all the time. Anyway I'm not saying that's 100% the reason, it's just a possibilty based on what you were describing.
Click to expand...
Click to collapse
Very good points! Never thought of it this way... Do you also think it's worth going back to stock and try to figure it all out or just take it "as is"?
If it is what I thought it was, it won't make a difference which rom you use, and it's a normal feature of the tablet. You must live in a very quiet place to hear it all the time or have very sensitive ears. If it's not that, then trying another rom as mentioned above may help you narrow down the list of causes. If it's annoying you too much then possibly it IS a fault with the tablet and in which case you'd need to get a replacement. If it was me I'd probably roll back to the stock rom just to see.
stuntdouble said:
If it is what I thought it was, it won't make a difference which rom you use, and it's a normal feature of the tablet. You must live in a very quiet place to hear it all the time or have very sensitive ears. If it's not that, then trying another rom as mentioned above may help you narrow down the list of causes. If it's annoying you too much then possibly it IS a fault with the tablet and in which case you'd need to get a replacement. If it was me I'd probably roll back to the stock rom just to see.
Click to expand...
Click to collapse
After 20 years of listening to metal I highly doubt that my ears are that sensitive but you never know I might try the stock ROM as soon as it has been rooted but for now I don't think it's worth it. I was more worried about something inside the device being tortured
funnycreature said:
Yes, I do. I use the PRIME! 1.4 ROM and the blades-clemsyn overclock kernel. It has been an issue since the 3.1 upgrade I think. Never had it stock though so I cannot comment on issues with the stock ROM, unfortunately.
Click to expand...
Click to collapse
I hear the buzzing sound too and I am also unning Prime 1.4 ROM and Clemsyn-Blades KERNEL. I hear it on the Left side of the tablet and sounds like its coming from the speaker but more towards the screen edge. Never heard it on Stock though.
dja2k
I'll have to wait for another reboot to test this, but I hear what I call high pitched 'tweeting' from the speaker I just have to touch the volume up/down button on the tablet and it seems to instantly stop.
I'll test here in a bit. Using Primordial 3.1 and the OC Kernel at 1.4 right now.
Update: 'twas my imagination on the touching of the volume button. It squeals a bit thru all the ASCII art and status boot screens, but settles down when the lock screen appears. Not a nuisance, but audible.
Sent from my Transformer TF101 using XDA Premium App
I updated the Clemsyn-Blades v6 KERNEL to v7ELITE and I don't hear the buzzing sound anymore. Maybe it was that version of the custom KERNEL. I will check it out, maybe it is just random.
dja2k
funnycreature said:
Yes, I do. I use the PRIME! 1.4 ROM and the blades-clemsyn overclock kernel. It has been an issue since the 3.1 upgrade I think. Never had it stock though so I cannot comment on issues with the stock ROM, unfortunately.
What makes this theory a bit wobbly is that the sound isn't always there. It seems to be application-specific. I would expect a backlight frequency (like a fluorescence bulb?) to be audible whenever the backlight is on and not during one application running but not the other.
Click to expand...
Click to collapse
It's the custom kernel you're using, mine was doing the same thing with some weird high pictched sounds too. I reflashed the stock ASUS kernel and it hasent done it since. Just to make sure, I reflashed the custom kernel you're using and the speakers make the humming noise again.
cdpriest said:
It's the custom kernel you're using, mine was doing the same thing with some weird high pictched sounds too. I reflashed the stock ASUS kernel and it hasent done it since. Just to make sure, I reflashed the custom kernel you're using and the speakers make the humming noise again.
Click to expand...
Click to collapse
I haven't noticed the humming since v7 of Clemsyn/Blades' kernel. But the popping is as bad as ever. I wish there was a fix for that too!
funnycreature said:
First of all, I know that I have read about this problem in other threads but I cannot find it; I think it was associated with custom ROMs but I'm not entirely sure.
I have two problems with my sound right now:
popping
Every time the tables boots up the speakers pop. No a big deal and it might be just because they get activated and the current causes the pop. But every time a sound is made? That is annoying!
humming/screeching/buzzing
Now this is the scariest problem. The sound that comes from "within" the tablet, i.e. behind the screen and not the actual speakers. It does not always appear but seems to be linked to apps trying to use sound. It almost sounds like a hard drive spinning irregularly or a distant old dial-up modem (weird analogy, I know). I don't know what's causing it but in my opinion it's not a good sign.
Again, if anyone here remembers where it has been discussed already I will take the blow as long as I can find out if the problem(s) have been solved somewhere.
Thanks y'all!
Click to expand...
Click to collapse
Sound like you got a Bee in there eathing rice crispies
Hey guys, so I was looking into buying the a used Motorola Defy since the TMOUS version can work on AT&T's 3G. I was just wondering if there are any general hardware-related problems that are common for Defy users.
For example, I know the LG Optimus 2X/G2X had a lot of problems with freezing and stuff, and my old Samsung Vibrant was known for having terrible GPS connection.
On a side note, how is CyanogenMod (either 7, 9, or 10) as far as bugs are concerned? I tried looking into the bugs but it's kinda hard to tell without being familiar with the Defy dev scene.
Thank you!
There was a problem with early defy where the phonespeaker doesn't work. The newer ones doesn't have this problem.
Cyanogenmod 7 is really stable and bugfree.
cyanogenmod 9 isn't in development anymore, so it isn't really stable or bugfree.
Cyanogenmod 10 works really good and is bugfree for me, however aokp jb works even better for me.
Exactly what I wanted to know. Thanks!
Sent from my HTC Sensation using xda app-developers app
Sorry for double-posting but there was another thing I was wondering. I keep reading about Red/Green Lens models, and how Green lens ones won't have a working camera if it's upgraded to gingerbread or something like that. Is that still true, or has it been fixed?
I can confirm the speaker problem. the stock ROM had Bluetooth problems too. Although that might just be a anti piracy measure butI couldn't send/ receive apks and later I couldn't send any files without using third party Bluetooth applications (Bluetooth File Transfer). But now I am running CM10 ( Hail quarx!!) The Bluetooth issue is solved but the speaker still stops playing music suddenly.
I wonder if there is a fix??
Sent from my MB525 (Running quarx's CM10 0912 nightly) using xda app-developers app
phantomsniper773 said:
Sorry for double-posting but there was another thing I was wondering. I keep reading about Red/Green Lens models, and how Green lens ones won't have a working camera if it's upgraded to gingerbread or something like that. Is that still true, or has it been fixed?
Click to expand...
Click to collapse
There are actually 3 Versions. The Defy MB525 with the Green Lense, The defy MB526 (the defy +), and the Defy MB525 with the redlense.
The redlense defy and the defy + are pretty much the same except the battery. The Greenlense defy is different because it has a different camera module. For some reasons motorola only gave an update to gingerbread for the defy+ and the redlense.You can also flash it on a green lense def but your camera wont work(kernel related issues).But if you choose to run a custom firmware you wont have those problems. Due to the fact that we found a way to run custom kernels some days ago, the problems with the camera module are gone in the future.
Oh, I see. So from what I understand after reading up a little bit more, the green lens camera should be working identically to the red lens, except only the red lens can do 720p. Is that correct?
But if 720p recording isn't all that important to me, the green lens should be fine for running all custom ROMs as well as the red lens, right?
my phone ran in to a problem where the search buttons led would not work however gave it to the service center and they replaced the part,i thing it was only my phone having this problems, anyways go ahead and buy the defy
Some
Hey there,
The common problems i can confirm is the ear piece speaker problem still occurring on the MB526's (Defy+).
The only other problem i occur qua hardware is the digitizer freaking out from time to time. it's usually fixed with a lock/unlock.
That's all i can tell from my experience with my defy+ for over a year
As some of us know, after knowing your Desire HD for quite a long time, flashing a ROM such as CM7 has incurred problems such as camera flash shutdowns.
The explanation for this is simple! :laugh: It is NOT (by about 99.999%) a hardware fault. It is due to the phone withdrawing too much power at boot due to some voltage settings and kernels...
Solution 1
Change your kernel and adjust voltage settings...
Solution 2 (The better one)
Replace your Desire HD battery, it may seem drastic for some cheapskates (like me), but is effective. ONLY do this is Solution 1 didn't work. Also, it may give you better battery life.
Solution 3 EXTREME MEASURES
Revert to a stock ROM... NOT a flashed one, I mean a full fledged RUU (Rom Update Utility).
For RUU's check out the Development forum.
FINAL SOLUTION (MOST EXTREMELY FREAKING WEIRD MEASURES)
Lock bootloader, undo s-off and contact HTC.
In my personal experience the battery solution was the best and worked like a charm.
Have a good day.
And click thanks.
Come on... 103 views and no thanks..? Come on people!!!
can you explain more about solution 1 !
Dr. Globbyglob said:
Come on... 103 views and no thanks..? Come on people!!!
Click to expand...
Click to collapse
Not sure if serious... :/
PHOENIX-9 said:
can you explain more about solution 1 !
Click to expand...
Click to collapse
Go to the development section, go to the index and look at the kernel category. Pick one that seems good to you and use it. The dev might also write about what voltages are good for the kernel, and to change them I recommend SetCPU
I hope I helped the poor poor people with this issue.
:good::good::good::good::good::good:
For me this issue comes and goes, so I guess it's a kernel/system settings related.
right now on Sabsa Prime v11 @1.5Ghz and no issues with flash.
-SmOgER said:
For me this issue comes and goes, so I guess it's a kernel/system settings related.
right now on Sabsa Prime v11 @1.5Ghz and no issues with flash.
Click to expand...
Click to collapse
That's nice, this tutorial was just for those people who are going absolutely KAY-RAY-ZEE at their DHD's. (like me)
I had the same issue, on a stock phone. The DHD would first shut down when doing a photo with flash, then when simply doing a photo, then sometimes without any apparent reasons, even with screen off. In the last times it would works only when without the sim card, every time i booted with SIM in the phone shutted down at the moment it was gaining signal.
I bought a new battery and, by now at least, it solved everything.
D-7 said:
I had the same issue, on a stock phone. The DHD would first shut down when doing a photo with flash, then when simply doing a photo, then sometimes without any apparent reasons, even with screen off. In the last times it would works only when without the sim card, every time i booted with SIM in the phone shutted down at the moment it was gaining signal.
I bought a new battery and, by now at least, it solved everything.
Click to expand...
Click to collapse
Yay just like me! Nice that it worked, it happened to me as well. Plus do click thanks though.
YAY!