yashsingh1/xdaforums huggingface dataset:
[E 2015 CDMA Android Development] deega:
I picked up a Sprint Prepaid XT1526 today and after finally getting it to activate I found this in the same location.

Note that the numeric=312530 mcc=312 mnc=530 was accurate under stock, but as soon as I flashed CAF-6.0.1 it was hunting in 310120 again. That provisioning client does some funny stuff.

I haven't fully activated service on the phone so I cannot confirm that 310120 is the proper carrier, but it does prompt me to log into the network using the n.sprpre.ispsn and gives an !4G indicator.

>>>>> Dumping cursor android.database.sqlite.SQLiteCursor@1c2d0
0 {
_id=2903
name=otasn
numeric=312530
mcc=312
mnc=530
apn=otasn
user=null
server=null
password=null
proxy=
port=
mmsproxy=68.28.31.2
mmsport=80
mmsc=http://mmsc.vmobl.com:8088
authtype=0
type=fota
current=1
protocol=IPV4
roaming_protocol=IPV4
carrier_enabled=1
bearer=13
bearers=null
mvno_type=
mvno_match_data=
sub_id=-1
profile_id=-1
modem_cognitive=0
max_conns=0
wait_time=0
max_conns_time=0
mtu=null
mode=17
}
1 {
_id=2904
name=otasn
numeric=312530
mcc=312
mnc=530
apn=otasn
user=null
server=null
password=null
proxy=
port=
mmsproxy=68.28.31.2
mmsport=80
mmsc=http://mmsc.vmobl.com:8088
authtype=0
type=fota
current=1
protocol=IPV4
roaming_protocol=IPV4
carrier_enabled=1
bearer=14
bearers=null
mvno_type=
mvno_match_data=
sub_id=-1
profile_id=-1
modem_cognitive=0
max_conns=0
wait_time=0
max_conns_time=0
mtu=null
mode=17
}
2 {
_id=2956
name=sprpre.pamsn
numeric=312530
mcc=312
mnc=530
apn=sprpre.pamsn
user=null
server=
password=null
proxy=
port=
mmsproxy=68.28.31.2
mmsport=80
mmsc=http://mmsc.vmobl.com:8088
authtype=0
type=dun
current=1
protocol=IPV4
roaming_protocol=IPV4
carrier_enabled=1
bearer=14
bearers=null
mvno_type=
mvno_match_data=
sub_id=1
profile_id=-1
modem_cognitive=0
max_conns=0
wait_time=0
max_conns_time=0
mtu=null
mode=17
}
3 {
_id=2957
name=sprpre.pamsn
numeric=312530
mcc=312
mnc=530
apn=sprpre.pamsn
user=null
server=
password=null
proxy=
port=
mmsproxy=68.28.31.2
mmsport=80
mmsc=http://mmsc.vmobl.com:8088
authtype=0
type=dun
current=1
protocol=IPV4
roaming_protocol=IPV4
carrier_enabled=1
bearer=13
bearers=null
mvno_type=
mvno_match_data=
sub_id=1
profile_id=-1
modem_cognitive=0
max_conns=0
wait_time=0
max_conns_time=0
mtu=null
mode=17
}
4 {
_id=2958
name=n.sprpre.ispsn
numeric=312530
mcc=312
mnc=530
apn=n.sprpre.ispsn
user=null
server=
password=null
proxy=
port=
mmsproxy=68.28.31.2
mmsport=80
mmsc=http://mmsc.vmobl.com:8088
authtype=0
type=default,mms,ia
current=1
protocol=IPV4
roaming_protocol=IPV4
carrier_enabled=1
bearer=14
bearers=null
mvno_type=
mvno_match_data=
sub_id=1
profile_id=-1
modem_cognitive=0
max_conns=0
wait_time=0
max_conns_time=0
mtu=null
mode=17
}
5 {
_id=2959
name=n.sprpre.ispsn
numeric=312530
mcc=312
mnc=530
apn=n.sprpre.ispsn
user=null
server=
password=null
proxy=
port=
mmsproxy=68.28.31.2
mmsport=80
mmsc=http://mmsc.vmobl.com:8088
authtype=0
type=default,mms,ia
current=1
protocol=IPV4
roaming_protocol=IPV4
carrier_enabled=1
bearer=13
bearers=null
mvno_type=
mvno_match_data=
sub_id=1
profile_id=-1
modem_cognitive=0
max_conns=0
wait_time=0
max_conns_time=0
mtu=null
mode=17
}
<<<<<
[Galaxy S6 Q&A, Help & Troubleshooting] Switiz:
Hey guys

