No sound from speakers - One (M7) Q&A, Help & Troubleshooting

My phone is was running the May 19 build of CM10.1 without any issues. Today, randomly, and not even while I was using the phone, I suddenly have no sound to my speakers. No music, ring tone/notifications, speaker phone...nothing. I tried updating to the latest build of CM, but it did nothing. I tried a clean fresh install of CM, nothing. I tried a clean install of ARHD 9.1, still no sound. My last attempt was going to be to return to stock via nandroid backup through TWRP, however when I click on "restore" within recovery there is nothing there to select. Upon checking the file folder there are 2 backups there?? Very frustrated! I have had this phone less than a week and for the life of me cannot figure out what could have caused this.
Any help would be sincerely appreciated.
Sent from my HTC One using xda premium

Seems an hardware defect, but it's strange.
Try with your backup (move it to sdcard/0), or with a RUU if there is

Careful with Beta builds... You won't know what's broken there and could break your phone's hardware. I had experience a broken touchscreen once when I tried using CM made for Xperia phones. I was just watching a movie with CM installed on my phone one night then woke up in the morning shocked that touchscreen won't work anymore. Flashed stock ROM and it's still broken until I sent it for warranty. Till then never tried any AOSP/CM builds anymore.

Related

[Q] nexus one all sound level goes verry verry low

i used this shipped rom when i got my n1 6 months ago,
Passion_Google_WWE_2.16.1700.1_FRG33_MFG_Shipment_ROM.zip
i received all the updates, it was working fine.
the other day, i decided to use the same passimg.zip file,
when phone read the sd card, i accidently selected recovery, it started to do recovery process, middle off the process i freaked out because that was not i wanted to do so i turned off the phone and install passimg.zip
i install all the programs i use and received all the updates,
now n1 sound level goes very low even it shows sound level is max,
its impossible to hear when it rings or playing music.
when i turn off and on the phone i get the sound back, after some time sound level goes very very low even sound level in max. so i turn off and on again and i get sond back,
i dont have any problem during calls i can hear,
right now
version 2.3.6
build number GRK39F
how can i fix this?
This used to happen to me on cm7 I did a full wipe and reflashed the ROM and it fixed the problem so I would suggest you reflash the passimg file.
i downloaded same passimg file and installed it to my nexus one, same proprem continuous.
when i turn off and on, everthing normal.
any ideas?
Dude Random21 said:
This used to happen to me on cm7 I did a full wipe and reflashed the ROM and it fixed the problem so I would suggest you reflash the passimg file.
Click to expand...
Click to collapse
"full wipe" means, using passimg file and install it again?
Full wipe means to do a factory reset, usually from recovery.
i figured it out. i dont know why but the problem was a program called voipraider,
i uninstalled it, problem solved, thanks for your replies...
Ok well I'm glad you got it resolved
I have this same problem. I don't have the app mentioned above installed, so I'm hoping someone can chime in with another app that may cause this issue? I've done a full factory reset, reinstalled everything (MIUI rom.) Rebooting the phone doesn't always fix the problem.. sometimes rebooting a few times will bring the sound back to normal, yet randomly all sound on the phone is barely audible at max settings. If a normal reboot doesn't work, normally wiping dalvik will fix it. Would this mean the problem lies in one of my apps somewhere? Any advice?
Are you using DarkTremor's a2sd? If so, it is a well-known problem. And wiping dalvik or just the regular cache will reset it. Due to this reason (and a few other minor ones), I switched to S2E for my app2sdext purposes, but I am not sure how well it works with MIUI (it was designed to work with CM7).
@bassmadrigal
Thanks. As I think about it, DTs a2sd is the only common thing I had in my testing. Even switching between ROMs, I kept flashing DT. Since I always have issues with MIUI's stock A2SD (based of DT).. I went back to CM7. I looked into S2E and will take that route.
I hope this fixes it.. the sound was frustrating when my alarm is going off in the AM and it's not making a peep. I'll post back in a few days in hopes that it's ceased to be a problem.
Thanks again for hopefully solving my major nuisance.

Reboot & Wifi "error" after 2 weeks of using any ROM

