ONKYO DP-X1 | Dual Sabre Dacs | Balanced | Sabre BTL Amp | MQA | DSD 256 | Android 5 |

[hansgw]

@hansgw only 5 more posts, almost there!!! Welcome to Head-fi!!!

Yes! Thanks for welcoming...

 

[Dillan]

Thats a lot of storage for a portable! Thats both hilarious and ingenious hehehe

 

[TheOneInYellow]

OK, but you have to download them again, of course!
https://we.tl/pPRiTCDtyd

Sorry, got busy.

Here's part two of hansgw crazy monster DP-X1 storage on steroids (part 1 link here!):

 

[TheOneInYellow]

Nice dream I wish come true. I would go not so far - first Orpheus OK for me to dream about Maybe I am retorgrade
Well, need to think how to connect X1 to Stax SRM T1 ..... need all family to send out from home for quiet evening

Ha ha, nice on first Orpheus HE90 choice

If you want to connect DP-X1 to Stax/any electrostatic headphone, there is a way...

The iFi Audio Pro iCan is a great upcoming amp with huge number of inputs and outputs, but eventually you can buy an iFi Audio Electrostatic Headphone Energiser add-on for the Pro iCan.

All you will need then is a 2.5 mm TRRS to dual 3-Pin XLR interconnect cable to connect DP-X1 to Pro iCan, get that energiser add-on when it's out, and then connect electrostatic headphones!

Sources:

• HiFi Philosophy (in English)
• Samma3a

You're welcome <3

 

[headfi19]

Ha ha, nice on first Orpheus HE90 choice

If you want to connect DP-X1 to Stax/any electrostatic headphone, there is a way...

The iFi Audio Pro iCan is a great upcoming amp with huge number of inputs and outputs, but eventually you can buy an iFi Audio Electrostatic Headphone Energiser add-on for the Pro iCan.

All you will need then is a 2.5 mm TRRS to dual 3-Pin XLR interconnect cable to connect DP-X1 to Pro iCan, get that energiser add-on when it's out, and then connect electrostatic headphones!

Sources:

1. HiFi Philosophy (in English)
2. Samma3a

You're welcome <3

Dear TheOneInYellow,
Would you please advise me that is there any way to find out by serial number whether it is newer units or older batches that have head phone Jack problem because I bought it two weeks ago from Ebay seller from Hong Kong and thinking to return it.Thanks

 

[TheOneInYellow]

  Dear TheOneInYellow,
Would you please advise me that is there any way to find out by serial number whether it is newer units or older batches that have head phone Jack problem because I bought it two weeks ago from Ebay seller from Hong Kong and thinking to return it.Thanks

 
I believe you PM'ed me this question, but my answer is relevant to all:
 
No, I cannot.

I mentioned that in my original post.

All I can say are two thing:

1. Contact Onkyo in your territory and let them confirm if you have an older batch.
2. If you see any, any, wobbliness on either output jack, it's an older unit.

I would say that if you bought it from Hong Kong via eBay...it might, might, be an older unit.

Sorry I can't help any further.

 

[DrGonzo]

@TheOneInYellow just wanted to take the time to THANK you for being helpful and informative on this thread. I have gained an insane amount of knowledge on these forums about a hobby that I am very passionate about. Members, like yourself, go the extra mile to help others on this awesome forum, so, again, Thank you!

 

[TheOneInYellow]

@TheOneInYellow just wanted to take the time to THANK you for being helpful and informative on this thread. I have gained an insane amount of knowledge on these forums about a hobby that I am very passionate about. Members, like yourself, go the extra mile to help others on this awesome forum, so, again, Thank you!

Awwwwww....I'm blushing...really... <3

I'm not the only member of course, and there are some stellar members on this thread too; I also do end up disappearing for weeks at a time, but I try my best to help full-on.

I have a simple rule: if I am going to post, I'll post well.

I'm more active on Twitter, but ignoring all that, I am humbled, and thank you DrGonzo ^^

 

[Peridot]

