Related
Has anyone heard a popping noise when unlocking the kindle. Its happened to me a couple times now. Wonder if its software or hardware issue. Thanks
Sent from my Kindle Fire HD using Tapatalk.
I get the same thing from time to time. Doesn't seem to be an issue if the volume is turned down halfway or lower, but over about halfway and I get it.
Sent from my KFHD using xda premium
I have this issue too
a ha~ it really happen in users' hands ，software issue， I am sure.
It keeps happening to me,sort of frustrating.
Sent from my Kindle Fire HD using Tapatalk.
I was having the same issue. Turned off Dolby Digital in sound settings and seems to have fixed it.
Sent from my EVO using xda app-developers app
Of course now the volume level seems much lower. I hope they fix this issue soon since it doesn't sound nearly as good without Dolby. I sent amazon some feedback on the issue. Hopefully everyone else who has this issue will let amazon know.
Sent from my EVO using xda app-developers app
petes67bird said:
Has anyone heard a popping noise when unlocking the kindle. Its happened to me a couple times now. Wonder if its software or hardware issue. Thanks
Sent from my Kindle Fire HD using Tapatalk.
Click to expand...
Click to collapse
I get this on occasion on my rooted fire HD. It was getting me worried that there was something wrong with mine.
I had the same problem in class today. My volume was turned all the way down, and I also had it in air plane mode. It didn't happen every time I unlocked the screen... maybe four times out of ten. Enough to be very annoying
Sent from my KFTT using xda premium
I am also getting this and in fact returned my original device for that, screen bleed and one other thing that was specific to me. Unfortunately the 2nd one is doing it as well.
Hey guys i thought i would share a simple fix for the touchscreen problems that people are having. I used to have some problems with my touchscreen on stock, basically sometimes the right side of my touchscreen would be difficult and unresponsive. Im not sure what happened, it seems that after i flashed the Codenamesammy ROM it started to have these problems. I though my first tablet was just faulty so i returned and recieved a new one. I flashed the same rom on it then went back to stock and was having similar problems. I thought to myself that it was a software problem, so here is how i solved it.
Fix
Unlock and root your tablet if have not yet. Flash This using TWRP or CWM.
How it works - Im not entirely sure why this worked even though i was in stock and it had stock drivers. Anyways it replaces the current drivers with the one in the build it has posted.
Credits - I give complete credit to the one who extracted these drivers and posted them.
Thought i might help some of you out with your problems before deciding to RMA it. If this does not work for you then it might be the actual hardware.
Is it still working?
Has anyone tried this fix and can confirm if it has worked for them?
Sent from my Nexus 7 using XDA Premium HD app
Touch Screen fix
I tried it this morning and I still have the touch screen issues as seen here:
http://www.youtube.com/watch?v=Cd2xtIxhEBA&feature=plcp
No joy... :crying:
ohmi_gaad said:
I tried it this morning and I still have the touch screen issues as seen here:
http://www.youtube.com/watch?v=Cd2xtIxhEBA&feature=plcp
No joy... :crying:
Click to expand...
Click to collapse
Looks like a grounding problem to me, don't think that can be fixed in software.
Thats deff a screen issue hardware related.
For me, this problem is solved : http://www.youtube.com/watch?v=ArlV8jTdkRM
video is buggy because my galaxy s is bad
People shouldn't really have to repair their nexus tablets on their own and run the risk of voiding the warranty. You should all have it under warranty.
For me I would keep returning it until I receive one that no longer has any defects, even if it means returning 10 of em. This way Google would see a high amount of returns and hopefully do something about it.
Sent from my Nexus 7 using XDA Premium HD app
I don't have the issue, but I'm on franco.Kernel + Team EOS Stable ROM + JRO03R Binaries. I thought I noticed the issue on stock though, but I could be wrong.
I have same this issue especially when the device is heated .. the touch unresponsive in the center..
But I return my N7 to the warranty before i see this topic..
Thank you
Sent from my Galaxy Nexus
this fixed the problems i was having with my screen. so awesome.
RoadZombie said:
this fixed the problems i was having with my screen. so awesome.
Click to expand...
Click to collapse
what issue were you having?
I was having dead spot issues. The screen not reading my touch, but now after update i could have sworn i saw a horizontal line flash across the screen. Never seen it before I've only noticed it once though.
Sent from my SPH-D710 using xda app-developers app
rgunara said:
what issue were you having?
Click to expand...
Click to collapse
Didn't fix mine... when i touch either side of my screen it thinks i'm touching both sides. Gonna have to RMA T_T
This unfortunately didn't resolve my issues, as can be seen here. Is there any other attempted fixes for this issue? If I reboot my device it seems to work dine for a while, but after several hours of being on, it experiences these problems.
GH0 said:
This unfortunately didn't resolve my issues, as can be seen here. Is there any other attempted fixes for this issue? If I reboot my device it seems to work dine for a while, but after several hours of being on, it experiences these problems.
Click to expand...
Click to collapse
If its still under warranty just return don't wait for a solution or perm fix cos you like others here will be waiting for a long time.
Sent from my Nexus 7 using XDA Premium HD app
Just wondering if you people have tried updating the drivers to JRO03R. It solved the problem for me. Sorry if you have.
Sent from my Nexus 7 using xda premium
PissPot said:
Has anyone tried this fix and can confirm if it has worked for them?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Sent from my Ainol Novo 7 Advanced with Tapatalk
StrangerWeather said:
Just wondering if you people have tried updating the drivers to JRO03R. It solved the problem for me. Sorry if you have.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Yes, I have. Those videos I took where after I had flashed the new drivers.
Still getting touchscreen issues after flashing over cm10. In fact it may now be worse. Now I get ghost taps and swipes, apps have a mind of their own. Fortunately turning the screen off and back on seems to clear it up though.
Sent from my Nexus 7 using xda premium
I thought this was the only phase it would follow, if I say okay only, it opens the search...or just okay google. Maybe google now? it is becoming a problem as my phone was on this morning on something searched I had not as it was on charger all night. Was randomly popping up seaches yesterday too. Anyone have this issue and know a way of resolving it? Makes me afraid for USC to get the 4.4 update...Thanks in advance.
Sent from my XT1055 Ghost USC (Moto X)
Ever since camera update and gnow update to take OK Google from search results my motox has been super sensitive. It will go off from nearly anything. 4.4 root.
Sent from my XT1060 using Tapatalk
Ever since I took the I 4.4 ota from Verizon. The touchless control has also been crazy sensitive too. It goes off all the time and I don't know until she says 'the command canceled'. Not sure it a factory reset would fix it but haven't been willing to try that yet. Any ideas what else might fix it from being more sensitive?
Not sure what to do but its terrible for me too on 4.4. I'm going to have to turn it off. Keeps going off all the time.
Sent from my Nexus 7 using Tapatalk 4
I've been having the same problem, phone will be in my pocket or on my desk and I will randomly hear "command canceled"
Its very annoying and happens several times a day, and nothing even close to "OK Google" is being said.
Seems to be a fairly common problem so hopefully a fix is in the works
Sent from my XT1060 using xda app-developers app
Try retaining the okay Google now command. It's important to do it in a quiet room and hold your phone at arms length.
Sent from my Nexus 7 using Tapatalk
I have read other posts here claiming that saying the training phrase more slowly helped with it accidentally turning on.
(I've had no problems myself, still on 4.2.2 with the camera update)
Sent from my XT1058 using xda app-developers app
I've had it turn on watching a trailer for a movie. Restarted the trailer and it popped up again in same spot.
Sent from my XT1056 using xda app-developers app
I've only had one "accidental" fire...
That's in quotes for a reason... My son and I were cooking on thanksgiving... My phone was in my pocket... His nexus 7 was displaying the recipe on the counter...
When the pie went in the oven...
"OK Google, set alarm for 30 minutes"
Nexus acknowledged the command and I told my son to come get me when the Alarm went off.
Obviously, he didn't need to... My phone's alarm also went off.
Sent from my MotoX, using TapaTypo
That's the odd thing, mine worked perfectly on 4.2.2 as well but ever since the upgrade to 4.4 it goes off randomly.
Of course I've tried retraining the phrase several times but it seems to make no difference.
Sent from my XT1060 using xda app-developers app
Yeah that is what's strange cuz I'm on 4.2.2 obviously since US Cellular hasn't got 4.4 yet. Even completely stock besides unlocked boot loader. Have used FXZ's in past week or two in order to lose root. Wondering if I should try a data and cache wipe. Not sure but today was actually pretty good without random searches.
Sent from my XT1055 using XDA Premium 4 mobile app
Hey all,
I recently (2 months ago) got a brand new HTC One. It's been great so far, love it.
Only issue I have is last week it started going to Speakerphone mode when making calls and receiving them. All I have to do is turn off the speakerphone to get it back to earpiece but it's slightly annoying.
I've tried resetting the device to no avail.
I'm running on the Rogers network in Canada running Kit Kat.
Any ideas would be great.
Thanks!
Basttrax said:
Hey all,
I recently (2 months ago) got a brand new HTC One. It's been great so far, love it.
Only issue I have is last week it started going to Speakerphone mode when making calls and receiving them. All I have to do is turn off the speakerphone to get it back to earpiece but it's slightly annoying.
I've tried resetting the device to no avail.
I'm running on the Rogers network in Canada running Kit Kat.
Any ideas would be great.
Thanks!
Click to expand...
Click to collapse
I had the same problem...it eventually got to the point where only speaker would work and not ear piece...now..the only thing that works is if I have it connected through headset...cyanogenmod fixed all my problems....any sense romss I try to use, give me the same problem...if u don't mind changing tons..jus install cyanogen...but if u find a solution, let me kno, cuz I can't find any info about it or a solution
Try deactivate chome browser and see if it solves the problem.
Skickat från min HTC One via Tapatalk 2
jonas111sanoj said:
Try deactivate chome browser and see if it solves the problem.
Skickat från min HTC One via Tapatalk 2
Click to expand...
Click to collapse
I tried that...didn't work, but may I ask why you think that?...Or some info onto why u think that
Still goes to Speaker phone even with browser deactivated. Arg. It's still under warranty but I'm nervous the ****ty refurbished phone they send me will be worse than this one.
Sent from my HTC One using XDA Premium 4 mobile app
i'm having this same issue...i looked all over the call settings and don't see a toggle that i might have accidentally switched on...anyone figure out a solution to this yet?
Sent from my Transformer Prime TF201
Everyone experiencing the issue have a custom ROM? What is it if so?
Sent from my HTC One using Tapatalk
100% stock for me.. Issue happened randomly it seemed after coming back from a trip overseas
Sent from my Transformer Prime TF201
I'm having this issue at the moment, occasionally I ring people and the speaker phone is automatically on.
First time it happened I didn't notice and someone answered as I put the earpiece to my ear, nearly burst my bl00dy eardrum!
I'm running ARHD 51.0.
Having the same issue since about 1-1.5 weeks or so. Using ViperOne 5.5.1 with latest FW and Elemental X 13 kernel.
Freakadude said:
Having the same issue since about 1-1.5 weeks or so. Using ViperOne 5.5.1 with latest FW and Elemental X 13 kernel.
Click to expand...
Click to collapse
Same here after upgrading to 4.4.2 with sense, never happened on GPE
oksagi said:
Same here after upgrading to 4.4.2 with sense, never happened on GPE
Click to expand...
Click to collapse
The weird thing is that i have been on 4.4.2 for a while now via ViperOne and this issue has just recently popped up (or so it seems to me). So not sure if this is related to sense based rom running 4.4.2. or something different.
Well I do feel slightly better that I'm not the only one. But also wished I wasn't part of this so special group. Ha!
After a little googling people seem to think it might have something wrong with the docking mechanism.
Sent from my HTC One using XDA Premium 4 mobile app
Basttrax said:
Well I do feel slightly better that I'm not the only one. But also wished I wasn't part of this so special group. Ha!
After a little googling people seem to think it might have something wrong with the docking mechanism.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Mentioning the dock makes me wonder if those who've looked thru the call settings have looked thru the dock settings to see if there is an option there to open with speaker phone on? Or in the headphone or bluetooth settings. My feeling for looking in these places is that if for some reason the device thinks it's connected to one of these devices that could be changing it's behavior? Anyway, I don't think I'm having this issue but I rarely get calls and usually when I do I use speaker phone, but I'm also pretty sure that I'm having to turn it on also.
HTC replied to someone on Twitter to boot into recovery and clear cache who also had reported the problem...they showed instructions on how to get into stock recovery and do it. I'm wondering if anyone can try that. Either stock or custom recovery.
Sent from my HTC One using Tapatalk
I'll give it a try today and get back to you on the results.
I know a full reset doesn't do the trick so it's worth a shot.
Sent from my HTC One using XDA Premium 4 mobile app
gustav30 said:
HTC replied to someone on Twitter to boot into recovery and clear cache who also had reported the problem...they showed instructions on how to get into stock recovery and do it. I'm wondering if anyone can try that. Either stock or custom recovery.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
So far so good. Tried calling home and my voice-mail and it didn't happen. It doesn't necessarily start up right away however so I'll have to keep an eye on it. I'll respond back here when/if it reappears.
Basttrax said:
So far so good. Tried calling home and my voice-mail and it didn't happen. It doesn't necessarily start up right away however so I'll have to keep an eye on it. I'll respond back here when/if it reappears.
Click to expand...
Click to collapse
And vola! It has returned. So we can wipe the "wipe the cache" fix off the board.
I have the problem randomly just satarted after 4.4.2 update. Stock unlocked phone still have it after yesterday's update.
Sent from my HTC One using xda app-developers app
qayak said:
I have the problem randomly just satarted after 4.4.2 update. Stock unlocked phone still have it after yesterday's update.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
So i guess this is a general sense 4.4.2 issue then and not custom rom, kernel, other specific. Strange that it seems to only start after a random amount of time as i deffinately did not have this issue for quite some time after upgrading to 4.4.2 based rom.
So, a couple of days ago my phone stopped vibrating. Guessing it might be a problem with the rom I had at the time (ViperOne_5.5.1) I decided to download the updated version and flash it. Flashing was fine and again, everything worked fine but the vibration. So I thought of installing another rom to see if it was Viper causing the problems so I installed Android Revolution, still nothing.
I've now reverted back to Viper and after hours of research into this and installing several apps that would, supposedely, fix the problem, I gave up and reached the conclusion that it must be a hardware fault. But lo and behold, my phone vibrated twice today. Once this afternoon and again just a couple of minutes ago. I've been texting and receiving calls and emails all day long but these were the only times when it actually vibrated.
So my question is, does anyone have any idea of what's going on with my phone? And if so, is there any some sort of a solution to this?
Hardware. It will eventually completely go. Mine died completely pretty early on
Sent from my HTC One using XDA Premium 4 mobile app
nateboi81 said:
Hardware. It will eventually completely go. Mine died completely pretty early on
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I see. Did you get it fixed?
Sent from my HTC One using XDA Free mobile app
I sent mine in because the usb port on the phone burnt out if you really want it fixed you can send it in for repair
Sent from my HTC One using XDA Premium 4 mobile app
nateboi81 said:
I sent mine in because the usb port on the phone burnt out if you really want it fixed you can send it in for repair
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
lol everything else is fine with my phone, it's just really annoying that it doesn't vibrate anymore as most of the time, both indoors and outdoors, I'm listening to music and won't actually hear notifications. Do you know if HTC will repair it if it's rooted? I don't actually have a warranty for the phone so I'm not too sure about sending it to a 3rd party repair shop that'll probably overcharge me.
nekographic said:
So, a couple of days ago my phone stopped vibrating. Guessing it might be a problem with the rom I had at the time (ViperOne_5.5.1) I decided to download the updated version and flash it. Flashing was fine and again, everything worked fine but the vibration. So I thought of installing another rom to see if it was Viper causing the problems so I installed Android Revolution, still nothing.
I've now reverted back to Viper and after hours of research into this and installing several apps that would, supposedely, fix the problem, I gave up and reached the conclusion that it must be a hardware fault. But lo and behold, my phone vibrated twice today. Once this afternoon and again just a couple of minutes ago. I've been texting and receiving calls and emails all day long but these were the only times when it actually vibrated.
So my question is, does anyone have any idea of what's going on with my phone? And if so, is there any some sort of a solution to this?
Click to expand...
Click to collapse
The phone must vibrate when you full restart, if it doesnt, then it's a hardware problem.
I had such a problem, and sent it to repair under warranty.
Yet, i had to get back to full stock.
Good luck!
Mine came back from repair for some other thing, and I noticed right away the vibrate function on my handset is way too much. (Rear module camera was changed, I guess it carried a new vibrate module with it?)
I'm just sending mine for repairs once I'm back from holiday. Really disappointed though, the phone is barely 3 months old.
Sent from my HTC One using XDA Free mobile app
List of Answers including Softwares and Hardware Solutions - Vibrate not work