Database Users

[Q] Reception/Bluetooth issues

Please, somebody tell me there's hope. 2 really annoying & disappointing things are happening. My bluetooth keeps randomly disconnecting, and to make matters worse the status bar icon still shows it is connected, but it's not. Second, I am dropping calls almost daily, and I'm mostly in places where 2 seconds before the drop I had 4 bars!!! I went to a store today & got a replacement SIM (50.01 vs. 39.01 markings) hoping that might solve it, not happening. And the signal strength almost never shows less than -105 dBm, sometimes -97. I NEVER had a dropped call or any bluetotth issues with either my old trusty G1 or the MT3G I just came from. I'm really trying to love the phone, it has so many positives. But the fact that it's a "phone" and it's basic function is skewered is pissing me off big time. Please, someone tell me I ain't the only one experiencing these issues, and, that either the OTA FroYo or Cyan's first ROM is gonna fix 'em? Better yet, any known fixes now? Are these issues in any way related to the data issues, possibly? When I called Tech Support last night they said to try a hard reset, but I really don't want to do so, unless I can flash one of the stock/de-TW'ed "stock" ROM's written about in the Dev. threads. Anyone have any concrete suggestions or explanations? Thanks...

TouchScreen issue resolved in gingerbread?

So before the gingerbread update i was experiencing the nexus one touch screen issue. This issue would happen mostly when the phone would be charging or warm, and the y coordinate of the touch screen would be off by about an inch. (I would post a link to youtube but i can't yet... new member =/ ) So if you try to answer your phone while the defect was active, you couldnt, because touching the slider would be recognized as trying to touch the 'menu' key on the phone.
Anyway, after gingerbread got pushed to my device, i have yet to experience this issue!! i havent been able to find anyone reporting this resolution. i'm extremely please about this because it was becoming a deal breaker after i missed an important call because i couldnt answer my phone due to the issue!!
anyone else experiencing this resolution!?

In my experiences it does still occur, although seemingly less frequently. It is a hardware problem though so probably won't disappear regardless of the OS

Hollow.Droid said:
In my experiences it does still occur, although seemingly less frequently. It is a hardware problem though so probably won't disappear regardless of the OS
Click to expand...
Click to collapse
Yup. For some reason I have worse now than before. Maybe I'm just using it more now. Lately it's driving me nuts, to the point of actually looking at a replacement.

Memnoch30 said:
Yup. For some reason I have worse now than before. Maybe I'm just using it more now. Lately it's driving me nuts, to the point of actually looking at a replacement.
Click to expand...
Click to collapse
this is where I was at before the push, i was seriously considering the incredible s, but for now it seems to have completely disappeared from my device...
I've also heard its a hardware issue (I do believe it to be true, not questioning that), so i found it extremely odd that its not happening now on my device.
Guess I'll just keep my mouth shut and enjoy

Observed no difference. The bug still appears every now and then. Doesn't bother me much because it usually occurs when the phone's charging. Not when I'm on the street using it. I heard that removing any kind of screen protectors can actually solve this problem.

NexusDro said:
Observed no difference. The bug still appears every now and then. Doesn't bother me much because it usually occurs when the phone's charging. Not when I'm on the street using it. I heard that removing any kind of screen protectors can actually solve this problem.
Click to expand...
Click to collapse
*gasp* not my invisible shield!?

Memnoch30 said:
Yup. For some reason I have worse now than before. Maybe I'm just using it more now. Lately it's driving me nuts, to the point of actually looking at a replacement.
Click to expand...
Click to collapse
I had it terribly after the GB OTA, I wiped cache & dalvik and it all but went away. One occurrence in a week and a half, and I've been using the crap out of the phone.

Slightly off topic question: On stock Android, is wiping cache the same as wiping the dalvik cache? The stock recovery doesn't have the "wipe dalvik" option, only "wipe cache".

No it's not, but if you have root you can wipe it manually by removing the contents /data/dalvik-cache/

Rusty! said:
No it's not, but if you have root you can wipe it manually by removing the contents /data/dalvik-cache/
Click to expand...
Click to collapse
Thanks. But every time you flash an official update, the cache gets wiped and rebuilt though, right? That's why after each update it takes a long time to boot.

I still have the touchscreen issue. i think it will never be solved because it's an hardware issue, not a software one.
So the problem still appears, maybe a little less frequently.

I still have the prob but it's different with 2.3
Before 2.3, the touchscreen problem was unpredictable and could happen at almost anytime, whether charging or not. I replaced the handset but the problem persisted.
Since upgrading to GB, I've noticed a very clear pattern. If I'm charging my device and unplug it before it is fully charged, the touchscreen becomes extremely erratic to the point I must reboot the phone. If it's allowed to charge completely it's okay.
It never happens when it's is not charging.
Still annoying as hell but I've moved to Africa and having the device replaced is a real challenge. So I guess I'm stuck with until I replace it.

Still has issue
Stock, no modification at all. Today when I was rearranging icons in ADW Launcher, it seems that the screen registered click below where my finger actually was, same as the problem I saw previous to updating to 2.3.3. The phone was not hooked to a charger at the time.

Stock GRI40 here on my Nexus One...same issues that i've already had with Froyo. As it was posted before, it's a hardware issue; and the Nexus S is the new kid on Google's block, so i'm not expecting anything to improve our screens.

filippogiad said:
I still have the touchscreen issue. i think it will never be solved because it's an hardware issue, not a software one.
So the problem still appears, maybe a little less frequently.
Click to expand...
Click to collapse
Theoretically, there is a chance they could fix a software workaround for the hardware problem. If the error happens in only specific circumstances, and ALWAYS happens in those circumstances, then just teach the phone to know when those circumstances are happening, and tell it what to do in those cases. However, I doubt anyone at Google is working too hard on this problem. I agree, it seems to be much less frequent than it ever was. Seems likely that they may have added a little something to help us out.

brettbellaire said:
Seems likely that they may have added a little something to help us out.
Click to expand...
Click to collapse
Or more likely, it could be unintentional.

So even with official OTA it's still here?
Remember me of the ''crazy'' screen problem we had before while charging,perhaps it's a hardware problem after all

This is a main reason why tomorrow i'm getting a new galaxy s.
I tried a lot of custom and stock roms, I sent my phone to HTC and they replaced hardware, but this issue still persist. And it cause me a lot of problems, especially while driving...

I also still get that glitch but not as frequently. I noticed that i didn't need to reboot the phone to fix it. All i need to do is tap the power button to shutoff the screen and then re-tap to turn it back on and it'll show the lock screen. Slide to unlock and the screen is precise once again.

The bug is still there for me also. However, I didn't seem to have it as bad as some did originally, and now I've noticed that it's happening even less frequently.

Freeze & WiFi

So I have the known freezing problem, where it freezes and have to reboot.
Well started having WiFi issues as well, ****ty connection, to having to turn off and turn back on the connection because it wouldn't work at all. This is related to the freezing problem correct? Also, how does it seem to be getting worse? Shouldn't it just be the same until they send an update?
Yes, I have tried all suggestions options.

From what I've read here on the forums along with a few other sites is that the WiFi freeze is an issue with GNex and 4.2.1. Just hold tight for an update and the issue should be fixed.
But with random reboots, are you using a stock ROM and Kernel?

TheGrayHatter said:
From what I've read here on the forums along with a few other sites is that the WiFi freeze is an issue with GNex and 4.2.1. Just hold tight for an update and the issue should be fixed.
But with random reboots, are you using a stock ROM and Kernel?
Click to expand...
Click to collapse
Yes it's stock everything.
Started noticing other things, think it's related to WiFi somehow, for example this site will not let me log in, I type my credentials it says thanks, and then loads the page again without my logged in. Also, another site does not let me type, i hit the first letter and the keyboard goes away.
Some weird things. Hoping it will all be fixed with an update.
I think I also noticed a very small light bleed (only noticeable on the nexus loading screen), should I try to exchange it or is that pretty much the same on all devices?

bmancell said:
Yes it's stock everything.
Started noticing other things, think it's related to WiFi somehow, for example this site will not let me log in, I type my credentials it says thanks, and then loads the page again without my logged in. Also, another site does not let me type, i hit the first letter and the keyboard goes away.
Some weird things. Hoping it will all be fixed with an update.
I think I also noticed a very small light bleed (only noticeable on the nexus loading screen), should I try to exchange it or is that pretty much the same on all devices?
Click to expand...
Click to collapse
Hmm, if your device does suffer from light bleed, then it should be reproducible (In my opinion).
To try and reproduce it I would do this:
Turn brightness all the way up and disable the AUTO setting
Download the app, Display Tester, from the Play store (There is a myriad of similar apps, find one for you)
Optional: Check for dead pixels by cycling through the colors
Get to the black preset and see if you notice any shades of white coming through. If the black is consistent with the remainder of the screen, then no bleed. If not, they you may have some
Truth be told, I've read many posts in-which people complain how this is their Nth unit. If you feel that the minor bleed ruins your experience with the device, then return it. If not, then enjoy it! My personal opinion is to keep the device and not risk receiving a device with greater issues. And with the wifi lag, are you using Chrome as your browser? If so, I would try boat Browser (Flash Support) or Dolphin Browser with Jetpack. If that solves the WiFi issue (credentials) then there you go! If it doesn't then you can always try flashing a ROM or Factory Resetting. Good luck! :good:

I will try that out.
And with the browser, it's not just the browser with issues, other internet apps do have issues as well.
*update
I tried the test, and it seems there are two small areas at the top right side of the screen. I can only see it on black, so it does not wreck my experience.
Something like this, does it get worse? The year warranty that it has, is this something they will fix/replace?

I found you can fix wifi issues temporarily by switching the channel to 8 or anything other than 11

ThomasBags said:
I found you can fix wifi issues temporarily by switching the channel to 8 or anything other than 11
Click to expand...
Click to collapse
You talking about the tablet itself, or in my router settings? How would I do that on the tablet?
I checked my router, it's on Channel 6, so not going to help me.

You should be able to change the channel, but I don't see a correlation between the two.

ThomasBags said:
I found you can fix wifi issues temporarily by switching the channel to 8 or anything other than 11
Click to expand...
Click to collapse
Changing the wifi channel may help, it would depend on your network and the networks around you though.
I've had the same issues with wifi it's an absolute nightmare. I thought my first tablet was genuinely faulty since I couldn't find too many complaints here about the wifi. However the replacement I have been sent is the same. I'm not sure if it's an issue with 4.2 and certain routers but I had the wifi drops, and more annoyingly I had poor wifi signal that would frequently drop to no bars and cut the video I was watching at the time. Very frustrating.
I have not had a chance to test my nexus 4 however the wifi reception on that is pretty poor too while my old desire hd is fine so I'm sure it's android. Not sure how long it's going to take for a fix of any kind, there are a few reports on the Google submission page with a lot of replies.
Best thing to do is to submit a bug report to Google. At the very least it may get them to actually acknowledge that there is a problem with jelly bean.

Yeah it's starting to pass me off, it's getting worse by the day. Almost unusable.
Not sure if I should send back or wait for update.

Display driver issue? fixes?

My phone seems to have developed a display driver issue where part of the screen ghosts images, turns 50 shades of gray, etc. Apparently this is a common problem at one time one if one searches "fix moto x pure display driver" on google but cant find a fix for it.
Does anyone know how to fix this? Did motorola address this issue with a fix? Perhaps reflash the driver? Ive already tried wiping the phone and flashing to Nougat ([7.1.2] AICP for clark). Neither made a difference. It shows in twrp as well btw.
running out of ideas here. Hate to have to retire the old girl.
any ideas on a replacement for verizon networks...i need an sd card slot for additional storage and of course the phone needs to be rootable. Maybe a moto G?

What makes you think this is a driver issue? If you do a screen shot when this is occuring does it look normal or messed up? If it is a software issue, the screen shot will look messed up, if it looks normal then the hardware is at fault. That would give you about a 80% accurate answer.
There are no "known issues" with the display drivers in the Moto X S/P, so if it's software, best would be to reflash stock via fastboot and retest. If the issue recurs it is likely hardware.

acejavelin said:
What makes you think this is a driver issue? If you do a screen shot when this is occuring does it look normal or messed up? If it is a software issue, the screen shot will look messed up, if it looks normal then the hardware is at fault. That would give you about a 80% accurate answer.
There are no "known issues" with the display drivers in the Moto X S/P, so if it's software, best would be to reflash stock via fastboot and retest. If the issue recurs it is likely hardware.
Click to expand...
Click to collapse
I thought it might be a driver issue by searching for "moto x pure display driver". My phone looks exactly like the one pictured in the first link in the search. Android authority is a pretty decent site and after reading through the comments section it does seem common enough.
Im going to try to reflash via fastboot as you suggested but im afraid i think youre right as it doesnt show on a screenshot. Its worth a try i suppose. Just dont have the $ for a phone right now.
thanks for the reply btw.

steveindajeep said:
I thought it might be a driver issue by searching for "moto x pure display driver". My phone looks exactly like the one pictured in the first link in the search. Android authority is a pretty decent site and after reading through the comments section it does seem common enough.
Im going to try to reflash via fastboot as you suggested but im afraid i think youre right as it doesnt show on a screenshot. Its worth a try i suppose. Just dont have the $ for a phone right now.
thanks for the reply btw.
Click to expand...
Click to collapse
I haven't heard of any display issues in this regard since the X's initial release, and that was fixed pretty quickly with an OTA. None sense then... The "display driver" is built into the kernel, and if this was an issue I'm sure we would have heard more about it.
Sorry to hear, but this sure sounds like a hardware problem.

Okay so my issue was similar just that instead of the bottom half, it was happening for the full screen and it seems to have fixed itself after having the screen on full brightness overnight. It was a mistake actually. It all started when I was replacing my old battery cus it got so weak. I had no heat gun or anything or that sort around so I figured I could heat the phone up internally. Started running clash royale as it got the phone hotter whenever I played and changed the sleep period to 30 minutes because those are the things that make my phone heat up. So I did that. Replaced the battery yada yada, it works perfectly now. So I forgot to set the sleep period back and went to bed with the screen on. Somehow it just continued to stay on all the way till morning (or I believe so). Woke up to the phone hot, screen brightness on full. It was under my pillow too so the heat just kept building up. Needles to say, when I realised I closed the apps running, turned the brightness all the way down and locked the screen. I put it aside to cool off because I had just gotten up, wasn't in the mood. But seeing as I can't keep my hands always from my phone I picked it up like 3 minutes later. I'm writing this an hour after and the brightness is on the lowest setting. No ghosting, no lines being drawn up anywhere, no lagging, nothing. It's currently working like brand new. I should mention that the phone was plugged in the whole time. And mobile network was on. WiFi was off.
I'll keep monitoring the issue and I'll post and changes if any. Hopefully there won't be any.

_arxn said:
Okay so my issue was similar just that instead of the bottom half, it was happening for the full screen and it seems to have fixed itself after having the screen on full brightness overnight. It was a mistake actually. It all started when I was replacing my old battery cus it got so weak. I had no heat gun or anything or that sort around so I figured I could heat the phone up internally. Started running clash royale as it got the phone hotter whenever I played and changed the sleep period to 30 minutes because those are the things that make my phone heat up. So I did that. Replaced the battery yada yada, it works perfectly now. So I forgot to set the sleep period back and went to bed with the screen on. Somehow it just continued to stay on all the way till morning (or I believe so). Woke up to the phone hot, screen brightness on full. It was under my pillow too so the heat just kept building up. Needles to say, when I realised I closed the apps running, turned the brightness all the way down and locked the screen. I put it aside to cool off because I had just gotten up, wasn't in the mood. But seeing as I can't keep my hands always from my phone I picked it up like 3 minutes later. I'm writing this an hour after and the brightness is on the lowest setting. No ghosting, no lines being drawn up anywhere, no lagging, nothing. It's currently working like brand new. I should mention that the phone was plugged in the whole time. And mobile network was on. WiFi was off.
I'll keep monitoring the issue and I'll post and changes if any. Hopefully there won't be any.
Click to expand...
Click to collapse
Later on the same day: So I fell asleep for about 4 hours with brightness on low. (damn I sleep a lot) woke up and the issue returned. But I had the brightness on full for a while and it seems to have resolved again when I put it back to low brightness.
That's all so far. Still monitoring

I'm glad someone else noticed that when you slide the brightness bar it effects the way this display issue behaves. I was starting to think I was alone on this. Now this is just my experience on my phone of course. It seems to be around 2/3 way to full bright that it starts to flash the white lines on and off and then 3/4 + it is pretty much acts as it should, they go away! So I took a screenshot as acejavelin suggested and the screenshot was clear. So this would explain why updates don't seem to change anything since it does seem to be a certain batch with bad hardware. Can this hardware be solder changed? Guess I will keep an eye out for sale of xpure with busted digitizer/good lcd to test and possible mb swap.

Yes 1575 definitely has a display driver issue, i've noticed this too. I don't think there is a way to fix this, unless it would be fixed in Nougat.

But how sure are you that it's a driver issue and not hardware? That's why I'm waiting for nougat. If it doesn't fix the issue then I'm just going to have to retire the phone.

Sorry bro
If you're encountering a display problem in aftermarket roms and even on the bootloader and recovery menus, then it's most definitely not a "display driver" issue. As @acejavelin already pointed out, it's not a known software problem unless you're running the shipped Lollipop software release.

Mine has the same issues now and then but a restart fixes it always.

Bill720 said:
If you're encountering a display problem in aftermarket roms and even on the bootloader and recovery menus, then it's most definitely not a "display driver" issue. As @acejavelin already pointed out, it's not a known software problem unless you're running the shipped Lollipop software release.
Click to expand...
Click to collapse
that's the point, problems are only in the stock rom. I've tried many custom roms and none of them have this issue, but unfortunately they have many other issues so i have to use the stock version.

But the Op!
onupirat said:
that's the point, problems are only in the stock rom. I've tried many custom roms and none of them have this issue, but unfortunately they have many other issues so i have to use the stock version.
Click to expand...
Click to collapse
steveindajeep said:
I've already tried wiping the phone and flashing to Nougat ([7.1.2] AICP for clark). Neither made a difference. It shows in twrp as well btw.
Click to expand...
Click to collapse
Oh. I just read this and assumed that we were all talking about the same thing. In your case, I'd perform some experimentation to make absolute certain that your findings aren't just coincidence.

Question re: hardware vs software
acejavelin said:
What makes you think this is a driver issue? If you do a screen shot when this is occuring does it look normal or messed up? If it is a software issue, the screen shot will look messed up, if it looks normal then the hardware is at fault. That would give you about a 80% accurate answer.
There are no "known issues" with the display drivers in the Moto X S/P, so if it's software, best would be to reflash stock via fastboot and retest. If the issue recurs it is likely hardware.
Click to expand...
Click to collapse
Hi ~ just read your msg, and tried your "screenshot test." The grayish area on my screen (which over time, comes & goes - haven't detected a pattern as to why/when) DOES show up on the screenshot.
If I understand correctly, that would tend to indicate that I am experiencing a software issue? (Not hardware)
I did do a Factory Data Reset, and am experiencing the same issue. I had not added any apps for an extended period of time, prior to this gray-area occuring. I did, however, drop the phone. I don't recall for certain, but I don't think the problem occurred immediately, rather, it started very shortly thereafter (1 -3 days).
And I am waiting for delivery of a battery, since that's shot (runs down very quickly, & shuts down with anywhere from 30% - 60%+ battery level).
Any suggestions for resolving this? I hope this post makes sense... And thank you for any ideas or assistance you can offer!

Hello everybody. I have the same problem.
And who ever changed the display? Do you want to understand this is the problem of the display, motherboard or drivers?

I think it's a software problem, a hardware will not stop glitches when you flash a different software until and unless you fix it. In my experience, after my phone break because of downgrade to marshmallow stock firmware, and with an unlock bootloader i update my phone using OTA update, suddenly it stop working. blank screen and i tried try to recovery it with xt1575 IMG file to boot it again, mine it was xt1572(India) then I start facing a lot of problem, glitches, can go back to marshmallow stock firmware so and so... Now I'm trying to find a solution !!!! Custom ROM, CM13 work better and no glitches till now... I will Report soon

Moto x style/pure display problem
steveindajeep said:
My phone seems to have developed a display driver issue where part of the screen ghosts images, turns 50 shades of gray, etc. Apparently this is a common problem at one time one if one searches "fix moto x pure display driver" on google but cant find a fix for it.
Does anyone know how to fix this? Did motorola address this issue with a fix? Perhaps reflash the driver? Ive already tried wiping the phone and flashing to Nougat ([7.1.2] AICP for clark). Neither made a difference. It shows in twrp as well btw.
running out of ideas here. Hate to have to retire the old girl.
any ideas on a replacement for verizon networks...i need an sd card slot for additional storage and of course the phone needs to be rootable. Maybe a moto G?
Click to expand...
Click to collapse
I think maybe due to brightness control problem, could be the software or hardware problem

WiFi static noise/buzzing sound

Hi, when WiFi is enabled (doesn't matter if connected to a wireless network or not) I can hear from the top of the phone static noise probably due to interference, this is very annoying during calls. When I turn off WiFi this strange noise disappear.
I think this isn't so normal. Has anyone run into the same issue?*

Send phone back to OnePlus, they should give you a new one.

Same with me. But is barely noticeable!

I'm experiencing this on Wifi and on cellular data as well. It's actually very annoying. Does anyone know why this could be happening? Is this like a warranty thing? Or. I have no idea how to approach this sort of thing.

It happened to me too one time. but it went away after a second update. No issue there. Happens to a lot of phones. Nexusline and even iPhones have it.

xgerryx said:
I'm experiencing this on Wifi and on cellular data as well. It's actually very annoying. Does anyone know why this could be happening? Is this like a warranty thing? Or. I have no idea how to approach this sort of thing.
Click to expand...
Click to collapse
It seems completely fixed with last update (4.5.3). Try and let me know.

einermusstot said:
It happened to me too one time. but it went away after a second update. No issue there. Happens to a lot of phones. Nexusline and even iPhones have it.
Click to expand...
Click to collapse
I'm on 4.5.3 now and no change at all. Never have experienced this before and this is my like, 10th Android phone.

xgerryx said:
I'm on 4.5.3 now and no change at all. Never have experienced this before and this is my like, 10th Android phone.
Click to expand...
Click to collapse
maybe it depends on more than just your wifi, there could be many interference signals. I dunno, I am not a developer.

xgerryx said:
I'm on 4.5.3 now and no change at all. Never have experienced this before and this is my like, 10th Android phone.
Click to expand...
Click to collapse
The unusual thing for me is that the issue disappeared and came back 2 or 3 times from Friday to today.

capitanouncino said:
The unusual thing for me is that the issue disappeared and came back 2 or 3 times from Friday to today.
Click to expand...
Click to collapse
I was finding that when I moved my head away or pushed the phone against my ear that the frequency of the sound would change too. Kind of like it was reacting to the distance. It could have also been that the tone changed since I was at different distances. I don't even have enough posts to submit a bug report on the OP forums. Can someone go do that? Maybe this is a warranty item. I saw nothing at all there about this issue when I scrolled through 10 pages of other things.

In have the same issue, on wifi and cellular data. It's not that annoying, but still.. Hope this can be fixed with an update.

OP5 brand new mobile creates buzzing sound
really i am also facing this buzzing issue at the receiver ...i have tried in safe mode also *#808# but no use the same buzzing sound comes ...... not continuous , but often which irritates and annoys me ..

The 4.5.5 update fixed my issue. Hopefully it does for everyone else. I will report back here if it happens again.