Hi all,
I've been unable to find a post about this for quite some time so I decided to make a threat about it.
I have a recurring problem with my captivate. Usually after about 2 weeks of using a ROM my phone will have 2 issues pop up simultaneously. They seem to always happen together. It seems to happen after my phone shuts off and will not turn back on until I battery pull. Once I do that I am presented with these two issues:
1.) When I try and toggle Wifi it attempts to then simply says "error" underneath it. I have found a few threads about this but no answers
2.) Upon installation OR restoration of any app with Titanium Backup my phone does a soft reboot (goes to spinning CM logo or for ICS goes to the multicolored squares flying around).
Edit: On the newest MIUI it now says "insufficient storage available" instead of rebooting when I try to install an app after the issues crop up, wifi "error" is still the same
I've had these same 2 issues occur with CM7 Stable, RC, and many nightlies, MIUI, and TeamHacksung's ICS build. I believe it may have happened with cognition too but am not positive.
I do not restore any data with TB. Before each flash I wipe system, cache, dalvik, and do factory reset and still this issue occurs without fail after about 2 weeks on any ROM and the only fix I have is to flash a new one.
Nandroid backups DO fix the problem. If anyone is willing to look through logs or something and see what was different I would be eternally grateful and certainly send you something through PayPal
Any help is greatly appreciated and I am willing to try anything at this point. Thanks!
Sorry for the double post,
Is there a better forum to post this in?
spectralite said:
Sorry for the double post,
Is there a better forum to post this in?
Click to expand...
Click to collapse
Nah this is the right place. That's a very strange problem you're having though, and I don't know what the exact solution is, if there even is one for this. The only thing I can suggest is going back to stock, and then reinstalling CM7 or whatever you want
Sent from my lightning fast Glitched 1.3Ghz CM7 i897 Captivate
Thanks,
Well happened again on newest MIUI. Gonna go back to stock and start over. I'll update the thread if it does or does not happen again.
Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance
spectralite said:
Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance
Click to expand...
Click to collapse
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.
I had this same problem with my fascinate. I flashed 1.10.21 MIUI follwed by glitch 13.1. This combination used to work, or so I thought. I flashed back to stock, 1.12.1 then a different package of glitch 13.1 and my wifi started working again. I know the captivates and fascinates are somewhat different, but try this out and see if it works.
bobbylx said:
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.
Click to expand...
Click to collapse
I guess I could try that, I just like CM7/MIUI so much. Another thing that happens is many different applications start FCing after the problems all begin.
I tried to restore to a nandroid backup I had made before it happened this time and I received an MD5 mismatch which I believe happened last time I tried to restore...
New info:
I have not realized this before but it seems that I start getting a message that says, "Google Talk Authentication Failed", around the same time. Also FCs happen much more frequently. Is there anything I could be doing to cause this?
New Info
Just going to keep this updated with things I have tried in case anyone ever searches for this that has this issue:
Full format of SD card and odin back to stock did not prevent the issue from cropping up on the DarkKnight3 ROM with Icy Glitch. At this point I can only assume it is somehow hardware relatedl

Strange microphone issue

