Why do I have to press and hold the power button to turn the screen on after/during a phone call? It's been driving me crazy for months. Its almost as if the proximity sensor is bad or something, how do I test it?
Affichage des articles dont le libellé est during. Afficher tous les articles
Affichage des articles dont le libellé est during. Afficher tous les articles
mardi 30 décembre 2014
samedi 27 décembre 2014
No Voice during calls 4.4.3 topic
Hello!
I have been having a problem where I cannot hear anyone or be heard during calls.
I am running ViperOne ROM 7.0.1 with base 4.3.3.
My question: I went to the Viper ROM website and there I found this:
" ATTENTION:
The 7.x.x rom is based on HTC latest 4.4.3 base and requires you to update your firmware.
You need to do that on your own, because we can’t install the firmare for you with the rom install.
If you don’t install the new firmware you will have*issues no voice during calls.
You can find several threads on xda how to update your firmware."
When I upgraded to 4.3.3, I didn't do anything fancy. I don't know what I did to upgrade it but I now have 4.3.3 and I never "found several threads on xda how to update my firmware."
I know this is noob, could someone send me to the thread where I can fix this, or do I have to downgrade then re- upgrade my firmware?
Thanks, sorry if this question is repeat, I did search..
Sent from my HTC One using xda-developers.com, powered by appyet.com
I have been having a problem where I cannot hear anyone or be heard during calls.
I am running ViperOne ROM 7.0.1 with base 4.3.3.
My question: I went to the Viper ROM website and there I found this:
" ATTENTION:
The 7.x.x rom is based on HTC latest 4.4.3 base and requires you to update your firmware.
You need to do that on your own, because we can’t install the firmare for you with the rom install.
If you don’t install the new firmware you will have*issues no voice during calls.
You can find several threads on xda how to update your firmware."
When I upgraded to 4.3.3, I didn't do anything fancy. I don't know what I did to upgrade it but I now have 4.3.3 and I never "found several threads on xda how to update my firmware."
I know this is noob, could someone send me to the thread where I can fix this, or do I have to downgrade then re- upgrade my firmware?
Thanks, sorry if this question is repeat, I did search..
Sent from my HTC One using xda-developers.com, powered by appyet.com
By:
dd
On 14:43
jeudi 25 décembre 2014
GT-S6310N bricked during root? topic
Hi,
I was following the instructions at rootmyandroid dot org/how-to-root-unroot-samsung-galaxy-young.html (sorry the forum won't allow me to post a direct link) to root my GT-S6310N, specifically the part after "rooting the GT-S6310N". The rest of the article talks about just S6310 without the "N", so I thought that'd be the instructions I should follow. Above it it also says "Only For Samsung Galaxy Young S6301 Owners", so it might have been the wrong process after all..?
Regardless, as per the instructions, I installed Odin 3.07, booted into Download Mode, ran Odin, and it reported a success (see attached screenshot). The device then booted as normal on its own, and when done, I did a normal shutdown, and booted into Recovery Mode. At this point I realized I don't have a microSD card in the device for the "UPDATE-SuperSU-v1.41.zip" file, so I selected "reboot" and the device again booted normally.
At this point I opened up the plastic back cover of the phone, and to my dismay, the battery fell out. I didn't think anything of it, and proceeded to look for a microSD card I could use. I didn't in fact find one, so I thought I'd boot the device up and figure out something else. But after carefully placing the battery and back cover back on, the device won't power up anymore. It won't vibrate, the display doesn't come on, nothing. If I plug it into a power outlet it doesn't show any signs of life. None of the Download/Recovery mode key combos work, either. Odin doesn't react to the device being plugged in in any way.
I guess I'm already willing to accept I managed to brick the device, but since I've successfully rooted 3 or 4 ones before, I'd like to at least understand what I did wrong. I've been under the impression that while many things can (and will) go wrong during rooting/CWM installation, most situations are recoverable (I've gotten devices e.g. stuck to a boot loop before).
At first I was convinced there must have been some physical damage done to the phone/battery when I opened the back cover, but after a careful inspection I can't see anything wrong with it. I've tried putting it back together at least 5 times. Also it should be noted that the battery fell out onto a soft couch, so I'm pretty sure it's not damaged in any way.
Any pointers welcome as to what went wrong and/or something I could still try. :/
I was following the instructions at rootmyandroid dot org/how-to-root-unroot-samsung-galaxy-young.html (sorry the forum won't allow me to post a direct link) to root my GT-S6310N, specifically the part after "rooting the GT-S6310N". The rest of the article talks about just S6310 without the "N", so I thought that'd be the instructions I should follow. Above it it also says "Only For Samsung Galaxy Young S6301 Owners", so it might have been the wrong process after all..?
Regardless, as per the instructions, I installed Odin 3.07, booted into Download Mode, ran Odin, and it reported a success (see attached screenshot). The device then booted as normal on its own, and when done, I did a normal shutdown, and booted into Recovery Mode. At this point I realized I don't have a microSD card in the device for the "UPDATE-SuperSU-v1.41.zip" file, so I selected "reboot" and the device again booted normally.
At this point I opened up the plastic back cover of the phone, and to my dismay, the battery fell out. I didn't think anything of it, and proceeded to look for a microSD card I could use. I didn't in fact find one, so I thought I'd boot the device up and figure out something else. But after carefully placing the battery and back cover back on, the device won't power up anymore. It won't vibrate, the display doesn't come on, nothing. If I plug it into a power outlet it doesn't show any signs of life. None of the Download/Recovery mode key combos work, either. Odin doesn't react to the device being plugged in in any way.
I guess I'm already willing to accept I managed to brick the device, but since I've successfully rooted 3 or 4 ones before, I'd like to at least understand what I did wrong. I've been under the impression that while many things can (and will) go wrong during rooting/CWM installation, most situations are recoverable (I've gotten devices e.g. stuck to a boot loop before).
At first I was convinced there must have been some physical damage done to the phone/battery when I opened the back cover, but after a careful inspection I can't see anything wrong with it. I've tried putting it back together at least 5 times. Also it should be noted that the battery fell out onto a soft couch, so I'm pretty sure it's not damaged in any way.
Any pointers welcome as to what went wrong and/or something I could still try. :/
By:
dd
On 14:07
[Q] Blackscreen During Boot topic
Hello, forum
For quite a while, I've been getting a weird issue - I get a black screen while booting. When the phone's about to boot, the boot animation comes up. I thought that it was my ROM (stock, rooted CM11S), but installing PA 4.6 got the same result. I have multiROM installed. Could that be an issue?
Thanks
Raptor
For quite a while, I've been getting a weird issue - I get a black screen while booting. When the phone's about to boot, the boot animation comes up. I thought that it was my ROM (stock, rooted CM11S), but installing PA 4.6 got the same result. I have multiROM installed. Could that be an issue?
Thanks
Raptor
By:
dd
On 11:33
[Q] Double tap during phone call ends call! Lollipop? topic
I believe I was having this phone disconnect issue since I flashed a lollipop based rom. What happens is when I am on a phone call, the call will disconnect. My proximity sensor is working fine. To test what was going on, I made a call, put my finger over the proximity sensor, and can double tap anywhere on the screen (which is off), even a slower double tap, and it will end the call and wake the screen.
I cannot find any setting for this. It appears my face bumps the phone while talking. I've had this G2 for a while, and only experienced it since I flashed CM12 lollipop, and I even tried another lollipop Resurrection Remix and it still does the same thing.
Also another tidbit, my screen was dropped and a local shop did replace the front glass and digitizer recently, and I think I upgraded to lollipop shortly after I got it back. Not sure if it has anything to do with it. All other features on my phone work great.
Any ideas?
I cannot find any setting for this. It appears my face bumps the phone while talking. I've had this G2 for a while, and only experienced it since I flashed CM12 lollipop, and I even tried another lollipop Resurrection Remix and it still does the same thing.
Also another tidbit, my screen was dropped and a local shop did replace the front glass and digitizer recently, and I think I upgraded to lollipop shortly after I got it back. Not sure if it has anything to do with it. All other features on my phone work great.
Any ideas?
By:
dd
On 07:32
dimanche 21 décembre 2014
no sound during call (401.11) topic
Hi,
I really don't know what to do today.
I am on hboot 1.57 s-on and I was stuck with the no sound in call problem,so I downloaded a stock version of Android with stock kernel and updated the software version(firmware?) To the 6.09.401.11 but on any rom (insertcoin, viper,stock) the no sound in call bug is still there(no sound and no microphone).
The problem is that i can't downgrade my firmware because of the s-on.
So i'm stuck with a phone that can't call and I really don't know what to do to solve this. :(
Right now i'm back on viper but even when flashing the fix phone calls won't work. So I really need your help here.
Thanks in advance!
I really don't know what to do today.
I am on hboot 1.57 s-on and I was stuck with the no sound in call problem,so I downloaded a stock version of Android with stock kernel and updated the software version(firmware?) To the 6.09.401.11 but on any rom (insertcoin, viper,stock) the no sound in call bug is still there(no sound and no microphone).
The problem is that i can't downgrade my firmware because of the s-on.
So i'm stuck with a phone that can't call and I really don't know what to do to solve this. :(
Right now i'm back on viper but even when flashing the fix phone calls won't work. So I really need your help here.
Thanks in advance!
By:
dd
On 06:59
jeudi 18 décembre 2014
[Lollipop] M7 GPE screen on during the call topic
After I have upgrade to Lollipop, I have encounter a issue that screen does not turn off when take device to ear during a call. Am I the only one encounter this issue?
By:
dd
On 20:33
Mic is going quiet during calls - receiver notices volume drop. topic
Hi there everyone,
I've regularly been getting reports that during a call, the other party notices the mic volume on my PQ drops - sounds like I'm far away from the phone.
More info: also does it when using bluetooth headphones, tried different sets
Sent from my PHOTON Q using XDA Free mobile app
I've regularly been getting reports that during a call, the other party notices the mic volume on my PQ drops - sounds like I'm far away from the phone.
More info: also does it when using bluetooth headphones, tried different sets
Sent from my PHOTON Q using XDA Free mobile app
By:
dd
On 17:58
samedi 13 décembre 2014
How to fix the current no audio during calls issue topic
Ive seen a lot of workarounds for this, but this is the only one that seems to work universally without breaking anything else. I also haven't seen it mentioned here yet (surprisingly). Requires root.
Go to play store and install Disable Service
Launch it and locate the listing for Google Play Services
Disable checkinservice ONLY
Reboot
Go to play store and install Disable Service
Launch it and locate the listing for Google Play Services
Disable checkinservice ONLY
Reboot
By:
dd
On 17:24
jeudi 11 décembre 2014
[Q] screen flicker during boot xt1033 topic
Guys im using xt1033 i converted it to gpe 4.4.4 and tried updating it to 5.0.1 via otg sideload and i got stuck in Google unlocked logo and so that i flashed stock rom again.after that whenever i boot my phone or whenever im in recovery there is a line orginating from top and flows till the bottom continuously. This stops only when i turn off the screen after boot and turn it on. Then my phone works normally. I wanted to know that weather this is a problem due to flashing? Or due to hardware? Or something else ? Need solution for getting rid of this. I also wanted to know that weather i can flash roms with this problem ? Im scared that my phone will not work if i flash something with this problem. Guys please get me through this... Thanks in advance...
By:
dd
On 21:16
lundi 8 décembre 2014
[Q] No sound during call (even if speakerphone is on) topic
Additionally no one can hear me on the other end.
This strange issue started happening this morning. I have tried a hard reboot.
I've confirmed that I can still play music (from Google Play Music), and when I end the call it makes the regular *beep* noise.
Running stock Android.
Any assistance in fixing this issue is greatly appreciated.
This strange issue started happening this morning. I have tried a hard reboot.
I've confirmed that I can still play music (from Google Play Music), and when I end the call it makes the regular *beep* noise.
Running stock Android.
Any assistance in fixing this issue is greatly appreciated.
By:
dd
On 14:39
samedi 6 décembre 2014
Blue Led, blank Screen during Bootloader Unlock topic
Hi there,
I tried to unlock my new Z1C with Sony Bootloader Unlocker from Kingo.
Currently the program is Stuck at the following Screen
img5.fotos-hochladen.net *dash* uploads/17mg2pno8qa.png (sorry I'm new an can't post images now)
It says fetching unlock data
The phones screen is blanc and the LED is lit blue.
In the Devide Manager S1Boot Fastboot is listed as unknown devices.
My question is now, what can I do to get the phone back working? Is it safe to just unplug USB?
Thanks a lot for help!
I tried to unlock my new Z1C with Sony Bootloader Unlocker from Kingo.
Currently the program is Stuck at the following Screen
img5.fotos-hochladen.net *dash* uploads/17mg2pno8qa.png (sorry I'm new an can't post images now)
It says fetching unlock data
The phones screen is blanc and the LED is lit blue.
In the Devide Manager S1Boot Fastboot is listed as unknown devices.
My question is now, what can I do to get the phone back working? Is it safe to just unplug USB?
Thanks a lot for help!
By:
dd
On 08:12
Inscription à :
Commentaires (Atom)
