ROM New Unofficial Lineage 14.1 d2spr WhenICanlies 4-10-18

MarkerB

Member
Oct 3, 2010
48
17
0
Distorted USB Audio

This ROM is great. It fixed the non-working camera and flashlight of the later official builds (the latest download I could find online was lineage-14.1-20171113-nightly-d2spr-signed.zip).

However, this ROM has problems with unlistenable USB audio. The sound is both distorted in the amplitude domain, and has a time-domain warble similar in sound to old tape with a very dirty capstan.

The T-Mobile variant exhibits the exact same problem as well. My Note 3 with the latest official T-Mobile LineageOS 14.1 ROM has no problem.

I've tried three different USB audio adapters, with the same results.

Since this is for my dedicated S3 media player, I sadly had to go back to the old official build with its camera/flashlight bugs.

I'm sure this is a rather technical problem. While I don't expect Joker1716 to have the time or resources to debug, the source to the abandoned official build is apparently still around. Perhaps whatever USB audio code was working in the official source code could be used to replace the code in this new unofficial build? I would be happy to test on the d2spr and d2tmo devices.

In any case, thank you Joker1716 for these noble efforts! Long live these old, solid devices...
 

Joker1716

Senior Member
Sep 24, 2014
201
331
103
St. Louis, MO. 63114
This ROM is great. It fixed the non-working camera and flashlight of the later official builds (the latest download I could find online was lineage-14.1-20171113-nightly-d2spr-signed.zip).

However, this ROM has problems with unlistenable USB audio. The sound is both distorted in the amplitude domain, and has a time-domain warble similar in sound to old tape with a very dirty capstan.

The T-Mobile variant exhibits the exact same problem as well. My Note 3 with the latest official T-Mobile LineageOS 14.1 ROM has no problem.

I've tried three different USB audio adapters, with the same results.

Since this is for my dedicated S3 media player, I sadly had to go back to the old official build with its camera/flashlight bugs.

I'm sure this is a rather technical problem. While I don't expect Joker1716 to have the time or resources to debug, the source to the abandoned official build is apparently still around. Perhaps whatever USB audio code was working in the official source code could be used to replace the code in this new unofficial build? I would be happy to test on the d2spr and d2tmo devices.

In any case, thank you Joker1716 for these noble efforts! Long live these old, solid devices...
In developer options there is this it may help
 

Attachments

MarkerB

Member
Oct 3, 2010
48
17
0
In developer options there is this it may help
Thanks. I hadn't seen that. I tried, and setting it to "Audio Source" doesn't seem to have any effect.

However, while trying this options in my various S3 ROMs, I've discovered that the problem comes and goes in all of them. Since the audio plays with inconsistent pitch, maybe it's a CPU load issue. The newer ROM may tax the CPU a little more, which might explain why it's more of problem there. My Note 3 might work fine because it's got a faster processor.

I'll see if I can manage my CPU usage better.
 

Joker1716

Senior Member
Sep 24, 2014
201
331
103
St. Louis, MO. 63114
Thanks. I hadn't seen that. I tried, and setting it to "Audio Source" doesn't seem to have any effect.

However, while trying this options in my various S3 ROMs, I've discovered that the problem comes and goes in all of them. Since the audio plays with inconsistent pitch, maybe it's a CPU load issue. The newer ROM may tax the CPU a little more, which might explain why it's more of problem there. My Note 3 might work fine because it's got a faster processor.