This phone is driving me crazy. I haven't seen this issue reported by anyone else before, so I'll try to sum it up:
I have a Galaxy Mini, with CM 7.1 RC1 installed, which I can no longer update or replace its ROM, no matter what ROM I install(I've already tried CM7.2, Andro-ID and every other ROM that I could get my paws on, it's hopeless; CM9 also seems to work, but it's so buggy, it's unusable), the microphone won't work anymore, even after clearing everything and fixing the permissions, I have to revert to CM 7.1., which is the only release which has a halfway working microphone implementation(it's buggy, to say the least, people just barely hear what I'm saying). There is a patch for libaudio which suposedly fixes the mic, but after installing it, ceases working, so I always have to revert to my CM7.1 Nandroid backup. I would install the vanilla Gingerbread again, because everything was working fine on that, but there is one small issue...the data cable broke not too long ago, so I'm stuck with only a MicroSD card reader, which is not of much help, because I can't flash it with Odin and, as this will be sold next week(the buyer asked me to reflash it with the original firmware), I'm not willing to buy a new one for it either.
My biggest mistake was that I forgot backup the original firmware, which might have been the simplest solution for this problem, so I'd be very grateful if someone could kindly dump and upload his/hers stock ROM backup from cwm, so I can try to restore it and finally get the mic working again. Also, if you know any other solution that might fit in this scenario, I'm willing to try anything.
mihait39 said:
This phone is driving me crazy. I haven't seen this issue reported by anyone else before, so I'll try to sum it up:
I have a Galaxy Mini, with CM 7.1 RC1 installed, which I can no longer update or replace its ROM, no matter what ROM I install(I've already tried CM7.2, Andro-ID and every other ROM that I could get my paws on, it's hopeless; CM9 also seems to work, but it's so buggy, it's unusable), the microphone won't work anymore, even after clearing everything and fixing the permissions, I have to revert to CM 7.1., which is the only release which has a halfway working microphone implementation(it's buggy, to say the least, people just barely hear what I'm saying). There is a patch for libaudio which suposedly fixes the mic, but after installing it, ceases working, so I always have to revert to my CM7.1 Nandroid backup. I would install the vanilla Gingerbread again, because everything was working fine on that, but there is one small issue...the data cable broke not too long ago, so I'm stuck with only a MicroSD card reader, which is not of much help, because I can't flash it with Odin and, as this will be sold next week(the buyer asked me to reflash it with the original firmware), I'm not willing to buy a new one for it either.
My biggest mistake was that I forgot backup the original firmware, which might have been the simplest solution for this problem, so I'd be very grateful if someone could kindly dump and upload his/hers stock ROM backup from cwm, so I can try to restore it and finally get the mic working again. Also, if you know any other solution that might fit in this scenario, I'm willing to try anything.
Click to expand...
Click to collapse
for stock rom is very simple go here http://forum.xda-developers.com/showthread.php?t=1464896 and get this rom flash with CWM and Voila!!! ^^
Hmmm...I wonder why that one isn't in the rom list. Anyway, downloading and reporting back.
well-it sure looks like stock, yet mic is still dead
bump......

Stability problem