I also hope that the Cavalli Audio Carbon amp can have multiple active headphone outputs; this is so that I can use my headphones direct into the amp, and one connection direct to my SubPac S2 seatback tactile bass system.

 
All headphone outputs are active and can be used simultaneously. 

 

[Larethio]

Does standard headphone out utilize just one or both DACs/Amps?

 

[TheOneInYellow]

All headphone outputs are active and can be used simultaneously. 

AWESOME

That means that I can use the 6.3 mm SE output for my SubPac S2 seatback tactile bass system (for bass only), and a DHC 2.5 mm to 4-Pin XLR ultrashort adapter for the 4-Pin balanced output (for either my Audeze EL-8 Titanium or Heir Audio 4.Ai IEM).

PERFECT

Thank you Peridot!

 

[Larethio]

I just did some digging and found that, while the bootloader is locked by default, it's ridiculously easy to unlock, as long as you have Android Studio and thus adb/fastboot installed.

Recheck the device info and the bootloader is unlocked.

It is also easy to boot into recovery (hold down power + next track) or the bootloader (hold down power + prev track) from powered off.

If we get a recovery image, there's no reason we shouldn't be able to fix any software issues ourselves.

Just as a precaution, I wouldn't recommend that anybody does this.  It serves no purpose at the moment other than to see that we can do it.  My device boots up fine and has been rooted for well over a month now, so as long as you are careful it shouldn't be a problem.

As for the user who deleted their build.prop, you can actually use "adb" to push a valid file back to the device and thus fix it without a ROM.

http://stackoverflow.com/questions/24887073/push-build-prop-to-system-build-prop

Spoiler: Default build.prop

#af.resampler.quality=4
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=LMY47V
ro.build.sw.version=0.1.30.8_20160322.215713
ro.build.display.id=LMY47V
ro.build.version.incremental=eng..20160322.215713
ro.build.version.sdk=22
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.1.1
ro.build.version.security_patch=2016-03-01
ro.build.date=二  3月 22 22:01:00 CST 2016
ro.build.date.utc=1458655260
ro.build.type=user
ro.build.user=
ro.build.host=josh
ro.build.tags=release-keys
ro.build.flavor=Rai_Zin_32-user
ro.product.model=DP-X1
ro.product.brand=Onkyo
ro.product.name=Rai_Zin_32
ro.product.device=Rai_Zin_32
ro.product.board=Rai_Zin_32
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=O&P Innovations
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8974
# ro.build.product is obsolete; use ro.product.device
ro.build.product=Rai_Zin_32
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=Rai_Zin_32-user 5.1.1 LMY47V eng..20160322.215713 release-keys
ro.build.fingerprint=Onkyo/Rai_Zin_32/Rai_Zin_32:5.1.1/LMY47V/03222200:user/release-keys
ro.build.characteristics=tablet
# end build properties
#
# from device/qcom/Rai_Zin_32/system.prop
#
#
# system.prop for msm8974
#
 
rild.libpath=/vendor/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
# Start in global mode
ro.telephony.default_network=10
 
debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=c2d
persist.hwc.mdpcomp.enable=true
debug.mdpcomp.4k2kSplit=1
debug.mdpcomp.logs=0
dalvik.vm.heapsize=36m
dev.pm.dyn_samplingrate=1
persist.demo.hdmirotationlock=false
 
ro.hdmi.enable=true
persist.speaker.prot.enable=false
qcom.hw.aac.encoder=true
#
# system props for the cne module
#
persist.cne.feature=1
 
#system props for the MM modules
 
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
mmp.enable.3g2=true
mm.enable.smoothstreaming=true
media.aac_51_output_enabled=true
#37491 is decimal sum of supported codecs in AAL
#codecs: AVI AC3 ASF AAC QCP DTS 3G2 MP2TS
mm.enable.qcom_parser=37491
 
# Default to AwesomePlayer
media.stagefright.use-awesome=true
 
# VIDC: debug_levels
# 1:ERROR 2:HIGH 4:LOW 0:NOLOGS 7:AllLOGS
vidc.debug.level=1
#
# system props for the data modules
#
ro.use_data_netmgrd=true
persist.data.netmgrd.qos.enable=true
ro.data.large_tcp_window_size=true
 
