Does anyone else have this problem? It has happened to me with both Blazer ROM and UnNamed ROM. I have to move the phone away from my face to get the screen to come on then I can change the volume.
Me too. I just noticed it yesterday.
Seems to be an EL29 thing.
Sent from this phone
patrick_1 said:
Seems to be an EL29 thing.
Sent from this phone
Click to expand...
Click to collapse
UnNamed is EL13 based and does it. It could be EL based I guess.
dan02gt said:
UnNamed is EL13 based and does it. It could be EL based I guess.
Click to expand...
Click to collapse
Good point!!
There was a post about this but it was on ek02. I didn't suffer from it on my ek02 stock rooted and notice the ppl suffering from it were on custom roms. Now i'm updated to el29 rooted and I still don't have this issue. Are all you guys running custom roms?
Sent from my SPH-D710 using XDA App
Yes to the custom ROM question. I had the issue with both UnNamed and Blazer. I haven't been on a stock ROM in so long I don't remember if I had the problem with it or not.
I noticed this as well. I believe it has something to do with the "volume up to change music tracks" mod. I've only noticed it on roms with this mod. Currently running calkulins 2.8.1 but I can deal with pulling the phone away from my face to change volume. I use the track change mod with Pandora all day long so I don't have to pull my phone out at work to skip a song.
Then I guess you guys finally got your answer to your phone in face volume adjusting issues.
Sent from my SPH-D710 using XDA App
momentary said:
I noticed this as well. I believe it has something to do with the "volume up to change music tracks" mod. I've only noticed it on roms with this mod. Currently running calkulins 2.8.1 but I can deal with pulling the phone away from my face to change volume. I use the track change mod with Pandora all day long so I don't have to pull my phone out at work to skip a song.
Click to expand...
Click to collapse
I have the same issue using Calkulins rom.
momentary said:
I noticed this as well. I believe it has something to do with the "volume up to change music tracks" mod. I've only noticed it on roms with this mod. Currently running calkulins 2.8.1 but I can deal with pulling the phone away from my face to change volume. I use the track change mod with Pandora all day long so I don't have to pull my phone out at work to skip a song.
Click to expand...
Click to collapse
One of the problems with having to pull the phone away from my face is the lag time before the screen turns on and you can actually adjust the volume. If you are on an important call, its inconvenient to have to do that to adjust the volume... Then realize you made it TOO loud/quiet, then have to do it again.
Nitpicky, yes... But if we ask nicely, we might get an optional .zip to flash to remove the mod.
Related
This has been happening on my Epic 4G for awhile now and it's really frustrating. I'm pretty sure this hasn't been happening the whole time I've owned the phone, but at this point it's hard to really remmber.
Basically, when I make or receive a call, within a couple\few minutes of the phone call the caller suddenly can't hear me - this happens whether it's using the phone normally, in speakerphone mode, or even a headset. As soon as it happens and the other caller starts the "Hello? Are you still there?" I can fix it by toggling the speaker on and off (or off and on) and it fixes it - but it can suddenly start again at anytime...couple of minutes later, five minutes later, etc.
Right now I'm slowly removing apps from my phone after every call this happens on - my goal is to determine if a particualr app is confusing my phone. I don't think it's the ROM or modem I'm using (Frozen 1.2, EC05) as I did a stock flash and flashed to those just recently and others aren't having the same problem. I DID restore some data so if I can't narrow down an app that's causing it, not restoring any data is my next option (but even more time consuming to figure out specifically which data is causing issues).
I'm pretty sure the phone hasn't always done this so I don't want to exchange the phone considering I don't have any other issues and I think this is software, not hardware related. Has anyone experienced anything similar to this?
Have you tried switching Roms, I have this same problem on EC05 when I moved to gingerbread it stopped happening.......
Do you voodoo installed?
Sent from my SPH-D700 using XDA App
I was having the same problem with EF02 and the EF02/EF10 modems. I switched back to the EC05 modem and haven't had the problem since (knocking on wood)...
Sent from my Transformer TF101 using Tapatalk
Try ee03 modem..
Sent from my SPH-D700 using Tapatalk
masaidjet said:
Have you tried switching Roms, I have this same problem on EC05 when I moved to gingerbread it stopped happening.......
Do you voodoo installed?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I do have Voodoo installed (since it comes with Frozen 1.2). I haven't tried switching ROMs yet but I have started looking again (I was pretty content with Frozen but if no one had a similar issue and changing the modem doesn't work then a ROM switch is my next try).
Thanks to others who suggested changing modems - I'm going to do that now and see if EE03 fixes this....*crosses fingers*
evancg said:
I do have Voodoo installed (since it comes with Frozen 1.2). I haven't tried switching ROMs yet but I have started looking again (I was pretty content with Frozen but if no one had a similar issue and changing the modem doesn't work then a ROM switch is my next try).
Thanks to others who suggested changing modems - I'm going to do that now and see if EE03 fixes this....*crosses fingers*
Click to expand...
Click to collapse
Go into you Voodoo sound settings and change recording setting to Original. Shoul fix your issue.
Sent from my SPH-D700 using XDA App
Sure you are not hitting the mute button by accident? Sounds dumb but I've done that before.
Blankrubber said:
Go into you Voodoo sound settings and change recording setting to Original. Shoul fix your issue.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I have the SAME EXACT PROBLEM and just like the OP it hasn't always been like that, did this work for you?
Sent from my rooted, suited, & booted Epic 4G kno dat!
I was having the same issues so I just applied this. People couldn't hear me on speakerphone at all...seriously. hopefully this helps. Thanks for the tip
Sent from my SPH-D700 using XDA App
evancg said:
Basically, when I make or receive a call, within a couple\few minutes of the phone call the caller suddenly can't hear me - this happens whether it's using the phone normally, in speakerphone mode, or even a headset. As soon as it happens and the other caller starts the "Hello? Are you still there?" I can fix it by toggling the speaker on and off (or off and on) and it fixes it - but it can suddenly start again at anytime...couple of minutes later, five minutes later, etc.
Click to expand...
Click to collapse
Yes! Mine started doing this a couple months ago, and I resolve it exactly the same way (though I have to hit the volume button once, either up or down, then toggle speaker on then off). It's definitely not the ROM because I've had it with both Froyo and GB ROMs. Unfortunately, I haven't found any other solution, yet. I'm hoping it will go away with official GB, but I have no real reason to think it will work. I'm going to play around with the Voodoo sound.
edonnelly said:
Yes! Mine started doing this a couple months ago, and I resolve it exactly the same way (though I have to hit the volume button once, either up or down, then toggle speaker on then off). It's definitely not the ROM because I've had it with both Froyo and GB ROMs. Unfortunately, I haven't found any other solution, yet. I'm hoping it will go away with official GB, but I have no real reason to think it will work. I'm going to play around with the Voodoo sound.
Click to expand...
Click to collapse
you guys shouldn't be having this problem make a backup then odin to ec05 stock and check if you still have the issue if you do just take it to sprint and show the tech your problem they should fix it or get you a replacement phone.
I have the same issue. I am completely stock. It usually happens 10 to 15 minutes into a phone call. I've already called sprint, taken it to a store but only reflashed the os, and I just recently spoke to someone on chat, who said the problem has been solved. If it happens again should I get a replacement phone?
Blankrubbers fix actually worked for me
Sent from my SPH-D700 using XDA App
steviee7 said:
you guys shouldn't be having this problem make a backup then odin to ec05 stock and check if you still have the issue if you do just take it to sprint and show the tech your problem they should fix it or get you a replacement phone.
Click to expand...
Click to collapse
I had this problem as well. I odinned stock and problem solved. Now I'm back on bonsai with no problems.
Edit: I just noticed that I don't have voodoo sound installed, I know that I used to, maybe deleting that solved my problem and not odinning back to stock.
Sent from my SPH-D700 using Tapatalk
evancg said:
This has been happening on my Epic 4G for awhile now and it's really frustrating. I'm pretty sure this hasn't been happening the whole time I've owned the phone, but at this point it's hard to really remmber.
Basically, when I make or receive a call, within a couple\few minutes of the phone call the caller suddenly can't hear me - this happens whether it's using the phone normally, in speakerphone mode, or even a headset. As soon as it happens and the other caller starts the "Hello? Are you still there?" I can fix it by toggling the speaker on and off (or off and on) and it fixes it - but it can suddenly start again at anytime...couple of minutes later, five minutes later, etc.
Right now I'm slowly removing apps from my phone after every call this happens on - my goal is to determine if a particualr app is confusing my phone. I don't think it's the ROM or modem I'm using (Frozen 1.2, EC05) as I did a stock flash and flashed to those just recently and others aren't having the same problem. I DID restore some data so if I can't narrow down an app that's causing it, not restoring any data is my next option (but even more time consuming to figure out specifically which data is causing issues).
I'm pretty sure the phone hasn't always done this so I don't want to exchange the phone considering I don't have any other issues and I think this is software, not hardware related. Has anyone experienced anything similar to this?
Click to expand...
Click to collapse
speak up i can't hear you
Sadly even after changing modems and making the adjustment in Voodoo Control I still have the same problem. Going to uninstall Voodoo all together and see if that resolves anything.
I just discovered that I'm having the same problem after I Odin'd back to stock EC05 for a different reason. So, EC05 and EC05 modem, and I'm having a problem that I didn't think I was having before I tried EF02.
Could something have been changed that going back to EC05/EC05 modem didn't resolve?
Sent from my Transformer TF101 using Tapatalk
evancg said:
Sadly even after changing modems and making the adjustment in Voodoo Control I still have the same problem. Going to uninstall Voodoo all together and see if that resolves anything.
Click to expand...
Click to collapse
This problem is not generated by Voodoo. I have a stock Epic (rooted) and have never had Voodoo installed on my device and I have intermittently had this problem in the past (haven't seen it for a while, though). My friend has an Epic (never rooted) and also has this problem.
About the only thing I've heard that people have said fixes this is to wipe cache and dalvik and then flash something using Odin. Stock or custom I don't think matters.
As others have noted, uninstalling Voodoo didn't fix it for me. I think what must be causing this is everytime I wipe and install a clean ROM I restore some data through TiBackup and SOMETHING I'm restoring is causing this. Guess I'll just have to wipe and be very careful about what I'm restoring.
This might be completely random, but by chance did other people that experience this problem happen to install NZBAir?
I'm on calkulin's ROM and when i'm on the phone and I need to change the volume, I can't do it unless I pull the phone away from my face and the screen comes on. Only then does the volume change.
Is there a fix for this? It's extremely annoying.
bryank930 said:
I'm on calkulin's ROM and when i'm on the phone and I need to change the volume, I can't do it unless I pull the phone away from my face and the screen comes on. Only then does the volume change.
Is there a fix for this? It's extremely annoying.
Click to expand...
Click to collapse
I too have this "issue" Maybe we should post it on Calks thread?
Experiencing the same issue on UnNamed 2.0.1
Yeah I don't think this is a ROM related issue, as I recall this even when I was totally stock. If you notice the screen does go to sleep when you are on a call, then when you pull it away from your ear the screen is awaken. I think it has something to do with that.
I've been having this issue on all the EL ROMs but I don't remember it doing this in EK02.
I'm pretty sure it still did this on my stock EK02.
Nope it doesn't do that on stock EK02. That's what I'm running rooted and I can change my call volume while in a call and the screen is sleep..
Sent from my SPH-D710 using XDA App
Same issue on Blazer 3.9. Can't seem to work the "long press to skip track" feature either, coincidentally..
I get the same thing with the Blazer ROM 3.7. I think it is an EL29 error. :/
ghostrider0945 said:
I get the same thing with the Blazer ROM 3.7. I think it is an EL29 error. :/
Click to expand...
Click to collapse
It is not. Its already been established in another thread that this is only in custom roms. Something about a music mod is the cause of it. I can change my volume in call with any stock build.
Sent from my SPH-D710 using XDA App
Ever since I've flashed this rom and kernel, i've noticed bad sound quality while on a call. Especially if I'm plugged to my car stereo via aux- I have to turn up quite a lot than usual and I can still barely hear. The call quality through the hand set is a little more forgiving but the volume is lower than usual. Another thing I noticed is that when on a call, the call volume settings slide, but seems to be nonresponsive in regards to functionality (i actually turned volume way down during a call and remained the same volume). Any fixes or thoughts?
Could try flashing some different kernels and radios
Sent from my SGH-T999 using xda premium
Reflash the rom to overwrite that kernel. I use the same rom wit stock kernel and all is well.
Sent from my SGH-T999 using Tapatalk 2
liberalswine said:
Ever since I've flashed this rom and kernel, i've noticed bad sound quality while on a call. Especially if I'm plugged to my car stereo via aux- I have to turn up quite a lot than usual and I can still barely hear. The call quality through the hand set is a little more forgiving but the volume is lower than usual. Another thing I noticed is that when on a call, the call volume settings slide, but seems to be nonresponsive in regards to functionality (i actually turned volume way down during a call and remained the same volume). Any fixes or thoughts?
Click to expand...
Click to collapse
I had the same setup yesterday. I noticed the bad sound quality as well. It was fast but not as stable as with the stock kernel. I wiped cache and fix permissions after full day of use to see if that would help any and then my phone got stuck in a boot loop, lost recovery, and root. Had to flash samsung recovery and stock rom with odin.
Just a tip. But I never flash a kernel when trying a new build for at least the first day. That way if you have problems its much easier to tell if its rom or kernel related.
If you're running one of the jb based roms, djintrigue posted the stock kernels yesterday.
Flash one of those and see if it stops.
Sent from my SGH-T999 using xda app-developers app
My touch sounds randomly turn on. Running on stock rom and LI3 update. It's happened a few times now even after turning them off. Anyone else experiencing this?
Sent from my SPH-L710 using Tapatalk 2
Happens to me once in a while.
I think it's a bug that is triggered from opening the camera app. I believe all lg8 and LI3 stock and custom roms have this bug. Not sure if it still exists in the jb leak.
I have the same here, but I didn't notice it started until after I had tried a few different launchers and was uncertain which had caused it
Sent from my SPH-L710 using xda app-developers app
epic4GEE said:
I think it's a bug that is triggered from opening the camera app. I believe all lg8 and LI3 stock and custom roms have this bug. Not sure if it still exists in the jb leak.
Click to expand...
Click to collapse
Nope, it seems to be fixed in the JB leak. I've been on LIH for at least a week and haven't had it happen to me. Happened all the time on ICS.
This only happens to me when I re-boot my phone. Maybe it is a bug on one of the o.t.a. updates....????
This is my signature...
If your rooted with a custom recovery I made a flashable zip to completely remove the touch sound for ICS Roms. It just replaces the touch sound with a silent .ogg. Ill also include a zip to restore the touch sound if you decide you want to have it back. Just flash the zip in recovery, reboot and enjoy.
Remove Touch Sounds Zip - CLICK HERE
Restore Touch Sounds Zip - CLICK HERE
its a bug thats activated whenever you switch from taking a still photo then turning it onto video.
tool2269 said:
its a bug thats activated whenever you switch from taking a still photo then turning it onto video.
Click to expand...
Click to collapse
I just tried that...and the sound was still off. Oh well...who the faack knows why its happening....its just annoying.
This is my signature...
I still haven't rooted my note 2. I want to root and get custom roms but scared the roms might not have good battery like stock. I'm not sure what's you guys opinion?
Sent from my SGH-T889V using xda app-developers app
Everything gets better with custom roms
Sent from my SGH-T889 using xda app-developers app
Stock.
Sent from my SGH-T889 using Tapatalk 2
I have rooted every Android I ever owned including ny Note 2... This is the only phone I have unrooted and went back to fully stock. I am very happy with the way this phone runs stock.
Sent from my SGH-T889 using xda premium
I absolutely had in my mind I wasn't going to root etc. but im running the latest jedi rom and it is phenomenal!
Sent from my SGH-T889 using xda app-developers app
There are some cool features tied in with touch wizard specific to our pen capability. If you go custom you may lose that. So I would look more at rooting like such. Do I want root to bypass tethering lockdown from the vendor or to make backups with Titainium? Do I really need to overclock or undervolt? Do a new ROM's features negate the potential loss of pen related features
Sent from my GT-N7105
Im rooted running stock, tried jedirom 10 and had to pull the battery after every phone call. Still havent gotten an answer as to why this was happening. Went back to stock rooted and done with custom roms until this gets ironed out.....on a positive note, that jedi 10 with that kernel was flying and im very disappointed that I couldnt stick with it as it has awsome features.
zellroot said:
Im rooted running stock, tried jedirom 10 and had to pull the battery after every phone call. Still havent gotten an answer as to why this was happening. Went back to stock rooted and done with custom roms until this gets ironed out.....on a positive note, that jedi 10 with that kernel was flying and im very disappointed that I couldnt stick with it as it has awsome features.
Click to expand...
Click to collapse
I was running stock rooted since I got my phone late last December. But today I finally decided to run a custom rom and jedi 10 was it. Flashed with no problems and do not see the problem you have. The rom is really nice. Here are some features I would suggest rooting for:
1. Free wifi tethering (it's a must for me since T-mobile charges $15 for me to use data that I'm already paying for).
2. Wifi calling (good option to have in case I do not have signals) - the jedi 10 rom offers this.
3. Multi-windown (any app) - a cool feature. I don't think I will use it much though. But it's good to use to show off.
4. Samsung keyboard with auto-correct. I wanted to keep the samsung keyboard so that I can use the s-pen sometimes. But the jedi rom has the auto-keyboard switcher embedded.
??????
I rooted my phone I think but now I dont know what to do next! How do I pick a rom and where do I go to pick a rom or download one? Also what are kernals and overclicking?
SAMOANBK47 said:
I rooted my phone I think but now I dont know what to do next! How do I pick a rom and where do I go to pick a rom or download one? Also what are kernals and overclicking?
Click to expand...
Click to collapse
Before you do anything else, search "nandroid" learn all about it, and make one.
Sent from my SGH-T889 using xda premium
I was stock until about 3 days ago. I moved into the Jedi ROM. I used CWM, the non-touch version. I don't know if I'm old school or worried about a non responsive screen but eh.
Originally I'd just thought to stay stock and not rooted so I could get OTA'S. Though with a ROM, I'm already miles ahead of the game.
As another person stated, using the tethering has really been good for me. I'm paying $70 a month, $15 more for the hot spot would of been ridiculously overkill.
Also, I've never seen or witnessed a phone become so buttery smooth and perform so well. I'm happy. ^_^
Just make sure you do back ups through TiBu and do nandroids.
Sent from my SGH-T889 using Xparent Green Tapatalk 2
I rooted, went to Jedi ROM, but had issues, like screen tearing, slow response (probably aggressive underclocking) and some other weirdness. Went to Tweaked ROM, and had to pull battery after using CNN app for 5 minutes. Also phone is very slow to wake. Turning screen off makes music player unusable. I think I should go to stock, but I would love to have TSM Parts thing on it. Wonder if there's a way to install it.
Meanee said:
...Went to Tweaked ROM, and had to pull battery after using CNN app for 5 minutes. Also phone is very slow to wake. Turning screen off makes music player unusable. I think I should go to stock, but I would love to have TSM Parts thing on it. Wonder if there's a way to install it.
Click to expand...
Click to collapse
This would likely be better off reported in the Tweaked thread...
But, w/ the CNN freeze up (was this an app or website? Reading text or watching video/listening to audio?) was there any FC at all? What kernel were you using? What version of Tweaked were you running, and what sort of options did you have installed? A logcat of such an issue would be immensely helpful Also - were you charging the phone and have the MIUI battery bar active? On other phones I've experienced issues w/ video playback and that combo.
Turning screen off makes music player unusable - what do you mean? The long-press volume controls weren't working? The music stops? What app were you using to listen to music?
Very slow to wake - is there anything more specific you can offer here? Like an amount of time it takes to wake? That really shouldn't differ from stock at all - and there will always be a bit of lag there (though I never have anything more than a second or so).
And fwiw TSMParts is regrettably not an independently functional sort of apk. It requires a bunch of other edits throughout aspects of /system to actually work. But man that would be nifty
Fyi...noting what I said before, I am currently running one of Tesh's rooted stock ROMs for the international version. I can run backups, do tethering (no carrier lockdown for international), and run another kernel if I wish. It also allows me to use some of the Exposed installer tweaks to keep the Note2 touchwiz benefits and still use things like per app resultions and all apps in multiwindow.
Sent from my GT-N7105
dwitherell said:
This would likely be better off reported in the Tweaked thread...
But, w/ the CNN freeze up (was this an app or website? Reading text or watching video/listening to audio?) was there any FC at all? What kernel were you using? What version of Tweaked were you running, and what sort of options did you have installed? A logcat of such an issue would be immensely helpful Also - were you charging the phone and have the MIUI battery bar active? On other phones I've experienced issues w/ video playback and that combo.
Turning screen off makes music player unusable - what do you mean? The long-press volume controls weren't working? The music stops? What app were you using to listen to music?
Very slow to wake - is there anything more specific you can offer here? Like an amount of time it takes to wake? That really shouldn't differ from stock at all - and there will always be a bit of lag there (though I never have anything more than a second or so).
And fwiw TSMParts is regrettably not an independently functional sort of apk. It requires a bunch of other edits throughout aspects of /system to actually work. But man that would be nifty
Click to expand...
Click to collapse
I didn't really so a lot of troubleshooting. It was a CNN app. I pushed Back button from an article and got a black screen only with top bar active. Pushed power button, screen turned off. Then it stayed off. Had to do a battery pull. Not charging, no MIUI battery bar.
As for music, turning off the screen makes it stutter and slow down. Turning screen back on fixed the issue. I am guessing with screen off, clock rate is way too low to support music playback.
Very slow to wake could mean 2-3 seconds after I push the power or home button. Same thing with phonecalls. I can hear the phone ring but screen would stay black. 2-3 seconds later I can finally see who's calling.
I guess I can resolve most of these issues by tweaking clock rates, just wish I had time to read up on it.
Edit: Forgot to mention, I am on 1.4. Downloaded and flashed yesterday.
Meanee said:
I didn't really so a lot of troubleshooting. It was a CNN app. I pushed Back button from an article and got a black screen only with top bar active. Pushed power button, screen turned off. Then it stayed off. Had to do a battery pull. Not charging, no MIUI battery bar.
As for music, turning off the screen makes it stutter and slow down. Turning screen back on fixed the issue. I am guessing with screen off, clock rate is way too low to support music playback.
Very slow to wake could mean 2-3 seconds after I push the power or home button. Same thing with phonecalls. I can hear the phone ring but screen would stay black. 2-3 seconds later I can finally see who's calling.
I guess I can resolve most of these issues by tweaking clock rates, just wish I had time to read up on it.
Edit: Forgot to mention, I am on 1.4. Downloaded and flashed yesterday.
Click to expand...
Click to collapse
Hmm... my thoughts:
- That may have just been wonkiness in the CNN app - not sure if anything I did could impact something in the way you described (but of course I could be wrong).
- Yeah that is way slow - and uncharacteristic from my experiences at least
- That plus the music issue makes me wonder - are you just using the stock kernel? If so you can't do much in the way of clock rate tweaking, but I also find it curious as I've heard little in the way of issues regarding the stock kernel.
- Did you do a full data wipe before installing?
Regardless - I am sorry to hear about the poor outcome - feel free to PM me if you want any suggestions/help troubleshooting. I'm not the best at it (especially remotely), but I'll try
Sorry for the off-topic stuff OP!
The question doesn't make sense.
Rooting just means you unlock the root account on the phone to have superuser access. This is required by some useful apps (ProxyDroid, Paragon NTFS & HFS+ which lets you mount any USB stick or hard drive using an OTG cable, backup programs...). You can very well keep the stock firmware and just root it, which is what I ended up doing on the Note II.
On my previous Galaxy S2 CM10 was working like a champ, so I figured I would try it on the Note II... I think at this point it's a total disaster and completely unusable, just not ready for prime time. Bluetooth is completely broken, the camera doesn't work, the video driver has problems, and most of all you lose a lot of the cool things you get with the stock firmware (multi-windows, stylus-specific features, etc...). Good enough if you're contributing to the ROM development and testing for bugs and missing features, but painfully not ready for prime time. The big problem is that you just don't know what feature will break next and will let you down right when you need it.
So for me, it's stock until CM10.1 goes RC. But of course I rooted it because I want to be able to use some apps that require rooting.
Note that some Samsung apps (Readers Hub) detect SuperSU and refuse to run. Uninstall SuperSU and use Superuser instead, and use Voodoo OTA Rootkeeper to temporarily unroot the phone if you need to use them.
Rooted on Stock Rom is the way to go.
I stay on stock ROM for Wi-Fi calling, but I had it rooted in order to transfer application data.
Backup your efs as well, because there has been several people that have lost their imei.