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.
Related
Hi,
Does anyone know a way to tweak a system file so that Inspire's volume is higher?
I personally find its stock volume rather low, and I want to increase it.
I downloaded Zedge. It is a free app with nice louder ringtones.
Hope this helps!
I'm wanting to up the volume system-wide. But, thanks for the info anyway
Yea, I tested a movie and sling player last night. The media volume was all the way up and it was quite.
I went from iPhone 4 (nice and louad) to Atrix 4g (nice and loud) to Inspire 4g (too quiet).
I am loving the Inspire but the sound volume and battery life are definitely the 2 big downsides of it. Still a winner over the Atrix any day though.
I personally don't have issues with the battery. I've removed all extra stuff. Even before removing them, I was happy with its battery.
It can't be that hard to change the system volume. It's done in every smartphone and OS before. Hopefully, some developer notices this thread and help us out.
goldentequila said:
I personally don't have issues with the battery. I've removed all extra stuff. Even before removing them, I was happy with its battery.
It can't be that hard to change the system volume. It's done in every smartphone and OS before. Hopefully, some developer notices this thread and help us out.
Click to expand...
Click to collapse
+1
I'm half deaf. Need a louder phone please.
same here, the phone volume is too low. Maybe if can acces service codes? I did it on my previous Samsung phone.
Hi, all.
So, I've been doing some digging around, and looks like there are 2 possibilities.
One is to modify the system files manually (which would be very complicated), but I personally prefer this method rather than having to install extra stuff. However, this method is not available to us unless some very smart person shares the method with us.
Two, which seems to be the only viable option at the moment, is DSP Manager. As far as I understand, it used to be available through ROM Manager, but it is no longer there. I saw a thread that said the author was not releasing it anymore because most MOD developers were now including it in their ROMs from the beginning.
So, if we can find a way to install DSP Manager, we may be able to tweak the max speaker volume. But, that's as far as I could find. I'd need someone smarter to look into this.
Hi,
An update and a new idea.
First, DSP Manager doesn't work on Inspire 4G, so don't bother.
Second,
Here's a new idea I have about the low volume sound fix. I just read a comment from HTC employee who said, "The front speaker is for phone calls and the rear speaker is for everything else."
In other words, if we can find a way to keep the front speaker enabled all the time, we should be able to get more sound. I don't know much about what kind of coding is involved in routing sounds from each speaker, but I wonder if this would be an easier hack than trying to increase the entire system volume, which may still feel low volume for as long as we can't get any sound out of the front speaker.
Maybe someone smart can add to this possibility?
#1! I like to use voice recordings as scheduled reminders, and the playback volume out of the rear speaker is way too low.
I did notice the low volume on a movie i downloaded but you never can tell with those sorts of things. Overall the sounds is incredible even through the speakers with (SRS) and dolby mobile.
Could use something to ++output level.
Id like to see an app to change audio volume levels while recording video.
(ive only had the phone a couple days i returned my samsung Cap upgrade for the 4g, forgive me if there is such an app out there)
How often do you go to watch an awesome looking concert video and the sound is trash? It would make for some beautiful recordings i think. I have yet to test this one, but the Captivate could not record decent sound at all in loud environment.
I personally have come to believe that it is really not that the "volume" is low but rather a "wrong" speaker is being used. I mean, if the main speaker is on the back facing away from us, of course we don't hear much sound. If you flip the phone while playing music or video, you'll notice that the sound is actually loud enough. So, if we can enable the front speaker for normal use, I really think that it'll be just fine.
about every HTC phone has a quiet speaker. but cyanogen typically always includes the audio boost add-on. so i'd just wait for cyanogen 7 to include it, and your troubles will be solved.
well, even if the volume is boosted, as long as the sound is coming out of the rear speaker, if you place your phone on its back on a table or something, the sound will still suffer. It makes more sense to find a way to enable the front speaker.
Most of all phone have a rear facing speaker. But some phone are loud and some are not..
Sent from my Desire HD using XDA App
goldentequila said:
well, even if the volume is boosted, as long as the sound is coming out of the rear speaker, if you place your phone on its back on a table or something, the sound will still suffer. It makes more sense to find a way to enable the front speaker.
Click to expand...
Click to collapse
+1 this would be quite useful!
kwin_captivate said:
Most of all phone have a rear facing speaker. But some phone are loud and some are not..
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
No, they don't lol. (you may be right if you are talking about specific brand or series, but certainly not "most of all phones").
I just came across something that may be relevant to the audio routing, but I'm not smart enough to figure them out. If anybody wants to take a look at it, it would be great:
http://developer.android.com/reference/android/media/AudioManager.html
There are several lines there that talk about Routing.
GT
This may sound ridiculous but works!
Hi, all.
I just came up with a very simple workaround for "only when you are watching a video or something."
Now, you're gonna probably laugh, but trust me. It really works.
Just play any video, and hold your phone as if you are scooping water. The key is the left hand. When you cup your left hand around the rear speaker, it creates a echoing chamber that redirect all sound toward you. You'll be able to hear the sound much better.
GT
I have three days to change my G2x for the Nexus S.
I need to know whether putting ANY custom ROM/root/whatever can fix every single problem with this phone:
Battery life drain
Software bugs
MOST IMPORTANTLY (why doesn't anyone care/notice?!): NOISY HEADPHONE JACK OUTPUT
Is this problem entirely software, or partly hardware? I have such minimal LCD bleed that its not noticeable.
Please chime in and check my thread on noisy output and take my FIVE SECOND test with your modded device to tell all of us whether it is fixed or not.
nevermind.
Using CM7 + Faux's EXT4 undervolt Kernel + GPS fix pretty much makes this phone perfect for me. I have absolutely no issues at all EXCEPT for screen bleed. That cant really be fixed with software though. Battery life is great. Yesterday I didn't use my phone much but I went OVER 24 hours on one charge. Didn't plug it in once. Woke up this morning and it still had about 15%. Of course I turned off data while I slept though so that probably helped a lot.
voodoo takes care of the headphone jack noise. in fact i've never ever experienced music with low of a noise floor below
adevilfish said:
voodoo takes care of the headphone jack noise. in fact i've never ever experienced music with low of a noise floor below
Click to expand...
Click to collapse
Can you please elaborate and confirm that you noticed the exact same noise as I described (for a second after any sound stops, or during a completely silent track playing?) And voodoo took care of it? So it is software causing the noise and not hardware?
I'm finally at peace with my G2X and it is solid reliable. ****ty battery life but what can you expect.
In my case my phone did have reboots and freeze while charging. I still don't trust having this phone charging overnight because it might crash.
Also went and deleted both Internal/External SD and properly WIPE like 5 times. Flashed CM7 RC1 + Google apps and fixed permissions. I had issues where email syncs failed after 8+ hours but after doing this full clean flush and Wipe, this piece of **** phone finally is reliable.
Its solid and finally enjoying the phone. Just need CM7 out of RC and I'm golden.
However, every time I went to stock I had issues. If you don't plan on Rooting/Flash don't bother with this phone. Its a piece of crap and LG sucks at making ROMS.
I love my phone but I reccimend you get the nexus S. I'm sorry, its just a better phone.
Ps....Please don't ostracise me from this forum lol.
Sent from my LG-P999 using Tapatalk
britishtomquin said:
I love my phone but I reccimend you get the nexus S. I'm sorry, its just a better phone.
Ps....Please don't ostracise me from this forum lol.
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Software-wise, yes. It's a better phone... Hardware-wise, HELL NO!
CM7 with Trinity kernel gets 24 hours of battery and no reboots from my experience.
Sent from my Nexus 5g using XDA Ultimate App
youd be a fool to trade for that phone... yes every problem fixed.. no problems for awhile for me... love my phone..
I have to agree. The G2x is a million time better then the Nexus S. The Nexus doesn't even do 4G.
The Nexus S is last generation, the only competition for the g2x is the htc sensation and the samsung galaxy s2.
Sent from my Nexus 3 using XDA Ultimate App
KingDavid63 said:
youd be a fool to trade for that phone... yes every problem fixed.. no problems for awhile for me... love my phone..
Click to expand...
Click to collapse
Long live the King!
G2x - July baseband/radio, Cm7 Nightlies, Faux OC/uv Kernel, Launcher Pro, Straight Beast Status! No Bugs! Smooth as my ps3 or 360 on gaming... gameloft is making some killer gamez... I love this phone... It's a sense or no sense issue if you ask me... I like both.. My last phone was the htc glacier i gave to my momma, it was a good phone... I wanted a senseless device and im glad i got this one.. not another 6-8 months down the road when the next 1.3+ Ghz batch of phones comes out i might go back to sense, but im completely content where im at right now with the g2x with the games and now netflix... dont get no better.. maybe the sgs2 but that's the most powerful phone in the world as far as buyin out the store... but the sensation.... NO!
k00zk0 said:
Can you please elaborate and confirm that you noticed the exact same noise as I described (for a second after any sound stops, or during a completely silent track playing?) And voodoo took care of it? So it is software causing the noise and not hardware?
Click to expand...
Click to collapse
I've never had a noise issue with the Jack and I use my g2x like an iPod. Battery life sucks but with Google music its been awesome. I've also been using the leaked gb off LG the only thing with that is now I can't seem to root my phone.
Sent from my LG-P999 using XDA App
I don't notice noise. I plug my G2x into my surround and crank it. Sounds like any other device I've owned (ipad2 being one of them)
LG G2x - Miui
www.SnapSiteAdmins.com
www.MiiWiiChat.com
NVfllash cwm and then install or restore rom = root...
So after getting CM7 and Faux's OC/UV/etc/Voodoo kernel I still have noise with the sound. Do I need the Voodoo app to enable a different kind of processing or something? I cleared 3x caches/data, installed .zips: CM7 b89, gapps, and Faux [2.6.32.41] (v0.3.4) before restarting.
This makes the sound even more apparent: Go to a silent place and turn the volume on the phone all the way down to vibrate. Put the speaker at the bottom right into your ear and push volume up once. You'll hear the quiet boop tone and a second of very loud hiss before it cuts out. Wait until the sound disappears after two seconds to notice that it was even there in the first place, before pushing the volume button again. It even turns the amp on when you set it to vibrate and there is no tone played. Two new units fresh out of the box have had this same noise. I can't believe users, especially devs don't notice this or see it as irregular, so I must be doing something wrong with Voodoo, and every unit in Canada is the same hardware-faulty. I've got three hours to swap it for the nexus; a primary use for this phone would be monitoring detailed music, and this is an unacceptable level of noise. Please try this and let me know if it's every unit or just every one in Canada, and if the 3 dollar Voodoo app is necessary to fix it!
k00zk0 said:
So after getting CM7 and Faux's OC/UV/etc/Voodoo kernel I still have noise with the sound. Do I need the Voodoo app to enable a different kind of processing or something? I cleared 3x caches/data, installed .zips: CM7 b89, gapps, and Faux [2.6.32.41] (v0.3.4) before restarting.
This makes the sound even more apparent: Go to a silent place and turn the volume on the phone all the way down to vibrate. Put the speaker at the bottom right into your ear and push volume up once. You'll hear the quiet boop tone and a second of very loud hiss before it cuts out. Two new units fresh out of the box have had this same noise. I can't believe users, especially devs don't notice this or see it as irregular, so I must be doing something wrong with Voodoo, and every unit in Canada is the same hardware-faulty. I've got three hours to swap it for the nexus; a primary use for this phone would be monitoring detailed music, and this is an unacceptable level of noise. Please try this and let me know if it's every unit or just this one, and if the 3 dollar Voodoo app is necessary to fix it!
Click to expand...
Click to collapse
I had never noticed the issue before, but when performing your test I hear it. This isn't a precisely calibrated, professional audio-phile level piece of equipment. For most people, this would not be an issue. If it is for you, then this is likely not the device for you.
The only thing I really don't like about the Galaxy S4 is that the vibration is fairly weak. Working in an office I need to have my phoen on vibrate as a colorful ringtone is simply not an option. But I miss text messages and phone calls on occasion because I just don't feel the phone vibrating in my pocket.
Heck even if I have it laying on a nearby table sometimes I still don't hear it vibrating.
I have come up with a sollution acceptable work around to this issue!
I made a vibration sound as my ring tone. So now when the phone vibrates it also goes BzzzBzzzBzzz out of the speaker.
It's barely loud enough to be heard by anyone but you if it's in your pocket. If anyone else does hear it, it still just sounds like a normal vibrating phone. No obnoxious ringtone.
If you want to try this out I've included 3 WAV files in the attached zip.
- Base Vibration Sound.wav - This is the sound file I used as a base for the final ringtones I made. I have scoured the internet looking for vibration sounds. This one is the one that sounded most like an actual vibrating phone. Use this file as your source if you want to try this technique out but don't like the final products I created.
- Ringer Vibration.wav - I added some bass and increased the volume, and extended the length of the original source file so make a loud, long, steady vibration sound that is roughly the length of a normal incoming call vibration.
- SMS Vibration.wav - Same bass and volume changes as the Ringer Vibration, but it's 3 short bursts insead of one long steady vibration. I did this because 3 short burts is how I've always set my my SMS vibration sequence. There are pauses between each vibration in the squence so you can hack up he file and change the vibration pattern as needed easily enough.
Hopefully this idea helps someone else.
Note, I still have the phone vibrate and ring in settings so it still vibrates. The vibration sound is jus in addition.
This is still a work in progress for me. So if you can improve on it please do and share your version here! If there are any real audiophile geeks out there who can make this sound really good, please share your talents! I am NOT an audio guy by any means. I just found a vibration sound file online and modded it with a little cutting and pasting and enhancement options using a free program called Audacity on Ubuntu. So if someone has and knows how to use high quality audio modification software to do this properly, by all means please show us what youv'e got!
Wow, thinking "out of the box"! Good sh*t! Another way to strengthen ur vibrate is through ktoonesz kernel, in the extras menu (ktweaker, comes with the kernel), you can change the strength.
norml said:
Wow, thinking "out of the box"! Good sh*t! Another way to strengthen ur vibrate is through ktoonesz kernel, in the extras menu (ktweaker, comes with the kernel), you can change the strength.
Click to expand...
Click to collapse
I use CyanogenMod for the T Mobile variant (I have a 919) and it has a feature to let you increase the strength of the vibration. But even at it's max it's not that powerful.
Does hat ktoonesz kernel make a significant difference for your variant? I don't have access to the kernel but I can certainly get devs to port that mod to 919 kernels if it works.
I think the problem isn't how much power that is sent to the vibration motor. It's that the unit itself doesn't vibrate much.
If you've never seen one, all a vibration unit is is a small electric motor with a lopsided weight on the end so it wobbles when it spins. When it spins fast the wobble becomes a vibration.
The S4 vibration unit (I'm trying REALLY hard not to call it a vibrator....haha) simply doesn't have a very lopsided weight on the end of the motor. So it doesn't wobble much.
I never messed with it, I just use his recomended settings (except for oc)...it ranges from 15-125. I'll mess with it and see for you. As far as a kernel goes, it's the best imo, never fc my phones unless I oc it to the max, which is 2.3 I think, I can oc to 2.1 with no problems. The incredible part is that it is great on the battery, even oc'd, i get better battery life than stock, weird imo, but I'm still very new to all this.
VIBRATOR check, LOL, didn't seem to change at ALL, felt the same, I have seen a lot of ppl commenting on it though, on how it works. You mentioned you don't have axx to it? You mean to work on it?
norml said:
I never messed with it, I just use his recomended settings (except for oc)...it ranges from 15-125. I'll mess with it and see for you. As far as a kernel goes, it's the best imo, never fc my phones unless I oc it to the max, which is 2.3 I think, I can oc to 2.1 with no problems. The incredible part is that it is great on the battery, even oc'd, i get better battery life than stock, weird imo, but I'm still very new to all this.
VIBRATOR check, LOL, didn't seem to change at ALL, felt the same, I have seen a lot of ppl commenting on it though, on how it works. You mentioned you don't have axx to it? You mean to work on it?
Click to expand...
Click to collapse
No I mean that kernel just runs TW roms, doesn't it? Or am I thinking of a different one?
I always run CM/AOSP ROMs and never use TW
Skipjacks said:
No I mean that kernel just runs TW roms, doesn't it? Or am I thinking of a different one?
I always run CM/AOSP ROMs and never use TW
Click to expand...
Click to collapse
He has Touchjizz and AOSP. NEW ver got rls'd today as a matter of fact.
file link http://goo.gl/AWZK5
OG thread http://forum.xda-developers.com/showthread.php?t=2289140
norml said:
He has Touchjizz and AOSP. NEW ver got rls'd today as a matter of fact.
file link http://goo.gl/AWZK5
OG thread http://forum.xda-developers.com/showthread.php?t=2289140
Click to expand...
Click to collapse
I've been using Albino's ChronicKernel. Its also really good if you want to try that out.
Sent from your phone. You should be careful where you leave that thing.
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.
I noticed the OXYGEN UPDATER APP now has Android 12 available to install but it hasn't quite made it to the official update in the settings. Just wondering if anyone has tried this update and whether you experienced or heard of any bugs?
I have no reason to think there is but Ive literally heard nothing good, bad or neutral. It's like no one owns this phone anymore. An update like this used to be noteworthy. That said, if anyone reads this and you have info, please share. Thanks
I have updated my device today and one thing I have noticed the most is that volume levels after the update are much lower than they were. I cannot use normally my earphones indoors and cannot image how bad it will perform outdoors.
Would be grateful if someone knows how to fix such problem.
uacyber said:
I have updated my device today and one thing I have noticed the most is that volume levels after the update are much lower than they were. I cannot use normally my earphones indoors and cannot image how bad it will perform outdoors.
Would be grateful if someone knows how to fix such problem.
Click to expand...
Click to collapse
I appreciate the feedback. I still haven't updated, but lately I've had volume issues. Both pairs of ear buds are noticeably lower than they were in the past. On one pair the right ear bud is barely usable, especially in a somehat noisy setting, but it's gotta be an issue with the ear bud.
In general, I need to crank them all the way up in the gym.
KLit75 said:
I appreciate the feedback. I still haven't updated, but lately I've had volume issues. Both pairs of ear buds are noticeably lower than they were in the past. On one pair the right ear bud is barely usable, especially in a somehat noisy setting, but it's gotta be an issue with the ear bud.
In general, I need to crank them all the way up in the gym.
Click to expand...
Click to collapse
I have fixed the issue with low sound levels when using earphones, but, unfortunately, I cannot describe clearly how 'cause it was a bit incomprehensible. I just connected one more time my earphones to smartphone, opened some video on YouTube, then pop-out of some option about volume came out. Then I tapped on it and there was an option that has strange description (maybe it is because of localization) that I switched on, and the volume issue fixed magically. After that, I couldn't find that option once again in settings.
Sounds familiar. I think it's a built-in volume limiter. Should be able to find something in the settings and if not maybe enable developer settings and see if you find it there. Something like "absolute volume".
But it looks like you got it sorted out anyway.
Actually nevermind. I got that confused with something else. I believe all that would do is keep the earbuds and the phone volumes separate.
There's been talk that Android 12 and Android Auto don't work well in some cars - not OnePlus specific, but in general. Has anyone tried Android Auto with 12 yet on the OP8?
Alan
I did the update, and here is what I notice:
The icons on top of the screen are not the same size.
The Notifications sometimes are lost (Whatsapp/text etc)
Whatsapp voice calls echo and sometimes the phone does not ring
Ghost touches when gaming (clash royale)
The screen goes ON for no reason
The battery sometimes is okay, sometimes it drains (your mileage may vary)
Screen unlock fingerprint behavior slow at times and sometimes is fine.
The volume issue that everyone is reporting
All of if has been reported to OnePlus. If you visit the OP forums everyone is pretty pissed off about it myself included.
Honestly, it feels like this is an Alpha version of the ROM and they are using the general public to test and find bugs.
This is pretty frustrating a phone is not a toy is a tool for work and to communicate with others.
Fingerprint unlock stops working after a few days. Reboot brings it back.
Just to update. AA works fine with Android 12 on my OP8