[FIX] Galaxy Nexus GSM low latency audio for Jelly Bean - Samsung Galaxy Nexus

One of the flaws of the new Android Jelly Bean OS compared to iOS is the big audio playback latency - about 48 ms. This impacts negatively many applications that emulate musical instruments and the ones that do VOIP like Skype or Google Talk. For VOIP apps the audio lag also has a negative impact on acoustic echo cancellation. I have to mention that Google improved from ICS where the playback latency was about 88 ms.
This is a similar thread to:
http://forum.xda-developers.com/showthread.php?t=1674836
but applies to Jelly Bean.
The attached package should be used only by experienced users that can eventually restore their system to the original state. I tested it on Android 4.1.1 GSM phone build JRO03C (maguro) and 4.1.2 build JZ054K.
The latency after aplying it should be 18 ms (no longer 11 ) with the new version - as reported by the "Caustic 2" app.
It does NOT work on Android 4.2!
Apps like Google Talk, Skype, YouTube, Play Music, Caustic 2, Pandora, TheDrum, My Piano... work very well with this change.
With the newest version all the apps I tested that work well with stock Jelly Bean work well with this patch, with the additional advantage of lower latency.
Status: stable (install and use at own risk)
Notes:
1) applying this might reverse changes made in other mods.
2) The "SCREEN OFF" BUG is FIXED as of July 16th night.
To install use "lowlatsnd41_18_inst.zip"
To restore to original state you may use "lowlatsnd41_rest.zip" or other restore methods if necessary.
Do not run the install twice in a row (run one install then one restore; you have to run restore only if you want to uninstall or before installing a new version when available...).
Since the volume is still a big issue for the Galaxy Nexus users I decided to address this with a Volume Boost patch.
Status: stable ( for 4.1, not tested in 4.2). Install and use at own risk...
The same rules for install/restore apply.
General comment: system updates may delete the backup of the original files; therefore the "restore" should be ran before an update followed by a new install after the update; restoring the original files is also required if the update performs sum checks.

I just installed it and my latency went from 168 ms to 18 ms in caustic 2.
Major ISSUE: When the screen is off audio is incredibly distorted (slowed down an incredible amount) when playing music through headphones. It seems to work fine when the screen is on, though.
I restored using your restore file and caustic 2 now reports my latency as 48 ms and music plays fine when the screen is off, too. Ha, I'm going to test to see if people still complain about horrible echo and delay when making GrooveIP calls over t-mobile 4G.
Thanks!

Megatr0n. said:
I just installed it and my latency went from 168 ms to 18 ms in caustic 2.
Major ISSUE: When the screen is off audio is incredibly distorted (slowed down an incredible amount) when playing music through headphones. It seems to work fine when the screen is on, though.
I restored using your restore file and caustic 2 now reports my latency as 48 ms and music plays fine when the screen is off, too. Ha, I'm going to test to see if people still complain about horrible echo and delay when making GrooveIP calls over t-mobile 4G.
Thanks!
Click to expand...
Click to collapse
Bug confirmed... I'm working on it...

Is the distortion due to the limited clock speed?
Sent from my Galaxy Nexus using xda premium

leets4uc3 said:
Is the distortion due to the limited clock speed?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
My GNex is running at 1536 Mhz CPU / 384 Mhz GPU w/ franco's kernel. Could that be causing my issues when the screen's off? Or did you mean that the issue is caused by the SOC clocking down by the scheduler to save power when the screen is off?

I was thinking it may have happened because I'm max screen off speed was 384 it was to low. But I changed it to always hold 12Xx and it bug still persisted
Sent from my Galaxy Nexus using xda premium

Megatr0n. said:
Major ISSUE: When the screen is off audio is incredibly distorted (slowed down an incredible amount) when playing music through headphones. It seems to work fine when the screen is on, though.
Thanks!
Click to expand...
Click to collapse
It is fixed now (as of 07/16/12 night - edited post). You may rename it after the download. Just make sure you don't run the install twice in a row...

leets4uc3 said:
Is the distortion due to the limited clock speed?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
No. The sound is just configured differently when the screen is off. There is still a issue, hopefully I'll fix it soon.

vonVideo said:
No. The sound is just configured differently when the screen is off. It should be OK with the new packages.
Click to expand...
Click to collapse
Could you rename the fixed version, please? I just downloaded what I think is the new version but I'm still having the same issue when the screen is off and since it has the same name as the original file, I can't be sure that the new version doesn't work.

Megatr0n. said:
Could you rename the fixed version, please? I just downloaded what I think is the new version but I'm still having the same issue when the screen is off and since it has the same name as the original file, I can't be sure that the new version doesn't work.
Click to expand...
Click to collapse
There is still a issue, hopefully I'll fix it soon...

I can confirm still an issue listening to mlb app with screen off. On the plus side, voip delay noticeably lessened.