Can someone port the S6 Edge+ or even the Note 5 camera apk to S6 ?

I really want the ISO50 and the shutter speed <3

I would do it but don't know how. Tried to push and give permissions to camera apk that I got from a S6Edge+ rom, but I get Fc's :(

Thx in advance
[XDA Assist] XDA Visitor:
Hello I'll currently deciding whether to get an Xperia s or the Xperia sp, I noticed that the S is on sonys AOSP page along with some other devices but the SP wasn't on there, what does this mean or doesn't it really matter, also I would really like Android M/6 on whatever device I choose does it affect that?
[XDA Assist] Saber:
Hi,

Thanks for using XDA assist.

If the device isn't listed on Sony's AOSP supported devices, that just means that they will only give updates with Sony's skin of Android. It won't impact custom ROM development as that will be dependent on the number of developers in the community with the same device as you choose, as well as the availability of the phone's source code. There are ROMs available on XDA for the Xperia SP visit the forum below:

Xperia SP Android Development

Xperia SP Original Android Development

Marshmallow is still a WIP for the Xperia SP device, so you may not see it as a suitable upgrade.

As for the Xperia S, here is the development forum below:

Xperia S Android Development

The xperia s has more marshmallow roms compared to the xperia sp, so you may prefer it because it is a more actively developed device.

Good Luck! - gsstudios
[XDA Assist] KING_SONY01:
Hello thanks for the reply, what do you mean by "only give updates with Sony's skin of Android" I thought neither the Xperia S or SP got updated anymore with them being older phones or am I not quite getting this haha? Also if you could recommend one I would really appreciate it thanks.
[Samsung Galaxy Gear] jordan235:
my gear isn't connecting to my rooted nexus 6. gear manager finds the watch but does not connect to it. Gear still says "in the samsung gear application, select the device you want to connect to." And version Gear manager ver.2.0.14031004 doesn't even start on my phone says "Unfortunately, gear manager has stopped" ,

The latest version says "Unable to connect to the gear. connecting to the gear is not supported by the mobile device or your software needed to be updated. check that your mobile device is able to connect to then update your mobile device software"

Please i need help asap

thanks in advance
[Galaxy Tab 4 Q&A, Help & Troubleshooting] AllenPlaysGames:
I have a Samsung Galaxy Tab 4 (SM-T337A) 5.1.1 LOLLIPOP but idk why Samsung Kies 3 is not recognizing my device, shouldn't smart switch be supporting those new samsung devices?
[MTCB Hardware Development] supaneko:
Hey, all.

I installed Malaysk's latest ROM on my Eonon GA5151F. It's one of the HuiFei units for a Mazda. Instantly I noticed the sound quality is garbage and am determined to turn it around. On second thought, it might a KDL type unit ... it doesn't actually say under hardware info.

I followed aluver's awesome advice on getting USB audio working after finally getting a FiiO E18 in the mail.

I'm stuck: I can only play via UAPP (USB Audio Player Pro) and even when I do play in UAPP, the sound quickly becomes jumbled and distorted. If I set to 25ms for the buffer, I get about 20 seconds of play time before it crashes.

I've tried a regular 1m cable and even a tiny, short .25m cable but no change.

I do see that I have better luck using alluver's provided audio.primary.rk30board.so file but that only gives me the 20 seconds of play time. That file is 133K in size while the one installed on the unit (or maybe it's from the Malaysk ROM) is 213K. I did not see anywhere in my unit's file to edit and hard write the pcmC2D0c.

