Related
I don't know if this is just an issue with me or if others are experiencing the same issue.
for some reason my proximity sensor is VERY sensitive... for example if I move my face just 1/2 and inch from the screen my screen turns on and I either press "Mute" or "Speaker" with my cheek OR i hang up on the person I'm calling when I place the phone back against my face.
This happens about 50% of the time... so every other call I make has this issue.
I don't know if I can change the sensitivity or the length of time before the screen turns on.
I'm coming form the Eris/D1/DX/Fascinate and I never had these issues with my older phones.
Any advice or Steps to fix this would be greatly appreciated.
Plz Advise
Happens to me too, but I don't manage to hang up or mute the calls normally. I'd love a solution as well!
Magicadder said:
I don't know if this is just an issue with me or if others are experiencing the same issue.
for some reason my proximity sensor is VERY sensitive... for example if I move my face just 1/2 and inch from the screen my screen turns on and I either press "Mute" or "Speaker" with my cheek OR i hang up on the person I'm calling when I place the phone back against my face.
This happens about 50% of the time... so every other call I make has this issue.
I don't know if I can change the sensitivity or the length of time before the screen turns on.
I'm coming form the Eris/D1/DX/Fascinate and I never had these issues with my older phones.
Any advice or Steps to fix this would be greatly appreciated.
Plz Advise
Click to expand...
Click to collapse
Which kernel / rom are you using? I have heard that some kernels have caused proximity sensor issues but I'm not sure if the issue others have experienced is the same as yours. I'd try a battery pull first, if that doesn't help try a different kernel and see if that fixes it. If the issue still persists, it could be a hardware issue and you might have to get the phone exchanged under the manufacturers warranty.
Sent from my Thunderbolt using Tapatalk
m00nshake said:
Which kernel / rom are you using? I have heard that some kernels have caused proximity sensor issues but I'm not sure if the issue others have experienced is the same as yours. I'd try a battery pull first, if that doesn't help try a different kernel and see if that fixes it. If the issue still persists, it could be a hardware issue and you might have to get the phone exchanged under the manufacturers warranty.
Sent from my Thunderbolt using Tapatalk
Click to expand...
Click to collapse
I'm using Stock firmware with bamf 4.3a Kernal
I've reset this thing too many times... installing different roms and such.. but I can verify that this is happening to another phone. My wife's phone does exactly the same thing. we purchased out tbolts on launch day ( if that helps )
The proximity sensor is located were the Verizon V is at
In between the big V is the sensor. Very hard to see go under a light a tilt the like you would if you want to find scratchs on your phone it really is between the V or I'm you can not find it. Make a phone call and get your index or any finger. And again make sure your under light and make the shadow of your finger go on top of the proximity sensor. Mine is very sensitive also.
-Monky_1
-Monky_1
My proximity sensor seems pretty touchy, as well.
I initially thought it to be a problem with a particular version of Adrynalyne's kernel, but I'm not so sure anymore. Adrynalyne also said that a kernel shouldn't affect the proximity performance -- that HTC puts these setting or whatever in the framework (what that means exactly, I'm not sure).
Anyway, I haven't done any exhaustive testing or anything, but I did notice one thing that seems to help keep my screen off is to have the thing pointed straight down while on the phone. My natural inclination is to have it along my jaw line, with the end pointed at my mouth. But the proximity sensor is to the left-of-center on the phone. Angling it moves the sensor away from your ear a bit. Assuming you've got it up to your right ear, that is.
I'd still welcome any other points folks might have about this.
calbruc said:
My proximity sensor seems pretty touchy, as well.
I initially thought it to be a problem with a particular version of Adrynalyne's kernel, but I'm not so sure anymore. Adrynalyne also said that a kernel shouldn't affect the proximity performance -- that HTC puts these setting or whatever in the framework (what that means exactly, I'm not sure).
Anyway, I haven't done any exhaustive testing or anything, but I did notice one thing that seems to help keep my screen off is to have the thing pointed straight down while on the phone. My natural inclination is to have it along my jaw line, with the end pointed at my mouth. But the proximity sensor is to the left-of-center on the phone. Angling it moves the sensor away from your ear a bit. Assuming you've got it up to your right ear, that is.
I'd still welcome any other points folks might have about this.
Click to expand...
Click to collapse
This is exactly what's happening. It's nice to see that I'm not the only one having this issue... even tho I'm sure it's annoying for everybody. Hopefully we'll be able to get some relief from this.
http://market.android.com/details?id=i4nc4mp.myLock.phone
This app keeps me from smashing my Droids.
this is not a signature I type it in every time maybe sent from my phone or my computer
rizzomegav said:
http://market.android.com/details?id=i4nc4mp.myLock.phone
This app keeps me from smashing my Droids.
this is not a signature I type it in every time maybe sent from my phone or my computer
Click to expand...
Click to collapse
Would this work even tho the Thunderbolt has no physical Trackball or Camera Button?
Not to discredit this app Kudos to the Dev who wrote it, but it seems like a work around and not an actual Fix.
But I'll try it out and reply back with some feedback
Here's what I do and it works for me most of the time. When making or receiving a call, once the call is 'connected' I quickly hit the 'home' button so I'm no longer on the 'phone screen' & then the power button which darkens & locks the screen. Even if the proximity sensor allows the screen to light up, the lockscreen is still there and prevents me from muting or hanging up on the other person. It's not a perfect solution since my jaw has managed to unlock the screen & randomly open apps occasionally but it beats hanging up on someone every 5 seconds.
Sent from my NookColor using Tapatalk
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
gatorguy said:
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
Click to expand...
Click to collapse
BAMF 1.5 is based on the new leak, which includes a fix for the proximity sensor. If the rom you are running isn't based on the recent leak for our phones, then you don't have the fix, and will most likely have problems with it.
Check this thread out at droid forums! It fixed my "problem" with the proximity sensor. Simply blow out the sensor with air. Apparently dust gets in there and jacks it all up. I can confirm big time results with this method.
http://www.droidforums.net/forum/thunderbolt-tech-support/142050-thunderbolt-proximity-sensor-issue.html
Edit: All those kernel switches and setcpu tweaks over pocket lint!!! Damnitman!
Magicadder said:
Would this work even tho the Thunderbolt has no physical Trackball or Camera Button?
Not to discredit this app Kudos to the Dev who wrote it, but it seems like a work around and not an actual Fix.
But I'll try it out and reply back with some feedback
Click to expand...
Click to collapse
Well the fix is only to hold the phone correctly unfortunately. My gf has no problem using either phone (hers or mine) but if I touch them its muted hang up bam.
One of my coworkers has the same problem as me another dosent. Its absolutely user errorish IMO.
It works with my thunder bolt sort of the home key still works. I don't mind it, moreso than buggered calls.
this is not a signature I type it in every time maybe sent from my phone or my computer
gatorguy said:
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
Click to expand...
Click to collapse
A screen protector was an issues for me. The first one I put on did not fit perfectly, so the top of the protector cut directly threw the center of the sensor and collected dust and gave me some issues. The second one i used was applied from the top down to not obstruct the sensor. Solved my problem.
My phone sensor will black out when I am on a call and the phone is against my face, but when I pull the phone away the screen won't come back up for some reason..
I find that it seems to reflect off the arm of my glasses, which is kinda glossy like. When the IR LED reflects back at it, it seems to assume infinite distance. Same thing happened on my Droid.
There was also a case that lacked the cutout for the proximity sensor on the Droid... screen would never turn off because it reflected the IR.
I'm glad to see I'm not the only one with this problem. It's been happening to me for a few weeks now. I've run the majority of available ROMs and kernels (pre- and post- radio update) in multiple combinations so, I believe its safe to say they are not to blame.
I'm not using a screen protector so, that can't be to blame. And I don't have any scratches on my screen either. I'm curious about this dust theory though. It may be the best one I've heard yet. Has anyone else put the air hose to their Thunderbolt yet? I think I'm gonna give it a go asap. But, in the meantime, I'd love to hear whether anyone else has had positive results. If not, I fear I may have to move on to the glasses theory. I really hope it isn't that one though. I don't want to choose between having my Thunderbolt or my sight!
Mine still does it and I'm using the leak , so I don't think there is a fix in it. If so it doesn't work. Locking the screen seems like a pain but that's the best bet for now.
Sent from my ADR6400L using XDA Premium App
dzigns said:
Here's what I do and it works for me most of the time. When making or receiving a call, once the call is 'connected' I quickly hit the 'home' button so I'm no longer on the 'phone screen' & then the power button which darkens & locks the screen. Even if the proximity sensor allows the screen to light up, the lockscreen is still there and prevents me from muting or hanging up on the other person. It's not a perfect solution since my jaw has managed to unlock the screen & randomly open apps occasionally but it beats hanging up on someone every 5 seconds.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
After trying many ways to work around this problem with the proximity sensor I have found that this is actually works the best .... And I can't thank you enough..... I've grown used to this method and so far its flawless.
Thank you again
Sent from my ADR6400L using XDA App
This is my third device and for 8 days it has been pretty rock solid, Yesterday I had 2 screen freezes and noticed it had been rebooting randomly.(for how long I do not know but I thought at first the app was turning itself off, than learned the device was actually rebooting itself) Today while at a restaurant I lost data and the signal would go in and out. In this same place my Vibrant gets 3-4 bars of 3G consistently. Upon arriving at home I had the same situation but additionally the GPS refused to lock or even see any sats. After rebooting twice it finally straightened out. I only have a couple of days left to decide whether to get a refund or take the chance of getting one that has even more issues or just keep this one and hope for the best. Anyone else have these or issues like them?
Are you running stock? There is a patch that fixes the slow Downs which can cause a reboot.
LG left the device in engineering mode which is why it boots up so fast.
Root and flash the patch, or wait for official gingerbread, or foot and flash CM7 which is doing me good.
LG G2x CM7 2.3.4
http://www.MiiWiiChat.com
http://www.SnapSiteAdmins.com
Yes, my data randomly gets stuck, switching to airplane mode and back fixes it sometimes, otherwise a reboot fixes it.
My GPS randomly dies and gets stuck, usually while navigating, only way I've found to fix that is yet another reboot. Cycling the GPS on and off does nothing.
Also, about once a week, the phone will crater, come back up to "system checking", decide it doesn't like something and do a factory reset! I'm actually scared every time I reboot that it'll come up reset.
Also notice if I make heavy use of the internal SD card, say, 1080p video recording, it'll randomly reboot. Defective memory?
Par for the course until LG figures stuff out. I wish this was like a computer and everything worked when it was expected to work!
Running the dexopt patch, rooted, and nothing else major.
player911 said:
Are you running stock? There is a patch that fixes the slow Downs which can cause a reboot.
LG left the device in engineering mode which is why it boots up so fast.
Root and flash the patch, or wait for official gingerbread, or foot and flash CM7 which is doing me good.
LG G2x CM7 2.3.4
http://www.MiiWiiChat.com
http://www.SnapSiteAdmins.com
Click to expand...
Click to collapse
Yes running stock and applied the patch as soon as it came out. I have not tried cm7 yet. The patch does not seem to do any good for this device.
Lightning Blue said:
Yes, my data randomly gets stuck, switching to airplane mode and back fixes it sometimes, otherwise a reboot fixes it.
My GPS randomly dies and gets stuck, usually while navigating, only way I've found to fix that is yet another reboot. Cycling the GPS on and off does nothing.
Also, about once a week, the phone will crater, come back up to "system checking", decide it doesn't like something and do a factory reset! I'm actually scared every time I reboot that it'll come up reset.
Also notice if I make heavy use of the internal SD card, say, 1080p video recording, it'll randomly reboot. Defective memory?
Par for the course until LG figures stuff out. I wish this was like a computer and everything worked when it was expected to work!
Running the dexopt patch, rooted, and nothing else major.
Click to expand...
Click to collapse
Gosh, sounds like we got the exact same phone!!LOL Almost my situation word for word!!!!!!!!!!!!!!!!!!! Do you really think that software patches will fix all the issues? I would like to believe but am doubtful. I went through the GPS debacle with the Vibrant and it still has not been fixed after almost a year for a lot of people.
As powerful this phone sounds I am hesitant of getting it because of the list of complaints. I think the g2 might be a better choice even though it has an inferior chip
The patch made a big difference with mine. After the patch is successfully applied, it will take longer to boot and won't slow down and laggy after a few hours.
I'm wondering if it was applied correctly? It would have to be applied after every wipe you've done. Thing is you have to remove the X-Factor from the equation. Flash CM7 and see if the problem is persistent or not. If it is, replace the phone. If not, then you owe me $5 cause I called it. There is a weird bug with the stock kernel. We are expecting an updated Kernel with the new Gingerbread rom that is about to be released.
@Jjday7: I wouldn't sweat it. I've been around the block and as far as hardware goes; the G2x is solid. The initial kernel is a little wonky but thank god we have CM7 right? I used my GPS today and had no problem getting a lock and keeping it. Of course I'm on CM7. I also don't have anymore random lockups.
player911 said:
The patch made a big difference with mine. After the patch is successfully applied, it will take longer to boot and won't slow down and laggy after a few hours.
I'm wondering if it was applied correctly? It would have to be applied after every wipe you've done. Thing is you have to remove the X-Factor from the equation. Flash CM7 and see if the problem is persistent or not. If it is, replace the phone. If not, then you owe me $5 cause I called it. There is a weird bug with the stock kernel. We are expecting an updated Kernel with the new Gingerbread rom that is about to be released.
@Jjday7: I wouldn't sweat it. I've been around the block and as far as hardware goes; the G2x is solid. The initial kernel is a little wonky but thank god we have CM7 right? I used my GPS today and had no problem getting a lock and keeping it. Of course I'm on CM7. I also don't have anymore random lockups.
Click to expand...
Click to collapse
I have applied it before and after GB update. I have hesitated flashing cm7 (have a couple of questions) If I do flash it and want to go back to stock or some other rom, would I have to flash a different kernel even with my nanroid? If so what would be the process for that? AS far as GApps I notice that you cannot use the one for tegra. All I have found at the cm7 site is universal which I suppose would be the one to choose. Do you know for sure?I have used cm7 on my nexus one but not on my Vibrant . Any and all help is greatly appreciated.
I also have all the same issues as the OP. Hopefully the update fixes all these issues. Did any of you notice the phone really hot when the reboots and freezes occurred?
Sent from my LG-P999 using XDA App
So where is this patch? My GPS has been non-functional this morning. Usually it just takes a LONG time to lock on. Also, last two days I've been getting the freezing while on a call. Black screen, won't come back, have to remove the battery. Early this morning after taking the phone off the charger was the first time it froze to black screen while not on a call.
Jjday7 said:
As powerful this phone sounds I am hesitant of getting it because of the list of complaints. I think the g2 might be a better choice even though it has an inferior chip
Click to expand...
Click to collapse
To my G2x friends above. Keep swapping phones. Don't give up. I was at my wits end until I swapped out a couple of times. My new phone has no bleed issues and the random crazy stuff has completely stopped.
lilaliend... take it back. get another. It should not do that. It will be nothing but a head ache/heart ache until you do. I get a solid lock within 5 seconds.
Jjday... if you get one, run the heck out of it the first few days to see if all is good. Any issues pop up...swap it.
This is a solid phone that seems to have had some issues with the first run of production. There are many detailed posts on how to fix any minor annoyances. TMobile sold out of them for a reason.
Swap bad behaving phones then read, read, and then read some more. The potential of this phone is awesome. I am a die hard WM guy who has been converted.
So .. I ended up exchanging my g2x in via t-mo customer support since I was out of the window of taking it back to the store (having 4g/wifi toggle issues etc, random reboots). The new phone is by far better, but I am having issues with the GPS still. It will see 10 satellites, all locked on (green via GPS test) but it takes forEVER to lock. When I first took the phone out of the box it locked within seconds inside my house ... should I send this back for another one again?
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
I have three days to change my G2x for the Nexus S.
I need to know whether putting ANY custom ROM/root/whatever can fix every single problem with this phone:
Battery life drain
Software bugs
MOST IMPORTANTLY (why doesn't anyone care/notice?!): NOISY HEADPHONE JACK OUTPUT
Is this problem entirely software, or partly hardware? I have such minimal LCD bleed that its not noticeable.
Please chime in and check my thread on noisy output and take my FIVE SECOND test with your modded device to tell all of us whether it is fixed or not.
nevermind.
Using CM7 + Faux's EXT4 undervolt Kernel + GPS fix pretty much makes this phone perfect for me. I have absolutely no issues at all EXCEPT for screen bleed. That cant really be fixed with software though. Battery life is great. Yesterday I didn't use my phone much but I went OVER 24 hours on one charge. Didn't plug it in once. Woke up this morning and it still had about 15%. Of course I turned off data while I slept though so that probably helped a lot.
voodoo takes care of the headphone jack noise. in fact i've never ever experienced music with low of a noise floor below
adevilfish said:
voodoo takes care of the headphone jack noise. in fact i've never ever experienced music with low of a noise floor below
Click to expand...
Click to collapse
Can you please elaborate and confirm that you noticed the exact same noise as I described (for a second after any sound stops, or during a completely silent track playing?) And voodoo took care of it? So it is software causing the noise and not hardware?
I'm finally at peace with my G2X and it is solid reliable. ****ty battery life but what can you expect.
In my case my phone did have reboots and freeze while charging. I still don't trust having this phone charging overnight because it might crash.
Also went and deleted both Internal/External SD and properly WIPE like 5 times. Flashed CM7 RC1 + Google apps and fixed permissions. I had issues where email syncs failed after 8+ hours but after doing this full clean flush and Wipe, this piece of **** phone finally is reliable.
Its solid and finally enjoying the phone. Just need CM7 out of RC and I'm golden.
However, every time I went to stock I had issues. If you don't plan on Rooting/Flash don't bother with this phone. Its a piece of crap and LG sucks at making ROMS.
I love my phone but I reccimend you get the nexus S. I'm sorry, its just a better phone.
Ps....Please don't ostracise me from this forum lol.
Sent from my LG-P999 using Tapatalk
britishtomquin said:
I love my phone but I reccimend you get the nexus S. I'm sorry, its just a better phone.
Ps....Please don't ostracise me from this forum lol.
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Software-wise, yes. It's a better phone... Hardware-wise, HELL NO!
CM7 with Trinity kernel gets 24 hours of battery and no reboots from my experience.
Sent from my Nexus 5g using XDA Ultimate App
youd be a fool to trade for that phone... yes every problem fixed.. no problems for awhile for me... love my phone..
I have to agree. The G2x is a million time better then the Nexus S. The Nexus doesn't even do 4G.
The Nexus S is last generation, the only competition for the g2x is the htc sensation and the samsung galaxy s2.
Sent from my Nexus 3 using XDA Ultimate App
KingDavid63 said:
youd be a fool to trade for that phone... yes every problem fixed.. no problems for awhile for me... love my phone..
Click to expand...
Click to collapse
Long live the King!
G2x - July baseband/radio, Cm7 Nightlies, Faux OC/uv Kernel, Launcher Pro, Straight Beast Status! No Bugs! Smooth as my ps3 or 360 on gaming... gameloft is making some killer gamez... I love this phone... It's a sense or no sense issue if you ask me... I like both.. My last phone was the htc glacier i gave to my momma, it was a good phone... I wanted a senseless device and im glad i got this one.. not another 6-8 months down the road when the next 1.3+ Ghz batch of phones comes out i might go back to sense, but im completely content where im at right now with the g2x with the games and now netflix... dont get no better.. maybe the sgs2 but that's the most powerful phone in the world as far as buyin out the store... but the sensation.... NO!
k00zk0 said:
Can you please elaborate and confirm that you noticed the exact same noise as I described (for a second after any sound stops, or during a completely silent track playing?) And voodoo took care of it? So it is software causing the noise and not hardware?
Click to expand...
Click to collapse
I've never had a noise issue with the Jack and I use my g2x like an iPod. Battery life sucks but with Google music its been awesome. I've also been using the leaked gb off LG the only thing with that is now I can't seem to root my phone.
Sent from my LG-P999 using XDA App
I don't notice noise. I plug my G2x into my surround and crank it. Sounds like any other device I've owned (ipad2 being one of them)
LG G2x - Miui
www.SnapSiteAdmins.com
www.MiiWiiChat.com
NVfllash cwm and then install or restore rom = root...
So after getting CM7 and Faux's OC/UV/etc/Voodoo kernel I still have noise with the sound. Do I need the Voodoo app to enable a different kind of processing or something? I cleared 3x caches/data, installed .zips: CM7 b89, gapps, and Faux [2.6.32.41] (v0.3.4) before restarting.
This makes the sound even more apparent: Go to a silent place and turn the volume on the phone all the way down to vibrate. Put the speaker at the bottom right into your ear and push volume up once. You'll hear the quiet boop tone and a second of very loud hiss before it cuts out. Wait until the sound disappears after two seconds to notice that it was even there in the first place, before pushing the volume button again. It even turns the amp on when you set it to vibrate and there is no tone played. Two new units fresh out of the box have had this same noise. I can't believe users, especially devs don't notice this or see it as irregular, so I must be doing something wrong with Voodoo, and every unit in Canada is the same hardware-faulty. I've got three hours to swap it for the nexus; a primary use for this phone would be monitoring detailed music, and this is an unacceptable level of noise. Please try this and let me know if it's every unit or just every one in Canada, and if the 3 dollar Voodoo app is necessary to fix it!
k00zk0 said:
So after getting CM7 and Faux's OC/UV/etc/Voodoo kernel I still have noise with the sound. Do I need the Voodoo app to enable a different kind of processing or something? I cleared 3x caches/data, installed .zips: CM7 b89, gapps, and Faux [2.6.32.41] (v0.3.4) before restarting.
This makes the sound even more apparent: Go to a silent place and turn the volume on the phone all the way down to vibrate. Put the speaker at the bottom right into your ear and push volume up once. You'll hear the quiet boop tone and a second of very loud hiss before it cuts out. Two new units fresh out of the box have had this same noise. I can't believe users, especially devs don't notice this or see it as irregular, so I must be doing something wrong with Voodoo, and every unit in Canada is the same hardware-faulty. I've got three hours to swap it for the nexus; a primary use for this phone would be monitoring detailed music, and this is an unacceptable level of noise. Please try this and let me know if it's every unit or just this one, and if the 3 dollar Voodoo app is necessary to fix it!
Click to expand...
Click to collapse
I had never noticed the issue before, but when performing your test I hear it. This isn't a precisely calibrated, professional audio-phile level piece of equipment. For most people, this would not be an issue. If it is for you, then this is likely not the device for you.
ok, been reading, searching, reading, reading, more searching. haven't found an answer. running stock GB 2.3.6, rooted, only difference is i changed the baseband. but i had this issue before that. here is issue:
usually phone works fine. i can hear callers, they hear me just fine. but if i let phone sit idle for a period of time, the speaker quits. if phone sits for hour or so, and i get a call, phone will receive call no problem, but i cannot hear anything. sometimes callers can't hear me. if i shut phone off and turn on again, all is fine. it's like the audio part of phone calls goes to sleep or something.
anyone else have this problem?
maxxman04 said:
ok, been reading, searching, reading, reading, more searching. haven't found an answer. running stock GB 2.3.6, rooted, only difference is i changed the baseband. but i had this issue before that. here is issue:
usually phone works fine. i can hear callers, they hear me just fine. but if i let phone sit idle for a period of time, the speaker quits. if phone sits for hour or so, and i get a call, phone will receive call no problem, but i cannot hear anything. sometimes callers can't hear me. if i shut phone off and turn on again, all is fine. it's like the audio part of phone calls goes to sleep or something.
anyone else have this problem?
Click to expand...
Click to collapse
I've had same thing happen to me on Stock, Embryo 6, CM10, AOKP, PaCMAN, PA... Running latest MIUI.US and so far so good. I'd like to know the reason for this too.
Other threads about this topic:
http://forum.xda-developers.com/showthread.php?t=2164921
http://forum.xda-developers.com/showthread.php?p=39678817
Yup had this happen to me once in awhile after running a ROM for a long time. I just reflash a different radio and its usually good for a few months
Had this issue crop up (hence why I'm here). Was going to re-flash back to 2/26, but after pulling the SIM card rebooting, then putting the SIM card back in (and rebooting), it fixed itself.Guess today's power outage was good for something... (was about to pop the SIM into a different phone when power came back.)