klobkelosh said:
I can confirm still an issue listening to mlb app with screen off. On the plus side, voip delay noticeably lessened.
Click to expand...
Click to collapse
Pls check out the new version (use the restore first, don't run the install twice in a row)

vonVideo said:
Pls check out the new version (use the restore first, don't run the install twice in a row)
Click to expand...
Click to collapse
Confirmed, it works fine! Nice job!

vonVideo said:
Pls check out the new version (use the restore first, don't run the install twice in a row)
Click to expand...
Click to collapse
Screen off sound issue seems to be resolved, thanks! I'll postback in this thread after using GrooveIP on both wifi and 4G for a bit to see if there's any improvement.

Any impact to battery life with this mod?
Sent from my Galaxy Nexus

btkli said:
Any impact to battery life with this mod?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Should be negligible.

Confirmed, audio on screen off working properly. Subjectively, voip tests are promising with little delay. I'll have to put it through some phone calls to really know. Thanks Von!

Works on Toro too! Thank you Von!

Megatr0n. said:
Screen off sound issue seems to be resolved, thanks! I'll postback in this thread after using GrooveIP on both wifi and 4G for a bit to see if there's any improvement.
Click to expand...
Click to collapse
You may check out the new version - the output latency is now 11ms!

vonVideo said:
You may check out the new version - the output latency is now 11ms!
Click to expand...
Click to collapse
if the code is good, why don't u push this to AOSP?

Related

[Q] Volume Issue - Questions

I've searched and searched, and pretty much every thread I read it says to use Volume+.
My poor Galaxy Nexus suffers from low speaker volume. When watching netflix, for example in my room with no external noises I can BARELY hear people talking. My ringtones (including custom) are low for both notifications and phone calls, alarms too. Youtube seems to be sort of OKAY some videos being loud, some quiet like normal.
I tried the paid version of Volume+, followed the instructions (change musicFX to Volume+), turned down the volume 2 notches and played a song then went through all the +'s (up to +10) with NO difference while returning the volume to max.
I'm running stock 4.0.1 Rogers. Is this an actual hardware issue that can be fixed via an update? I'd prefer not to root and flash to fix this issue.. I'm still in my 30 Day return window and I'm seriously contemplating returning it.
Any ideas?
First of all you can get the app for free from www.androidaudiohacks.com...
It works really well on my gsm gnex
Verstuurd van mijn Galaxy Nexus met Tapatalk
I don't think the Volume+ he has in the market is the one that he has worked for the Galaxy Nexus. Check out thread: http://forum.xda-developers.com/showthread.php?t=1449513
I'm using the most recent one from his website and it definitley works....
I used the paid version from his website (which yes, is free). That's what I was talking about.
Jinfuse said:
I used the paid version from his website (which yes, is free). That's what I was talking about.
Click to expand...
Click to collapse
You want version: 1.8.1.0
Is that the version you are running?
KernelK said:
You want version: 1.8.1.0
Is that the version you are running?
Click to expand...
Click to collapse
Yes. Little to no change, even on +10. Even after rebooting, changing Music Settings to Volume+, etc.
Perhaps it's an issue with the ROM you are on: stock 4.0.1?
Maybe it needs to be on the 4.0.3? Not sure what the limitations are though, just throwing that out there. I'd contact the Dev and see what he says.....
KernelK said:
Perhaps it's an issue with the ROM you are on: stock 4.0.1?
Maybe it needs to be on the 4.0.3? Not sure what the limitations are though, just throwing that out there. I'd contact the Dev and see what he says.....
Click to expand...
Click to collapse
Stock 4.0.1 is all we can update to at the moment on Rogers without rooting and flashing, something I'd like to avoid.
just go with the equalizer app instead, its so much better and will nearly double the volume when you crank each frequency up. and it ties in with the system audio api and music effects etc.
Have it set to +10 for the Equalizer, it made a difference but not much. +15 just distorted the crap out of the quality (with all sliders up).

low volume on nexus

Hi All
I've recently come over from the Desire S forum, was running a custom rom, and before that i had a rather unfortunate love affair with blackberries!
well i've got my hands on a Galaxy Nexus and i LOVE the phone! however the only downside is that this phone is really really really quiet....
its running on teh 4.0.2 update, build number ICL53F, and I've tried searching but can't seem to find a fix for this....
i'm struggling to hear the other person when i'm sitting in a library and my alarm barely manages to stir me in the mornings!
help!!!
Why not search? Install equalizer or volume+ and max out each frequency. Your volume will double for ringer, notifications, music and audio.
RogerPodacter said:
Why not search? Install equalizer or volume+ and max out each frequency. Your volume will double for ringer, notifications, music and audio.
Click to expand...
Click to collapse
Volume+ is great... it's useful beyond the nexus as well. Made a big difference on our Nook Colors
I did search, and read about both of these apps, however I was thinking more along the lines of perhaps an ACTUAL FIX which fixes this issue in the nexus rather than just an app that boosts the volume...
thanks for the suggestions guys..
duke_stix said:
I did search, and read about both of these apps, however I was thinking more along the lines of perhaps an ACTUAL FIX which fixes this issue in the nexus rather than just an app that boosts the volume...
thanks for the suggestions guys..
Click to expand...
Click to collapse
If there's an actual fix (which I'm sure there is) it'll probably be in an OTA.
duke_stix said:
I did search, and read about both of these apps, however I was thinking more along the lines of perhaps an ACTUAL FIX which fixes this issue in the nexus rather than just an app that boosts the volume...
thanks for the suggestions guys..
Click to expand...
Click to collapse
volume+ is an actual fix. It changes the volume level under the covers.
I don't see any difference using Volume+ or at least i can't tell!
MasterLapa said:
I don't see any difference using Volume+ or at least i can't tell!
Click to expand...
Click to collapse
at a bare minimum, you should set your ringer/notifications at +4. I've used +6 for the past month and it's been fine.
I got it working with a reboot, +5 or similiar looks just fine
well those apps are a fix. Google exposed the audio api's after gingerbread for anyone to raise system audio output. So these apps just tie into the system audio and raise it as much as you like. Only call volume is not exposed. Sure maybe google will raise the volume in an update soon. But using apps that use the audio api really is the same thing.
The latest ota leak increased volume.
Sent from my Galaxy Nexus using Tapatalk

What do we know about the JB low speaker volume?

So, many of you are aware of how abysmally low the speaker volume is on the phone after getting the JB update. Unfortunately all the information on it is scattered among several different posts and threads, and I just wanted to get some clear answers and use this as an informational post for others who are annoyed by this bug.
What, if anything, do we know about why it happens? Is there a definitive fix system-wide, or do I have to use volume boosting apps? I run franco kernel, are there going to be any compatibility issues with proposed fixes? I like using mostly stock JB, can I get a ROM that makes minimal changes to the original while still fixing the volume issue?
After randomly doing a search for volume fix a few minutes ago I saw this. Did search for same exact reason (gnex 4.1.1). Awesome beats (one of multiple equalizer apps) is said to work. I'm gonna try it in the morning (so as not to have a very annoyed girlfriend at 4am). There's probably a good amount more info on this. As for the last part..pure-ish 4.1.1 aosp Roms are very pleasing...like buttah lol.
Sent from my Galaxy Nexus using xda premium
earlyberd said:
So, many of you are aware of how abysmally low the speaker volume is on the phone after getting the JB update. Unfortunately all the information on it is scattered among several different posts and threads, and I just wanted to get some clear answers and use this as an informational post for others who are annoyed by this bug.
What, if anything, do we know about why it happens? Is there a definitive fix system-wide, or do I have to use volume boosting apps? I run franco kernel, are there going to be any compatibility issues with proposed fixes? I like using mostly stock JB, can I get a ROM that makes minimal changes to the original while still fixing the volume issue?
Click to expand...
Click to collapse
If you have Franco.kernel, download his app from the play store (it costs a few bucks, not super expensive). In the settings tab there is an option to increase the max sound volume. I recommend setting it to 2; if you set it to 3 sometimes the sound will cut out on max volume.
https://play.google.com/store/apps/...t=W251bGwsMSwxLDMsImNvbS5mcmFuY28ua2VybmVsIl0.
hongzhou94 said:
If you have Franco.kernel, download his app from the play store (it costs a few bucks, not super expensive). In the settings tab there is an option to increase the max sound volume. I recommend setting it to 2; if you set it to 3 sometimes the sound will cut out on max volume.
https://play.google.com/store/apps/...t=W251bGwsMSwxLDMsImNvbS5mcmFuY28ua2VybmVsIl0.
Click to expand...
Click to collapse
I have no idea if this is correct information or not, so take it with a grain of salt, but I read earlier today in the Franco thread that that setting only affects the headphone volume, not speaker volume. I can tell you it does nothing for the volume on my GNex (speaker). I love this phone dearly, but I absolutely hate the low volume. I never have music on my phone, but I use the speaker phone multiple times a day while at work in my truck. I've yet to find a fix that actually increases the speaker volume on calls, and I've tried just about every ROM and tweak around. I'm beginning to think the people that swear some of these fixes work are just having a placebo effect.
Sent from my Nexus 7 using Tapatalk 2
It seemed to make my speaker sound louder, but I am also using it in tandem with the AwesomeBeats mod for AndroidMe ROM, so it might be one or the other.
Sent from my Galaxy Nexus using xda app-developers app
KentuckyHouse said:
I have no idea if this is correct information or not, so take it with a grain of salt, but I read earlier today in the Franco thread that that setting only affects the headphone volume, not speaker volume. I can tell you it does nothing for the volume on my GNex (speaker). I love this phone dearly, but I absolutely hate the low volume. I never have music on my phone, but I use the speaker phone multiple times a day while at work in my truck. I've yet to find a fix that actually increases the speaker volume on calls, and I've tried just about every ROM and tweak around. I'm beginning to think the people that swear some of these fixes work are just having a placebo effect.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I remember reading that too. It does nothing for my GNex speaker either. Volume+ works though. I just tried it yesterday. It definitely increases the volume but only so much before it starts distorting the sound pretty bad. But it is a godsend volume wise for sure.
Sent from my Nexus 7 using xda premium
I can confirm that Franco Kernel sound boost only increases headphone volume. I'm just waiting for Volume+ to update...
kyokeun1234 said:
I can confirm that Franco Kernel sound boost only increases headphone volume. I'm just waiting for Volume+ to update...
Click to expand...
Click to collapse
you can get the latest beta version for free from the authors website listed on the play store.. it already works on the Gnex
pdxtechdoctor said:
you can get the latest beta version for free from the authors website listed on the play store.. it already works on the Gnex
Click to expand...
Click to collapse
oh, does it work now? I gotta check than. Cheers
EDIT: I can confirm that Volume+ still haven't updated yet, therefore, it doesnt work yet.
kyokeun1234 said:
oh, does it work now? I gotta check than. Cheers
EDIT: I can confirm that Volume+ still haven't updated yet, therefore, it doesnt work yet.
Click to expand...
Click to collapse
I dunno if it makes a difference but I'm using the pay version and it most certainly works on my GNex.
EDIT: on JRO03L aosp
Sent from my Galaxy Nexus using xda premium
ian42086 said:
I dunno if it makes a difference but I'm using the pay version and it most certainly works on my GNex.
EDIT: on JRO03L aosp
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Huh that's odd. Even the dev of the app said that Jelly bean is incompatible at the moment. I'm sure it's not working, even in paid version
earlyberd said:
So, many of you are aware of how abysmally low the speaker volume is on the phone after getting the JB update. Unfortunately all the information on it is scattered among several different posts and threads, and I just wanted to get some clear answers and use this as an informational post for others who are annoyed by this bug.
What, if anything, do we know about why it happens? Is there a definitive fix system-wide, or do I have to use volume boosting apps? I run franco kernel, are there going to be any compatibility issues with proposed fixes? I like using mostly stock JB, can I get a ROM that makes minimal changes to the original while still fixing the volume issue?
Click to expand...
Click to collapse
There some ROMs that have it fixed...if you have a sprint gnex...the perfect android ROM has an incredibly loud speaker volume
Sent from my Galaxy Nexus using xda premium
kyokeun1234 said:
Huh that's odd. Even the dev of the app said that Jelly bean is incompatible at the moment. I'm sure it's not working, even in paid version
Click to expand...
Click to collapse
The dev says it doesn't work with the system stuff (like ringtones, notifications, etc.) Works for music volume on JB though. Check it out, seems like a lot of people with various JB roms are using it successfully. It's kinda hard to be sure it's not working without trying it. I assure you..again..I'm using it..it works for music. Re-read what the dev said.
Sent from my Nexus 7 using xda premium
ian42086 said:
The dev says it doesn't work with the system stuff (like ringtones, alarms, etc.) Works for music volume on JB though. Check it out, seems like a lot of people with various JB roms are using it successfully. It's kinda hard to be sure it's not working without trying it. I assure you..again..I'm using it..it works for music. Re-read what the dev said.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I try Volume+ on my jelly bean nexus. Only the music volume work, not the system volume (like ringtones). I missed so many call because the ringtone vol is not loud enough even at max vol level. I know I can install ROM, but I prefer stock right now.
There are no mods available as of now for boosting ringtone or notification volume for galaxy nexus on jelly bean. All the mods like awesomebeats/volume+ and also the default musicfx only work on music volume.
I have tried all the mods on all JB Roms which claim to boost ringtone volume, but none really work. The effect if at all is very marginal.
The problem lies with the way google has implemented Jelly Bean. The solution has probably go to come from them until one of the geeks here manage a workaround.
Lets see if volume+ developer manages to release a working version.
I am currently using volume+ on AOKP milestone6(ICS 4.0.4) to great effect.
There is no point in upgrading to JB unless the ringtone volume level problem is addressed. What is the use in owning a phone which you cannot here ringing.
Really need a stock solution. The reason I have the Galaxy Nexus is to avoid flashing madness with the stock experience. Is it a tracked bug?
Sent from my Nexus 7 using xda app-developers app
aidanbree said:
Really need a stock solution. The reason I have the Galaxy Nexus is to avoid flashing madness with the stock experience. Is it a tracked bug?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
+1
I could not find a way to lodge a formal bug report to google about this.
Sent from my Galaxy Nexus using xda app-developers app
kannan66 said:
There are no mods available as of now for boosting ringtone or notification volume for galaxy nexus on jelly bean. All the mods like awesomebeats/volume+ and also the default musicfx only work on music volume.
I have tried all the mods on all JB Roms which claim to boost ringtone volume, but none really work. The effect if at all is very marginal.
The problem lies with the way google has implemented Jelly Bean. The solution has probably go to come from them until one of the geeks here manage a workaround.
Lets see if volume+ developer manages to release a working version.
I am currently using volume+ on AOKP milestone6(ICS 4.0.4) to great effect.
There is no point in upgrading to JB unless the ringtone volume level problem is addressed. What is the use in owning a phone which you cannot here ringing.
Click to expand...
Click to collapse
Nexus louder v3 worked for me. My sister has the same phone and mine is very noticeably louder.
i guess if i want to boost the volume im going to need to root? my GS2 was louder :crying:
runderekrun said:
Nexus louder v3 worked for me. My sister has the same phone and mine is very noticeably louder.
Click to expand...
Click to collapse
Where do I get this 'Nexus Louder v3'....had a quick search but came up with nothing...
---------- Post added at 12:27 PM ---------- Previous post was at 12:25 PM ----------
aidanbree said:
Where do I get this 'Nexus Louder v3'....had a quick search but came up with nothing...
Click to expand...
Click to collapse
actually, just found it
http://forum.xda-developers.com/showthread.php?t=1748803

[Official] CM10 Nightly Thread is up for Galaxy s3 and its a Daily Driver

Here is the CM10 Nightly thread - all thanks go to Steve (cyanogen) and the CM10 team... I simply posted the updated info up
http://forum.xda-developers.com/showthread.php?t=1846514
This is a daily driver and most everything seems to work...
neverends said:
Here is the CM10 Nightly thread - all thanks go to Steve (cyanogen) and the CM10 team... I simply posted the updated info up
http://forum.xda-developers.com/showthread.php?t=1846514
This is a daily driver and most everything seems to work...
Click to expand...
Click to collapse
does netflix work on it
brollikk said:
does netflix work on it
Click to expand...
Click to collapse
No. Cyanogen has been in touch with Netflix I guess trying to find a fix.
Sent from my SAMSUNG-SGH-I747 using xda premium
brollikk said:
does netflix work on it
Click to expand...
Click to collapse
Everything does work.
One app is simply not compatible.
Igotsanevo4g said:
Everything does work.
One app is simply not compatible.
Click to expand...
Click to collapse
is NOT only one app:
*Netflix
*PLEX
*WatchESPN
*Time Warner Cable
*HBO Go
*Cinemax Go
it is not an app issue is the ROM, Netflix works just fine using CM10 on the HTC ONE X.
and...
LED does not work properly, it does not turn red when phone is charging or green when is fully charged
eortizr said:
is NOT only one app:
*Netflix
*PLEX
*WatchESPN
*Time Warner Cable
*HBO Go
*Cinemax Go
it is not an app issue is the ROM, Netflix works just fine using CM10 on the HTC ONE X.
and...
LED does not work properly, it does not turn red when phone is charging or green when is fully charged
Click to expand...
Click to collapse
Doubt its a "ROM" issue. Judging by those apps, its not passing some sort of authentication check within those apps.
*Notification* led works fine. The Samsung implementation as it is on stock doesn't work, which makes sense.
Plex works, you just have to set it up right.
Sent from my SAMSUNG-SGH-I747 using xda premium
zmore said:
My point was that there's more people who DON'T use those specific broken apps than who do, so, CM10 can be a daily driver for MOST people.
And I didn't say LED notifications weren't working (they are); I just said that the Touchwiz-specific charging/charged mostly-useless-notification isn't implemented in CM.
Click to expand...
Click to collapse
Really? Where's your completed survey and statistics? Stop saying you have a point, I'm still where it is, or where you left it.
FirstNoobToBrickHisPhone said:
Really? Where's your completed survey and statistics? Stop saying you have a point, I'm still where it is, or where you left it.
Click to expand...
Click to collapse
I need poll results before I can declare that more people don't use Netflix on android than do? Ooookay.
I don't like netflix.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Netflix sucks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Call Echo and Netflix
The only real issue I'm having now is the echo that the person you call hears that started when the fix was added for being unable to hear phone calls on answer (until you toggled speaker). I see there is a merge regarding audio in the latest nightly (0823), but it specifically references d2usc not d2att, so I'm not sure it even applies, even if it is related to this issue. Does anyone know if the echo on the other end is still present after 0823?
Other issues I still have even after a full wipe, but that aren't as important (and are otherwise well-known), are the inconsistent wake behaviour of the home button (just use power button instead), and occasional screen flicker when you don't disable hardware overlays. There's also the >160 character SMS thing, but mine seems to split the messages in half OK (instead of sending it as one message, which would be preferable).
As for Netflix I do not use it, but when browsing the changes at r.cyanogenmod.com a few days ago I came across one that stated in the comment that it was to fix the Netflix issue for our phones. It wasn't merged at the time, though, and I can't seem to locate it now. I'll post it if I do so you can watch if/when it gets merged. Either way, they are aware and working on the issue, and it seems to be fixable with ROM changes.
can someone confirm if netflix is working on the galaxy s3 at&t model with cm10?
brollikk said:
can someone confirm if netflix is working on the galaxy s3 at&t model with cm10?
Click to expand...
Click to collapse
Netflix does not work as stated above numerous times.... In fact the whole conversation right before your post is about Netflix.... If you are not going to read the whole thread at least read the 5-6 previous posts
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
id10terrordfw said:
Plex works, you just have to set it up right.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Can you share your setup for Plex? I can't get it to work with any of the JB based roms.
lordmorphous said:
Can you share your setup for Plex? I can't get it to work with any of the JB based roms.
Click to expand...
Click to collapse
What worked for me was Advanced Settings, use Plex OpenGL Player, Transcode Off, Direct Play Enabled, and Device Supports HLS OFF(unchecked).
Ok so my thoughts so far after using the latest build (08/23) is that its good and I will use it as my daily driver, a few things here and there that I miss from touchwiz, but overall its an awesome rom hiccups here and there, but stable enough as a daily driver.
zap12341 said:
Ok so my thoughts so far after using the latest build (08/23) is that its good and I will use it as my daily driver, a few things here and there that I miss from touchwiz, but overall its an awesome rom hiccups here and there, but stable enough as a daily driver.
Click to expand...
Click to collapse
+1
I gave up on the preview build a few weeks ago, but it's much better now. I won't consider going back to stock until JB is officially released.
...unless I change my mind before then.
That setting will basically stream the movie without any type of transcoding or compression which defeat the purpose of using Plex. Also you will not get audio on any video unless is only stereo. The purpose of Plex is to be able to stream your movie collection without having to worry about compatibility with your device.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
eatonjb said:
so far so good. still having an issues with the Echo, wonder if the 24th fixes that. its killing me!
Click to expand...
Click to collapse
CM10 Developer versions are always better compiled then stock, so im sure even when the stock version is released, the Developers version will get improved on a higher scale...

Cm10.1 Buglist/Workarounds Discussion

Made This because i see the same question/bugs referenced in the cm thread over and over for each build so I figured id place them all here so people wont have to look. And will know its a problem to start with and to keep the general talk out of the original development forum/aid the developers with a plain list of bugs/workarounds.
Feel free to add anything im missing.
To enable developer options:
settings---) about ---) scoll to the bottom and tap build number like 8x
now power menu reboot options are there also as a safety feature
Build
Jan 24 2013
A2DP IS NOW FIXED
headphone button hangup does not work
wifi tethering on stock kernel dont work (use kt's or a kernel that says wifi fixed)
Enabling "AirPlane" mode when Bluetooth is on and in-use causes it to forever be stuck in "Turning off Bluetooth..." status. Only a reboot will fix it.
when calling an 800 or automated number you cant dial a number at a prompt. For instance "Press 1 for english" doesn't work sometimes hapens when trying to answer gv with call screening every 1 in 10 or so
Can someone pleaseee confim that bluetooth is 100% fixed it works fine for me on kt
Build
Jan 4 2013
Keyboard/touch screen a little wonky try changing the hwoverlay settings in developer options works for some.. fixed in 1/3?
Call volume low:
The in call volume bug will continue to exist until the audio enhancements ( IE DUAL MIC) are finished and merged in. For now goto phone > settings and uncheck "Noise suppression". its not a fix but it helps.
Click to expand...
Click to collapse
music players not working or fc? [/QUOTE]Download rom toolbox and open the build.prop editor search for lpa.decode=true and change it to lpa.decode=false[/QUOTE] Seems to be working as of 1/3
Camera Crashes :
just close it and clear data start again works fine from there on out
Click to expand...
Click to collapse
Bluetooth A2DP :
bluetooth voice dial does not work in cm10 or cm10.1. It opens but cannot "hear" any commands.
Disable voice dial in "manage apps", then install "Bluetooth launch" from the play store. After this, set it to launch activity "com.Google.android.googlequicksearchbox.voicesear chactivity" under the "Google search" application.
Now connect your Bluetooth device, press the button you would normally use to initiate voice dial, and tap "Bluetooth launch" when prompted, then tap always use.
have to use the voice command button twice, but it works like a charm!
Click to expand...
Click to collapse
BT A2DP not functioning properly some say to make a call and hang up using bluetooth
GPS shows locked in notification drawer even after being turned off
Camera:
gtuansdiamm said:
When using ffc on camera mode switching to video mode screws color
Work around. Using the 8mp camera I in video mode and switch to ffc
Color is fixed but it is still a bit wonky
Click to expand...
Click to collapse
* unconfirmed
NO GPS?
flash back to any tw rom get a lock and then flash back to cm/aokp
Memory:
CNexus said:
"I can't find my apps and/or documents and/or anything thats supposed to be on my sdcard!"
From JB and up everything that was on the root of the sdcard (in previous versions) is now located inside the "0" folder
Click to expand...
Click to collapse
Screen wakes: screen wake only on stock kernel use ktoonsez kernel make sure min mhz is stock * possibly fixed in 1/3?
4g: ehrdp hand off still a bit wonky toggle airplane mode if it has trouble not sure. some reports of it working find others its.*
App switcher bug please confirm?
anything else? submit a reply and ill ad it to the op! your help is appreciated!
Bug fixed? as bugs get squahsed ill remove them again this is ment as a running list cuz theres no bug tracker
Dreamlogix said:
Made This because i see the same question/bugs referenced in the cm thread over and over for each build so I figured id place them all here so people wont have to look. And will know its a problem to start with and to keep the general talk out of the original development forum/aid the developers with a plain list of bugs/workarounds.
Feel free to add anything im missing.
To enable developer options:
settings---) about ---) scoll to the bottom and tap build number like 8x
Build
Jan 1 2013
Keyboard a little wonky try changing the hwoverlay settings in developer options works for some..
you think the call volume is too low? get volume+ in the play store
music players not working? Download rom toolbox and open the build.prop editor search for lpa.decode=true and change it to lpa.decode=false
Camera Crashes on first start: just close it and clear data start again works fine from there on out
random Bluetooth problems? not sure. some reports of it working find others its a lil buggy possible work around is make a call and hang up then streaming works.
GPS shows connected even after being turned off
Click to expand...
Click to collapse
Volume+ is a placebo
Sent from my SPH-L710 using xda premium
When using ffc on camera mode switching to video mode screws color
Work around. Using the 8mp camera I in video mode and switch to ffc
Color is fixed but it is still a bit wonky
Sent from my SPH-L710 using xda premium
Edit: it could have been that I had the color effect neon on
I though it did nothing since it was on top and in 8mp camera mode it did nothing
The color effect none is on the bottom
rrmzr1 said:
Volume+ is a placebo
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
how about voodoo? i know it wasent on the s2 and s1 it allowed positive db amp
"I can't find my apps and/or documents and/or anything thats supposed to be on my sdcard!"
From JB and up everything that was on the root of the sdcard (in previous versions) is now located inside the "0" folder
--
Btw, really good idea OP :good:
rrmzr1 said:
Volume+ is a placebo
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Ya I don't see a option for the earpiece speaker. Just the main back speaker. Anything else that will fix the low in call volume?
Sent from my SPH-L710 using Tapatalk 2
ooxteme said:
Ya I don't see a option for the earpiece speaker. Just the main back speaker. Anything else that will fix the low in call volume?
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Try voodoo
Just installed cm10.1 again and the screen randomly flashes sometimes. Fix for that?
Sent from my SPH-L710 using xda app-developers app
DerIdiot said:
Hey all, any idea why when I try to play music or videos with sound the phone freezes hard? I have been having the issue on CM nightly 12-24, 29 and 30th. I'm sure there's just an app that needs data wiped.
Any help appreciated.
Click to expand...
Click to collapse
DerIdiot said:
Hey all, found a solution:
Use "File Explorer" with root access, go into /system/build.prop - scroll down until you see lpa.decode=true and change it to false, save and close and reboot.
Seems to work for now, though I imagine any new nightlies will require doing this at least for a while until they fix it.
Click to expand...
Click to collapse
---
@haynesr07, did you do a complete wipe? several times even? Sometimes stuff can leak through from your last rom and mess with your settings in your new rom, try clearing everything a couple times (2 or 3 times per item) and flash again
Also if you restored any data, that might be it, I've seen weird problems when people do that...I don't think this issue is rom specific though or it wouldnt be stable enough to be released
CNexus said:
---
@haynesr07, did you do a complete wipe? several times even? Sometimes stuff can leak through from your last rom and mess with your settings in your new rom, try clearing everything a couple times (2 or 3 times per item) and flash again
Also if you restored any data, that might be it, I've seen weird problems when people do that...I don't think this issue is rom specific though or it wouldnt be stable enough to be released
Click to expand...
Click to collapse
aye thanks m8
CNexus said:
---
@haynesr07, did you do a complete wipe? several times even? Sometimes stuff can leak through from your last rom and mess with your settings in your new rom, try clearing everything a couple times (2 or 3 times per item) and flash again
Also if you restored any data, that might be it, I've seen weird problems when people do that...I don't think this issue is rom specific though or it wouldnt be stable enough to be released
Click to expand...
Click to collapse
I wiped everything as usual...Hm, wonder what happened. Happened on liquid too..
haynesr07 said:
I wiped everything as usual...Hm, wonder what happened. Happened on liquid too..
Click to expand...
Click to collapse
you wiped system and factory reset and caches and then fixed permissions.
http://db.tt/GJ2NYrlb
This is the current build props i use. Leave out the Bootanimation one if you want to keep your boot animation. Do not edit buildprop if you have no experience. Look up the proper way to use them, Dreamlogix explainsto use rom toolbox above. Dont add all in. Check if value exists and change to the new value. If an entry is missing add it but dont assume its not there because double entries cause issues and if you mess up your build prop you might not boot. Have the rom file ready in case. One would need to dirty flash to get back to current install or a backup. If on a custom kernel after reinstalling rom, run kernel cleaner and reinstall kernel. Gapps will work on the dirty install without reinstalling them.
Use at your own risk i am not responsible for damages to ones phone. This is my build prop values i add or use not my actual build prop just the values and entries that i add or change.
The file is in plain text file format
GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
mw86 said:
http://db.tt/GJ2NYrlb
This is the current build props i use. Leave out the Bootanimation one if you want to keep your boot animation. Do not edit buildprop if you have no experience. Look up the proper way to use them, Dreamlogix explainsto use rom toolbox above. Dont add all in. Check if value exists and change to the new value. If an entry is missing add it but dont assume its not there because double entries cause issues and if you mess up your build prop you might not boot. Have the rom file ready in case. One would need to dirty flash to get back to current install or a backup. If on a custom kernel after reinstalling rom, run kernel cleaner and reinstall kernel. Gapps will work on the dirty install without reinstalling them.
Use at your own risk i am not responsible for damages to ones phone. This is my build prop values i add or use not my actual build prop just the values and entries that i add or change.
The file is in plain text file format
GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
Click to expand...
Click to collapse
what else did you change other than hw and ipa ?
and if you use inverted gapps you have to reflash.
Dreamlogix said:
what else did you change other than hw and ipa ?
and if you use inverted gapps you have to reflash.
Click to expand...
Click to collapse
Thanks i didn't remember inverted gapps you are right. I changed and added all of the values in the txt document i posted. They weren't for a fix, i always use them. Thats a list if the values i use.
Edit: most of them all add performance in some way. I didn't use any network build props so it could be more universal for other roms...
GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
I confirmed this morning that ktoon kernel (12/29) breaks audio (pandora, google music, 8tracks, etc) while stock kernel is fine on 1/1 nightly (clean flashed). On stock kernel, BT audio (google music) will play ok for 10-20 secs and then start fading in and out at a faster playback speed. You can reset this by making a phone call, but then you get another 10-20 secs of good audio before it starts up again. Someone should mention this on the dev thread at some point.
Also: if you're having problems with stock 1/1 nightly...do a clean flash. all my problems went away.
Dreamlogix said:
Try voodoo
Click to expand...
Click to collapse
I havent found a compatible version of Voodoo for the SG3, can you share yours?
livito said:
I havent found a compatible version of Voodoo for the SG3, can you share yours?
Click to expand...
Click to collapse
me either im on the search for a fix as wee speak have you tried the headset gain in phone settings? seems to be implemented couple of nightlys ago
mw86 said:
Thanks i didn't remember inverted gapps you are right. I changed and added all of the values in the txt document i posted. They weren't for a fix, i always use them. Thats a list if the values i use.
Edit: most of them all add performance in some way. I didn't use any network build props so it could be more universal for other roms...
GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
Click to expand...
Click to collapse
agreed thanks for thoes prop tweaks whats your network tweaks i assume they only effect 3g
zkz90 said:
I confirmed this morning that ktoon kernel (12/29) breaks audio (pandora, google music, 8tracks, etc) while stock kernel is fine on 1/1 nightly (clean flashed). On stock kernel, BT audio (google music) will play ok for 10-20 secs and then start fading in and out at a faster playback speed. You can reset this by making a phone call, but then you get another 10-20 secs of good audio before it starts up again. Someone should mention this on the dev thread at some point.
Also: if you're having problems with stock 1/1 nightly...do a clean flash. all my problems went away.
Click to expand...
Click to collapse
there is a workaround in the op for streaming music players not working on kt kernel
Dreamlogix said:
agreed thanks for thoes prop tweaks whats your network tweaks i assume they only effect 3g
there is a workaround in the op for streaming music players not working on kt kernel
Click to expand...
Click to collapse
Your welcome, ui should be smooth with those.
I am not using any network build props is what i mean. I didn't want to play with tt for now to ensure my network works fine. So that txt document has none in it either. It is a bunch of tweaks gathered but no real network adjustments (i didn't want to negatively effect my setup or others)
GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk

Categories

Resources