Hello, I'm using Semaphore + CM10 JB for few weeks (installed with your support).
However I have a problem. The stability. My phone likes to resets byself, even few times per day. It happens irregularly. What's interesting, sometimes phone resets to the CWM. Sometimes resets and backs to work, sometimes totally offs the phone (and i need to pull out the battery) or freeze on cyanogenmod start screen (but not on normal start, only when resets)
Sometimes it happens when i'm using the phone, sometimes not. He likes to do that when i'm sleeping (for example, goes to the CWM and discharge the battery by whole night on full bright).
And much smaller, but maybe important issue: when the phone starts, shows the message Warning! A problem was detected with your device. Your device IMEI number is invalid. And invalid IMEI number could cause network issues including the inability to call emergency numbers.
Firstly I installed CM10, i had the problems with the network, but after @xsenman's help (reinstall with older ROM before flashing CM10) everything works correctly and i can see IMEI too. I made an EFS backup in that old ROM, should i use that? This message doesn't intrude me, but i'm just thinking if this could be connected with reseting problems. My SGS works really nice, but that one issue is really annoying.
100 views and really no one can help?
Come on, i feel so lonely
I'd recommend flashing a clean GB stock, restoring your IMEI, flashing CM9 twice and then flashing CM10 ROMs (if you want them lol). Always be sure that you wipe your phone after installs.
Sent from my Gameboy Color
thanks for your answer. However, maybe it's not a ROM problem? Maybe some application makes an issue. Is there any log where i can check that?
That IMEI stuff definitely isn't app-caused. I can only repeat my statement above. Don't worry about data, you can backup everything using Titanium Backup and SMS Backup+.
Btw: What ROM are you on?
Best regards
Sent from my Gameboy Color
True, IMEI not, but it's not a real issue for me. Actually, i'm absolutely satisfied of my i9000 (maybe flashlight absence, but it's hardware). Everything works fine, but reseting problem makes me nervous when I use the phone as car dvr or for endomondo ect.
I use Cyanogenmod 10, one of october's nightly versions.
So basically you don't want to change anything but you want us to help you? Sorry, that's not the way a community works.
You didn't understand me. My problem is phone reseting. I want to find the reason of the issue. Because without it, i can install new software and still have the same problem.
przemek211 said:
You didn't understand me. My problem is phone reseting. I want to find the reason of the issue. Because without it, i can install new software and still have the same problem.
Click to expand...
Click to collapse
Since when has this problem occurred? I doubt an app makes a phone reset itself.
Edit: I looked around your post history and you seem to have posted in the semaphore thread. Maybe something is wrong with the kernel?
Sent from my GT-I9000
Thanks for your answer. It's hard to say because I've flash a ROM and out of hand I installed the applications. It's the worst type of problems, because it doesn't happen instantly or regularly. Actually since i wrote the topic, i didn't see the problem, however i saw two-three times the attention about IMEI, so i think, the phone resets, but not seen.
/// amerkiller: you are using i9000 too, could you recommend me any other ROM? Probably I will need to install a ROM and wait, two-three days and check if the ROM makes any issues.
/// maybe, but how can i check it? It looks like work nice, my question in Semaphore's thread was about the features
I use Remics-JB, you can try it out if you want a Samsung touchwiz feel, and apps from the S3.
Slimbean if you want a minimalist ROM.
Hopefully, the problem will disappear.
Powodzenia
Edit: regarding the kernel, you can flash Devil and see if the problem persists.
Sent from my GT-I9000
So I will try Devil + Slimbean, thank you
amerkiller1995 said:
Powodzenia
Click to expand...
Click to collapse
Poles everywhere?
pozdrawiam
BlueFlame4 said:
I'd recommend flashing a clean GB stock, restoring your IMEI, flashing CM9 twice and then flashing CM10 ROMs (if you want them lol). Always be sure that you wipe your phone after installs.
Sent from my Gameboy Color
Click to expand...
Click to collapse
Ok, so i want to reflash my i9000. So - i have JVU's gingerbread ROM, is that correct stock ROM? Should i make the WIPE here? I'm not sure about restoring IMEI. Should i do that in GB's temporary ROM or (as I think) later in JB's? Of course, earlier I need to backup the efs folder with IMEI so i think i should do that in GB's and restore it in CM10 (or in Slimbean which I want to test). And one more doubt. You said flashing CM9 twice. Why is that? And how can I do that if i'm installing the ROM in CWM?
przemek211 said:
Ok, so i want to reflash my i9000. So - i have JVU's gingerbread ROM, is that correct stock ROM? Should i make the WIPE here? I'm not sure about restoring IMEI. Should i do that in GB's temporary ROM or (as I think) later in JB's? Of course, earlier I need to backup the efs folder with IMEI so i think i should do that in GB's and restore it in CM10 (or in Slimbean which I want to test). And one more doubt. You said flashing CM9 twice. Why is that? And how can I do that if i'm installing the ROM in CWM?
Click to expand...
Click to collapse
You can find tutorials about flashing to stock.
http://forum.xda-developers.com/showthread.php?t=1102881
Flashing the stock ROM will recover your IMEI number if you currently don't have it and will wipe your personal files. Backup your IMEI while you're on GB and if you lose it, then restore it. Fyi I never lost my IMEI, it's not common. You should flash JB / cm10 twice, ICS/cm9 should be okay after one flash. Remember to wipe if the instructions say so.
When you'll attempt to flash cm10 in recovery, you'll get a warning about partition change. You'll have to chose to flash second time, this time it should work and the phone will reboot into a bootloop. Pull out the battery and enter recovery and flash cm10 again. This time it well install and reboot successfully.
Sent from my GT-I9000
It's everything working nicely? Asking out of curiosity.
Sent from my GT-I9000
Hi, thanks for your interest
Two days ago I made a re-flash Stock > CWM > CM9 (twice) > CM10
Attention about IMEI doesn't longer appear
I've installed apps. The phone has resets for a one time when I was using some app. It is not a big problem for me if SGS makes that from time to time (maybe some apps are not adapted to the JB very well). However today I used him to record my drive (dailyroads voyager) and when i tried to stop the recording, he doesn't backs to life (just I needed to pull the battery out) and video file was corrupted. But when I was getting back to home it worked correctly. I have no idea why that's happen.
przemek211 said:
Hi, thanks for your interest
Two days ago I made a re-flash Stock > CWM > CM9 (twice) > CM10
Attention about IMEI doesn't longer appear
I've installed apps. The phone has resets for a one time when I was using some app. It is not a big problem for me if SGS makes that from time to time (maybe some apps are not adapted to the JB very well). However today I used him to record my drive (dailyroads voyager) and when i tried to stop the recording, he doesn't backs to life (just I needed to pull the battery out) and video file was corrupted. But when I was getting back to home it worked correctly. I have no idea why that's happen.
Click to expand...
Click to collapse
Restarts shouldn't happen that was some unusual circumstance. The video problem is weird, post here if it happens again, lets hope its just bad luck.
Ok, I'll look on it.
I have one other question and maybe you will know.
Call recording. There are two options for use this feature. Simple MIC recording apps and 'two-way call recording' which is much better, however it needs kernel with handle of it. I didn't find anyone for SGS, so I want to use MIC recording. There are many apps in Google Play. However any of them makes 0kB files of record on JB's CM10. When I was using gingerbread it didn't worked too however files were good, but the second side of call didn't hear me.
przemek211 said:
Ok, I'll look on it.
I have one other question and maybe you will know.
Call recording. There are two options for use this feature. Simple MIC recording apps and 'two-way call recording' which is much better, however it needs kernel with handle of it. I didn't find anyone for SGS, so I want to use MIC recording. There are many apps in Google Play. However any of them makes 0kB files of record on JB's CM10. When I was using gingerbread it didn't worked too however files were good, but the second side of call didn't hear me.
Click to expand...
Click to collapse
In regards to two way recording, i don't think it's solved...
http://forum.xda-developers.com/showthread.php?t=863074&page=38
I never needed that feature, so i won't be much help, try different apps and remember some apps are on XDA, not only the play store.
Sent from my GT-I9000
I saw that, but it is only for Froyo, when i installed it into gingerbread i needed to re-flash my SGS
I tried a lot of apps, however it looks like being locked (if worked they made 0kB files)

Huawei U9000 european version incredibly unstable

Ever since I got this phone in 2011, it's never worked properly.
When I was running the standard software (2.3) it still crashed regularly without notice, it might have taken an hour, 20 seconds from reboot or go a full day.
After I went back to the electronics store I bought it from, they sent it to be repaired and came back just the same, completely useless.
This repeated itself several times untill I couldnt be arsed to try anymore.
So I rooted the phone and installed probably 10-15 different versions of android without much luck.
I've already gotten a new phone and i'm no longer using the Huawei handset, but I'm mostly just curious to see if anyone else have experienced the same issues that I have. I've been looking around the internet but i've been unable to come across any forum threads.
Would be nice to have a backup phone, but at the moment it's useless.
no such problems seen in two years of usage still my x6 runs like a new one apart from few scratches
i was on stock firmware very very long back but had few random reboots (2.3)
try using sharp modded stock firmware it is the most stable as of today.sill if u have reboots in sharp you can conclude that the problem is with the HARDWARE
Hi,
I have been using this phone (Spice MI-410) since 2 years. No major issues.
Tried out a lot of custom ROMs. Currently am running MIUI 2.4.13 v7.
Suggest you try out this ROM, but please ensure that you follow all steps required for installing the custom ROM.
As a start, please find the steps below:
1. Put the downloaded new rom. (.zip) to your SD card
2. Install Tjstyle RC3 via SUT 1.8 (RC3 comes with CWM preinstalled.)
3. Go to 'backup and restore ' and take a backup
4. Format Data, Cache and Dalvik
5. Install the zip from SD card
6. Reboot system and you are done
7. Reboot once again and login to your google account
Cheers...
reversegear said:
no such problems seen in two years of usage still my x6 runs like a new one apart from few scratches
i was on stock firmware very very long back but had few random reboots (2.3)
try using sharp modded stock firmware it is the most stable as of today.sill if u have reboots in sharp you can conclude that the problem is with the HARDWARE
Click to expand...
Click to collapse
I installed the latest version of the sharp firmware, and at the moment it seems to actually be working.
I find it kind of funny that this firmware is more stable than the factory provided one to be honest.
I'll update the thread if there are any huge changes to the stability.
Thank you both for the advice, it's nice to have a working handset again.

Categories

Resources