Any ideas?

Note: I see a similar thread of a similar issue but thought it would be rude to light back. :)
[MTCB Hardware Development] supaneko:
I tried to open up the unit but the CD drive is preventing me from getting a good look in. The USB cable that runs from inside to outside the unit is quite long. Seems like it might actually be 1.5 meters.

How can I get in there to pull this thing out and try a short cord? Or should I look in to a powered USB hub (such as the one sold by Carnetix)?
[MTCB Hardware Development] supaneko:
How interesting: I purchased a 7-port powered USB hub (these are quite hard to find in stores!) and now it works! I just plugged the thing in and connected a regular 1m cable to the hub and FiiO and UAPP plays without issue. I did have to enable the first two tweaks in the settings but it's a good start.

Issue continues though: only UAPP will play for me. I am guessing this is a driver issue but not sure where to begin on solving this.

Also, if I have the device turned on while the head unit boots, the head unit sits in safe mode.
[MTCB Hardware Development] aluver:
[MENTION=4979796]supaneko[/MENTION]

Congradulations! Now you have enough power to supply your E18.

About how to make it possible all android sounds going to E18 without UAPP.

All ROMs higher than 4.2 android have audio.primary.rk30board.so file without that numbers to change - it's dynamic.

I have found the other way on 4.4 to make sound routing. It's more right way. Through ALSA.

But I'm not sure I can write a guide now, because I can't remember all I did in details.

And, secondly, I hope there is a more simple way, that was founded by kumarai, that I did not tested yet. His solution is to use system.img from KGL_rk3188_h(20151019) in his ROM. He says he just copied my drivers and wrote insmod strings to install-recovery.sh and all works flawlessly, with hot-plug, as I have working too.

Here is his post with that custom ROM on russian KGL HU forum http://4pda.ru/forum/index.php?showtopic=704299&view=findpost&p=45437941

You can try it (at your own risk, of course)
[MTCB Hardware Development] supaneko:
aluver, your kindness is contagious. Thank you for that. :)

I will try the link you provided and report back. I'm guessing flashing system.img shouldn't kill me because I can always reflash if needed.

At this point, I am still super determined to get this working. You've helped me in the right direction, aluver. Thanks again!
[MTCB Hardware Development] supaneko:
Well .... I thought that would be useful but I am on an RK3188 unit and then, it also dawned on me, I have the latest Malaysk ROM running. I was thinking I could just install this and extract the install-recovery.sh but it's not for the same unit.

I downloaded the update.rar listed and it only had an update.img in it. I tried to extract it using simg2img but it gives me an error.

I've PM'ed kumarai on here in hopes that he can help me out. :)

I'll give it another go tomorrow.
[MTCB Hardware Development] aluver:
[MENTION=4979796]supaneko[/MENTION]

Oh, sorry, I thought you have RK3066. That image is not for RK3188 HU of course. But I think it makes things simpler. The trick of kumarai was exactly RK3188 system.img. It must work on RK3188 ROM "from the box" with your HU...

You just need to check what system.img version (date) Malaysk has used for the ROM you have. Or just give me a link to your ROM version. I'll check it by myself.

I use RK3xxx Firmware Tools for unpacking Rockchip update.img, system.img, boot.img & recovery.img
[MTCB Hardware Development] supaneko:
I am using the latest (posted here anyway) Malaysk ROM for 800x480 RK3188: https://yadi.sk/d/R0RY7sxbmmuwi

I located the RK3xxx Tools but .... they're for Windows and I'm on Linux. :\

I'd appreciate the help, aluver. :D
[MTCB Hardware Development] aluver:
I have compared system folders of ROMs from kumarai and yours from the link you provided.

They are differ by files at /system/lib

but files at /system/lib/hw are the same

I think something in libaudioflinger.so or other library at /system/lib may do the trick with sound routing.

kumarai's system version 20151012.145613

yours - has a later date - 20151130.180905

