Hi all,
Friend and I both have the Incredible S, loving it! He has a slight issue and I can't for the life of me solve it. Everything was working fine but now when he has an incoming call and the screen is off the incoming call screen flashes up briefly then disappears and device shows normal 'desktop' - you can't answer the call!
If you call his phone and the screen is active, incoming call screen pops up as expected and you can answer call.
Any ideas peeps?
Thanks
Ant
Hmmm,
I'm having the exact same problem. Running Fresh Evo on HTC Evo. Would love to know why this is happening. Any ideas?
Sliphorn said:
Hmmm,
I'm having the exact same problem. Running Fresh Evo on HTC Evo. Would love to know why this is happening. Any ideas?
Click to expand...
Click to collapse
Never worked it out, friend did factory reset in the end to fix it.
Ant
Bummer. Here's some info:
Latest Fresh EVO
Rom Manager
Rom Manager Janitor
Juice Defender Ultimate Juice
Titanium Backup Pro
Cachemate for Root
ShootMe
Adfree Android
adbwireless
Call Control (problem before this, though)
Launcher Pro
Any hints?
Having the same exact issue. This sucks... This started today for me around noon ( no calls before then), and has persisted throughout the day. Yesterday was fine.
I use Google voice for all of my calls.
The only thing I've done today that I haven't done every other day was that I installed the Gtalk app this morning. In the past, I've used Gmail directly. However, my computer was off during at least one of the phone calls I received today, so I can't imagine this could be it...
Perhaps because I installed gAlwaysIdle (an addition to Gtalk that makes you never go idle or always be idle) as well?
Does this correspond with anyone else's experience?
I'll probably just reflash my phone
<Rooted Atrix 4g running GingerBlur>
hmm this sounds like a serious firmware problem tho..
all i could suggest is flash a firmware that the most of the ppl are using, and dont got probs with...
well doing a good reboot seems to help alot these days. So disable the fastboot option en turn it off, wait a while (10 secs should be enough) en start the device again.
Also had some of the trouble like crashing things and this solved it for me. Give it a try and hope it will fix it.
Otherwise there seems to be no other way than a factory reset (go htc!)
I upgraded my Captivate to gingerbread/talon/continuum yesterday.
That went fine and everything was hunky dory.
Phone was working fine the whole day today, incoming/outgoing calls, data.
I came home and installed Skype and thats when all hell broke loose.
Now the phone part is dead (kinda!). I can make calls fine but if I get a incoming call, the call gets disconnected after 1 ring and I get a msg popup (like some error) but I cant really see what the message is.
I also noticed that it disconnects me from ATT network when a call comes in and then after a little bit it reconnects.
I also verified this by going to the About->Status screen and then making a call.
It normally says ATT but for a couple of secs after call drop it says 'Unknown'.
What did I do to screw it up and how can I fix it?
Thanks
Glaring obvious first question -- did you try uninstalling Skype to see if that resolved anything?
mK
mommehK said:
Glaring obvious first question -- did you try uninstalling Skype to see if that resolved anything?
mK
Click to expand...
Click to collapse
Sorry, I should have added that to my first post.
Yes, I did uninstall Skype and reboot the phone, just incase, but no difference.
Still the same.
Update:
After playing around with various things for a couple of hrs, I finally gave up and reflashed Continuum.
Everything started working again.
Applied my Ti backed up config and loaded Netflix. Same problem. Dialer died with an incoming call.
I reflashed Continuum again and everything started working as expected.
I then applied my Ti backup, still everything working.
I am in the process of updating all my apps and then lets see if everything is still working.
The only thing that is missing for now is the Netflix app.
I will keep everyone updated if its the Netflix app causing the issue or its the Skype.
activemind: Keep us posted if you find a cause. I am on a Samsung Vibrant (3g) via TMOB but have been having the same issue today with a completely different rom (simply honey). This is actually about the 6th thread I've found in the past two days having this same issue on Galaxy S phones.
I have had this problem before and what caused it was restoring system data with titanium. Make sure you are only restoring apps.
Sent from my GT-I9000 using XDA Premium App
Hello Guys,
a Friend bought a used i9000 on ebay for 130€ from a business man, which got a ne phone from his company and sold hin mobile on ebay and he asked me for a litte work around of his "new" phone.
Optically is the phone perfect BUT if I take a call on Android 2.3.6 display stays black (with backlight) and I can make the call. But I can't do anything more, hang up etc. If the opponent hangs up, I hear the hang up sound but display stays black and thephone wount do anything. So it's needet to pull battery, put it back and restart the phone. On doing a call, the phone has similar problems, it freezes.
After a couple of re-flashes with odin nothing changed.
So I tryed to switch to actual android OS. I flashed SlimBean 2.7. Every thing workes well. but even call-issues. If i receive a call, the phone woun't do anythin and it keeps ringing and "holds" the call for exactly 32 seconds. Now I can talk with the caller. But most callers don't wait 32 seconds to call to me If I do a call in JB I can talk from the first second on, but display freezes and I can't hang up. Thats the state for around 28 seconds and then phone will response normally and I can hang on and do everything I whant.
Even in Slim I tryed reflash a fiew times with no cahnge.
Has anyone an idea?
I think thats a hardware related problem. But in fact its possible to do a call, but only with that issues/delays. So I need a solution, that JB (SlimBean 2.7) don't "hold" the call/freezes for 32 seconds. I think because its every time 32 seconds, thats a fix value in JB. so I need something to cahnge the value from 32 secs to may be 0 oder maximum 5. But thats only guessed by me so I need help of a PRO here to solve that nerving issue.
I also tryed to install other dialers, but thats not a good solution, because the use for calling the stock rom dialer (phone.apk), damn
Please help me guys (sorry for my bad english )
UPDATE: I did read a litte in web and found, that the light sensor could cause issues in calling (start and end). So I downloaded a app whitch will show me he values of the light sensor. Ands its true, the sensor will show me whole time same values. I changed the sensor od the device of my friend and mine but that does not solve the problem. same issue.
In second Post I'll load a some Pictures of both devices up. My device shows around 30 lux and the one of my friend around 5.
UPDATE 2: After some more reading in web I found more guys with same call problem but no solution. May be it could help to disable GP2A Driver oder better only to overwrite the lightsensor value with a fix one.
UPDATE 3: OK I tested with 3 apps and the proximity sensor of the phone is broken ...now i need a solution to disable it or set a fix value in android so that the sensor is unused.
Any ideas?
UPDATE 4: I downloaded the "Hardware Disable" app from Play store and disabled GP2A.
It works for now, I just have to switch off the screen manually by pushing power button at a call and turn it on by pushing power again. But thats no problem for me anf my friend and much better as the call related freezes.
But I need at every startup to confirm to disable the sensor. So I'm looking for a permanent solution for this. Also because the device feels a little bit laggy now.
Pics
SOLUTION
So Guys I found a good working solution fpr proximity sensor delay, 32 second freeze by taking a call.
I wrote my Solution in SlimBean thread
http://forum.xda-developers.com/showpost.php?p=32809014&postcount=4406
Schould work on any ROM (GB, ICS and JB) because they all use the same Hardware .so (sensors.aries.so in this case)
Hi,
Recently I've started to experience call issues. During the call (not always) after some time (sometimes half miunte, sometimes 4 minutes, pretty random) audio is gone, we can't hear each other. After ending the call and calling other side again, there is some issue, call cannot be set up, i have to wait like 30sec/1 minute, and even after that audio is missing sometimes. My Note 5 is N920K, yesterday I've flashed latest official firmware (but there was DRK missing error), and flash Dr Ketan ROM after, and it didn't fix the problem.
Does anyone have any idea what could cause it? Is it hardware problem? If so, what i should change or how i can diagnose it?
So problem was with S8 port ROM
Good afternoon,
I have had a Nokia 8 for a few weeks now and have now found that my microphone only works during calls. While I'm on the phone everything works normally but in all other apps nothing happens, e.g. in Whatsapp you only hear a short crack when you hear a voice message and then nothing, although you have said something (see attachment), also other apps that use the microphone like the Google Home App or a guitar vocal app don't work. Of course the permissions are set correctly for all apps but apparently this has no effect (see attachment). I've already written with Nokia Support, but after 14 mails about permissions, emptying caches and doing softresets they couldn't help me. Finally I was told to wait for the next Android update and hope that my problem was fixed there, or I should send my phone back to the dealer. My hope now is that one of you has an idea what could be the cause of the problem.
Thank you for your time!
- Joeigel
Attachments:
picload.org/view/dclcpodg/screenshot_20181201-165257.png.html
picload.org/view/dclcpodr/screenshot_20181201-165237.png.html
Audio Message from Whatsapp:
instaud.io/30ZI
Hello to everyone there,
I have next problem on my Nokia 8:
When somebody calls me or when I call someone on viber, I turn on speakers and other side can't hear me. Also when I put it on video call the same issue conitnuous to take. Regular GSM calls or viber VoIp calls works great as well as video calls with headphones.
I open ticket to a viber about this problem, and they told me I need to contact my manufacturer.
Yesterday I installed an Android pie from beta labs, but the problem still exists. How do you think the problem is hardware?
ratola said:
Hello to everyone there,
I have next problem on my Nokia 8:
When somebody calls me or when I call someone on viber, I turn on speakers and other side can't hear me. Also when I put it on video call the same issue conitnuous to take. Regular GSM calls or viber VoIp calls works great as well as video calls with headphones.
I open ticket to a viber about this problem, and they told me I need to contact my manufacturer.
Yesterday I installed an Android pie from beta labs, but the problem still exists. How do you think the problem is hardware?
Click to expand...
Click to collapse
Hi ratola,
you can dial *#*#372733#*#* for a hidden FQC test menu, here you can test each mic seperated, i guess in your case it's the second mic in the top-speaker.
- Joeigel
Joeigel27 said:
Good afternoon,
I have had a Nokia 8 for a few weeks now and have now found that my microphone only works during calls. While I'm on the phone everything works normally but in all other apps nothing happens, e.g. in Whatsapp you only hear a short crack when you hear a voice message and then nothing, although you have said something (see attachment), also other apps that use the microphone like the Google Home App or a guitar vocal app don't work. Of course the permissions are set correctly for all apps but apparently this has no effect (see attachment). I've already written with Nokia Support, but after 14 mails about permissions, emptying caches and doing softresets they couldn't help me. Finally I was told to wait for the next Android update and hope that my problem was fixed there, or I should send my phone back to the dealer. My hope now is that one of you has an idea what could be the cause of the problem.
Thank you for your time!
- Joeigel
Attachments:
picload.org/view/dclcpodg/screenshot_20181201-165257.png.html
picload.org/view/dclcpodr/screenshot_20181201-165237.png.html
Audio Message from Whatsapp:
instaud.io/30ZI
Click to expand...
Click to collapse
Hi Joeigel, unfortunately I have the same issue (and story regarding contacting support). The only way I can make calls via for instance WhatsApp is by using a handfree headset, or setting it to speaker-mode.
Waiting for the Android 9 release, if this isn't fixed with it, I'll send it in for warranty.
I do have another issue with the phone, and that's when I unlock my phone using the fingerprint scanner, 1 out of 4 times or so, the phone enables split screenmode. Do you (or someone else here) have similar experiences. It's quite annoying.
Update: Installed Pie, and no improvement. Issues still persists. Returning the phone today.
Sorry for the late response, my phone is also on it's way back to GB...
Joeigel27 said:
Sorry for the late response, my phone is also on it's way back to GB...
Click to expand...
Click to collapse
Ok, just got an update from the repair-center, they replaced a part and it should work OK now. Curious to see what they did and if it's resolved. Have to wait until it's shipped back. But keep us also posted about your progress
Off-topic: another issue I sometimes experience is when I unlock my phone with fingerprint, it sometimes switches automatically to the split-screen mode. It happens quite often and it's a bit annoying. Did you experience something similar with your Nokia?
odyon said:
Ok, just got an update from the repair-center, they replaced a part and it should work OK now. Curious to see what they did and if it's resolved. Have to wait until it's shipped back. But keep us also posted about your progress
Off-topic: another issue I sometimes experience is when I unlock my phone with fingerprint, it sometimes switches automatically to the split-screen mode. It happens quite often and it's a bit annoying. Did you experience something similar with your Nokia?
Click to expand...
Click to collapse
I didn't experienced something like this. Did they send it back to you yet? Maybe they fixed both... ^^'
Microphone issue here too.
Internal mic on front facing camera is the culprit. I noticed a few weeks back that my 'ok google' hotwords were no longer working. This became a problem after I installed the december security patch. I rolled back to the november security patch and this did temporarily fix the issue, after I had gone through the initial setup of the phone, my 'ok google' hotwords worked, until i went to use the camera to see if the issue still existed... unfortunately it does. Contemplating rolling back to july to see if the issue is resolved, or trying to move forward and installing pie.
nagesco said:
Microphone issue here too.
Internal mic on front facing camera is the culprit. I noticed a few weeks back that my 'ok google' hotwords were no longer working. This became a problem after I installed the december security patch. I rolled back to the november security patch and this did temporarily fix the issue, after I had gone through the initial setup of the phone, my 'ok google' hotwords worked, until i went to use the camera to see if the issue still existed... unfortunately it does. Contemplating rolling back to july to see if the issue is resolved, or trying to move forward and installing pie.
Click to expand...
Click to collapse
Could any up or downgrade fix it?
Joeigel27 said:
Could any up or downgrade fix it?
Click to expand...
Click to collapse
I've tried going up or down, I have oreo and pie on each of my A/B partitions and it does nothing. When i downgraded to oreo it worked for awhile but updating the google app or some sort of background service broke it again. Its definately mic 3 that has a fault, it has background interference noise when i do the test, it also occurs when recording video with the front facing mic on camera, the problem with the mic never goes away, after up/downgrading, I can't say whether this is related since it works prior to updating. rolling back/disabling doesn't solve the problem for the apps. Microphone/earpiece holes are clean and undamaged.
nagesco said:
I've tried going up or down, I have oreo and pie on each of my A/B partitions and it does nothing. When i downgraded to oreo it worked for awhile but updating the google app or some sort of background service broke it again. Its definately mic 3 that has a fault, it has background interference noise when i do the test, it also occurs when recording video with the front facing mic on camera, the problem with the mic never goes away, after up/downgrading, I can't say whether this is related since it works prior to updating. rolling back/disabling doesn't solve the problem for the apps. Microphone/earpiece holes are clean and undamaged.
Click to expand...
Click to collapse
After further testing of this issue, the 'OK Google' issue is still present, if I want to ask google assistant 'ok google' the microphone barely picks up anything or even my question, practically screaming into the microphone is the only way to activate it, this matches with the results on my google activity, listening to my recordings of my queries shows evidence that the microphone sensitivity is way too low.
HOWEVER, when using google assistant by means of pressing the microphone and then asking the question, the result is clear and understandable and doesn't suffer from volume issues, I can't pinpoint if this is an issue with the Nokia specifically, it is not a problem with any other application that uses the microphone.
Having the same issue with Mic 3. It means I can't use it in speakerphone mode during calls or in Skype. It doesn't prevent me from using the Google assistant though.
My smartphone was sent in and repaired (complete motorboard replaced). During the time it was gone Android 9 came out, so I'm not sure if it was the repair or the software update.
But it works again without any problems
Kind regards
Joeigel