Hi folks
I have a Nexus S (i9020a). It has stock 4.1.2 Jelly bean from Google (downloaded the stock image and flashed it). It worked fine for over a month.
Suddenly few days back this device got a problem. When I dial any number I can't hear any dialing sounds and even after the call has connected I can't hear the opposite person and the opposite person also can't hear me (The phone still shows as 'Dialing' though it's already connected). The same is true when I answer any call. Both parties can't hear anything.
This is solved by rebooting the phone for the first phone call only. After I reboot, the 1st phone call works fine, then this problem persists for any calls I make/receive until I reboot the phone again.
I tried flashing a different radio but this problem is still there. I tried my sim card on a different phone and it works fine, so the problem is not that too. My 3G data works just fine.
I need this phone for the next few days/weeks (hopefully not months) before my Nexus 4 gets delivered :laugh:
Thanks..
Edit: Modified the title; Probably gave the wrong meaning that the problem is solved.
<bump> Modified the title. Earlier title gave an impression that the problem is solved whereas I still have a problem.
Have you installed any apps which could somehow affect the dialler?
Unless someone else can give you a different advice, I can't think of any other option than do a full wipe and reflash.
I haven't installed any such apps.
Also, I already did a full wipe and flashed the stock image again. The problem is still there.
Don't know what else you could try, sorry mate - hope someone else can help you sort it out!
Thanks for trying. I think I will go to some hardware shop and see if they can figure out..
Try using a headset for making phone calls so that we can identify if it's really the hardware's problem.
ej8989 said:
Try using a headset for making phone calls so that we can identify if it's really the hardware's problem.
Click to expand...
Click to collapse
That's the first thing that I tried... doesnt work.
mailrachit said:
That's the first thing that I tried... doesnt work.
Click to expand...
Click to collapse
I had similar problem when RAM running out. Usually a reboot fix the problem for a bit.
What I did:
1. With Titanium Backup Pro, froze unused RAM hogging system apps, like Google+, Google play magazine,etc
2. Froze or uninstall Facebook, Word with Friends, etc which are resident and hog RAMs .
3. Install marmite kernel, free up more usable RAMs.
Hope it helps you too.
_android_ said:
I had similar problem when RAM running out. Usually a reboot fix the problem for a bit.
What I did:
1. With Titanium Backup Pro, froze unused RAM hogging system apps, like Google+, Google play magazine,etc
2. Froze or uninstall Facebook, Word with Friends, etc which are resident and hog RAMs .
3. Install marmite kernel, free up more usable RAMs.
Hope it helps you too.
Click to expand...
Click to collapse
Thanks for the suggestion!
I tried this too but doesn't work...
Try any custom ROM instead of stock ROM and a different kernel too. There could be chances that you've flashed the wrong ROM / radio too.
Sent from my Nexus S
Problem solved.
I went to a hardware store today. The guy said that it's a problem with the 3G service of my carrier (Vodafone India). The moment I enabled the '2G only' option in the Mobile networks settings area, this problem was gone. The technician said that this issue is affecting some people randomly. He said that since 3G service was launched just last year, the networks are not yet capable of handling all kinds of devices (he claims that the bug is so erratic that another Nexus S i9020a may work just fine with the very same bootloader/radio/rom which doesn't make any sense). When I said that 3G service was working fine before, he said that most probably my carrier changed some settings on their side which is causing this issue for me.
I have tried this for 6-8 hours now, making a lot of phone calls and it seems that the issue is gone. It saddens me that I am off 3G for now but at least my phone calls and basic EDGE internet works fine. I will have to work with Vodafone to solve this or simply wait for my new phone (Nexus 4) and hope it won't have the same problem..
Related
I have a Nexus S i9023. I was trying different ROMs and everything was working fine untill I installed MIUI. What it actually did, it listed my ph twice on play store and after that my ph stopped incoming/outgoing calls and sms but 3G kept working. At that time I didn't know what is the real problem so I tried changing ROM, radios, kernel even going back to stock ROM. Later I realized that sometimes its working sometimes but when I try to install something from my computer it say its installed but it doesn't appear on my mobile it also blocks calls and sms again. But when I put another sim card then it all works fine. I dont know how to resolve this. I tried to search how to delete devices on play store but found nothing.
Any help would be highly appreciated...
Okay so i have 4.4.2 in my gt-p3100 and am facing continuous network loss.
One second its there and the other second it says no service.
Then it identifies my cell network but shows this -
No Service- TATA DOCOMO
(Tata docomo is my network provider)
This happens usually when i am about to make a call or message or about to recieve a call or message.
The incoming call gets displayed for a split second and then bam..!
The network goes away.
And then again it shows no service and the cycle continues.
Toggling the airplane mode on and off sometimes helps, but mostly i cant get it even after several reboots or sim changes and everything.
I am really annoyed now.
This started only 5-6 days ago.
I completely reformatted this tab and had a fresh install but still it continues.
I have a custom messaging app called 8sms and xposed framework installed although i use just X-Privacy.
Besides i read that moto G users in my region are facing the same issue in their current KitKat version.
Just for reference : https://forums.motorola.com/posts/027c60e48f
Any help is urgently needed, thanks.
Bump...???
I hope this helps.
Clean install ROM. do not restore backup apps first. first log-in through your google account and restore all..
I experience same problem with other roms also slimkat, sensonic, dhollmen. what i did is restore my contacts and apn setting from my google account not from a backup. i hope this helps.
Well i had just cleaned and installed but what i did was let google restore the contacts and apn.
Then i manually restored some apks via app backup and restore.
And then i used Titanium Backup to restore the data in all of them.
Is this the wrong way.?
Thanks btw.
@gangpe well i changed the APN as u said.
But i was playing GTA San Andreas.
And a call came and it rang for a split second and then same..the network goes away.
But it came back automatically.
Still the issue is not solved coz it happens randomly .
Is the apn still there, or did it disappear? I ran into an issue once where the apn did not save for some reason...
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Well its still there...
I chose the same name for it too, would that conflict.?
Also randomly it happens when sending/recieving a message too.
I click on send and suddenly it says no service and then the message cannot be sent even after 2-3 reboots. :-/
Bump..
Any one know any solution..?
Its starting to get on my nerves.
Random no service msgs.
And wont get stable unless 2-3 reboots..:-/ :-/
Not sure what to tell you. A few days ago, I had a few weird issues (could not install xposed framework, quick settings panel would not work), so I ended up wiping cache, data, system, and dalvik. After wiping, I re-installed the ROM, and I have been good since.
In my case, there was probably an old setting I had that was causing issues. If you haven't tried wiping those four options, then I would suggest you try wiping/reinstalling.
If you have tried that, not really sure what to say. Sounds like you might need to head back to stock for a while until a later release resolves the issue.
Mmmm...the thing u are telling is a case of wrong dirty flash of a rom, i mean u must have flashed a previous version rom without wiping over other rom version.
I have faced this too..but the thing i was facing seems to have gone now on current latest release.
Dont know but i did not fixed permissions from TWRP this time after OTA and now the issue hasnt surfaced since 24 hours.
Maybe i'l wait some more and check and report back here.
Thanks anyways.
Now i m gonna pull my hairs out..!!!!
Wtf is this sorcery.. I was watching a vid on MX player and again the no network issue started happening as soon as a call came....!
This MX player is the culprit i think..usually while watching vids this happens...
Same issue for me on p5100, it happens both on Dhollmen and Mokee.
I don't have MX player installed.
Often happens when watching videos, but I'm not sure if it happens ONLY WHEN watching videos.
However, no further way out than rebooting.
Sent from my GT-P5100 using xda app-developers app
Well i am facing this randomly..but usually while mx player is on.
I cant seem to find any solution to this.
In rare cases i need 2-3 reboots to fix this.
M soo very disappointed guys.
Have not a single site as great as xda and not many people are even looking at our problem.
I generalized the problem to most full screen apps.
And it happens usually while pausing the app and flicking down the status bar and doing some multitasking from there or pressing the home button.
Anyone....???
Or should i just try Omni Rom.?
Maybe Mokee has this bug..?
If you try Omni Rom, I really appreciate if you let me known the results in any case, since I have no free time and currently I cannot flash this rom
Okay mate, i'l flash that in about a week as my exams are going on.
Omni has just this battery drain issue.
It seems no one knows about the problem we are facing on mokee.
@loboz well i flashed omni and its feature packed..
No issues till now, a little different from mokee and you'l be glad you did as mokee's OTA are dead too..
Satisfied with omni..
Sent from my GT-P3100 using XDA Premium 4 mobile app
Since I got my phone on release day and I haven't been able to use it to make calls in my 2012 mazdaspeed3. My other phones have worked fine so I thought I needed a software update on my radio. Well everything is up to date and that didn't fix it.
The problem is when I make or receive a phone call the Bluetooth will connect and disconnect every 5-10 seconds. This makes it impossible to talk on the phone.
So I have tried stock roms, sense based roms, and all the CM based roms and they all did the same thing. Yesterday I was trying to figure it out so I sat in my car in the garage and the phone was in a constant connect disconnect loop. During this time I was disabling apps and services hoping to stop it when all of a sudden I turned off WiFi and it stopped. I then called my wife and had a 10 min conversation with no problems. So I now run a tasker profile that when Bluetooth connects it turns off WiFi so I can make calls. The problem is I have a nexus 7 dash mounted and I use the WiFi hotspot to run apps.
So after all that, does this sound like a hardware issue or a software issue? Should I return my phone for an exchange? Thanks for the help
Sent from my HTC6525LVW using Tapatalk
smalltownbird said:
Since I got my phone on release day and I haven't been able to use it to make calls in my 2012 mazdaspeed3. My other phones have worked fine so I thought I needed a software update on my radio. Well everything is up to date and that didn't fix it.
The problem is when I make or receive a phone call the Bluetooth will connect and disconnect every 5-10 seconds. This makes it impossible to talk on the phone.
So I have tried stock roms, sense based roms, and all the CM based roms and they all did the same thing. Yesterday I was trying to figure it out so I sat in my car in the garage and the phone was in a constant connect disconnect loop. During this time I was disabling apps and services hoping to stop it when all of a sudden I turned off WiFi and it stopped. I then called my wife and had a 10 min conversation with no problems. So I now run a tasker profile that when Bluetooth connects it turns off WiFi so I can make calls. The problem is I have a nexus 7 dash mounted and I use the WiFi hotspot to run apps.
So after all that, does this sound like a hardware issue or a software issue? Should I return my phone for an exchange? Thanks for the help
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Borrow the ole ball and chain's phone and see if it acts the same way.
Tried it. It works fine in my car, she has an S4. My phone also does the same in her car...
Sent from my HTC6525LVW using Tapatalk
Sounds like u need to swap it out for a replacement. Never had an issue unless using custom kernals.
deeznuts said:
Sounds like u need to swap it out for a replacement.
Click to expand...
Click to collapse
^ ^ What he said^ ^
Weird...
My M8 should be here today and I have a 2010 Mazdaspeed3. I hope this isn't an issue with all of them. Although, my MS3 has a long history of it's bluetooth not getting along with HTC phones.
Did you have any issues?
Sent from my HTC6525LVW using Tapatalk
smalltownbird said:
Did you have any issues?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
So far, no. It took me like 20 minutes to get the phone to pair but once that was done it hasn't disconnected at all. I have music constantly streaming through Bluetooth to the car and I've taken a couple calls with no issue.
having the same issue here. My vehicle is a 2013 Ford F150 with Sync.
Worked up until about a day ago .. Now i can't get stock or aosp roms to lock in bluetooth
jdebutts said:
having the same issue here. My vehicle is a 2013 Ford F150 with Sync.
Worked up until about a day ago .. Now i can't get stock or aosp roms to lock in bluetooth
Click to expand...
Click to collapse
Have you tried clearing data and cache in settings?
the Red Viper ROM
I am having the same issue.
It is connecting and disconnecting repeatedly, and it is SUPER annoying because it essentially renders my pebble watch useless.
For a while i was using the Automatic Link (car link) and was getting 'bluetooth share has stopped' errors, but found that when I stopped using the Automatic app it helped a little bit (stopped giving me the 'share has stopped' error), but it still connects and disconnects repeatedly.
The weirdest thing about this is that when I first got this phone I wasn't having this problem, everything was working fine for the first month or so, but it seems to keep getting worse.
I have tried wiping cache, dalvik, fixing permissions, etc. and have not had any luck, but I don't want to do a complete wipe of all my data and lose my text messages, etc. unless ABSOLUTELY NECESSARY, since there are images and things in there that I continually refer to for work, and I have not found that titanium backup restores them very reliably.
Has anybody had any luck with this issue? Could it be a defective device? It seems to me like it should be a software problem because it is not something I was having problems with from the start...
I am very frustrated with this, even more so because I love this phone so much. I have never had a phone that I liked as much as this one, usually the first thing I do is install an AOSP rom, but I even like Sense 6 in some ways. With Nova Launcher's 'OK Google' hotword support this phone is a dream come true... if only the bluetooth worked.
jonkunke said:
I am having the same issue.
It is connecting and disconnecting repeatedly, and it is SUPER annoying because it essentially renders my pebble watch useless.
For a while i was using the Automatic Link (car link) and was getting 'bluetooth share has stopped' errors, but found that when I stopped using the Automatic app it helped a little bit (stopped giving me the 'share has stopped' error), but it still connects and disconnects repeatedly.
The weirdest thing about this is that when I first got this phone I wasn't having this problem, everything was working fine for the first month or so, but it seems to keep getting worse.
I have tried wiping cache, dalvik, fixing permissions, etc. and have not had any luck, but I don't want to do a complete wipe of all my data and lose my text messages, etc. unless ABSOLUTELY NECESSARY, since there are images and things in there that I continually refer to for work, and I have not found that titanium backup restores them very reliably.
Has anybody had any luck with this issue? Could it be a defective device? It seems to me like it should be a software problem because it is not something I was having problems with from the start...
I am very frustrated with this, even more so because I love this phone so much. I have never had a phone that I liked as much as this one, usually the first thing I do is install an AOSP rom, but I even like Sense 6 in some ways. With Nova Launcher's 'OK Google' hotword support this phone is a dream come true... if only the bluetooth worked.
Click to expand...
Click to collapse
Sounds like the common theme may be root for whatever reason. I assume when you first had the phone and it worked that you were not rooted? Possible issue?
Sent from my SM-N900V using Tapatalk
jonkunke said:
I am having the same issue.
It is connecting and disconnecting repeatedly, and it is SUPER annoying because it essentially renders my pebble watch useless.
For a while i was using the Automatic Link (car link) and was getting 'bluetooth share has stopped' errors, but found that when I stopped using the Automatic app it helped a little bit (stopped giving me the 'share has stopped' error), but it still connects and disconnects repeatedly.
The weirdest thing about this is that when I first got this phone I wasn't having this problem, everything was working fine for the first month or so, but it seems to keep getting worse.
I have tried wiping cache, dalvik, fixing permissions, etc. and have not had any luck, but I don't want to do a complete wipe of all my data and lose my text messages, etc. unless ABSOLUTELY NECESSARY, since there are images and things in there that I continually refer to for work, and I have not found that titanium backup restores them very reliably.
Has anybody had any luck with this issue? Could it be a defective device? It seems to me like it should be a software problem because it is not something I was having problems with from the start...
I am very frustrated with this, even more so because I love this phone so much. I have never had a phone that I liked as much as this one, usually the first thing I do is install an AOSP rom, but I even like Sense 6 in some ways. With Nova Launcher's 'OK Google' hotword support this phone is a dream come true... if only the bluetooth worked.
Click to expand...
Click to collapse
you need to let HTC backup app take care of backing up your texts etc...what if you dropped the phone in the toilet tonight or got pushed into a pool?
this app is free...will backup your stuff daily or on demand and will restore email accounts/texts/desktop/apps/blinkfeed settings etc.
http://www.androidfilehost.com/?fid=23329332407589902
install that, backup to the cloud (uses Google drive) and then continue troubleshooting without fear of losing stuff.
Sent from my SM-T320 using Tapatalk
If my phone is on for more than 10 minutes, I lose calling functionality. When I try to call someone, it freezes and the Pixel becomes unresponsive, forcing me to hold down power for 10 seconds for a reboot. After this, it works just fine for another 10 or so minutes.
I have no idea when calling functionality begins to be lost because I can still send and receive texts, but I can't make or receive calls. I don't even get a wave of missed calls or anything when it works after a reboot.
Google Assistant has it's own issues when this happens too. It won't come up with "Hey, Google" at all. When I long press the home button, Google Assistant comes up, but I just get the floating dots. Fortunately, it doesn't freeze when I try this. Restart the phone and I'm good for about 10 minutes or so. I tried installing 3rd party calling apps, but the problem persists.
Hoping this is a Pie issue and waiting for the next security patch, will likely do a sideload flash-all. Any suggestions as to what the problem is from? Could my SIM card be the problem? Any apps I could try to help narrow down the issue? I had no issues with Oreo.
Thanks in advance.
Tried rebooting in safe mode. Slightly similar results: works fine for about 10 minutes but then it's just the mic not working. I can make and receive calls with out the phone freezing, but no mic.
mbstone said:
If my phone is on for more than 10 minutes, I lose calling functionality. When I try to call someone, it freezes and the Pixel becomes unresponsive, forcing me to hold down power for 10 seconds for a reboot. After this, it works just fine for another 10 or so minutes.
Click to expand...
Click to collapse
I have a similar issue with a used Pixel I purchased. I couldn't place or receive calls, with everything else working fine. Did the prerequisite online searches with results finding most everyone experiencing this issue chalking it up to hardware but I'm still thinking software. I tried a different phone app (drupe-enabled as default) with some success, then the problem returned (a few days later, rarely get/make calls). The default google phone app (version 23.0) fails every time. Currently looking into TWRP/Root and hoping to eliminate certain default apps to experiment further. Will be keeping an eye on this post! :cyclops:
--- Three weeks later ---
Could there be an issue within google play services with phone dialer app (any/or stock app)?
After continued issues I parked phone in drawer a bit then pulled out and tinkered with a few weeks later. Tried to isolate problem using logcat and on a hunch I flashed TWRP and a custom ROM but NOT any gapps package. Sticking sim in and using the built in phone app (Resurrection Remix -com.android.dialer) it works without issue. What? I flashed gapps (correct version/etc) and sure enough the problem returned. Went back to rom minus gapps, works fine. So, with straight up stock rom - stock phone dialer fails, custom rom - it works without a gapps package but not with.
Aimless Rambler said:
I have a similar issue with a used Pixel I purchased. I couldn't place or receive calls, everything else working fine. Did the prerequisite online searches with results finding most everyone experiencing this issue chalking it up to hardware but I'm still thinking software. I tried a different phone app (drupe-enabled as default) with some success, then the problem returned (about 5 days later). The default google phone app (version 23.0) fails every time. Currently looking into TWRP/Root and hoping to eliminate certain default apps to experiment further. Will be keeping an eye on this post! :cyclops:
Click to expand...
Click to collapse
Went back to Oreo before I had the problems and... problems persist. I'm sad. I had the privilege of speaking to someone from Google Support who was very knowledgeable. Unfortunately, my best option from the rep was to take it in to one of their authorized repair places.
Are you guys on Verizon? I'm having this problem with my dad's pixel on vzw.
brkshr said:
Are you guys on Verizon? I'm having this problem with my dad's pixel on vzw.
Click to expand...
Click to collapse
AT&T
---------- Post added at 07:47 AM ---------- Previous post was at 07:45 AM ----------
mbstone said:
Went back to Oreo before I had the problems and... problems persist. I'm sad. I had the privilege of speaking to someone from Google Support who was very knowledgeable. Unfortunately, my best option from the rep was to take it in to one of their authorized repair places.
Click to expand...
Click to collapse
--- Three weeks later ---
Could there be an issue within google play services with phone dialer app (any/or stock app)?
See my updated post (# 3) for what I've tried since..
Vzw ended up replacing my dad's phone through extended warranty. I talked to Google for awhile. Multiple factory resets, factory image installs, tried older phone apks. Nothing worked.
brkshr said:
Vzw ended up replacing my dad's phone through extended warranty. I talked to Google for awhile. Multiple factory resets, factory image installs, tried older phone apks. Nothing worked.
Click to expand...
Click to collapse
Older/newer phone dialer apps didn't work for me either ... custom rom and eliminating google play services did (no gapps). I'm still tinkering with the device ... installing frequently used apps using F-droid and Yalp, will test it. Not quite sure why but it works.
I ended up flashing Lineageos for Microg, presents it's own problems in the learning experience but it works.
Nothing ever worked in the end. No, not with Verizon. Bought through Canadian carrier called Fido.
Called Google tech and they weren't overly helpful. I started a chat with a Google Tech and they suggested I take it to UBreakIFix. They did a free diagnostic test and I referenced https://support.google.com/pixelphone/forum/AAAAb4-OgUsIW_gxTpXX3s/?hl=by that thread. Said they'd fix it for free even thought I was out of warranty. Got a new motherboard and my phone works like a charm.
Hey
Does anyone experience problems of phone having full signal and then dropping it.
The problem I'm experiencing is frequent dropout during calls and being unable to establish them afterwards.
I can send texts and use the internet one minute and the next the phone doesn't work and drops my calls as well as doesn't accept them.
I tried swapping SIMs, rebooting, flight mode, you name it. The phone starts working again after about five minutes.
Here is the error:
https://drive.google.com/file/d/1e6_D3RM6luCK_LWDQSmOq-gJmmxjQOd9/view?usp=sharing
I would really appreciate some help. I highly suspect that this started happening with one of the latest updates.
I'm on a vanilla 12.0.3 Global rom.
Cheers
DavidMarmon said:
Strange
Click to expand...
Click to collapse
Yup. I have it pinpointed to a software problem as the phone worked just fine until a couple of updates ago. I can't however work out what could cause it.
I'm currently trying toggling VoLTE and changing APN settings (APN had wrong settings but still worked). Maybe the combination of both could cause problem.
I have also found out that SMS and data connection works fine all the time. It's just the calling function that causes the problem. I can listen to Spotify all day and it will work but as soon as someone tries to call me the signal will drop and everything stops. When I call the same thing happens. The bars just drop to 0 and playback stops. It resumes right after and works fine as long as I don't try to call. If I do the same thing happens.
The issue resolves itself after 5-30 minutes or so and then everything works totally fine.
So yeah if I had a rooted phone I would definitely contribute this to faulty rom or a rogue app. But I don't have one so it should work fine.
I've managed to capture it on video (sorry for the shaky camera but it was hard to film using one hand):
https://www.youtube.com/watch?v=kxusuCwsiBc&t=2s
Reboots, flight mode, swapping SIM cards (using a brand new one), using a SIM in slot 1 or slot 2, heck both slots, VoLTE on or off... I have literally tried everything. Nothing changes. Placing the same card in my other phone is fine. The problem happens everywhere and not only in one place so it's not reception. Also it doesn't matter if I'm moving or not so it's not switching between towers.
Same prob
I have the same prob, and I also tried every thing even flashing lineage didn't help, did u manage to find solution????
fautsoops said:
I have the same prob, and I also tried every thing even flashing lineage didn't help, did u manage to find solution????
Click to expand...
Click to collapse
Sort off. I had to send it to a service center and they've returned my money as it was deemed irreparable.