[Q] Mokee OS v1.0, earphones dont work - LG Optimus 3D

ive just flashed this rom and think its really good, however when i have earphones plugged in the music cuts off after a few seconds, this is not a problem playing through speaker though, anyone have any idea what could fix this?

Check SetCPU
cwillaz said:
ive just flashed this rom and think its really good, however when i have earphones plugged in the music cuts off after a few seconds, this is not a problem playing through speaker though, anyone have any idea what could fix this?
Click to expand...
Click to collapse
Did this by chance happen after you closed lock screen? and do you have your CPU governor set to Hotplug?
Download SetCPU and use it to change your cpu Governor to Performance. This fixes the issue. Cyanogenmod has this issue and has had it since the alpha days.

ah right cool ill try thanks

Related

Updated findings: Bad audio out thru headphone jack to car fm transmitter

First off I'm not sure if this is the right forum for this and I also searched for the past few days and have had no luck finding anything much on this. Most stuff I come accross is talking about the phone having a built in fm transmitter that doesn't work - blah blah blah. So here goes, I'm now on Paul's Froyo ROM and for the first time decided to try using the phone for playing music in my car thru a wired fm transmitter and it was not good. I now have three fm transmitters (2 I bought and the final one my brother gave me his that he used to use in his car with no problems) all give me the same results which is it seems okay playing through parts of songs that don't have much bass but once bass starts to hit it gets all awful stattic sounding and the Stereo (ST) indicator on my radio blinks so somehow the sound quality goes all bad. I've narrowed it down to obviously being something with the phone somehow cause I've tried with iPhones and another MP3 player and they (FM transmitters) work perfectly. I've also tried it with IntersectRaven's and CM's kernels for Froyo to see if the kernels might make a difference and no luck. So my question is, is this a known issue with the N1 or is this an issue with Froyo and isn't the case with say CM 5.0.7.1, anyone with experience can shed some light? Was thinking to go back to CM but after seeing all the threads of the issues in doing so decided not to but if this is not the case with other ROMs then it would make me switch back until a official Cyanogenized Froyo is out. If this is the wrong forum then my apologies and Dev's plz move to correct forum.
Update: I've messed with it some more and have been able to get it to play fine with Pershoots kernel but I have to turn down the media volume to approximately 70%. So it seems to me that with the media volume up all the way it must be drawing too much power or something from the headphone jack to make the output all distorted. I haven't tried with IntersectRaven's kernel to say if I get the same result since I'm just happy the darn thing works now. I'll also do a post in the Develoment forum linking to this in case anyone there may want to investigate this issue.
Sounds to me like every experience I've ever had with every FM transmitter. They just don't transmit loudness or bass well. I don't think it's the phone, I think its the FM Transmitter technology.
edit: could just be the volume boost or something on the specific kernel (not even sure if the kernel's you are talking about have a volume boost) but that may increase the max volume out and cause the problem.
derfasaurus said:
Sounds to me like every experience I've ever had with every FM transmitter. They just don't transmit loudness or bass well. I don't think it's the phone, I think its the FM Transmitter technology.
edit: could just be the volume boost or something on the specific kernel (not even sure if the kernel's you are talking about have a volume boost) but that may increase the max volume out and cause the problem.
Click to expand...
Click to collapse
yes exactly, try a vanilla kernel and see how that plays out... I am curious of your findings...
Kman Gymrat said:
First off I'm not sure if this is the right forum for this and I also searched for the past few days and have had no luck finding anything much on this. Most stuff I come accross is talking about the phone having a built in fm transmitter that doesn't work - blah blah blah. So here goes, I'm now on Paul's Froyo ROM and for the first time decided to try using the phone for playing music in my car thru a wired fm transmitter and it was not good. I now have three fm transmitters (2 I bought and the final one my brother gave me his that he used to use in his car with no problems) all give me the same results which is it seems okay playing through parts of songs that don't have much bass but once bass starts to hit it gets all awful stattic sounding and the Stereo (ST) indicator on my radio blinks so somehow the sound quality goes all bad. I've narrowed it down to obviously being something with the phone somehow cause I've tried with iPhones and another MP3 player and they (FM transmitters) work perfectly. I've also tried it with IntersectRaven's and CM's kernels for Froyo to see if the kernels might make a difference and no luck. So my question is, is this a known issue with the N1 or is this an issue with Froyo and isn't the case with say CM 5.0.7.1, anyone with experience can shed some light? Was thinking to go back to CM but after seeing all the threads of the issues in doing so decided not to but if this is not the case with other ROMs then it would make me switch back until a official Cyanogenized Froyo is out. If this is the wrong forum then my apologies and Dev's plz move to correct forum.
Update: I've messed with it some more and have been able to get it to play fine with Pershoots kernel but I have to turn down the media volume to approximately 70%. So it seems to me that with the media volume up all the way it must be drawing too much power or something from the headphone jack to make the output all distorted. I haven't tried with IntersectRaven's kernel to say if I get the same result since I'm just happy the darn thing works now. I'll also do a post in the Develoment forum linking to this in case anyone there may want to investigate this issue.
Click to expand...
Click to collapse
what you are describing is quiet normal if you drive the input of the fm transmitter too hard. You even found out the solution; lower the volume.
Yeh, but the thing that was baffling me was that the iPhones I tried worked fine with volume blasted and so did a MP3 player and that was with 3 different FM transmitters. I originally thought it was the transmitter so that's why I ended up buying another one to try then asking my brother for his which I know he used to have running with no issues. But after thinking about it for a while and searching some more I found posts in the kernel threads about audio boost so that's what made me think to turn the volume on the phone down.
Would like to try a vanilla kernel if you can link me to where to find one that's compatible with Froyo.
And actually I think I'm using CM's Froyo kernel but from what I understand it has pretty much the same tweaks as Pershoot's. Also need to go back to IntersectRaven's and try again with the vol down a bit but I don't have enough battery life left to feel comfortable flashing it.
For the FM-transmitter that I use in my car it's actually stated in the manual that you should keep the volume at about 50% on the device as to not ruin the sound. So I guess this is quite normal and just means you have to adjust the volume on the car stereo a bit.
Kman Gymrat said:
Yeh, but the thing that was baffling me was that the iPhones I tried worked fine with volume blasted and so did a MP3 player and that was with 3 different FM transmitters. I originally thought it was the transmitter so that's why I ended up buying another one to try then asking my brother for his which I know he used to have running with no issues. But after thinking about it for a while and searching some more I found posts in the kernel threads about audio boost so that's what made me think to turn the volume on the phone down.
Would like to try a vanilla kernel if you can link me to where to find one that's compatible with Froyo.
And actually I think I'm using CM's Froyo kernel but from what I understand it has pretty much the same tweaks as Pershoot's. Also need to go back to IntersectRaven's and try again with the vol down a bit but I don't have enough battery life left to feel comfortable flashing it.
Click to expand...
Click to collapse
All kernels are compatible with froyo, just go to the kernels thread and find a sock one

Persistant Volume Issue in Gingerbread

Quoting from another thread, apparently I'm not the only one with this issue so I'd like to dedicate this thread to finding a possible fix (PS, if someone can suggest a better title let me know).
open1your1eyes0 said:
Hmm maybe it's just me but I think I discovered the oddest bug ever. For some reason, the first sound I hear after like 30 seconds of idle is quieter than what I'm set to in the volume settings and then if I keep using the device without idle all the sounds are loud like normal after that first sound.
For example, I have the device locked with screen off for a while, I unlock the device and the unlock sound is really quiet, then I immediately lock it and unlock it again and now the sound is loud like normal. I keep doing that and it sounds fine each time after that, but as soon as I lock it and leave it idle for like 30 seconds or more and unlock it again, the unlock sound is quiet again.
Also this doesn't only affect the unlock sound, it affects everything, notifications, alarm, ringer, etc....and all my volume is set to maximum I even checked with a 3rd party app. The same thing happened on the previous 2.07 and 2.10 leaks, it's almost like Gingerbread introduced this weird "automatically lower master volume after idle mode". I can't seem to find any option that would affect it.
Click to expand...
Click to collapse
So basically the first sound you hear after a short or long idle time will always be quieter than your actual setting and then keep using the device and everything sounds normal. I almost overslept and missed calls several times cause my alarm and ringtones are so quiet now.
Anyone have any ideas what could be done or taken a look at here?
EDIT: FYI, someone else claimed they had it since MR1 update but I had no issues on Froyo whatsoever. This only became introduced to me with the first 2.07 leak.
I've noticed this as well. I didn't find it to be a big deal, but thought I'd share.
Sent from my HTC CyanogenBolt powered by CyanogenMod 7 RC1.6.1
all i know is even with volume+ the volume sucks on this phone. my wife's lg vortex is 5x louder. we need a dev to look into this.
I honestly thought I was alone on this one. I miss texts and calls all the time because the volume is so quiet after idle.
It is easy to see this with gingeritis all you have to do is turn the volume up to max for your ringer, and then turn the screen off and let it sit for a minute or two. Then turn the screen back on and push the volume up key, you will notice the first sound it makes is really soft, and if you push it again, it makes the normal loud sound.
I hope someone sheds light on this...I for one would like to stop missing calls
I am about to try the official RUU and see if it still does it, but it's only done it since I started using gingerbread roms.
arunningpir8 said:
I honestly thought I was alone on this one. I miss texts and calls all the time because the volume is so quiet after idle.
It is easy to see this with gingeritis all you have to do is turn the volume up to max for your ringer, and then turn the screen off and let it sit for a minute or two. Then turn the screen back on and push the volume up key, you will notice the first sound it makes is really soft, and if you push it again, it makes the normal loud sound.
I hope someone sheds light on this...I for one would like to stop missing calls
I am about to try the official RUU and see if it still does it, but it's only done it since I started using gingerbread roms.
Click to expand...
Click to collapse
aosp roms are louder but not loud enough. we for sure need a volume boost. i cannot imagine it would be that hard to do.
I was just getting ready to start a thread about a possible volume booster.. I can't remember if it was the tb or fascinate i had it on but, adrynalyne had a program called drm i think in his roms that enhanced the volume.. the problem I'm having is the media volume.. I'm trying to listen to MLB at bat here at work but can barely hear the broadcast.
Sent from my ADR6400L using XDA App
Hmm volume booster does seem to be a good workaround idea but I think the main issue is the fact that the volume level automatically changes regardless of the volume loudness. If only someone might be able to figure out what this can be caused by.....
Also I noticed something interesting today. On some sounds it actually seems like it starts off quiet and then makes it louder while the sound is playing. It's hard to tell cause it's so fast but it's definitely noticeable in some cases.
On cm7 there is an option to play notifications and ringtone through the speaker (even though I thought they did anyway) but I haven't noticed the problem with that selected.
Sent from my HTC CyanogenBolt powered by CyanogenMod 7 RC1.6.1
someone should look into the lg vortex volume and try to port the mod over. my wifes phone is 10x louder than my tbolt. hers is aosp too.
FYI, I have only tested this on the official leaks. No custom ROMs or AOSP yet. Though I'm quite tempted to find out if this occurs on other ROMs as well (especially AOSP).
open1your1eyes0 said:
Quoting from another thread, apparently I'm not the only one with this issue so I'd like to dedicate this thread to finding a possible fix (PS, if someone can suggest a better title let me know).
So basically the first sound you hear after a short or long idle time will always be quieter than your actual setting and then keep using the device and everything sounds normal. I almost overslept and missed calls several times cause my alarm and ringtones are so quiet now.
Anyone have any ideas what could be done or taken a look at here?
EDIT: FYI, someone else claimed they had it since MR1 update but I had no issues on Froyo whatsoever. This only became introduced to me with the first 2.07 leak.
Click to expand...
Click to collapse
It takes a split second for the audio amplifier to fire up. The kernel is probably not accounting for this. The audio amplifier suspends after usage just like the screen does to prevent battery drain.
Sent from my A501 using Tapatalk
nelboy said:
It takes a split second for the audio amplifier to fire up. The kernel is probably not accounting for this. The audio amplifier suspends after usage just like the screen does to prevent battery drain.
Sent from my A501 using Tapatalk
Click to expand...
Click to collapse
Hmm that's an interesting theory but just FYI, the screen times out later than the volume begins to idle to quiet (if it matters). You think flashing another kernel might fix the issue?
open1your1eyes0 said:
Hmm that's an interesting theory but just FYI, the screen times out later than the volume begins to idle to quiet (if it matters). You think flashing another kernel might fix the issue?
Click to expand...
Click to collapse
Sorry. I didn't mean they time out at the same time. Just meant that it also suspends to save battery. I have a feeling this won't be solved until the gingerbread sense kernel source is released. A really good kernel dev might be able to look into this with their current source. You might also notice a pop or crackle sound due to this same issue. Again it is coming from the amplifier powering up WHILE the audio is playing instead of BEFORE. There could be an underlying latency in the hardware but I doubt that's true since it wasn't really noticeable on Froyo. Android has always had a problem with audio latency although it has been pretty much "worked around".
Sent from my A501 using Tapatalk
nelboy said:
Sorry. I didn't mean they time out at the same time. Just meant that it also suspends to save battery. I have a feeling this won't be solved until the gingerbread sense kernel source is released. A really good kernel dev might be able to look into this with their current source. You might also notice a pop or crackle sound due to this same issue. Again it is coming from the amplifier powering up WHILE the audio is playing instead of BEFORE. There could be an underlying latency in the hardware but I doubt that's true since it wasn't really noticeable on Froyo. Android has always had a problem with audio latency although it has been pretty much "worked around".
Sent from my A501 using Tapatalk
Click to expand...
Click to collapse
Hmm I see. FYI, I also noticed this issue is extremely obvious when opening the phone dialer for the first time and just press like the number 1. You can hear for a split second as if it "boots up" the audio amplifier the dialing sound for the button grows from silent to normal volume. Then as you dial the rest it sounds fine. But cancel out of the phone dialer and back into literally after like as short as 5 seconds press a number on the dialpad again, you hear it making dialing sound quiet to louder and then normal for the rest of the dialing.
Such a bizarre issue, I really don't understand why this problem just occurred in Gingerbread builds if it's been absolutely fine on older Froyo builds. You would think something as obvious as this would be one of the first bugs they try to resolve. And it seems like it wouldn't be that hard also (assuming it's just a setting in the kernel coding or something).
FYI, if it helps anyone willing to look into it I found out the audio amplifier for the Thunderbolt is a TI TPA2051.
I am really hoping some of our higher up guys can take a look at this. I am really curious to know what (if anything) can fix this issue.
i do know the overall volume on sense roms are much quieter than aosp. what a waste of a good speaker. we for sure need a fix here.
It might not be as easy as it sounds. Audio can be handled quite differently from OEM to OEM. I'm not sure if the thunderbolt is using the native Android audio or if HTC is using their own implementation. You also have to throw the audio Codec into the mix. Here is a link that although it doesn't explain our specific problem, you can see the complexity and the inherent issues with Android audio http://groups.google.com/group/android-ndk/browse_thread/thread/1744088af0924ed9/7170773c13aabe2f i'm not sure about now but the general consensus with audio developers used to be that google needed to stop trying to implement fancy bells and whistles in the audio and get a good solid foundation to start with. Gingerbread was supposed to address some of these issues but I don't believe it did.
Anyway, i'm not positive but you may notice the problem more in gingerbread because there were quite a few changes in the native audio implementation.
Sent from my A501 using Tapatalk
nelboy said:
Sorry. I didn't mean they time out at the same time. Just meant that it also suspends to save battery. I have a feeling this won't be solved until the gingerbread sense kernel source is released. A really good kernel dev might be able to look into this with their current source. You might also notice a pop or crackle sound due to this same issue. Again it is coming from the amplifier powering up WHILE the audio is playing instead of BEFORE. There could be an underlying latency in the hardware but I doubt that's true since it wasn't really noticeable on Froyo. Android has always had a problem with audio latency although it has been pretty much "worked around".
Sent from my A501 using Tapatalk
Click to expand...
Click to collapse
Gingerbread Kernel Source for Thunderbolt just released: Link
I know this thread is old, but something i've noticed in regards to this. Im running a semi-stock ROM (xda-bolt), with a stock kernel. I noticed the volume changes don't happen on this ROM, however with a modified kernel such as IMOs 6, the problem arises. Any other non-stock kernel i've used has this problem, but stock kernels do not.

SynergyRom Static Noise

I just updated to Synergy ROM r290 and I am getting static noise in my headphones. The static noise can be best heard through Bluetooth headphones with the volume up on both the phone and the Bluetooth headphones. I switched out headphones to wired ones and can still hear it but it is more faint. I tried playing it through my cell phone speakers and it's there too but faint so I know it's the ROM. Any suggestions for a fix?
Do you notice it more when the device is idle or the screen is off? It might be a voltage issue. Try flashing LeanKernel. Or try boosting voltages on Ziggy kernel.
BattsNotIncld said:
Do you notice it more when the device is idle or the screen is off? It might be a voltage issue. Try flashing LeanKernel. Or try boosting voltages on Ziggy kernel.
Click to expand...
Click to collapse
I really can't tell the difference when the screen is off or on but i'll try to flash to LeanKernal after i figure out how to do it. I'm very new to this so i probably won't get to it until later this weekend. Thanks for your suggestion.
Could someone tell me how to access Leankernal or ZiggyKernal to change voltage? I've never done it before and what voltage should i change my phone too?
cetaphil said:
Could someone tell me how to access Leankernal or ZiggyKernal to change voltage? I've never done it before and what voltage should i change my phone too?
Click to expand...
Click to collapse
we all hav different settings for it but will say he has it set already but try pro tuner
wingtytn said:
we all hav different settings for it but will say he has it set already but try pro tuner
Click to expand...
Click to collapse
Thanks for your help. I flashed back to 169 and my music works fine now. I tried r326, r290, and r257 but they all had static noise on my blue tooth headset. Dalvik cache and cache partition were the only things that i did a wipe on.

Sound clipping issue.

I've got this really annoying issue that I keep somehow getting rid of, but it comes back on it's own.
Any sound that plays from the phone e.g. Ringtones, YouTube, Poweramp, etc...
The audio levels get clipped, like something is trying to adjust the gain of the sound, parts that should be loud are not loud, but instead clipped to a really low level.
I've disabled AudioFX, cleared the data for it, and disabled the audio settings within Poweramp.
I've tried to get an example of it with my camera, but of course it's not doing it when I pull out the camera, next time Poweramp does it, I'll record it.
If I receive a call it clips the ringtone sometimes, but I tried calling the phone a second time and it didn't clip.
Really don't know what's going on, just want the audio to work properly.
I'm on 33R, Unlocked Bootloader Rooted.
If anyone knows how to fix this, I'd be really happy.
Could anyone also recommend an app that's like Poweramp, but free? I like it, but it's not quite right.
Removed Poweramp and the problem appears to be gone.
Even though I had all the audio settings disabled in Poweramp?
Still having the issue...
I have no idea what to look for now.
I seem to be having the same issue occasionally. It doesn't bother me overly much though. I just don't think the internal speakers of of the highest quality but everything else on this device is superb
I do however believe at least some of the issue is caused by the fact the the speaker grill holes are quite small so when the volume is high a lot of air pressure is created in the speaker cavity which may attribute to the the problem.
It's purely software.
Happens with the volume at 50% as well.
I have this issue too. Thought it was my headphones so tried all my pairs and it happens on all of them. Its an issue the Nexus 5 has as well and it has to do with how the phone handles the signal from the towers from you're carrier. As to my knowledge there is no fix for it yet.
https://github.com/anarkia1976/AK-OnePone/commit/8babaa621600e5b9e4614537aa75dd64988c9288
I switched to SlimKat ROM, haven't had the issue since my last post in this thread.
ak said:
https://github.com/anarkia1976/AK-OnePone/commit/8babaa621600e5b9e4614537aa75dd64988c9288
Click to expand...
Click to collapse
So are the working on a fix or how do we fix it? Because its annoying af.
Just wanted to report in again.
Still haven't had the audio clipping issue since switching to SlimKat.
The audio issue was really the only reason I had to even bother trying a ROM other than CM11S.
My experience with SlimKat on I9300 was a no-brainer to be the first ROM to try on my One.
Borgschulze said:
Just wanted to report in again.
Still haven't had the audio clipping issue since switching to SlimKat.
The audio issue was really the only reason I had to even bother trying a ROM other than CM11S.
My experience with SlimKat on I9300 was a no-brainer to be the first ROM to try on my One.
Click to expand...
Click to collapse
Running PA 4.6 Beta and its horrible. I can't stream one song on Spotify with out it clipping through. May be downloading SlimKat tonight to give it a go.
I still get the clipping on Slimkat, battery life is great tho.
Which build? I'm on Stable 7.0
When I call someone, the ringing sounds kind of funny, but other than that, every other sound works perfect so far.

[Q]Audio playback choppy when screen off

I listen to allot of online radio eg 'tunein' and mp3 stored on my phone, problem is that this phone plays back audio choppy when the screen times out.
This happeneds esspecially when streaming audio - its intermittent with mp3s..I have had allot of phone and Ive never ever had this kinda problem before...
Im rooted and have played with the stock kernel settings abit but have no change in behavior,.. Anyone know what I can do here? I hate to have one of the most advanced unusable phones ever
JF-GINO said:
I listen to allot of online radio eg 'tunein' and mp3 stored on my phone, problem is that this phone plays back audio choppy when the screen times out.
This happeneds esspecially when streaming audio - its intermittent with mp3s..I have had allot of phone and Ive never ever had this kinda problem before...
Im rooted and have played with the stock kernel settings abit but have no change in behavior,.. Anyone know what I can do here? I hate to have one of the most advanced unusable phones ever
Click to expand...
Click to collapse
When I was on my Note 2 I had to increase the low end on the cpu speed. I think the Lowest I could use was 400 to 500 (sleep mode) I own the setcpu pro app so it was easy to adjust. Give that a look see. Every time the screen went off while Bluetooth was on it would skip and shutter. I noticed today my Edge seems to have the same problem.
Charles
ceabbott2 said:
When I was on my Note 2 I had to increase the low end on the cpu speed. I think the Lowest I could use was 400 to 500 (sleep mode) I own the setcpu pro app so it was easy to adjust. Give that a look see. Every time the screen went off while Bluetooth was on it would skip and shutter. I noticed today my Edge seems to have the same problem.
Charles
Click to expand...
Click to collapse
Hey, you too eh? hmm,.. I tried raising the cpu limit with no change,.. mine does stay awake on bluetooth only... anywho, there is not much I can do with the stock kernel., I tried just about everything, scripts, build hacks,.. no I noticed that Wifi does not stay connected and only gets max 3mps - Ive been thru 2 phones and this Canadian version is buggy, have no problems with my note 3 or my LG , wish I could figure all this out. or wait for a custom rom/kernel for my variant
JF-GINO said:
I listen to allot of online radio eg 'tunein' and mp3 stored on my phone, problem is that this phone plays back audio choppy when the screen times out.
This happeneds esspecially when streaming audio - its intermittent with mp3s..I have had allot of phone and Ive never ever had this kinda problem before...
Im rooted and have played with the stock kernel settings abit but have no change in behavior,.. Anyone know what I can do here? I hate to have one of the most advanced unusable phones ever
Click to expand...
Click to collapse
Make sure power saving mode is off if not try turning that off and it may resolve the issue.
Also like in one of my previous posts on my device anyway I've been experiencing what I'd describe as antenna issues. Both wifi drops and blue tooth cuts in and out. Doesn't matter if the screen is on or off for me
when I experience these issues.

Categories

Resources