Related
I have done a reasonable amount of searching on this and have not found anything specific to my problem so figured I should post a question.
I have an issue with my Dimaond when it gets hot generally either using Wifi or Phone Data connection that the screen goes out. Basically everything goes to the left side of the phone so if you hit the Task Icon in the top right corner you get the Start Menu. Phone is basically useless at this point and you have to wait for it to cool down. Has happened since day one and is generally worse when using it when charging. I was watching Utube on it the other night 5min video while on AC charge and it went out. I am running Dutty 2.5 Rom and 25.07 radio have tryed 25.08 and 25.05 no difference was happening when the phone had orginal HTC ROM as well. Also will happen on a long call if the screen is on.
Basically feel issue is hardware related and maybe faulty screen still under warrenty so wanted to know peoples opinion on weather I should send back. Problem is will take a couple of weeks and I don't really wnat to wait that long if I can help it. Also assume it would be best to flash standard ROM back, should I do anything with HARDSPL eg should this be changed back as well if I send it back.
And before anyone says it I have tryed searching this topic and have found lots about HOT dimaonds but nothing related to screen going out at the same time :-(
Thanks
I had this issue in my JasJam (Hermes) whre the screen would simply go white after a while of use and I would have to leave it for a while for it to work again.
Unfortunately it sa hardware issue and you should claim a warranty repair on it
I can't see how this could be a software problem so I figured it must be the screen eg hardware related. Would be nice to know if anyone has had the same issue with a dimaond... Seems we may be spending some time apart, just hope it doesn't take long to fix..
I've had the same issue
http://forum.xda-developers.com/showthread.php?t=428976
My first device had been replaced recently (i.e. today) by my network provider (o2) and the new device seems to work without any problems now even if it's "hot".
(i.e. default screen adjustment + creating heat by activating the phone, wlan, bt + recharging it)
I sent an email to HTC regarding the fault and they said it would have to go back for a warrenty repair. I brought it through a resellar so has to go back to HK from NZ so will be away three weeks uurggghhh... Just seems odd I don't have any physical damage on the screen but hte problem has been around since day one as I remember having the problem the first day I got it. Juyst seems to be getting worse and is easily reproduced by usiung utube over wifi gets hot and it is all over. Just wondering if I should put an offical ROM from HTC back on the device before I send it back as I currenty am running Dutty ROM, what do you think....
i put the original rom back on and they still found out the the rom had been flashed, and would not repair on warranty
yep, i also asked about this problem
http://forum.xda-developers.com/showthread.php?t=438733
there are some youtube video's of how the phone behaves
my phone seems to do it less frequently since stopping using panosha's rom
im using alpha zero 7 at the moment..
i've also noticed that it isnt necessarily a heat issue, my phone does it completely at random
yesterday i found though, that when the phone did the alignment issue, i gave it a good shake.. and hey.. its all aligned again?!
maybe it was just a fluke, it hasnt freaked out since..
holding thumbs
Hey,
I also have the same screen problem, but my Alignment goes to right.
If I press on the left side, a press on the right side is recognized.
Good to know that Im not the only one with this problem.
greets doena
I got my phone back a week ago replaced the screen has been away for over two months, complete disaster, anyway all sorted now and I have not had the problem since....
I had this exact same issue (out of the box).
It was a hardware fault and I exchanged it for another one.
Haven't had any problems since.
Minus-1 said:
I had this exact same issue (out of the box).
It was a hardware fault and I exchanged it for another one.
Haven't had any problems since.
Click to expand...
Click to collapse
Hardware's fault ? Most likely not. I will give u an example of why I think it was software related. My device ran hot as well but I simply switched roms and now it's the complete opposite. Your most recent device most likely come with a different Rom in the phone.
I don't know what caused this.
I got my G1 today. It worked for probably 2-3 hours perfectly fine.
I had an app freeze (either Barcode Scanner or Lock 2.0) and had to do a full hard reset.
Now, whenever the phones screen darkens or I put it to sleep manually, it WILL NOT come back up.
I have factory reset three times now to try and get this to work.
When the screen is black, all buttons on the phone still light up and so does the LED indicator up top. I had my phone set to use a locking pattern screen at one point during one reset to test out and when the screen went black, I was still able to try and log in by doing my pattern. It unlocked, but still showed nothing on the screen.
Please help!
I've tried:
Turning Wi-Fi off
Turning 3g Off
Disclaimer: Yes, I've searched. I can find other users with the same problem but none of them seem to have a solution.
Phone is NOT ROOTED and has the factory ROM.
Update 1: Update: It only freezes/blacks out when I try to wake the phone from one of the front key buttons.
If I'm sliding to unlock, it seems to be fine.... (but if I've already tried to open from the front it doesnt)
Update 2: If I mash all the buttons in random orders for about a minute or two it seems to come back. Anyone have any idea?
Update 3: I'm thinking this has to be an issue with none of the buttons waking the phone up when closed. If I lock the phone with the "END" key, and then click the front "END" Key again, nothing happens. If I slide the phone open, and click it twice - the phone wakes up.
Update 4: Confirmed update 3. Phone will not unlock via front keys unless it's slid open (or open enough to trigger).
I would really, really appreciate help with this.
Hate to bump this, but I've added some detail on the top and bottom. Have to leave for work, hopefully someone might have an idea by the time I get back.
Well you can try to reload the factory rom or root it and try a custom rom and see if the problem still exist. If it is still happening then it would be a hardware problem and need to be sent in. And yes you will still be covered under warranty with HTC since the phone is still less than a year old.
I had a problem with exactly the same symptoms. It turned out that the SD card was cocked-up so home, core, and some other process would hang trying to read it and the phone would not wake-up the screen any more.
Did you try removing the SD card and seeing if that helps?
Karolis said:
I had a problem with exactly the same symptoms. It turned out that the SD card was cocked-up so home, core, and some other process would hang trying to read it and the phone would not wake-up the screen any more.
Did you try removing the SD card and seeing if that helps?
Click to expand...
Click to collapse
Removed the SD card and rebooted the phone.
No change ( still acts the same way ).
Did you factory reset after or was it an instant change?
I don't mind losing data to fix this.
supremeteam256 said:
Well you can try to reload the factory rom or root it and try a custom rom and see if the problem still exist. If it is still happening then it would be a hardware problem and need to be sent in. And yes you will still be covered under warranty with HTC since the phone is still less than a year old.
Click to expand...
Click to collapse
Wouldn't I have to root to reload the factory rom? Is there a rooting tutorial based just on that?
zeabrid said:
Wouldn't I have to root to reload the factory rom? Is there a rooting tutorial based just on that?
Click to expand...
Click to collapse
If you use the official update you don't have to have root. There are some links on here. I'll see if I can find it for you.
https://android.clients.google.com/updates/signed-gfh-CRB43-from-CRB21.c88b03d2.zip
That should be it, but can't confirm since I'm on my work computer.
Some thoughts--may be useful, or not:
Mine was doing that too, but it was caused because I dunked mine underwater during an urban exploring mission. I dried it out, replaced the LCD screen, and everything worked until it would go to sleep. Then I had to do a variety of button mashes and opening the keyboard to get it to come back to life. Sometimes it just wouldn't come back. The problem grew worse over time.
If wiping and reflashing (no need to use a stock ROM) gets you nowhere, then I would suspect a deeper hardware issue. I see you bought it used, can you contact the seller?
If you want to check for water damage, take out the battery and look at the tiny circular sticker in the battery chamber--if it is not white, it has been water damaged. (And the warranty will not be honored.)
Other Lesson: No urban exploring with G1s.
The link didn't work, btw.
derfolo said:
Some thoughts--may be useful, or not:
Mine was doing that too, but it was caused because I dunked mine underwater during an urban exploring mission. I dried it out, replaced the LCD screen, and everything worked until it would go to sleep. Then I had to do a variety of button mashes and opening the keyboard to get it to come back to life. Sometimes it just wouldn't come back. The problem grew worse over time.
If wiping and reflashing (no need to use a stock ROM) gets you nowhere, then I would suspect a deeper hardware issue. I see you bought it used, can you contact the seller?
If you want to check for water damage, take out the battery and look at the tiny circular sticker in the battery chamber--if it is not white, it has been water damaged. (And the warranty will not be honored.)
Other Lesson: No urban exploring with G1s.
Click to expand...
Click to collapse
Zero water damage.
That's great news zeabrid! In that case, I agree with an earlier poster--you should be covered by warranty. Wipe and flash a good rooted rom, and if that doesn't work, revert to stock and demand a new phone.
derfolo said:
That's great news zeabrid! In that case, I agree with an earlier poster--you should be covered by warranty. Wipe and flash a good rooted rom, and if that doesn't work, revert to stock and demand a new phone.
Click to expand...
Click to collapse
Do you have a link to a guide that teaches how to do this (with the stock rom)? I can only see a few that're spread out.
I'm not entirely sure my phone can boot into safe mode/disk mode, so we'll see about that.
Another update: When I boot into safe mode, the same problem exists.
Edit: Just emailed HTC.
This can officially no longer be considered a software issue.
I just rooted and installed a standard ROM. Same issue.
It happens all the way at boot now, just realized this.
HTC emailed me back and told me to call them directly. Will do that tomorrow.
if I find a solution I'll post it immediately.
Alright, my phone is officially ****ed.
Restored back to the original rom.
New problem now: When I close the screen, the backlight goes out and doesn't come back on. (I can still barely see everything, but there's no light).
Calling HTC today.
Edit: Called T-Mo support. They suggested deleting programs to free up space (I only have 2 downloaded and to reset (already done)
=(
Edit2: Called and placed a RMA with HTC after talking to two of their customer support reps. Thankfully, they forwarded me up the support tier after only about a minute with each person when they realized I had already tried all other steps.
The RMA process was surprisingly easy. I have everything set up, and when I get paid (tomorrow) I'm going to ship the phone out. I was given an estimation of 7-10 business days for full repair and return shipping (which sounds great in my opinion - I've never sent anything in for warranty work before).
I'll update you guys once I hear from their repair team on whether or not I'm going to be covered under warranty (I told them that the phone was a gift to me), and if not what the cost is going to be. Like I said earlier in the thread, all water damage indicators are clear and I have unrooted my phone, so I should be covered hopefully.
Thanks to anyone who posted in this thread.
zeabrid said:
Alright, my phone is officially ****ed.
Restored back to the original rom.
New problem now: When I close the screen, the backlight goes out and doesn't come back on. (I can still barely see everything, but there's no light).
Calling HTC today.
Edit: Called T-Mo support. They suggested deleting programs to free up space (I only have 2 downloaded and to reset (already done)
=(
Edit2: Called and placed a RMA with HTC after talking to two of their customer support reps. Thankfully, they forwarded me up the support tier after only about a minute with each person when they realized I had already tried all other steps.
The RMA process was surprisingly easy. I have everything set up, and when I get paid (tomorrow) I'm going to ship the phone out. I was given an estimation of 7-10 business days for full repair and return shipping (which sounds great in my opinion - I've never sent anything in for warranty work before).
I'll update you guys once I hear from their repair team on whether or not I'm going to be covered under warranty (I told them that the phone was a gift to me), and if not what the cost is going to be. Like I said earlier in the thread, all water damage indicators are clear and I have unrooted my phone, so I should be covered hopefully.
Thanks to anyone who posted in this thread.
Click to expand...
Click to collapse
Yea it defitenly sounds like a hardware issue and needs to be fixed. Glad your getting it fixed and you'll be covered no problem.
Do you know if they charge return shipping if it's covered under warranty? I have to pay my own shipping there, and they had me put a credit card down on file in case I either bail when its already there or they need to charge for repair.
zeabrid said:
Do you know if they charge return shipping if it's covered under warranty? I have to pay my own shipping there, and they had me put a credit card down on file in case I either bail when its already there or they need to charge for repair.
Click to expand...
Click to collapse
To be honest I don't know the answer but would like to say they would pay for it. But they would have to let you know of the charge before they apply a charge to a credit card.
wow its weird cause im just having a similiar issue now.. in landscape mode.. phone and back light work perfectly. but one i close the screen everything goes virtually blank, everything is running perfectly just the screen light wont turn on..
will try some of your previous methods.. hopefully it works on mine..=/
thanks, for the info zeabrid
So the phone (XT860 Bell) has problems when I unlock it the screen stays black. The phone works though cause when someone calls I can still pick up as I know somewhat where the green button is. But for the rest I can't do anything.
The only way to get the phone back is to remove the battery and restart the phone. Then it works again.
Anyone else had this problem?
have you tried hard resetting it?
No will do so. But before doing that I thought maybe there is some simple solution.
After the update to 2.3.6 things went all a bit wrong I think.
If you got this after the update, I am quite confident data wipe will solve your problem. You can try wiping cache only first - this way you won't lose your configuration and might solve the problem. The update supposedly wipes cache, but maybe that didn't work properly while you were updating. Enter stock recovery and give it a try.
Hey thanks for the help. But just did a reset. Not sure what went wrong when I did the update. Did wipe. Annnnyways. Right now it's stable. Let's see if it stays like this.
Ok sadly the reset didn't fix it. It took a whole day to go black again but still happened.
Any other solutions? I am scared that it's a hardware failure...but let's hope not cause I am in Holland.
I have the droid 3 and the same exact thing is happening to me. Sorry to tell you this but it has to deal wit the connector between the keyboard and screen. I've taken mine to get checked by a "phone doctor" and they told me that. I will tell you this now ,since it is still in the early stages, it's going to get worse to the point that it will stay black. Get it fixed by a techy or get a replacement soon. Mine reached it's point today and I am going to need to get it fixed. Hope it helps.
Johnny2293 said:
I have the droid 3 and the same exact thing is happening to me. Sorry to tell you this but it has to deal wit the connector between the keyboard and screen. I've taken mine to get checked by a "phone doctor" and they told me that. I will tell you this now ,since it is still in the early stages, it's going to get worse to the point that it will stay black. Get it fixed by a techy or get a replacement soon. Mine reached it's point today and I am going to need to get it fixed. Hope it helps.
Click to expand...
Click to collapse
Doesn't sound good man :-(......
Though it happened a lot the passed days since the reset ( knock on wood) only once. Do wonder why it happens less now.
Yea you can reset all you want it's going to go blank. I had to right the dial pad numbers with marker on the screen just to make calls. I say get it fixed or replaced soon
I've got the same issue here. I know the thread is old, but I'm from the Netherlands (just like eezdva) and would like to know how to repair this.
lucaspr said:
I've got the same issue here. I know the thread is old, but I'm from the Netherlands (just like eezdva) and would like to know how to repair this.
Click to expand...
Click to collapse
If you can't take it back and want to try to fix it yourself you need to search for a droid 3 flex cable. The one you want has the front facing camera, front sensors and earpiece speaker on it. Then head on over to ifixit for a teardown guide (sorry no repair manual yet, I plan on working on one).
I have to add that taking this phone apart to replace this part is no small feat, and it would probably be better finding a phone doctor to do it for you, or just getting a new phone.
When you buy the part, request an OEM part, I have been sent cables where the front facing camera displays sideways, or doesn't work at all. Most also don't come with the front button deflector, and that has to be transferred from the old cable.
Hope this helps
Ok . Well I don't really know what the problem is. But it went away. Actually it started I think after applying the update . I got myself another external sdcard . At a certain moment I decided to remove it and things cooled down. It now actually never happens anymore.
Well I gues you're lucky!
My screen sometimes starts all scrambled and the phone doesn't power on. Sliding the screen a couple of time sometimes helpes, but most of the time I don't really know howto get the phone working again. I think it's more stable when I leave the phone 'slided out' (don't know the right word now).
And I searched Motorolas website and found 2 reparing companies in the Netherlands. They both are authorized by Motorola, as of such I think this repair will be in warranty.
I do have to send it for repair. I don't want to take it apart because of what bitz_dv said. I'll let you know!
No Fix
When I was gone on a short holiday my college got a call from the 'authorized' motorola repair center. They can't fix my phone. I need to pay 11 euro to get it back and that's it. I tried calling them but there was no answer.
I sended my phone in on 22 may 2012 and now they decided they can't repair it. I spoke to Ted from Negri Electronics who told me to get in touch with Motorola as my warranty is still valid.
I'm a little confused, where should I go if an official repair center can't fix my phone but do tell me the repair is within warranty..
What can I do? Besides ordering the parts and take the phone apart myself..
I started my search for the flex cable... I did repair a N97 once, within the warranty period and later on sended it in and they repaired it under warranty....
Is this the cable I'm searching for:
http://www.globaldirectparts.com/Motorola-Droid-3-XT862-Motherboard-Flex-Ribbon-p/mot1040660.htm
I am from Netherlands, and have the same problem with the screen, looks like many users from Netherlands do.. coincidence?
When i jst slide out the keyboard , a little bit is enough, and the screen goes black ( black screen of death ) it doesnt power on with power button.
I looked for a flex cable at ebay, and it surprised me , that cable is also doing the front camera, and speaker... My front camera wasnt working too, and speaker made strange sounds many times, so it could be that cable, but not sure.
Check my thread, i have also uploaded a video to make it more clear
http://forum.xda-developers.com/showthread.php?t=1955892
Hey guys,
Does anybody who ever or being suffered from the call issue like hearing nothing from the receiver during phone calls??Sometimes it work,but sometimes it doesn't!!And the speaker works in most of the cases,whereas sometimes it also breaks down liked the receiver.Moreover,I can hear some cracks from the receiver in some cases.
I am totally freaked out because I am sure that the receiver is good (no problems with skype and wechat,and I also have checked it by using "*#0*#" when the situation happens) and it seems impossible to be solved after wiping and flashing different firmware(both by cwm and odin),and so do the modems.
Any solutions or suggestions will be totally appreciated!!!:crying:
Edit: I've tried to flash the Perseus and disable the dac direct,it seems that the cases happen less frequent.
Update:
I found sth strange about the call issue by chance: when I lock the screen maybe for more than 5 mins,then wake it up and make a phone call soon,the receiver can't work every times.However, when I put it into use(light the screen) for more than 3 or 4 mins,and then the receiver works again during calls.
What I want to say is: maybe there are sth wrong with the cpu setting or the power management?
I actually got the static phone call issue today (first time) after installing ripper rom yesterday but im sure it was just a once off issue because I could not reproduce the same result
Change roms ect but if the issue persists then your only option is to jump on triangleaway, stock firmware and dial away to Samsung or your telco
Sent from my GT-I9305 using xda premium
takooo said:
Hey guys,
Does anybody who ever or being suffered from the call issue like hearing nothing from the receiver during phone calls??Sometimes it work,but sometimes it doesn't!!And the speaker works in most of the cases,whereas sometimes it also breaks down liked the receiver.Moreover,I can hear some cracks from the receiver in some cases.
I am totally freaked out because I am sure that the receiver is good (no problems with skype and wechat,and I also have checked it by using "*#0*#" when the situation happens) and it seems impossible to be solved after wiping and flashing different framekworks(both by cwm and odin),and so do the modems.
Any solutions or suggestions will be totally appreciated!!!:crying:
Edit: I've tried to flash the Perseus and disable the dac direct,it seems that the cases happen less frequent.
Click to expand...
Click to collapse
It's a hardware issue. I had the same thing with my i9300; You have to take it to a repair center for motherboard replacement. It's the audio chip that goes bad (on the i9300 the component number is U604). Happened to me twice, with both my new and replacement motherboard, but it happened to go away for me the 2nd time.
Product F(RED) said:
It's a hardware issue. I had the same thing with my i9300; You have to take it to a repair center for motherboard replacement. It's the audio chip that goes bad (on the i9300 the component number is U604). Happened to me twice, with both my new and replacement motherboard, but it happened to go away for me the 2nd time.
Click to expand...
Click to collapse
Thanks!! I've saw your thread and now I have nothing to do with it except considering repair.If the issue happens again,i will probably send it back to the company which I bought this phone.
BTW,are you sure both your phones are now preforming good during the calls?You have said that the issue happened again a month later after it got the first repaired? If you have some news with your phones,please notice me~~~
Magik_Breezy said:
I actually got the static phone call issue today (first time) after installing ripper rom yesterday but im sure it was just a once off issue because I could not reproduce the same result
Change roms ect but if the issue persists then your only option is to jump on triangleaway, stock firmware and dial away to Samsung or your telco
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Yep!! Last time I had flashed the ripper rom and then I found this issue.First I thought it was the problems that come from the rom,but after several tries then I thought it probably due to the hardware issue that I cant solve....
Anyway,thanks for your suggestions!!
takooo said:
Thanks!! I've saw your thread and now I have nothing to do with it except considering repair.If the issue happens again,i will probably send it back to the company which I bought this phone.
BTW,are you sure both your phones are now preforming good during the calls?You have said that the issue happened again a month later after it got the first repaired? If you have some news with your phones,please notice me~~~
Click to expand...
Click to collapse
I've had the phone for about 6 months total. The first time the issue happened, I had owned the phone for 3 months. The phone came from a company in Germany, and I live in the US (purchased through Amazon). The i9300 is not sold or repaired in the US (because the US version has different components), so I had to ship it to the seller, to ship to a repair center on my behalf. The phone itself carries a 2 year warranty, which is good because in the US phones only have a 1 year warranty. However, it cost me $80 to ship the device to Germany, and about a month total time before I got it back.
Anyways, I got a paper back in German that detailed the issue and said they had to replace a component, which turned out to be the entire board. They also copied over the original IMEI number to the new board. The second time this issue started happening was literally on New Year's Day (on 12:00 AM EXACTLY). I tried to call a car service place for my girlfriend and her family, and my phone had no audio going in or out for calls. My phone was working perfectly before that and I hadn't flashed anything new for over a month (I was on Omega ROM 35 with Siyah kernel 1.8.6). Immediately I knew the issue had come back again. For whatever reason, the issue went away maybe 4 days later and hasn't come back. I flashed the latest modem (for the i9300 it's XXELLA), but I'm still on Omega ROM v36. I don't think me flashing anything fixed anything; more likely that it went away on its own since it's 100% a hardware issue.
To clarify, sometimes an incorrect modem for your region CAN cause there to be issues with calls, but if it happens out of the blue, and flashing anything doesn't help, it's a hardware issue. Take it to a Samsung repair center for sure. The i9300 and i9305 use the same parts except for the modem and a few other things. Other than that they're the same exact device.
Product F(RED) said:
I've had the phone for about 6 months total. The first time the issue happened, I had owned the phone for 3 months. The phone came from a company in Germany, and I live in the US (purchased through Amazon). The i9300 is not sold or repaired in the US (because the US version has different components), so I had to ship it to the seller, to ship to a repair center on my behalf. The phone itself carries a 2 year warranty, which is good because in the US phones only have a 1 year warranty. However, it cost me $80 to ship the device to Germany, and about a month total time before I got it back.
Anyways, I got a paper back in German that detailed the issue and said they had to replace a component, which turned out to be the entire board. They also copied over the original IMEI number to the new board. The second time this issue started happening was literally on New Year's Day (on 12:00 AM EXACTLY). I tried to call a car service place for my girlfriend and her family, and my phone had no audio going in or out for calls. My phone was working perfectly before that and I hadn't flashed anything new for over a month (I was on Omega ROM 35 with Siyah kernel 1.8.6). Immediately I knew the issue had come back again. For whatever reason, the issue went away maybe 4 days later and hasn't come back. I flashed the latest modem (for the i9300 it's XXELLA), but I'm still on Omega ROM v36. I don't think me flashing anything fixed anything; more likely that it went away on its own since it's 100% a hardware issue.
To clarify, sometimes an incorrect modem for your region CAN cause there to be issues with calls, but if it happens out of the blue, and flashing anything doesn't help, it's a hardware issue. Take it to a Samsung repair center for sure. The i9300 and i9305 use the same parts except for the modem and a few other things. Other than that they're the same exact device.
Click to expand...
Click to collapse
Ok,thanks a lot for telling me these!!! I've sent a email to the customer service and hope to get respond soon.Anything news i will update it.
So, fist time post.
Anyway, a friend of mine gave me his Flex the other day. He was upset because he couldn't get the sound/audio to work and no one could hear him on his end, showing his mic wasn't working (first time this has happened). After tinkering around for a bit (cleaning over and over), trying everything I could, even downgrading it from 4.4.2 to 4.2.2 to see if it was a software problem. Still nothing. Yet, when a headset or just normal headphones are plugged in everything works fine.
So, after all of that we took it in and they said it wasn't a hardware problem, but they couldn't find a solution and they couldn't replace the handset with his warranty already expired. So, I was hoping there was someone here who could help me. I was thinking maybe if there was a software problem I didn't catch if installing a custom rom on it would help. I was hoping to hopefully get some insight before going to that.
Also, sorry if this is in the wrong section, still new here.
There are no "custom" per say ROMs besides the cm11 one Playfulgod and I have posted in the dev section. If you're on 4.2.2 download Playfulgod's cm11. But it doesn't stay booted and there is no data. Download mine ,which is only Playfulgod's cm that I've modified to boot with 4.4, and the is no sound but it has data and stable boot. I don't suggest either one as your fix though. If you flash the stock 4.2.2 or the stock 4.4.2 software to it and there still is no sound except through the headphone jack then I can't imagine it not being a hardware issue. I mean it pretty much has to be a hardware issue.
And besides the kats at these stores selling you the phones or answering your questions, stereotypically no smarter about the devices than any other 20 year old that has googled and memorized the specs of the phones. They know specs and sales pitches. Other wise they have to revert to the computer and go through a series of elimination questions to diagnose your issue. Ive even had to show one rep how to use lg PC suite to flash his g2 back to stock. And that's the standard issue software that we all have.
My best guess on your issue is the device could have been dropped or damaged in some way that has loosened or broken a connection or part inside rendering the speaker useless. But that's my opinion.
Well I don't think it's been dropped. At least he said he didn't drop it. After pulling it apart I made sure everything was in the right place and nothing was shorted out or disconnected. So I'll probably send it into a repair shop to see if they can do anything with it. Though a headset would probably just be the better way to go, it's just an inconvenience.
Notabelic said:
Well I don't think it's been dropped. At least he said he didn't drop it. After pulling it apart I made sure everything was in the right place and nothing was shorted out or disconnected. So I'll probably send it into a repair shop to see if they can do anything with it. Though a headset would probably just be the better way to go, it's just an inconvenience.
Click to expand...
Click to collapse
Absolutely. I would hate to have to through in my ear buds every time I had to answer a call
Well after installing Master Volume Control, I have been able to test that the speaker does in fact work. But no sounds of any kind aside from voice call, work, the normal beep you get when using the volume rockers. This is starting to drive me crazy.
might have solution
Just received my refurbished flex phone, realized no sound from speaker. Popped the back off a couple times, suddenly I hear sound! The cable over the battery when lifted and remove the crease caused by shape of battery removed, speaker now works! I hope this helps you. Best of luck.
Notabelic said:
So, fist time post.
Anyway, a friend of mine gave me his Flex the other day. He was upset because he couldn't get the sound/audio to work and no one could hear him on his end, showing his mic wasn't working (first time this has happened). After tinkering around for a bit (cleaning over and over), trying everything I could, even downgrading it from 4.4.2 to 4.2.2 to see if it was a software problem. Still nothing. Yet, when a headset or just normal headphones are plugged in everything works fine.
So, after all of that we took it in and they said it wasn't a hardware problem, but they couldn't find a solution and they couldn't replace the handset with his warranty already expired. So, I was hoping there was someone here who could help me. I was thinking maybe if there was a software problem I didn't catch if installing a custom rom on it would help. I was hoping to hopefully get some insight before going to that.
Also, sorry if this is in the wrong section, still new here.
Click to expand...
Click to collapse