#system props for time-services
persist.timed.enable=true
 
#
# system prop for opengles version
#
# 196608 is decimal for 0x30000 to report version 3
ro.opengles.version=196608
 
# System property for cabl
ro.qualcomm.cabl=1
 
#
# System props for telephony
# System prop to turn on CdmaLTEPhone always
telephony.lteOnCdmaDevice=1
 
#
# System props for bluetooth
# System prop to turn on hfp client
bluetooth.hfp.client=1
 
#
# System props for bluetooth LE Always on feature
#
ro.bluetooth.alwaysbleon=true
 
#Simulate sdcard on /data/media
#
persist.fuse_sdcard=true
 
#
#snapdragon value add features
#
ro.qc.sdk.audio.ssr=false
##fluencetype can be "fluence" or "fluencepro" or "none"
ro.qc.sdk.audio.fluencetype=none
persist.audio.fluence.voicecall=true
persist.audio.fluence.voicerec=false
persist.audio.fluence.speaker=true
 
ro.qc.sdk.sensors.gestures=true
ro.qc.sdk.gestures.camera=false
ro.qc.sdk.camera.facialproc=false
# system prop for NFC DT
ro.nfc.port=I2C
#property to enable user to access Google WFD settings.
persist.debug.wfd.enable=1
#property to choose between virtual/external wfd display
persist.sys.wfd.virtual=0
tunnel.audio.encode = false
 
#Buffer size in kbytes for compress offload playback
audio.offload.buffer.size.kb=32
 
#Enable offload audio video playback by default
av.offload.enable=true
 
#enable voice path for PCM VoIP by default
use.voice.path.for.pcm.voip=true
 
#hwui properties
ro.hwui.texture_cache_size=72
ro.hwui.layer_cache_size=48
ro.hwui.r_buffer_cache_size=8
ro.hwui.path_cache_size=32
ro.hwui.gradient_cache_size=1
ro.hwui.drop_shadow_cache_size=6
ro.hwui.texture_cache_flushrate=0.4
ro.hwui.text_small_cache_width=1024
ro.hwui.text_small_cache_height=1024
ro.hwui.text_large_cache_width=2048
ro.hwui.text_large_cache_height=1024
 
#disable dsp gapless mode by default
audio.offload.gapless.enabled=true
 
#MIMO++ 20150701 for Elton ask(OTG mass storage)
persist.sys.isUsbOtgEnabled=true
#
# PCM offload
#
#audio.offload.pcm.16bit.enable=true
audio.offload.pcm.24bit.enable=true
 
#
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.carrier=unknown
ro.config.alarm_alert=Alarm_Classic.ogg
ro.vendor.extension_library=libqti-perfd-client.so
persist.radio.apm_sim_not_pwdn=1
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
drm.service.enabled=true
ro.com.widevine.cachesize=16777216
ro.com.google.clientidbase=android-onkyo
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=5.1_r3
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm.features=div
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
persist.gps.qc_nlp_in_use=1
persist.loc.nlp_name=com.qualcomm.location
ro.gps.agps_provider=1
ro.pip.gated=0
 

This didn't by chance delete all your data did it?

 

[sq3rjick]

No, unlocking my boot loader did not erase anything (I suspected it might). To be safe, though, I had a full backup of the device through Titanium Backup stored on my SD Card and removed my SD card from the device before I did anything.

I am currently trying to get a build of TWRP custom recovery built for the device.

 

[Johnny Woody]

No, unlocking my boot loader did not erase anything (I suspected it might). To be safe, though, I had a full backup of the device through Titanium Backup stored on my SD Card and removed my SD card from the device before I did anything.

I am currently trying to get a build of TWRP custom recovery built for the device.

Looking forward to update firmware through TWRP without unrooting my unit!

 

[Larethio]

No, unlocking my boot loader did not erase anything (I suspected it might). To be safe, though, I had a full backup of the device through Titanium Backup stored on my SD Card and removed my SD card from the device before I did anything.

I am currently trying to get a build of TWRP custom recovery built for the device.

Finally! A developer! I commend you for helping us.