I'll see if I can manage my CPU usage better.
It may be the battery saver also I noticed that the Bluetooth audio is messed up when it is allowed to be managed so I would also try to turn off battery saver settings/battery, three dot menu ,battery optimisation , click on not optimised , select all apps, and look for cm audio .( I'm guessing its the cm audio services) also try the MIDI option
 
Last edited:

MarkerB

Member
Oct 3, 2010
48
17
0
It may be the battery saver... look for cm audio... also try the MIDI option
They sounded like good ideas, but no improvement. I turned off battery optimizations for CM Audio and everything else that seemed audio related.

I noticed the chances of no distortion get better if I use a simpler music player. I'm still trying to see if there are any other CPU controls.

I really appreciate the attention on this! Sorry I was so sure it was a solidly reproducible issue before.
 

MarkerB

Member
Oct 3, 2010
48
17
0
What Baseband is Recommended

I thought I'd try updating my baseband from ND8 to NJ2, to see if that helped my garbled USB audio issues. I installed the complete NJ2 stock ROM, which worked fine and had no USB audio issues. I wiped and then installed the latest LineageOS 14.1 Unofficial from this thread. It boots into the GUI, displays several "XXX app has stopped" messages, then does a reboot and never again leaves the animated LineageOS boot logo.

There's also an OH1 baseband, but people have complained about it.

What is the ideal baseband version for this unofficial d2spr LineageOS 14.1 build?

Thanks!
 

madbat99

Senior Member
Mar 1, 2014
5,538
3,285
113
I thought I'd try updating my baseband from ND8 to NJ2, to see if that helped my garbled USB audio issues. I installed the complete NJ2 stock ROM, which worked fine and had no USB audio issues. I wiped and then installed the latest LineageOS 14.1 Unofficial from this thread. It boots into the GUI, displays several "XXX app has stopped" messages, then does a reboot and never again leaves the animated LineageOS boot logo.

There's also an OH1 baseband, but people have complained about it.

What is the ideal baseband version for this unofficial d2spr LineageOS 14.1 build?

Thanks!
Be careful, there are 2 different OH1. One is for the triband, do not flash that.

All of those crashes are due to the way Android 5.0+ encrypts data. L-M-N all behave this way. Make sure to format data in twrp. Make sure to Format, not just wipe. Internal storage too. So make sure anything important is on your external sd.
 

MarkerB

Member
Oct 3, 2010
48
17
0
Be careful, there are 2 different OH1. One is for the triband, do not flash that.

All of those crashes are due to the way Android 5.0+ encrypts data. L-M-N all behave this way. Make sure to format data in twrp. Make sure to Format, not just wipe. Internal storage too. So make sure anything important is on your external sd.
Wow. Thanks for the knowledgeable response! I'll try a full format as you suggest.

It's odd, as I already had ND8 baseband working fine with this Nougat LineageOS. I was merely trying the NJ2 baseband. Is there an encryption difference between those?

The year-old final version of CarbonROM works great with NJ2. Sadly, it doesn't have an AptX HD ZIP available like LineageOS does.

Would the non-triband version of OH1 be something to try? One cannot downgrade a baseband, so I'm hesitant.
 

madbat99

Senior Member
Mar 1, 2014
5,538
3,285
113
Wow. Thanks for the knowledgeable response! I'll try a full format as you suggest.

It's odd, as I already had ND8 baseband working fine with this Nougat LineageOS. I was merely trying the NJ2 baseband. Is there an encryption difference between those?

The year-old final version of CarbonROM works great with NJ2. Sadly, it doesn't have an AptX HD ZIP available like LineageOS does.

Would the non-triband version of OH1 be something to try? One cannot downgrade a baseband, so I'm hesitant.
Your fine on nj2. Oh1 isn't really a big deal.
The encryption is from going from nougat back to KitKat.
You can downgrade, just not to anything older than nd8 (pre Knox).
I would stay on nj2. I have 2 that are still on nj2. Both work fine.
 

MarkerB

Member
Oct 3, 2010
48
17
0
Your fine on nj2. Oh1 isn't really a big deal.
The encryption is from going from nougat back to KitKat.
You can downgrade, just not to anything older than nd8 (pre Knox).
I would stay on nj2. I have 2 that are still on nj2. Both work fine.
OMG, you're a life saver! I did all you recommended, and things went very well. Now I have this official build, Aptx HD, and what seems to be more stable USB audio and Bluetooth audio. Thank you so much!

I still really don't understand the part about why going from ND8 to NJ3 would have caused an inability to install LineageOS, while another modern ROM tolerated it. I guess it would be good to know for the future. I have a T-Mobile S3 I'm thinking about doing something with... !
 

madbat99

Senior Member
Mar 1, 2014
5,538
3,285
113
OMG, you're a life saver! I did all you recommended, and things went very well. Now I have this official build, Aptx HD, and what seems to be more stable USB audio and Bluetooth audio. Thank you so much!

I still really don't understand the part about why going from ND8 to NJ3 would have caused an inability to install LineageOS, while another modern ROM tolerated it. I guess it would be good to know for the future. I have a T-Mobile S3 I'm thinking about doing something with... !
Maybe because when you went to nj3, you flashed the whole firmware without formatting. It happened to everyone who tried to go back to stock from anything higher than lollipop. But once you format data, it usually fixed it. Glad to hear it worked out.
 

cashmundy

Senior Member
Mar 9, 2010
247
64
0
d2usc? (SCH R530U)

I have a d2usc lying around I would like to use as a wifi-and-bluetooth tablet, don't care if the phone radio works. There are no builds I can find for this in the last few years, but it is a decent little phone/camera/tablet/whatever.

Here is something that might be useful if you want to look into it. I *think* the phone is about the same as d2spr or d2vze.

https://github.com/LineageOS/android_device_samsung_d2usc

I could pull the source and try a build if I had a 'device' tree that might work. It's been years since I built anything.
 
Last edited:

madbat99

Senior Member
Mar 1, 2014
5,538
3,285
113
I have a d2usc lying around I would like to use as a wifi-and-bluetooth tablet, don't care if the phone radio works. There are no builds I can find for this in the last few years, but it is a decent little phone/camera/tablet/whatever.

Here is something that might be useful if you want to look into it. I *think* the phone is about the same as d2spr or d2vze.

https://github.com/LineageOS/android_device_samsung_d2usc

I could pull the source and try a build if I had a 'device' tree that might work. It's been years since I built anything.
What's the model number? The sprint and Verizon models are completely different. They used to do unified builds for all the s3's (d2lte) but that stopped a long time ago. If the us Cellular version is sph L710, you can probably flash this rom just fine. You just won't get data. But if it's not, just use whichever "major" carrier model matches. Like if it has the same model number as Verizon, just try to find a d2vzw build, etc.
 

MarkerB

Member
Oct 3, 2010
48
17
0
Maybe because when you went to nj3, you flashed the whole firmware without formatting. It happened to everyone who tried to go back to stock from anything higher than lollipop. But once you format data, it usually fixed it. Glad to hear it worked out.
Well, it turns out the USB audio distortion/warbling came back. The problem tends to come and go rather randomly, so it's sometimes hard to know if I've fixed it until I've used it for hours.

I just gave up and went back to the stock ROM NJ2, and it seems to not have a problem. I'll have to limp along with stock after all. Bummer.

Thanks again for all your help!
 

madbat99

Senior Member
Mar 1, 2014
5,538
3,285
113
Well, it turns out the USB audio distortion/warbling came back. The problem tends to come and go rather randomly, so it's sometimes hard to know if I've fixed it until I've used it for hours.

I just gave up and went back to the stock ROM NJ2, and it seems to not have a problem. I'll have to limp along with stock after all. Bummer.

Thanks again for all your help!
Bummer. But a device is useless if it doesn't do what you want it to do. Stock isn't that bad, just old. Have fun. Glad to help.
 

cashmundy

Senior Member
Mar 9, 2010
247
64
0
SCH-R530U

It's an SCH-R530U:

http://phonedb.net/index.php?m=device&id=3625&c=samsung_sch-r530_galaxy_s_iii_lte

Samsungs with same cpu-gpu:

http://phonedb.net/index.php?m=device&s=query&d=detailed_specs&cpu=299#result

Such as SPH-L710:

http://phonedb.net/index.php?m=device&id=3648&c=samsung_sph-l710_galaxy_s_iii_lte

Unless the install checks are hacked, a rom for one phone model generally won't install on another model. I can try it if you think it might. d2spr or d2refreshspr?

What's the model number? The sprint and Verizon models are completely different. They used to do unified builds for all the s3's (d2lte) but that stopped a long time ago. If the us Cellular version is sph L710, you can probably flash this rom just fine. You just won't get data. But if it's not, just use whichever "major" carrier model matches. Like if it has the same model number as Verizon, just try to find a d2vzw build, etc.
 
Last edited: