My earpiece volume is LOW.
I turn it all the way up and its till hard to hear.
Happened after a flash of some rom/kernel combo.
Not sure which one.
I have tried LouderVolumeHack, to no avail. I've also tried DSP
My ringer/noti/speaker phone are plenty loud.
Only the earpiece is low.
My current rom/kernel is: WTSB 1.9 with Latest Tiamat
So is there something I can pull and change or anything?
Thanks
It could be the audio settings in the rom. I have been using the audio files from infected rom on my roms and they work great, seems better than stock. I had the same problem as you a while back, I dont remember what rom it was on.
What files are those?
I was using an Infected ROM before.
Had a few issues, but love it anyway.
still here
I flashed MiUI 1.10.14 and still low sound.
Nobody knows where i can find the audio files to mess with?
I use the etc/soundimage file from infected along with the AdieHWCodec.csv, AIC3254_REG.csv, AIC3254_REG_DualMic.csv, and CodecDSPID.txt. Those all seem to container audio stuff. You might also check lib files. The rom that I use is my own custom rom that I have compiled over the last month and a half, I use stuff from a bunch of different roms, so Im not sure what is from what......sorry.
thanks, i'll load those and see how it goes!
i've tried those and now i have have NO sound from earpiece. even flashed new rom (sickSense) ...
now it's nothing.
If I was you, or if I was me, I would RUU back to stock (I usually do once a month or so anyway) and see if that fixes it. If that fixes it, try flashing a different rom and see if the volume changes.
I had terrible problems with my volume for a while. I RUU back to stock, then I did ##786# and factory reset, allong with *#7780#, and ##72786#. Im not saying that you should do all of that, but that is the only way I could find to revert all of the changes that I made in QPST. It will put your phone completely back to stock, so you will need your MSID to get your services set back up.
I have no issues with my audio now
im trying the above right now. so far just RUU did not restore sound.
at least if all of these don't work, my phone wont look shady when i take it back to Sprint and claim ."i dunno what spazed on it?!!"
Thanks for all of your help shiftr! i hit thanks like twice i think!
No prob man, I just hope it helps.
Related
hi guys i think i saw a thread or post before about this but i am not quite sure, and hate to post the same question that has been answered before but i couldnt find that.. anyways i am running straight up axura 2.3.1 and i noticed whenever i play music on it, i would only hear it on headphones/earphones but not on the phone speaker. any ideas?
thanks i appreciate the help alot
It is like stuck on headphone mode even headphone isnt plug. Ive odin back to stock, reflashed and nothing works
Edit. I dont have any system sound. i can hear alert sounds and all. hmmmmmmm any ideas?
Unless you have the speaker turned off (which I doubt) you may just have a bad flash I have this rom on my wife's phone and I just checked it works fine. So reflash is probably the easiest and fastest way to fix.
oka1 said:
Unless you have the speaker turned off (which I doubt) you may just have a bad flash I have this rom on my wife's phone and I just checked it works fine. So reflash is probably the easiest and fastest way to fix.
Click to expand...
Click to collapse
i reflashed and back to stock, flashed bionix, axura. still no media sound and system sound. i highly doubt its axura itself, since i flashed it a couple times before and had no/little bugs but not anything with the sound
edit: i was researching and found that somewhere between the line, it might be this issue
http://forum.xda-developers.com/showthread.php?t=991465
how can i flash that?
I sold my 3D to someone and have been trying to put a new rom on it for em. Everytime I flash a 2.3.4 rom everything works EXCEPT during a call you can hear the person talking but they cant hear you. And I know the speaker works because voice commands work fine but during it call it doesn't work, period.
Sounds Like a personal phone issue..I've been on 2.3.4 with multiple roms and never had this issue.
Sent from a little place called ETERNITY in the 3rd Dimension.
I never had that problem running 2.3.4 ROMs either.
I honestly don't get it. Every 2.3.4 rom I tried to put on the phone would have the issue with not being able to be heard during a call. I tried 4 different roms and had the same issue everytime. Put a 2.3.3. rom on it and I could be heard during calls fine. I dunno but I got tired of fooling with it.
I did notice one thing though... when wiping in recovery I got an error that said
E:can't give path "/sdcard/.android_secure" to format_volume
Think that might have something to do with it?
OP, did you do the EVRC-B mod? If so, undo it.
Compusmurf said:
OP, did you do the EVRC-B mod? If so, undo it.
Click to expand...
Click to collapse
I don't even know what that is lol. This is basically the scenario. I can flash ANY 2.3.3 rom or lower than that and everything works perfectly fine. But as soon as I flash any rom with a 2.3.4. base everything works except for callers being able to hear me. It's crazy... I even tried the stock 2.3.4. deodexed update and it was the same thing. Flash a 2.3.3. rom and boom, they can hear me again.
brownhornet said:
I don't even know what that is lol. This is basically the scenario. I can flash ANY 2.3.3 rom or lower than that and everything works perfectly fine. But as soon as I flash any rom with a 2.3.4. base everything works except for callers being able to hear me. It's crazy... I even tried the stock 2.3.4. deodexed update and it was the same thing. Flash a 2.3.3. rom and boom, they can hear me again.
Click to expand...
Click to collapse
The EVRC-B mod enhances voice, the same settings found on Verizon phones but in some cases it might not be supported by the tower. Its accessed in the EPST edit menu, via your MSL code.
But if you're flashing the ROMs with voice performance changing, I'm not sure whats going on. As I seriously doubt the EPST settings get changed by the ROM.
I could be wrong.
I don't know either... im clueless. First time i've ever had a hangup like this when flashing. I put it on the phone for her and everything was all good until she got a call and realized they couldn't hear what she was saying. I thought maybe it was a bad flash but hell i've tried every rom in the development forum almost.
none
Give the guy his money back, put it under your car tire, then smoke the tires, that phone sounds retarded.
Try revolution by Mike and see if that shows the same issue.
If it does then either your doing something wired while flashing, have some app messing crap up, or its hardware problem somehow.
Likely its user error somehow though. I dunno any roms that flip evrb on for voice by default for the mere fact that its not supported everywhere.
Sent from my PG86100 using XDA App
But how would it be user error only for the 2.3.4. roms lol. Im sayin... i'm not doing anything different. Just download, transfer from pc to sd and flash through recovery like I always have. If it was user error it seems like id have problems with the 2.3.3. roms too. I gave up on it though.. technically it's not even my phone anymore lol
Grrr, ok I've rooted my Galaxy Player wifi 4.0. I'm using Terrasilent 3.5 and Ethereal Rom 2.4. Everything has been running good the last week or so, but now my player has developed a snapping, crackle, popping noise coming through the speakers. Any time something makes a sound, this noise comes through the speakers. I can still hear the expected sound, but also the noise with it. I can drown it out by turning up the volume, but when there's no sound being played, it almost sounds like someone's cooking bacon inside my player. I've unrooted and gone back to stock, but still the noise is there. I re-rooted it and still the noise remains. Do you guys think this is a hardware problem? It's loud enough that it's very annoying and noticeable. I would think if it was software related it would have gone away after going back to stock. Any advice how to fix this would be appreciated.
It sounds like a hardware problem to me, but you could do a full restore (see Zaclimon's full recovery thread) to make sure. I have a similar hardware problem - I hear a feint hissing sound, but only when it is very quiet around me.
Sent from my YP-G1 running LinromV2
Yah I'm thinking it's hardware too. I actually used Zaclimons full recovery thread to put it back to stock and it still made this noise. And this noise is loud enough I can hear it from across the room.
Now I'm not totally newbiish, but there's a lot I don't know about how the rooting and recovery works. When I root it and install the new kernel and rom or doing a full recovery back to stock, does it completely wipe every piece of data off the player? I know it wipes out all program settings and personal data, but does it get rid of everything else. I wonder this because I was looking at upgrading to ICS, but there's a big warning about backing up efs. Why don't I have to worry about the efs getting wiped when doing new roms or going back to recovery?
Gaideran said:
Yah I'm thinking it's hardware too. I actually used Zaclimons full recovery thread to put it back to stock and it still made this noise. And this noise is loud enough I can hear it from across the room.
Now I'm not totally newbiish, but there's a lot I don't know about how the rooting and recovery works. When I root it and install the new kernel and rom or doing a full recovery back to stock, does it completely wipe every piece of data off the player? I know it wipes out all program settings and personal data, but does it get rid of everything else. I wonder this because I was looking at upgrading to ICS, but there's a big warning about backing up efs. Why don't I have to worry about the efs getting wiped when doing new roms or going back to recovery?
Click to expand...
Click to collapse
Doing a "full" recovery will wipe all data and return you to exactly what your device was when you bought it. It won't touch certain elements, like the boot loader and the efs. The efs has device specific info and is required for your lock screen and other features so it is empirical that you back it up yourself before flashing cm9 (cm9 has a bug that wipes it). Normal GB ROMs shouldn't mess up your efs, but you might want to back it up to be safe before flashing one.
Sent from my YP-G1 running LinromV2
Dose the same noise come through on your earphones?
Well on ethereal, hanthesolo boosted the output on I believe both the headphones/speakers. He also boosted the bass response with the beats mod too. Did you try switching to IcyFusion to see what happens?
I think my base band got updated to the latest T-Mobile when I flashed a de-bloated T mobile ICS rom. Not sure if this is the case as I am S-ON and am not sure if it's possible for an unsigned rom to flash the baseband, but whatever. Was wondering if there are any users out there who have stayed on Telus stock ICS and what their baseband is. Was having some radio issues and wanted to try and flash stock baseband. Thanks
Which one did you flash?
Sent from my HTC_Amaze_4G using xda app-developers app
chevycowboyusa said:
Which one did you flash?
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
I'm on the latest T-Mobile I believe 1.14.550L.17DC. For all I know this is the Telus ICS baseband but I was having volume issues with the earpiece being too loud even at lowest setting. I do have control over the volume, unlike all the CM based ROMs, I just feel like the earpiece volume is a bit too high compared to what I remember it being when the phone was bone stock. Just wanted to see if I was on the "wrong" radio. I have no issues regarding voice and probably none in regard to data (haven't checked). Just volume. From what I've heard many people who are not on T Mobile have flashed the lattest T mobile radio for improvements. Thing is I'm S-ON so now I figured the radio could not be updated regardless of what ROM I flashed unless it was signed official Telus. Maybe not? Tried De Bloated T Mobile ROM and Telus Rooted ROM and both work well. I'm really just curious at this point I guess. If I'm not on the right radio I'm not sure I'm willing to go S-OFF and start flashing stuff just because my earpiece is a bit too loud. Just would like to know.
Post a screen shot
mdrv500 said:
I'm on the latest T-Mobile I believe 1.14.550L.17DC. For all I know this is the Telus ICS baseband but I was having volume issues with the earpiece being too loud even at lowest setting. I do have control over the volume, unlike all the CM based ROMs, I just feel like the earpiece volume is a bit too high compared to what I remember it being when the phone was bone stock. Just wanted to see if I was on the "wrong" radio. I have no issues regarding voice and probably none in regard to data (haven't checked). Just volume. From what I've heard many people who are not on T Mobile have flashed the lattest T mobile radio for improvements. Thing is I'm S-ON so now I figured the radio could not be updated regardless of what ROM I flashed unless it was signed official Telus. Maybe not? Tried De Bloated T Mobile ROM and Telus Rooted ROM and both work well. I'm really just curious at this point I guess. If I'm not on the right radio I'm not sure I'm willing to go S-OFF and start flashing stuff just because my earpiece is a bit too loud. Just would like to know.
Click to expand...
Click to collapse
Can you post a screen shot of your baseband? or type it in?
Would help. Also, having a slightly louder volume isnt so bad, you can turn the volume down manually..
chevycowboyusa said:
Can you post a screen shot of your baseband? or type it in?
Would help. Also, having a slightly louder volume isnt so bad, you can turn the volume down manually..
Click to expand...
Click to collapse
1.14.550L.17DC Latest T mobile. The lowest volume setting is pretty loud so being able to control volume doesn't mean much. It's not unbearable but it's seems significantly louder than stock so that's sort of why I'm looking at going back to stock or possibly going S-OFF to flash radios. The stock telus ICS zip will not install from bootloader. It either needs stock Telus gingerbread installed as a base or an earlier radio or something. Installing stock gingerbread (executable) requires an hboot downgrade (it checks hboot) and possibly a radio downgrade as well. At this point I may just stay where I am but it wouldbe nice if I could try the stock ICS radio. I was also wondering if it's even possible to flash the baseband when I install a custom ROM when I'm S-ON?
S-OFF Super CID
mdrv500 said:
1.14.550L.17DC Latest T mobile. The lowest volume setting is pretty loud so being able to control volume doesn't mean much. It's not unbearable but it's seems significantly louder than stock so that's sort of why I'm looking at going back to stock or possibly going S-OFF to flash radios. The stock telus ICS zip will not install from bootloader. It either needs stock Telus gingerbread installed as a base or an earlier radio or something. Installing stock gingerbread (executable) requires an hboot downgrade (it checks hboot) and possibly a radio downgrade as well. At this point I may just stay where I am but it wouldbe nice if I could try the stock ICS radio. I was also wondering if it's even possible to flash the baseband when I install a custom ROM when I'm S-ON?
Click to expand...
Click to collapse
I would definately S-off it really helps. chat with @ravike14 he can help you thru it.
If you s-off and super cid you should be able to flash the firmware without issue.
I'm not sure about the baseband thru custom rom. There should never be a firmware upgrade in a custom rom.
Poeple should also warn someone if it does.
I was upset that a certain rom I flashed had a modified recovery and it wasnt mentioned in the op.
Can you send/post your build.prop file? There are some settings that can be controlled there.
Chevy
chevycowboyusa said:
I would definately S-off it really helps. chat with @ravike14 he can help you thru it.
If you s-off and super cid you should be able to flash the firmware without issue.
I'm not sure about the baseband thru custom rom. There should never be a firmware upgrade in a custom rom.
Poeple should also warn someone if it does.
I was upset that a certain rom I flashed had a modified recovery and it wasnt mentioned in the op.
Can you send/post your build.prop file? There are some settings that can be controlled there.
Chevy
Click to expand...
Click to collapse
Thanks for the info. I wound up going the s-off route and flashed a t mobile stock ruu which worked out fine. The volume issue I believe was my mistake. Rather than making a regular phonecall I was making a *888 call which was an automated message giving account balance with a certain Telco. For whatever reason this message was way loud. Regular voice calls seemed to be fine. So l went to evervolve 3.3 but the battery drain was real bad so now I run energy rom and everything is great. If 10.2 ever gets call audio fixed I would consider going back to that as it was soooo smooth even with a couple bugs
Good Job!
mdrv500 said:
Thanks for the info. I wound up going the s-off route and flashed a t mobile stock ruu which worked out fine. The volume issue I believe was my mistake. Rather than making a regular phonecall I was making a *888 call which was an automated message giving account balance with a certain Telco. For whatever reason this message was way loud. Regular voice calls seemed to be fine. So l went to evervolve 3.3 but the battery drain was real bad so now I run energy rom and everything is great. If 10.2 ever gets call audio fixed I would consider going back to that as it was soooo smooth even with a couple bugs
Click to expand...
Click to collapse
Glad to hear everything worked out.
Evervolve is looking like a very good rom!
Jellybean sense is in the works and it's really smooth and snappy, but has a lot of issues right now, and the kernel is proving to be a very difficult problem.
Hello friends,
I recently picked up an i717 and am in the process of sorting it out. It was originally a Bell phone, though of course it's unlocked these days. I've been hacking at various Android phones for years now and have managed to work through just about everything, but this has me stumped...
I've tried almost all the 4.4 roms, and most of the 4.3 as well. I've tried various kernels/modems/combinations/etc. I've used CWM and TWRP. They all invariably lead to the phone either rebooting constantly from the "optimizing apps" dialogue, or a few times I've made it to the welcome screen, but it's always just up for a minute or two, crashes, then reboots. I haven't found a live download for 4.2 yet, so I don't know if it would work or not. 4.1 stock and Padawan run just great. I've been doing multiple full wipes before installation, flashing the rom a few times, then hitting the caches a few more times for good measure. I can't imagine my flashing technique being at issue here.
I do know that there is at least some physical damage to the phone. The capacitive buttons don't work. But it doesn't see immediately obvious to me that these would be related. Of course, I've seen stranger things. Running Padawan the phone will hum right along at max speed all day with no apparent issues, so that side of the hardware seems okay.
Sometimes CM roms will end up at the CM welcome screen and pop up a "com.android.acore has stopped" dialogue. But the constant reboots are there on every rom I've tried.
Does anybody have any ideas?
Outside of the, every once in a while you just need to go all the way back to stock just to make sure all the garbage is taken out, have you considered the infamous stuck power button?
Though I have yet to, many have experience the stuck power button. It may feel ok and you may even hear it click, but that doesnt mean anything. Give your phone a couple good flicks to the back behind the button. Though it does seem odd that it would run one rom without issue and not others, but it is worth a shot.
Again taking your phone to 100% stock every blue moon or so can be a good remedy too.
Keep us posted. We can work you through this.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
I thought about the power button issue. However, it proceeds to boot into the OS until after a time when the screen locks then reboot, which would seem too long to be the power button in any case. Regardless, a few sharp flicks didn't help much. And, of course, it runs quite happily all day long running on 4.1.
I have restored to stock JB, though admittedly not earlier than that. I guess I could try going all the way back to GB to see if that makes any difference.
In my experimentation tonight I've found that 4.2 also does not work, while I can add 4.1 non-tw roms to the working list. My best guess seems like something about one of the many under-the-hood things that changed with 4.2 doesn't get along with something about my particular phone. But, who knows.
For now I'll try rolling back to GB in Odin and see where that gets me.
I would say ICS is about as far back as you need. Recently I was having issue getting anything 4.3 and up to work or even flash. No different recoveries had effect either.
Wiped slate clean and started over from ICS, and Bob was my uncle. Everything that failed before was not an issue. Running latest 4.4 now and might I say "Orgasmic"
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Ahh, if only I were on 4.4 on my Note, life would be good Though, to be honest, I'm quite digging this thing, even at 4.1.
Last night I rolled back to GB, and had no luck. Although the Odin tar that I found apparently didn't include recovery, so that had to be flashed separately. I don't know if that might make a difference. That might be my experiment for tonight if I can find a tar that includes everything. Might be easier to find on ICS.
Just running my mind through other stuff I've thought of, I remember reading about kitkat having some issues with SD cards, so I've mostly been experimenting with the card pulled and a fresh format on the internal storage, with no real difference. Tried safe mode, no dice (not that I would expect this to make a difference on a fresh flash, but who knows lol...).
It's just such a weird thing. It boots into the OS with seemingly no issues. On occasions when I can actually get to the lock screen, everything runs fluid as can be until it freezes and reboots. Sometimes when it gets stuck at the 'optimizing' screen it'll just restart the count every boot, sometimes the number of apps to be done go down each time until there are 3-4 left which persist through each reboot.
I wonder if I could check logcat via adb before it reboots. Might be able to find some clues there.
Here's a factory firmware image of 4.1.2 to be flashed with Odin.
http://www.mediafire.com/view/g7gn29h7nu63id5
I've used this to revert many times. Install it. Run it once, then factory reset and run it for at least a few hours. If you experience issues you probably have hardware failure. If you don't have issues you can proceed with installing the latest clockwork mod recovery. Then wipe system and internal memory 3 times with recovery. Now flash the zip of your favorite kit Kat rom. Reboot and run it. Then factory reset and hopefully run it forever! If you're on a kit Kat build and experience sd card issues, there's an xposed module that might be able to help with that.
Thanks a lot, Bro. I'm downloading the image right now and will flash it then give it some time to settle in. Fingers will be crossed!
Just to give you guys an update, I flashed that stock image, ran it that way for a day, then attempted a few different 4.4 roms. Still no lock.
But thanks for the ideas so far!
I guess it's not the worst thing in the world. At least it runs 4.1 like a top.
Bassism said:
Just to give you guys an update, I flashed that stock image, ran it that way for a day, then attempted a few different 4.4 roms. Still no lock.
But thanks for the ideas so far!
I guess it's not the worst thing in the world. At least it runs 4.1 like a top.
Click to expand...
Click to collapse
Have you tried to turn on USB Debugging and run "adb logcat" to see what errors are causing the problem? If it is an optional program or hardware feature you may be able to disable it and run the newer ROMs. I know bluetooth has been an ongoing pain point for people. Which modem are you running? I know that some of the older modems do not work with the newer ROMS.
Good luck.
Brett
corrupt radio
i had the same issue, flashed 4.4.4 and ran like a charm for 1 day them the radio took a dump. downgraded and worked for another day.
imei became unknown and the no radios were able to fix this. went as far back as 2.3.6 hoping my radios would be fixed and no dice.i have tried endless for weeks to fix my phone and seems doomed.
none of the bricked threads helped and flashing stock with odin is no help. there seems to be no fix to the null imei and unknown baseband