Don't understand what's wrong with it...

Now I going to find Malaysk's ROM with same version of system.img as kumarai has.
[MTCB Hardware Development] aluver:
Can't find needed version among Malaysk's ROMs. Looks like he didn't use that.

The previous to yours version has 20150824.182544 system.img only.

But I have another solution for routing for now.

You can replace audio.primary.rk30board.so by my patched version (already tested on RK3188). Do a backup of the original file, check it's permissions before.

Copy attached audio.primary.rk30board.so to /system/lib/hw folder and change permissions to original file had.

Power off HU and wait few minutes it complitely turned off.

After Power on check the sound is going to DAC (you may hear effect even without reboot - just after replacing the file).

If you will have a problem with sound stucks after some time, you'll need to edit /etc/audio_policy.conf (make backup first)

Delete whole this alsa_usb part of it:

alsa_usb {
outputs {
alsa_usb {
sampling_rates 44100|48000
channel_masks AUDIO_CHANNEL_OUT_STEREO
formats AUDIO_FORMAT_PCM_16_BIT
devices AUDIO_DEVICE_OUT_ANLG_DOCK_HEADSET|AUDIO_DEVICE_OUT_DGTL_DOCK_HEADSET
}
}
inputs {
alsa_usb {
sampling_rates 8000|11025|16000|22050|32000|44100|48000
channel_masks AUDIO_CHANNEL_IN_MONO|AUDIO_CHANNEL_IN_STEREO
formats AUDIO_FORMAT_PCM_16_BIT
devices AUDIO_DEVICE_IN_ANLG_DOCK_HEADSET
}
}
}

Because it can make a conflict. Reboot is needed to take effect.

By the way, did you have checked insmod's result? It must load all 4 modules *.ko without any errors.

Good luck and post any information about your progress.
[MTCB Hardware Development] supaneko:
SUCCESS!!

The insmod commands were already in there thanks to your original post, aluver. I replaced the .so file originally supplied in that post with what you attached here and ... it works! The ALSA lines were already in there so I didn't need to change that.

IT WORKS! I am terribly excited. :D

One final thing: if I have the FiiO device turned on when the Android boots, the unit boots into Safe Mode. I suspect there might not be much of a solution for this. Any ideas, aluver?
[MTCB Hardware Development] supaneko:
Alright. Made the drive home and ... it kept on working! I am so happy, aluver. Thank you.

I saw in another thread a mention about the volume control not working. This does indeed seem to be the case for me as well. I tried using the alsa_amixer command in Terminal but get a "Command not found" error when I do.

Out of curiosity, what DSP do you use, aluver?
[MTCB Hardware Development] aluver:
You didn't understand - You have to DELETE all that strings I wrote from audio_policy.conf and save it. They make a conflict I think.

I think this problem should gone, if you delete strings from audio_policy.conf as I told you.

Sorry, can't understand this... What drive?

Did you install Alsamixer from google play? It must be installed before use of mtc-service and\or alsa_amixer commands.

I think we need to make sound routing scheme better. As for me, I made it through alsa, not by replacing digits in audio.primary.rk30board.so.

With alsa configuring, we can make lossless 24bit volume control. Now we have a dynamic range losses because of 16bit volume control only.

Each -6dB from max digital volume are equal to 1-bit of bit depth loss.

I.e. if you listening music at volume position 10 of 30, it is about -40dB, you hear about (16bit - 40/6)~=10bit sound only!

But we know that a human's ear is logarithmic, so we can hear this losses.

To prevent that we can do the trick with adding amount of zero LSBs to make 24bit sound from 16bit source.

Then the digital volume will not become by fear for us.

Sorry for my English. I hope you understand.

I have russian amplifier with built-in modified by myself 8-channels DSP, based on 2 chips Analog Devices ADAU1701. But this DSP is not "for all". The sound processing algorithms for it I build in SigmaStudio. This is hard for usual people, but is very interesting for me :).

