[SOLVED] Hardware Issues After WiFi Tethering - Nexus One Themes and Apps

I have been having a few issues with my Nexus One during after wifi tethering. Usually it only happens after extended periods of tethering, but sometimes it happens after shorter periods. My phone frequently gets from 100-113F (as measured with CurveFish BatteryLife app. I'm not sure how accurate it is). Perhaps the temperature has to do with the issues I am experiencing. Strange, because my G1 got just as hot and I never had a problem.
Issues:
1) Touch screen does not register correctly and I have to reboot the phone.
2) Microphone does not work properly when making phonecalls. I can hear the person clearly, but they tell me I keep blanking out.
Has anyone else had these issues or any other issues after tethering?
[edit]
I am now using a new Nexus One (RMA'd the last one for a dead pixel) and have not had any of these issues.
Apparently my last device was simply defective.

You do understand that WIFI Tether is still in beta process and will have problems right?
I have also noticed that the phone gets hot when charging and wifi on, I dont see this as a problem unless it is burning hot because components will get warm.
For concern 2, do you by any chance accidentally cover the rear microphone when speaking to someone? It is a nice feature for noise cancellation, but if the rear mic is covered, with your hand or on your shoulder, it will cut out your voice. Just throwing that out there.

I am using wifi tethering with Cyanogen addon.
I see a problem since CPU loading is 99% after wifi tether has started.
I guess we need to wait for bug fix

rydr1 said:
You do understand that WIFI Tether is still in beta process and will have problems right?
I have also noticed that the phone gets hot when charging and wifi on, I dont see this as a problem unless it is burning hot because components will get warm.
For concern 2, do you by any chance accidentally cover the rear microphone when speaking to someone? It is a nice feature for noise cancellation, but if the rear mic is covered, with your hand or on your shoulder, it will cut out your voice. Just throwing that out there.
Click to expand...
Click to collapse
Yes, I realize it is still a beta. This thread is not meant to complain by any means, and I apologize if it came off that way. I'm glad I have tethering at all
I am simply trying to diagnose my problem, and I figured seeing if others experienced similar issues would be a good way to start.
My first thought about the issues with people not hearing me was that noise cancellation was not working properly, but I am 100% sure I'm not covering the mic on the back of the phone.
I'm pretty sure it has something to do with tethering.

I am now using a new Nexus One (RMA'd the last one for a dead pixel) and have not had any of these issues.
Apparently my last device was simply defective.

mhaedo said:
I am now using a new Nexus One (RMA'd the last one for a dead pixel) and have not had any of these issues.
Apparently my last device was simply defective.
Click to expand...
Click to collapse
Nice! Good to hear you got that taken care of.

Related

Captivate microphone issues

Hello all:
I am on my first replacement phone, and am experiencing a recurring problem that I also had on my original phone. At times during the call, the person on the other end will not be able to hear me (a la 'mute'), but I can hear them. I have confirmed that the mute function is not activated (even turned it on then off), but no luck. My initial impression was just a faulty microphone/hardware, but given that my second phone is also experiencing then same problem, I wonder if it is something that I am doing. I can assure you that I am not in any way blocking the microphone hole at the bottom of the phone (experimented with that to see if it was the cause). I can also rule out network issues due to moving between cells - I have experienced this problem driving and sitting still at my desk.
This problem, more than the GPS issue, will be the deal breaker for me - this is a business phone and I spend a substantial amount of time every day on work related calls.
Thanks in advance.
Thomas
I have the same issue. My coworker had the same issue with his the replacement under warranty.
If I use the headset it works fine. If I mute the phone and un-mute it it starts working.
Something is fishy with the microphone of this model ...
Okay, now this is getting ridiculous. Either I have really bad luck, or I am doing something wrong. On my second replacement phone, and like the last two, I have problems with the microphone cutting out during the middle of calls. Am I completely alone, or am I just lucky in getting phones with bad mics?
I keep the phone in my pocket with a body glove case. The mic is not plugged up, and it seems random. Could there be a software issue (ie a piece of software interfering and taking over the soundstream from the mic)? Even though the person on the far end cannot hear me, I can hear them.
Thanks
T
@ banesong: I'm having similar issues. I've had my phone for a little more than 24 hours. last night i couldn't hear anything coming from my mic and obviously could not communicate from my end. taking the battery out and back in fixed it for me. but i look at this as only a temporary solution. hopefully this isn't a hardware issue
I am having the same issue. I've had my Captivate since the end of July and it is running stock 2.1 that came with it and unrooted. I can't remember when the issue first started. But it has been doing it a lot more lately. It seems to happen around 8 or 9 minutes after I am on the phone call. At first I would hang up and just call back. Then I discovered that the mic would start working again if I just turned the speakerphone on and then off again.
It is really starting to get annoying now. I am thinking about getting a warranty replacement. The only reason why I didn't get a warranty replacement sooner is because I don't feel like having to remember and reinstall all the apps that I have on my phone now.
Having the same issue here and I have an idea about the problem.
If you remove the lid on the back that covers the battery the microphone is disabled and no warning appears on the screen. This is the same behaviour we are all experiencing.
There are two round blank spots on the inside of the cover matching two contacts on the phone. My idea is that the 'lid open' detection checks if the lid connects these two contacts.
My microphone usually starts working when I squeeze the phone.
Not sure about a workaround yet but connecting the two connectors directly inside the phone should solve it permanently (but voids the warranty).
Hope that helps.
T
Sorry, please ignore my previous message. I couldn't reproduce it yesterday so it must have been coincidence.
However, I have the same microphone problem and would like to know if there is a fix for it.
Cheers
T
Possible fix
I know this is an old thread but I have one of these old phones and was having this problem. After fiddling with the settings a bit I found a setting under Call Settings->Voice Call->Noise suppression. I unchecked the box and the mic seems to be working - for now.

Am I the only one having serious proximity sensor problems (hang ups)

this has gotten to be a real serious problem for me - hanging up with my face while on a call. i am surprised this isn't talked about more here. any help would be appreciated! is it possible for the dev's to not only remove the end call button but the mute as well?
so far you are the only one that has ever reported anything like that,ya know it could be a hardware defekt
sent via my bamfed out tbolt
Nope I'm in the same boat as im sure are many others. I have only ever had it actually impact me I think twice on phone calls out of almost a hundred or so that I have had since I purchased the phone. All the others times though it was extremely annoying to keep hearing the click sounds of the screen turning on and off on and off on and off etc.
I keep hoping for a software update that addresses the sensitivity of the sensor, but still no
I also wonder how much the battery is affected by the screen turning on and off repeatedly while in a phone conversation...
I get the same. More on my right ear than my left, but it will often take a digit that I just typed for an automated system and try to dial it, resulting in an alarm tone in my ear during the conversation.
sorry but i have 3 different bolts,the 1st one was rooted stock had that problem but it also went into the brick loop so it got replaced,rooted that one but never had the prob again,this one has the bamf 2 prev 3 on it and no probs that is why i suggested harware cause my first one had major hardware issues
sent via my bamfed out tbolt
i get it too. but i dont call so much. so i dont really care lol
I too had this problem, and did some quick searching on Google. Stumbled upon someone who said to spray it with canned air to clean it out. To my surprise, it worked. There is just enough room between the screen and the body of the phone for dust/crap to get in and it hinders both the light and proximity sensors.
You might be holding the phone in a weird position?
THUNDERBOLT
Damn, you lean something new every day, this thing makes phone calls too!
I've had the issue too recently. But it only started when I returned the last phone to stock. Before that, I had a small issue with it, but it didn't happen often.
pnd4pnd said:
this has gotten to be a real serious problem for me - hanging up with my face while on a call. i am surprised this isn't talked about more here. any help would be appreciated! is it possible for the dev's to not only remove the end call button but the mute as well?
Click to expand...
Click to collapse
I have the screen turn on during calls, but I've never had a face hang up. Honestly I think the screen turns on for me, but can't be interacted with.
Scratch that just did a test. I guess I'm lucky. Then again I don't hold the phone flat to my face. So I guess I would never hit it...
i have had hangups, the mute button pressed, and a 3 way call started. i just tried blowing the screen out with some compressed air as someone suggested. it seems better - will give an update after some testing.
No issues with hang ups for me. Had that problem all the time coming from the X.
Sent from B.A.M.F. 1.7 using Tapatalk
I have the same problem and have had it with every Rom I've run and stock. I'm surprised we don't have a way to adjust the proximity sensor yet, that's something I really miss about my Droid X.
After answering a call and putting the tb to my ear, my screen stays on.
Sometimes my ear dials numbers, sometimes the screen stays illuminated but doesn't respond to any touch! I have to toggle the screen on/off with the power button to get the touch response working again.
I have never had an issue. Been on mostly whatever the latest bamf release since rooting.
It happens to me whenever I forget the bluetooth especially after working out or anytime facial area is warmer then normal. I have a screen protector and clean the screen frequently.
I am having the same issue, so I called Verizon yesterday and they are sending me a new phone. I hope it works, because it makes talking on the bolt almost impossible.
Sent from my ADR6400L using XDA App
this is the first I am hearing of this. No problems for me.
Have the same problem...its really annoying man....will not get a refurbished unit until they fix the reboots

Beginning to think the Sensations Issues, WIFI, SCREEN ETC. Are from Grounding.

The phone has such a ground issue that its causing all this, screen issue seems ground issue, wifi, ground, unlock screen, ground.
There is something completely wrong with the way this is grounded causing all the issues, hell even the charger issues could be because of that. I think they need to redesign this thing. I know some claim to have good ones, but Ive had 3 so far with the same issues. I just dont know what to do anymore. Damn g2x wasnt so bad after all.
Any more mad cap theories??
No issues here. Maybe there is a problem with the batch you have been replacing your devices from. No need to redesign the phone.
Sent from my HTC Sensation 4G using XDA App
Not seen any issues with mine, 100% fine.. must be a bad batch or certain firmware revision. O2 UK firmware and phone fine.
Sent from my HTC Sensation Z710e using XDA App
smashpunks said:
The phone has such a ground issue that its causing all this, screen issue seems ground issue, wifi, ground, unlock screen, ground.
There is something completely wrong with the way this is grounded causing all the issues, hell even the charger issues could be because of that. I think they need to redesign this thing. I know some claim to have good ones, but Ive had 3 so far with the same issues. I just dont know what to do anymore. Damn g2x wasnt so bad after all.
Click to expand...
Click to collapse
Any issues I've had were down to the ZDBox app. After I've uninstalled that I've no issues really
Sent From My HTC Sensation using Xda premium App
smashpunks said:
The phone has such a ground issue that its causing all this, screen issue seems ground issue, wifi, ground, unlock screen, ground.
There is something completely wrong with the way this is grounded causing all the issues, hell even the charger issues could be because of that. I think they need to redesign this thing. I know some claim to have good ones, but Ive had 3 so far with the same issues. I just dont know what to do anymore. Damn g2x wasnt so bad after all.
Click to expand...
Click to collapse
Hello guys,new guy here.
There may be a ground issue with the user,not the phone.
Bear with me:
I used to have a good buddy that could never wear a wrist watch for mare than a week.
After that,they died.
It didn't matter how expensive a watch he bought...they all died.
In this case,there could very well be a static buildup coming from the user's body.
Clothes,diet,etc. can affect body chemistry.
If it acts up again,try touching the backside of the phone to a water faucet for a few seconds.
See if grounding out the case helps.
smashpunks said:
The phone has such a ground issue that its causing all this, screen issue seems ground issue, wifi, ground, unlock screen, ground.
There is something completely wrong with the way this is grounded causing all the issues, hell even the charger issues could be because of that. I think they need to redesign this thing. I know some claim to have good ones, but Ive had 3 so far with the same issues. I just dont know what to do anymore. Damn g2x wasnt so bad after all.
Click to expand...
Click to collapse
No issues with mine whatsoever.....
Keep in mind before these blanket statements are made, that most owners do not have all the issues you might have. It's by no means the norm. As others mentioned, you may simply have a bad device....or bad app, SD card.
The vast MAJORITY of owners have no such problems....it gets WAY blown out of scale on these and other forums. It would be better to title your thread "I have grounding issues"...
Also, as always, anyone with major issues needs to make sure they still have said issues after a factory reset with nothing installed, no 3rd party apps, no SD card etc. If ya still have issues after that....ya got a defective device.
The vast majority of Sensations are fine....let's keep it real.
We get it....you're having problems with your device....You don't need to start a new thread everyday....I'm sure this could have went into one of your MANY OTHER THREADS YOU'VE ALREADY MADE. As for your "grounding issue", the same thing was said about the nexus one and the EVO....and in the end NEITHER OF THEM HAD A GROUNDING PROBLEM. Just as this phone DOES NOT have a grounding issue either. That being said, if you're having so many problems, return your phone, and go back to your G2X. There really is no reason for a grown man to be whining so incessantly. You have already started several threads about your many problems...post in those....No need to keep creating new threads every time you feel like complaining.
PS
As the previous posters have stated, no I don't have a problem either.
Cass67 said:
Not seen any issues with mine, 100% fine.. must be a bad batch or certain firmware revision. O2 UK firmware and phone fine.
Click to expand...
Click to collapse
I've got a TMo US Sensation, and it's great. The only "problems" i've noticed is the rare sense lag, but it always clears up in a matter of seconds. And the battery life is amazing compared to my Evo (i can go 2-2.5 days on a charge, same usage level would drain my evo in 10ish hours). While I eagerly await s-off and persistent root, I think this is a very good phone especially so recent after release.
This is your 2nd or 3rd thread that you have made to complain about something. Thread closed, start another thread complaining and I am going to consider infractions.

GPS accuracy

This weekend for the first time I had to use my Nexus 5 turn-by-turn navigation on Google Maps to get somewhere. I'm no stranger to the feature, as my previous Note 2 had a dashboard mounting bracket in my truck for this very reason.
Besides the speaker not being loud enough to hear the directions (one of my complaints with this devie), I found the GPS isn't very accurate at all. I have it set to High Accuracy, using GPS, WiFi and data network to find my position. The software often put the arrow about a block away from where I actually was and it kept falling behind telling me where I was supposed to turn.
I was driving at about 40-50 km/h at night with a cloudy sky. I reckon this was never an issue with my Note 2, both with stock TouchWiz and custom ROMs. My Nexus 5 is on stock 4.4.
So, what's going on here?
I honestly can't say I face this issue. My GPS is on point whether driving or just using it when I go hiking or camping.
A couple of weeks back I helped a buddy move into a new place and I loaded up my truck and he gave me the address and I popped it in the GPS, it locked within seconds and got me there just fine. No issues.
I also use it when I go camping. I'll find a nice place to pitch the tent and mark the campsite, then go exploring. Anything interesting I put a pin on it and can find my way back real easy. The speaker issue, sure. I use Viper4android (sound mod) and custom kernels to raise the output gain and make the speakers louder so that's a non-issue for me.
If you're rooted, check out FasterGPS (and if you're not rooted.. go and root).
Regarding sound loudness: try fauxsound (you'll need a compatible kernel and root). It boosts speaker, handset, and aux output significantly without adding distortion (although you can push it far enough to distort if you please).
Great, thanks for the tips.
Yes, it's rooted.
Regarding the sound boost apps, do they work on stock kernel, or do I need to flash a new one, like franco? I really don't want to do a clean wipe at the moment to install a new kernel.
GPS accuracy might be a loose antennae. As for speaker sound, not sure what to tell you. I had the phone resting on the seat beside me since I have no dock, with the radio going at highway speeds and had no problems hearing the voice directions. I didn't even have to max the volume, it was about 70%. No modifications.
Perhaps you have the extra glue around the speakers issue?
I've had the same GPS issues and they have just gotten worse over time. Have had the phone for 10 months. Finally called Google and a replacement is in the mail.
bionemesis said:
I've had the same GPS issues and they have just gotten worse over time. Have had the phone for 10 months. Finally called Google and a replacement is in the mail.
Click to expand...
Click to collapse
Let me know if the replacement is better. My GPS has also degraded significantly, but I wasn't sure if that was related to using CM11.
I haven't driven much lately, so this issue alone doesn't warrant a return for me.
However, the disappointment is stacking up over time. It seems to me that the N5 does a lot of things, but none of them very well. It's basically a tinkerer's toy with an attractive pricetag for the specs. Maybe it's because I came from a former flagship Note 2 device, but I do sometimes miss it.
Ajfink said:
Let me know if the replacement is better. My GPS has also degraded significantly, but I wasn't sure if that was related to using CM11.
Click to expand...
Click to collapse
Will do. I did go back to factory, unrooted and relocked the boot loader. GPS is much, MUCH, worse. It actually loses GPS signal now all the time. I'm convinced now more than ever that this is a hardware issue that gets worse over time combined with software that makes it worse. Hopefully the new, albeit refurbished, phone is better.
My GPS has never worked well, I have had mine for about 10 months as well. I've opened it up so the warranty is void but I don't care about that. I would fix it myself if I knew what exactly the problem was.
I use navigation at least a few times a week and I've never had a single issue with the GPS. It locks on right away, and is always accurate.
I had a nexus 5 from Sprint and the GPS was noticeably off, returned it and Sprint (terrible coverage). I got one from the play store and it's spot on.
Sent from my Nexus 5 using XDA Free mobile app
Got the replacement. Preliminary results...huge difference. Better than the phone originally was when I got it. GPS locks in immediately. And this is rooted stock with elementalx kernel. Will update again after a few days of use, but so far, so good.
Ultimate test passed earlier today. Wife and I went golfing and she dropped her phone somewhere. Loaded up Android Device Manager on my Nexus 5 and drove right to her phone. GPS was bang on.
bionemesis said:
Ultimate test passed earlier today. Wife and I went golfing and she dropped her phone somewhere. Loaded up Android Device Manager on my Nexus 5 and drove right to her phone. GPS was bang on.
Click to expand...
Click to collapse
Gps set to always on? Or can device manager swtich on gps?
doctor_droid said:
Gps set to always on? Or can device manager swtich on gps?
Click to expand...
Click to collapse
Device manager turns on GPS remotely.

I think this call quality issue is actually a SIM issue

Hi there,
I'm one of the many that's been hit by the call quality issues of the Pixel 3. I use a Pixel 3 white with Tele2 in the Netherlands and I cannot make or receive calls when the problem hits. I also have the problem where I'll cut out every 20 seconds or so any people will tell me they can't hear me.
Restarting it fixes it temporarily and then it just goes on again. It's ridiculous. I'm on my second phone already.
I've found that when this happens, when I go to settings in the Phone app, go to calls and then call forwarding or additional settings, nothing loads. It may even say SIM read error. When I restart the phone, and I can make phone calls properly again, these settings load again. Seeing as these settings are loaded from my SIM settings, I have a feeling something with the phone reading the SIM isn't quite right.
Got T-Mobile NL and especially at home, most times, people can't hear me properly.
call quality
I'm on verizon, and when I call into work conferences from home, I get complaints that I sound like I'm underwater. I've tried disabling advanced calling and that doesn't change anything (was a recommendation in a Google forum). I haven't experienced dropped calls yet, but I don't make a ton of phone calls, so that doesn't mean much.
There are tons of threads like this talking about sound issues when calling. For me the only problem I have is when someone calls me they cant hear me on speaker phone until I turn that off and talk on the regular mic. I dont know why Google hasnt addressed it yet? Leads me to believe that it may not be a software issue that it is more like a hardware problem so they will just keep swapping them out until you are good or they are done swapping and your screwed.
Super-Veloce said:
Got T-Mobile NL and especially at home, most times, people can't hear me properly.
Click to expand...
Click to collapse
Same here, if a call goes through. Usually it won't even connect
Archangel said:
There are tons of threads like this talking about sound issues when calling. For me the only problem I have is when someone calls me they cant hear me on speaker phone until I turn that off and talk on the regular mic. I dont know why Google hasnt addressed it yet? Leads me to believe that it may not be a software issue that it is more like a hardware problem so they will just keep swapping them out until you are good or they are done swapping and your screwed.
Click to expand...
Click to collapse
It's so strange, it seems like a software issue. I got one replacement and it does it as well. But a restart fixes it and doing some of the cache clearing fixed it for me for 3 days. Now it's back again.
It would be nice if it were a software issue but it doesnt even seem to be on Googles radar to fix? If they just swap out enough phones for the next few months until the next phone is announced by Google, everyone will want the Pixel 4 and forget about these issues.
Legendhidde said:
It's so strange, it seems like a software issue. I got one replacement and it does it as well. But a restart fixes it and doing some of the cache clearing fixed it for me for 3 days. Now it's back again.
Click to expand...
Click to collapse
P3 white / SIM O2 Germany. I have No problems.
The SIM card is not the problem. When I had my Pixel 3XL and my wife had a Pixel 3, we replaced both our SIM cards. This failed to resolve the issue with both phones. Go read the official product forums. Too many people have ruled that out.
After 3 months without the ability to make phone calls, the only troubleshooting step that worked was to returned the phones and get another model (Oneplus 6t). Calls have been crystal clear using the same SIM cards in all the same environments.
This is either a software issue, or a component issue. I suspect its a component issue. I would put money that there is a bad transmitter or chip-set in the phone. As someone who works with electronics on a daily basis, the intermittent nature of the problem follows the type of symptoms I see when a circuit is slowly building stray capacitance and has no way to bleed out extra potential. Similar to static electricity. This would explain why it goes away for most people for a brief period when they power cycle their phone. It would also explain why not everyone experiences it.
Google may be able to band-aid the hardware defect with software by actually cutting out HD quality on calls and fudging it, and most people won't be able to tell the difference. They might have the ability to power cycle and fulling resent a single component after each phone call. They did the same type of thing when the bottom speaker on the 3XL was buzzing at certain frequencies. They simply programmed the software to prevent the bottom speaker from playing sounds from within those frequencies. Most people aren't going to notice that one of the two speakers is slightly muted.
The only way to remedy this is to have 4g enabled at all times. Calls should then be using volte or HD voice and the issue goes away.
I anable 4g even when wifi is on and calls on both my Pixel 3 (Sold) and Mate 20 Pro are clear and rock stable if not a tiny bit tinny or raspy at the high end due to HD voice.
This is on EE Uk , but I would imagine is similar on cariers from other countries.
On a side note, with O2 I do not have this issue at all so maybe it's something to do with the frequencies or bands the mobile operator is using.
It is definitely not related to the SIM. I have replaced my regular SIM with eSIM on T-Mobile CZ and I still have this issue. I have even transferred my number from Vodafone CZ due to my contract expiring, and its still there.
Hoping after Android Q , this issue will shine [emoji848][emoji848][emoji848]
Sent from my Pixel 3 using Tapatalk
I have this issue too, updated to the Android Q beta in hopes this would stop it from happening - but it is still happening.
I can hear everyone perfectly well but they say I am breaking up or sometimes I hear terrible interference and the call is dropped. Tried all the troubleshooting steps.
One thing is I noticed if I am using hands free (car's bluetooth or the pixel headphones) the issue never occurs (so far). I am thinking the antenna might be interfered with while it's in my hand. Can everyone try using hands free solutions while not holding the phone and see if it persists?
Thanks
Factory reset and removal of certain third party apps seems to have fixed the problem for me
Div250 said:
Factory reset and removal of certain third party apps seems to have fixed the problem for me
Click to expand...
Click to collapse
and now we need to know which are those "some 3d party apps"
please, thank you
Remove recently downloaded apps one by one , restart phone normally, then make a call to see if removing that particular app solved the problem. If not, continue until you do find that app. In my case, I had my suspicions on the two that I removed and that was it.
check SIM for scratches
My SIM card is scratched. Could the phone be damaging the SIM upon insertion?
I saw on another forum that their call quality issues go away when they use the headphones that come with the phone. So that would not be consistent with a SIM issue... hmm.

Categories

Resources