So my main issue right now is no sound whatsoever unless I use a wired headset (earbuds etc).
No sound through speaker. Any changes made in options to troubleshoot have failed.
Also, I have no camera app at all. It's like it never existed for this phone.
I'd be okay with it, simply because I finally got the phone up and running again after a battery and mid-frame assembly replacement, but I need sound and camera. Especially the camera due to my banking app.
My Setup
twrp-3.2.1-0-shamu
RR-N-Neo-v5.8.5-20180119-shamu-Unofficial - Android N 7.1.2
open_gapps-arm-7.1-mini-20180122
Magisk 15.3 (from official XDA thread)
*optionally - Viper4android 2.5.0.5
So the two main problems are no sound at all unless I have headphones in.
No camera app or anything
I will add, I can access the non-existent camera through the gallery app included in that RR Neo build, but it FC's immediately and continually.
I've done every wipe imaginable minus a factory image flash of the last Nougat build for our phones.
Complete wipes including: in TWRP the "yes" option on Format Data.
Factory Reset followed by Dalvik, Cache, System, and Data wipes.
Essentially everything I've been doing without issue for the few years I've owned this phone.
If anymore info is needed I'm willing to provide it, sincerely hope someone can help me diagnose or possibly fix this phone.
Seriously, thanks for any help provided.
Just help me get away from this iPhone 5 loaner
ProjectAlly said:
So my main issue right now is no sound whatsoever unless I use a wired headset (earbuds etc).
No sound through speaker. Any changes made in options to troubleshoot have failed.
I finally got the phone up and running again after a battery and mid-frame assembly replacement
Click to expand...
Click to collapse
The above concerns me...
Was the sound working prior to the replacement?
Sent from my Nexus 6 using Tapatalk
Neo said:
The above concerns me...
Was the sound working prior to the replacement?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yep, was working perfectly before replacement and for about a day or so after.
Only issue I had sound-wise was with static-y audio when headphones or aux cable was plugged in for my car's head unit.
Not sure what happened. I did notice on the mid-frame assembly I bought, there was no earphone speaker, it's the module next to the camera. So today I added it to the new mid-frame and no dice...also to be sure I used my old headphone jack on the old frame, and no change.
Could it be the battery isn't strong enough?
EDIT:
The battery I bought: https://www.amazon.com/gp/product/B01DJZMJH4/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1
Midframe: https://www.fixez.com/motorola-nexus-6-midframe-and-bezel-midnight-blue
ProjectAlly said:
Yep, was working perfectly before replacement and for about a day or so after.
Only issue I had sound-wise was with static-y audio when headphones or aux cable was plugged in for my car's head unit.
Not sure what happened. I did notice on the mid-frame assembly I bought, there was no earphone speaker, it's the module next to the camera. So today I added it to the new mid-frame and no dice...also to be sure I used my old headphone jack on the old frame, and no change.
Could it be the battery isn't strong enough?
Click to expand...
Click to collapse
No, wouldn't be the battery.
Ok so, that speaker you added to the mid frame by the camera on top, has two pins. Those two pins need to be facing towards the camera (they touch two metal contacts). If those pins aren't touching those contacts, it won't work. Likewise, the speaker on the bottom that is attached to the motherboard, has two tiny pins (one on each side) that make contact to two metal plates on the mid frame. Check and make sure these things are making contact.
Sent from my Nexus 6 using Tapatalk
So I just checked the contacts, and that speaker is seated properly.
No sound.
It's killing me right now. This battery is doing fantastic, but I can't use the phone.
Still no camera either. Just doesn't show up in app drawer, on launcher or anywhere but gallery.
Starting to think the phone might be a goner. Which would be a shame...
ProjectAlly said:
So I just checked the contacts, and that speaker is seated properly.
No sound.
It's killing me right now. This battery is doing fantastic, but I can't use the phone.
Still no camera either. Just doesn't show up in app drawer, on launcher or anywhere but gallery.
Starting to think the phone might be a goner. Which would be a shame...
Click to expand...
Click to collapse
That's a shame man. Sounds like something was either damaged during the replacement or some ribbon cables may not have been seated all the way, idk. If it were me, I'd do a complete tear down and put it all back together and hope for the best.
Sent from my Nexus 6 using Tapatalk
UPDATE:
@Neo
I took your suggestion, tore everything apart, at least on the frame, turns out the frame wasn't making good contact with the LCD panel. Once that was established, I put everything together again and thankfully had one of the last factory images released from Google, re-flashed stock with the toolkit, and once it booted up, camera worked and so did the sound! But only out of one speaker.
Checked the frame again, turns out the new one had that clear plastic blue, sticky tape looking stuff, moved that and bottom speaker worked too.
TL;DR
Problem solved, turns out I wasn't thorough enough with making sure all ribbons and modules were making contact with the frame and LCD panel. Oh and flashing a factory image fixed all software related problems (no camera app showing up or working etc).
Happy camper for now!
ProjectAlly said:
UPDATE:
@Neo
I took your suggestion, tore everything apart, at least on the frame, turns out the frame wasn't making good contact with the LCD panel. Once that was established, I put everything together again and thankfully had one of the last factory images released from Google, re-flashed stock with the toolkit, and once it booted up, camera worked and so did the sound! But only out of one speaker.
Checked the frame again, turns out the new one had that clear plastic blue, sticky tape looking stuff, moved that and bottom speaker worked too.
TL;DR
Problem solved, turns out I wasn't thorough enough with making sure all ribbons and modules were making contact with the frame and LCD panel. Oh and flashing a factory image fixed all software related problems (no camera app showing up or working etc).
Happy camper for now!
Click to expand...
Click to collapse
That was the only thing I could think of
Improper contact with the pins. If you had done all this and it still didn't work, I'd have been at a loss lol. Glad you're up and running.
Neo said:
That was the only thing I could think of
Improper contact with the pins. If you had done all this and it still didn't work, I'd have been at a loss lol. Glad you're up and running.
Click to expand...
Click to collapse
Neo the great to the rescue!! [emoji108]
Related
Hi i'm using a rooted htc one and people often complain they cant hear me during calls. I was wondering if there was anyway I could enhance the microphone so that my voice is louder. I'm using android 4.1.2 and sense 5. The case i'm using has a hole on the back in the top right corner and on the bottom to the left of the usb adapter jack where I think the microphone(s) are. I looked at other threads but I was having this problem before I rooted my htc one and was hoping that now it has been rooted there was some sort of hiden control I can use to turn up the michrophone setting. Thanks
bump
If it wasn't working right before you rooted it, then it means it is a hardware problem. I don't think this is necessarily a sensitivity issue. I think it has to do with the noise canceling.
Talk to HTC or whatever carrier you have.
Also, make sure to hide all signs of root!
Hej layzz, there is a thread with a similar problem: http://forum.xda-developers.com/showthread.php?t=2380867
Just as I mentioned there, it could be the hole at the underside of your case being just way to small, or (as I realized just recently) a very special hardware problem (so to say). During calls I had always covered the mic with my little finger, no wonder no one understood me.
Give it a shot
Xayden said:
Hej layzz, there is a thread with a similar problem: http://forum.xda-developers.com/showthread.php?t=2380867
Just as I mentioned there, it could be the hole at the underside of your case being just way to small, or (as I realized just recently) a very special hardware problem (so to say). During calls I had always covered the mic with my little finger, no wonder no one understood me.
Give it a shot
Click to expand...
Click to collapse
i had a similar problem too, i upgraded to 4.2.2 on 2.24 (ARHD) and now its fixed.
the proximity sensor is also fixed
Muhammad.Muayad said:
i had a similar problem too, i upgraded to 4.2.2 on 2.24 (ARHD) and now its fixed.
the proximity sensor is also fixed
Click to expand...
Click to collapse
The mic hole at the bottom of the device is clearly visible. Would you mind posting a link to that rom please?
layzz said:
The mic hole at the bottom of the device is clearly visible. Would you mind posting a link to that rom please?
Click to expand...
Click to collapse
forum.xda-developers.com/showthread.php?t=2183023
This ROM is based on 4.2.2 on 2.24 all my problems are pretty much fixed
I have this very same problem on my brand new stock device. I created a thread for the same problem. I found that the earpiece quality was brilliant but again people could not hear me or said I was very quite. I experimented with case on and case of and calls to different phones and 9/10 times the problem was there. I then decided to install android revolution hd to see if there was a problem with the stock rim for some reason. Sadly this didn't work. I then turned my attention to the lower microphone. Now I am not suggestion you do this by any means however in my case I felt I had nothing to lose as I was going to have to send the phone to HTC to get fixed if I could not sort it myself.
I got the small sim removal tool and stuck it into the mic hole in a bid to try and open the hole up abit as it seemed very small and I wondered also if it was blocked. I did this a little at a time and then tried calling people to see if there was any change. Instantly there was an improvement. However, now it seemed like 5\10 calls were low. So, I tried the same again.
I now have not had the problem in the last 15 or so calls I have made however what I have noticed is that now for what ever reason when I'm in calls the person on the other end sounds a little distorted through the earpiece. Don't know why this should be and maybe a completely unrelated problem or something linked to installing the other rom. Either way at least people can hear me now.
Sent from my HTC One using xda premium
Thanks everyone. The problem seems to be fixed after installing that custom rom
Forum, I have HTC One M8. This morning the following message started showing up: duo camera is blocked, please make sure all lenses are uncovered.
Does anyone have any idea?
PS. All lenses are uncovered and thoroughly cleaned.
Thank you
Doesn't look like your case is the culprit. Having said that, have you tried using the camera without the case? Only time I've encountered this issue is when my finger was in the way of the duo camera itself.
Magnum_Enforcer said:
Doesn't look like your case is the culprit. Having said that, have you tried using the camera without the case? Only time I've encountered this issue is when my finger was in the way of the duo camera itself.
Click to expand...
Click to collapse
I have identified the problem... defective camera itself. When i pick up my phone, and shake it gently, there is a rattle sound thats coming from the camera. In addition, the top camera (under the lens) rotates every time i jog or shake the phone. So in short, its defective camera, but since i do not have the coverage, im SOL for now.
Thank you
I broke my screen last week , it fell and was damaged, and the camera stopped working too. I fixed the screen, but the camera is still offline, tried to change the rom, but no changes., i am getting the "Error, camera not available". When i click on camera icon, it shows a black screen after some delay and then right away an error message pops up with "Error! Camera not available". When i load this from any application, such as snapchat or instagram, it crashes the application. Has anyone dealt with such issue before? Give me some hope, what could be wrong.
The camera was not working even before i replaced the screen. (The screen repair was good, i made sure nothing was touched that should'nt be touched.
The phone's proximity sensor seems to be a bit off too, the phone also vibrates ( like it received a text message) randomly.
Unrelated issue: the screen i install has a round ring that appears if i press the screen to hard at a certain spot. it's not too annoying but it is there.
Broken flat cable, broken camera. Physical damage.
Sent from my C6903 using XDA Free mobile app
electrash said:
Broken flat cable, broken camera. Physical damage.
Sent from my C6903 using XDA Free mobile app
Click to expand...
Click to collapse
Ah! what do you think , can it be saved DIY?
marksee said:
Ah! what do you think , can it be saved DIY?
Click to expand...
Click to collapse
Well i didnt opet Z1 before, so i dont know if you can only replace flat cable (if that is problem) or you must replace whole camera module.
Best bet is to give to service center, probably they will put new module on it, and its best in my opinion.
electrash said:
Well i didnt opet Z1 before, so i dont know if you can only replace flat cable (if that is problem) or you must replace whole camera module.
Best bet is to give to service center, probably they will put new module on it, and its best in my opinion.
Click to expand...
Click to collapse
Most likely put a new module in there as the modules are machine made are probably solid.
Status Update
So i opened the phone again, and seems like i was able to fix the screen issue.
Issue of camera remains. I removed the camera from the socket, and disconnected its wire from the motherboard. When i accessed camera without wire connected, it straigth away went to "ERROR. Camera not available. Earlier, when wire was connected, it took about 5 seconds and then outputted the Error. Flash/ Front camera are still not accessible or usable even when front camera was plugged out.
Weird vibrations are felt randomly, i am still trying to pinpoint what causes them, but they have decreased significantly.
My question now is, will replacing the camera fix the camera issue? Or is there a deeper wire/motherboard issue here? What would be your next step to investigate it further. Also, can this be not a broken screen issue but a camera issue covered in warrantly?
Additional info: i have tried reinstalling ROM, flashed T-mobile's original ftf file, cleared camera cache, files etc. used 3rd party apps but no success.
#####SOLVED: SCREEN HAS WEIRD FLOATIES WHEN WE TOUCH AREA NEAR THEM
This is caused because of dust between the digitizer and the back of the phone. To fix this, simply open the phone up and remove any dust particles between the digitizer and the phone. Screen will work perfectly after that.
JustPlayingHard said:
Most likely put a new module in there as the modules are machine made are probably solid.
Click to expand...
Click to collapse
When you say module? you mean the camera with the connection wire ? or something more than that?
marksee said:
When you say module? you mean the camera with the connection wire ? or something more than that?
Click to expand...
Click to collapse
The camera with connection wire
Update: so bluetooth call recieving does not work, people call me, and if i pick it up, voice does not work over bluetooth anymore. music skips randomly too. My question was that will camera module replacement fix this? or is this a deeper issue, such as cable that connects the camera module? what will i need to replace .
I don't think that anybody here could answer your questions. You should take your phone tot a service center.
Sent from my C6903 using XDA Premium 4 mobile app
SOLVED it.
Fixed it! The issue was that the back camera module was malfunctioning. Because of that, phone chip that controls camera (also controls vibrations) was not functioning properly. I bought a used camera module from ebay, plugged it in and phone works perfectly now
Feel free to pm me if anyone else has questions about this, or need help dismantling phone. Xperia Z1s I AM BACK!!!
Does anyone have a clue why the above issue persists with Cyanogen Mod roms? I have tried several and still get the same problem.
What I'm talking about exactly is, when I try to play music in my truck via Bluetooth, the music will play for about 3 seconds then the audio will mute for 1 second.
I have tried several different things to get it to stop but it appears that it is a CM problem. When I go back to an aosp rom it works just fine.
My Bluetooth issue is a big deal to me. And for the record this problem is with my 2015 Tacoma.
Does anyone know of a fix for this? If any devs have any ideas and would like me to test anything for a fix I would be glad to help.
konaman said:
Does anyone have a clue why the above issue persists with Cyanogen Mod roms? I have tried several and still get the same problem.
What I'm talking about exactly is, when I try to play music in my truck via Bluetooth, the music will play for about 3 seconds then the audio will mute for 1 second.
I have tried several different things to get it to stop but it appears that it is a CM problem. When I go back to an aosp rom it works just fine.
My Bluetooth issue is a big deal to me. And for the record this problem is with my 2015 Tacoma.
Does anyone know of a fix for this? If any devs have any ideas and would like me to test anything for a fix I would be glad to help.
Click to expand...
Click to collapse
Well... if you're playing with CM, you're bound to get burned. There are a couple of reasons;
1) Everybody (and I mean *everybody*) throws stuff at the CM gerrit server (sometimes, even for comedy/trolling purposes), these bits being thrown at it are mostly independent and generally NOT tested in conjunction with all the other bits that get thrown at it. So what happens, is one of the maintainers sees a commit they like and adds it, sometimes not realizing the consequences of it, and major breakage happens.
2) Sometimes in the aforementioned situation, minor breakage happens, and it can persist for months, or even forever.
3) CM12 is very young, with lots of changes still flying. It is by no means stable, or even settled.
4) The CM definition of "stable" is that which nobody bothers working on any more. I.e., everybody right now is interested in Android 5.0, so 4.4 is not getting much attention... it is "stable" -- despite being horribly broken in many many ways.
If it works well with the factory system image, then you pretty much have the answer... it is a defect that has been introduced to CM. I think that CM has their own bug tracker that you can use, but I'm not sure if they have even opened it up to receive reports against 5.0 yet.
BTW: Sweet truck eh? I have a 2011. Pay some attention to the front cab mounts. If you look up into the cab mounts with a flashlight, you will notice that at the back where they are welded onto the main frame rails, there is a huge opening to the inside of the boxed section. When you drive through salty road slime in the winter, all that salt crap that flies off the front wheels gets sprayed up and into the INSIDE of the boxed section of the frame. Get a tube of roof repair tar from HD, and a couple of old CD's. Cut the CD's down to a diameter of 3.5 inch. Stick the cut down CD's up into the opening of the cab mounts and tar them in really well. While you are at it with the tar, plug up all the other holes into the frame around the front wheels (you may need some plastic plugs for this). That will keep the road sludge out of the frame, so it won't rust from the inside out.
I am running LiquidSmooth/franco kernel. I am running the 1/19 build because it was the last with the nice Dark UI and have no problems with Bluetooth in my Prius. I mainly use Pandora.
@ doitright
Thanks for the reply. I have a better understanding about cm roms from it and I have been searching this issue all over. It is definitely a cm problem.
As for my truck, yeah I love it. I have the double cab TRD off road 4x4 model. When the weather clears/warms up I will check the areas you mentioned. I know the history on Toyota frames all too well.
@ prod
I had the same issue with that rom as well.
Are you still having issues with this on nexus 6? I am on s5 and willing to buy a nexus 6 to fix it but i'm starting to wonder if it will matter.
konaman said:
Does anyone have a clue why the above issue persists with Cyanogen Mod roms? I have tried several and still get the same problem.
What I'm talking about exactly is, when I try to play music in my truck via Bluetooth, the music will play for about 3 seconds then the audio will mute for 1 second.
I have tried several different things to get it to stop but it appears that it is a CM problem. When I go back to an aosp rom it works just fine.
My Bluetooth issue is a big deal to me. And for the record this problem is with my 2015 Tacoma.
Does anyone know of a fix for this? If any devs have any ideas and would like me to test anything for a fix I would be glad to help.
Click to expand...
Click to collapse
jd603 said:
Are you still having issues with this on nexus 6? I am on s5 and willing to buy a nexus 6 to fix it but i'm starting to wonder if it will matter.
Click to expand...
Click to collapse
I had constant problems with this phone. I am not new to flashing roms or modding phone by any means but this phone had me beat. CM roms had the Bluetooth issue and I never got it fixed. Normal roms worked pretty good but the phone was still buggy.
I got so sick of it that I sold it. Though it has been a few months ago, maybe they got the bugs worked out, idk. I couldn't take it anymore.
I went got a 128gb iPhone 6 plus now and have never been happier. I haven't had an iPhone since the 4 and I forgot how flawless they operate out of the box.
Rear camera-hardware detected, yet black image. Camera "bus" malfunctioning?
Hi
Half a year ago my girlfriend accidentally gave my Z3 Compact a rollercoaster ride in our washing machine (full tour). The screen broke, but it could turn on and everything looked fine (gave no errors) when connecting to HDMI.
Yesterday I received a replacement LCD, which gave it a new life. It seems that everything works except for the rear camera. When opening any camera-app, the HUD is visible, but image is black, and no error. If i switch to front camera, which works, and back to the rear camera, it shows a freezed image of the last image from the front camera.
I checked some debug-apps to see if it detects the camera-module, and it does. If it's connected, alle the specs of the camera is listed, and if disconnected, the module is not listed.
I then got a broken Z3 Compact from a friend, and I tested both rear camera modules in both phones. The modules are working in his phone, both doing the same black screen in mine.
I tried hard reset, PC Companion-repair, updates, clearing camera cache etc., but with no luck.
Do you have any suggestion to how I can fix this?
Do you know where on the motherboard I could look for dirt in relation to some "rear camera bus/chip"?
Thank you for any help!
Edit: And isn't it amazing that this phone works to this extend after 2½ hours in 60 degrees celcius (140 fahrenheit) warm water with soap and 1400rpm? Wow! (Btw., all panels were open, and screen totally broken, so water must have been everywhere in the phone.)
I have a similar issue on my partners z3c after the screen cracked, I have replaced the screen and it works great however the camera shows a black screen. I know the camera module is working as I have tried it in another phone. Having searched for this issue I seen it has effected quite a few others not only those who have opened their phone.
what software you used to debug so I can verify that the phone can also see the camera module
This is happening to me too a year down the line of ownership.
Replaced with new camera from eBay still black screen. Between your experience and mine of both testing the camera we've prices it's not the lens, so what could it be.
Need to fix don't know what to do
The camera module itself may work but the chip which handles the rear camera may be damaged even if the phone works pretty good.
So if the chip or anything else related to the camera is dead, you can even try thousands of camera modules from different phones on YOUR phone, none of them will work.
That's my opinion - guy's who work in electronical industry for 3,5 years now and have seen hunderds of differend kinds of damages on different stuff.
I see what you are saying however it would be nice to have an idea of where any chip/bus is that may be damaged to see if it xan be fixed or is replaceable.
romcio47 said:
The camera module itself may work but the chip which handles the rear camera may be damaged even if the phone works pretty good.
So if the chip or anything else related to the camera is dead, you can even try thousands of camera modules from different phones on YOUR phone, none of them will work.
That's my opinion - guy's who work in electronical industry for 3,5 years now and have seen hunderds of differend kinds of damages on different stuff.
Click to expand...
Click to collapse
zackariah said:
I see what you are saying however it would be nice to have an idea of where any chip/bus is that may be damaged to see if it xan be fixed or is replaceable.
Click to expand...
Click to collapse
Yes, you are 100% right but there's another thing.
In the present times, in a rush of miniaturization, there's a little chance of such reapair to be profitable. The chip/bus may be damaged but in fact not only one thing may be dead... I'm talking about tiny little resistors, capacitors, diodes, transistors (if there are any on the motherboard...) which are many. I'm not saying it won't be possible to repair the phone but without a proper diagnosis what is damaged... I'd be like looking for a needle in a haysack and everyone can tell you that only replacing the whole motherboard will be worth the time.
But still... this is an interesting case of malfunction... I hope you'll find a solution for this or at least someone else will do it for you for a reasonable price.