The chain is: HU RK3066 Android 4.4.4 -> HiFiMeDIY Sabre U2 24/96 USB-DAC -> toslink -> Ryazanpribor X1 mkII (w/mod DSP X5 8channels)-> Focal Performance PS165FX, P25F+Pioneer GM-D8601
[MTCB Hardware Development] supaneko:
You amaze me, aluver. Again, thank you.

I installed Alsamixer AND the modified MCT service app. Volume control is working! There is one bug though: when I hit the volume up or down, a + and - toast pops up. The problem is that if I go from a volume of 30 down to 0, this +/i will pop up 30 times ... that's along with the volume bar at the bottom of the screen. I can turn it off by turning off the Media keys option in MCT but doing that kills, well, the media keys.

Also, I removed the lines specified from audio_policy.conf. If the FiiO is turned on while Android boots, it still goes in to Safe Mode. I did notice that after removing those lines, I started to get crackling, hissing, and just overall poor sound quality so I re-added the lines and the problems went away. It's still TOO QUIET though!

How can I make these changes you mention in ALSA? I have some sharp hearing myself and it's driving me nuts that things just don't sound as good as they should. I am curious to see your own ALSA parameters.

Quite the setup you have, aluver. I find it inspiring. One day, maybe I'll have the patience to program my own slopes and equalizations. We'll see. ;)
[MTCB Hardware Development] aluver:
I am glad to help somebody, who has a good target :) About a + and - toast popups - it can be disabled in the code of mtc-service. I do not like that too, but have no time to make this job.

It is very interesting effect.... I can't explain it yet. Let's try to determine the problem's cause by looking at logs. Just install CatLog from google play and try to show me what happens at start of HU with FiiO turned on.

Sorry, but I cannot write it right now. I need to collect all information and copy changed drivers from my HU. Then I going to do a full guide. I made my installation at summer, and I am affraid to forget some details.

Thank you. All is in our hands. Keep moving ;)

I forgot about "too quiet". Didn't you install any android mixers or volume regulators?
[MTCB Hardware Development] supaneko:
aluver, I haven't forgotten. Been a very busy week.

I got a new DSP and put that in (though not as fancy as your's ;) ). Totally resolved my volume/gain issues but I'm wondering: what do you mean about the volume and the bits changing from 24?

I installed CatLog and when I did a reboot with the DAC powered on, the unit got stuck in a bootloop. It's never done that before. I'll have to give it a try again tomorrow or figure out what's changed to cause that. I'll report back again soon.

Thanks again, aluver! :)
[MTCB Hardware Development] aluver:
[MENTION=4979796]supaneko[/MENTION]

What DSP did you get? Does it have a remote volume control unit? And what's the cause for volume/gain issues?

About bit depth and volume - read this http://www.head-fi.org/t/671220/eff...e-to-keep-software-at-full-volume-is-nonsense

That is why I say we need 24bit for the lossless volume regulating within HU.

If you have DSP with remote control unit now, you better use that, because it has 56 or 64 bit of internal processing deph (Volume at HU must be 100%).

About a bootloop. You can try to comment the 4 usb-audio driver insmod strings in install-recovery.sh (check the permissions after that! do not lose root!), then reboot without them, run catlog, and then type insmod commands at terminal emulator (don't forget "su" at first), and see what happens in catlog.
[MTCB Hardware Development] supaneko:
[MENTION=6011328]aluver[/MENTION], I picked up an AudioControl DQDX. It has a remote control but it only controls the bass or sets the various delays and other settings. I am thinking of swapping out the DAC I picked up with another single DIN head unit that supports DAC. That way, I can control the volume with an analog dial and still have steering wheel controls work. That's down the road though. I need to upgrade my amp and some other items first. Might just use the volume control on the DAC I picked up for now.

I'll post the CatLog logs in a bit. Thanks again, aluver.
[MTCB Hardware Development] aluver:
Wow, your DSP is very rare in my world :) AudioControl's conceptuality is a vintage radicalism.

I don't understand why are you going to swap your DAC with a single DIN HU. In most cases analog volume control can't be used when you build a system with DSP. And analog volume control has it's own noise...

I think you better have to think about swapping of DSP. Something like Helix DSP Pro or anything else, more widely using our time.

About using the volume control on the DAC - You better have to connect your DSP and DAC by digital interface if you don't want to kill the sound by needless DA-AD conversions.
[MTCB Hardware Development] supaneko:
You make me laugh, aluver. :D

Yeah, one day I'll have the cash for a Helix DSP but ... for now ... I have to be budget conscious. Helix DSP is certainly in the plans though. Just gotta get the "eaiser" stuff like this Android head unit working first! :)

Again, I'll post the logs later!

aluver, I'm looking over the specs of the Helix DSP and ... wow. I'm impressed. I've added it to my bucket list. Will have to pick one up after I swap out my speakers for better ones.

Those Focal's you run, did you find them too bright at all? I've heard the Focals can be a little bright and I am sensitive to the higher freqs.
[MTCB Hardware Development] aluver:
To stay in budget - look at MD.Lab DSP 8. It's rather good quality product from China (Trademark - Germany). They already made even WiFi-module to recieve sound from any Android/iOS device... but I think it is not SQ way, because it's connection to DSP is analog.

Yes, Focals are bright, and I like them. But if you are going to use DSP - it's not a problem :) Soundstage is very good! What styles of music do you listen?
[MTCB Hardware Development] supaneko:
My music style varies but lately it's mostly been EDM (complextro, glitch hop, drum & bass, electro house).

I have "good" news: the DQDX already started acting up. I came out to the car this morning and she wasn't sending any audio to my subs. Once Amazon refunds the money, I'm gonna pick up the Helix DSP.

Question for you aluver: what USB DAC should I get? I am thinking a HiFiMe 9018 since it has opitcal out. I have heard of the Sabre U2 but it seems they've been disconnected.

And ... what kind of music you play on your system, aluver?
[MTCB Hardware Development] aluver:
Yes, I think you need some more dark than focal fx series for your music. My basic styles are... all from rock to progressive metal, but I like some pop too - a-ha, adele, sia... :) (especialy when my children are in car)

I am very glad for you. With Helix you will be able to switch automaticaly between the optical and analog inputs.

So you will be able to listen HU radio and bluetooth when music from dac stopped.

About 9018 - it rather good choice, but note, it has adaptive mode instead of asynchronous in sabre U2, and it's quite good ess9018 DAC will never be used in case of optical connection (money for nothing). I will try to search a better-quality async usb-spdif converter for that money (without DAC chip). For example, litle more expensive Hiface two is known as a quite best SQ converter and it can work with andoid, but it has coax out only. If you are going pick up helix dsp (not pro version), it's not for you.

I think about xmos-based usb-spdif converter with a very low jitter, but it must be checked for android compatibility. Do some search and post then.

Also, look at this - very good choice.
[MTCB Hardware Development] supaneko:
I'm gonna pick up the UH1 unless you say otherwise, aluver. My only concern is: will it be powered successfully via our head units? I wonder if I should pick up a powered USB hub to go with it too just in case.
[MTCB Hardware Development] aluver:
Good choice! Yes, sure. I think the power of HU's usb will be more than enough, but within a well-powered hub (using any Ultralow Noise Regulator) you'll get a more clear uh1 supply.

Your system is going to be named "Noneconformist" :good:
[MTCB Hardware Development] supaneko:
Hmmm ... Ultralow Noise Regulator? When it comes to USB hubs, how do I know if this one has it or not? This is what I was thinking of picking up, if needed:

http://www.amazon.com/DC-Powered-4-Port-USB-CNX-P5USB-systems/dp/B004NDU37A

Noneconformist!? I like the ring to it, aluver.
[MTCB Hardware Development] aluver:
The UNR may be listed in a description of hub.

Your linked hub has (looks like this) a low noise DC-DC converter. This is rather same thing, but little more noisy, not surely noticeable. It's quite enough quality for power supply of uh1, I think.