You are using an out of date browser. It may not display this or other websites correctly. You should upgrade or use an alternative browser.
DX340 iBasso developed Discret DAC, Easily replaceable batteries, Amp Modules! ***New firmware on 1st page. v1.03 local update. AMP16 NOS Tube amp. Review on the 1st page! 4/6/25
Thank you! I’ve been looking for a sturdy desktop stand for a bit and seemed to only find option with large bars at the bottom the would cover the ports. Ordered!
Yea the first thing I did with the device was drain it all the way down till it shut down. Then i plugged it into a 5v 2amp charger to charge overnight. After 6 hours it was only at 80 percent
Yea I always do this on android devices when I get them. I drained it till it shut iff then used a 5v 2 amps charger and slow charged it overnight night with it off. It took over 6 hours. Im on 1.02 and used and wiped the device and reinstalled it via PC following the guide. If your charging your device with the supplied cable which utilize usba or ANY usba to usbc cable you will most likely not see this issue. I travel so i have a bunch of 150 watt multi port chargers. All of them show some sort of odd behavior when charging from usbc which is going to be PD protocol. The ones that have an a port, when its plugged into that everything is perfect. So far it seems like multiple people are seeing what I'm seeing. Trust me thats not how it’s supposed to work unless they don’t support PD which they haven't made public. To be a flag ship device expectations are for me anyway I should be able to plug this into my iPhones charger or what ever I have laying around and achieve the rapid charging this day and age. There may be one or two that don't agree but not 20. My Kaunn ultra listed on the there web site PD and QC 3.0. It charged properly with what ever i plugged it into. Im not noticing any power drain when turned off or anything like that, its literally seems to be the hand shake between the device and the charger for pd when trying to go into rapid charge, which its designed to do if the power is available. If your using a 10 watt chargers then its not going to go into rapid charger ohms law wont allow for that at only 10 wattts.
I ran several tests and realized that the the on/off dial doesn't depress as much as before. By pressing the lower part of the the on/off dial harder, I can start it, but not every time.
Very strange, I've never had any problems with the DX300/320.
Yea the first thing I did with the device was drain it all the way down till it shut down. Then i plugged it into a 5v 2amp charger to charge overnight. After 6 hours it was only at 80 percent
Yea I always do this on android devices when I get them. I drained it till it shut iff then used a 5v 2 amps charger and slow charged it overnight night with it off. It took over 6 hours. Im on 1.02 and used and wiped the device and reinstalled it via PC following the guide. If your charging your device with the supplied cable which utilize usba or ANY usba to usbc cable you will most likely not see this issue. I travel so i have a bunch of 150 watt multi port chargers. All of them show some sort of odd behavior when charging from usbc which is going to be PD protocol. The ones that have an a port, when its plugged into that everything is perfect. So far it seems like multiple people are seeing what I'm seeing. Trust me thats not how it’s supposed to work unless they don’t support PD which they haven't made public. To be a flag ship device expectations are for me anyway I should be able to plug this into my iPhones charger or what ever I have laying around and achieve the rapid charging this day and age. There may be one or two that don't agree but not 20. My Kaunn ultra listed on the there web site PD and QC 3.0. It charged properly with what ever i plugged it into. Im not noticing any power drain when turned off or anything like that, its literally seems to be the hand shake between the device and the charger for pd when trying to go into rapid charge, which its designed to do if the power is available. If your using a 10 watt chargers then its not going to go into rapid charger ohms law wont allow for that at only 10 wattts.
I had similar behavior at first. After calibration I have a playback time of well over 10 hours. It also charges without a problem. Do you have a charge limit of 80% set? Try turning it on and off.
I had similar behavior at first. After calibration I have a playback time of well over 10 hours. It also charges without a problem. Do you have a charge limit of 80% set? Try turning it on and off.
No charging limit set and I have well over 200 hours on it. What kind of charging brick and cable are you using? c to c or a to c? If you’re using a 35 watt or lower brick and an a to c brick and cable you probably are not going to see the problem I'm seeing. The unit will charge fine. And its only the higher wattage PD bricks that are showing the issues constantly, lower wattage PD chargers behave better. https://a.co/d/i68gLYa
Ive got three of these and none of them will charge the device on usbc. It just loops charging not charging. The usb a port work fine. I had a 320 and multiple other devices. The 340 is the only device Ive ever had this type of issue with. If you have macbook pro charger with the usbc output it will almost show the behavior 90 percent of the time. Thats what charger bloom recommended I use form the get go, they also said they saw the behavior i was talking about but it would always settle in and charge so they just ignored it. Which it will on certain chargers. The one like in the post here it will it settle in and charge at all. It charge loops. I also have another anker brick that charge loops as well.
No charging limit set and I have well over 200 hours on it. What kind of charging brick and cable are you using? c to c or a to c? If you’re using a 35 watt or lower brick and an a to c brick and cable you probably are not going to see the problem I'm seeing.
I have a DX340 that I love. Since this morning, I've been unable to start it: pressing the dial, even for a long time, doesn't do anything. However, when I connect the USB charger, the screen lights up and tells me that it's 70% charged. I'm afraid the dial is broken.
Flash it. Did it work fine before? Did you do OTA FW update recently or in past? It is showing a battery charge so the battery must be connected. If no battery it will not even get to Fastboot.
This is the issue as far as I'm aware once it negotiates for the highest voltage and current it can use it doesn't drop down to 5 volts from the 9. The current drops off. Normal android and snapdragon chips negotiate for the optimal quickest charge that the device can handle and start to drop down the current as the battery charges. The fact that yours is dropping to 5 is strange. The issues I am observing is that with the battery below 80 percent and you plug in most PD chargers the charging indicator will go green then go white then go green again and sometimes it will stay charging at that point. If I'm monitoring it on my meter it starts charging at 5v then it cuts the charging circuit and the meter cuts off then it comes back on at 5v again then back off then back on at 9 and will continue to charge normally. Depending on the brick or battery pack this could happen 2 or it could happen 5 times. On the anker prime packs and prime brick I have it never settles on a charging voltage and just keep looping. If your seeing the the battery indicator go from green to white and back to green after you plug in the charger that's not normal. I wish I could post a video i can make it do it at will depending on what charger I use. It doesnt do it with every charger and bank. I have a shark geek bank that works fine with it. My unit is fully charged and plugged into a usb a port with the screen off it only is pulling about .5 watt but the voltage does not step down after its fully charged.
This is the issue as far as I'm aware once it negotiates for the highest voltage and current it can use it doesn't drop down to 5 volts from the 9. The current drops off. Normal android and snapdragon chips negotiate for the optimal quickest charge that the device can handle and start to drop down the current as the battery charges. The fact that yours is dropping to 5 is strange. The issues I am observing is that with the battery below 80 percent and you plug in most PD chargers the charging indicator will go green then go white then go green again and sometimes it will stay charging at that point. If I'm monitoring it on my meter it starts charging at 5v then it cuts the charging circuit and the meter cuts off then it comes back on at 5v again then back off then back on at 9 and will continue to charge normally. Depending on the brick or battery pack this could happen 2 or it could happen 5 times. On the anker prime packs and prime brick I have it never settles on a charging voltage and just keep looping. If your seeing the the battery indicator go from green to white and back to green after you plug in the charger that's not normal. I wish I could post a video i can make it do it at will depending on what charger I use. It doesnt do it with every charger and bank. I have a shark geek bank that works fine with it. My unit is fully charged and plugged into a usb a port with the screen off it only is pulling about .5 watt but the voltage does not step down after its fully charged.
Sorry, it doesn't drop to 5V, I don't remember well because I checked it a long time ago. Charging starts at 5V and switches to 9V. Anyway, I had similar behavior to your unit and now I don't have a problem with it. I also didn't buy any new chargers.
Sorry, it doesn't drop to 5V, I don't remember well because I checked it a long time ago. Charging starts at 5V and switches to 9V. Anyway, I had similar behavior to your unit and now I don't have a problem with it. I also didn't buy any new chargers.
What version of firmware are you on? I know there were some issues with charging on the OG firmware. I updated to 1.02 for the amp 16 but it’s possible 1.01 had this fixed then 1.02 brought back the bug. Ive seen this happen before if development on the software for the amp 16 started before the fix from the old software was implemented it may still have the old code.
What version of firmware are you on? I know there were some issues with charging on the OG firmware. I updated to 1.02 for the amp 16 but it’s possible 1.01 had this fixed then 1.02 brought back the bug. Ive seen this happen before if development on the software for the amp 16 started before the fix from the old software was implemented it may still have the old code.
It seems like, when first released, some DX340 users felt like the low end frequencies were at least a little light compared to DX320. Is that still the case?... that the sub-lows and lows are maybe not as substantial in DX340 versus the DX320? Really getting interested in DX340 reading all the positive characteristics in the comments here. But if the 340 sub-bass, bass, upper-bass, low-mids really is lighter or less than the DX320, that could be a deal-breaker for me.
It seems like, when first released, some DX340 users felt like the low end frequencies were at least a little light compared to DX320. Is that still the case?... that the sub-lows and lows are maybe not as substantial in DX340 versus the DX320? Really getting interested in DX340 reading all the positive characteristics in the comments here. But if the 340 sub-bass, bass, upper-bass, low-mids really is lighter or less than the DX320, that could be a deal-breaker for me.
I feel like this is a true statement with the stock amp 15. With the amp 16 in ab mode I feel like it’s more like the 320 sound signature. Saying that sound is strictly subjective. Also the headphone or iems your using make a difference as well.
It seems like, when first released, some DX340 users felt like the low end frequencies were at least a little light compared to DX320. Is that still the case?... that the sub-lows and lows are maybe not as substantial in DX340 versus the DX320? Really getting interested in DX340 reading all the positive characteristics in the comments here. But if the 340 sub-bass, bass, upper-bass, low-mids really is lighter or less than the DX320, that could be a deal-breaker for me.
Personally (AMP15), I can only speak highly of the DX340, because it takes me to places I have never been, because it is perfectly tuned to my expectations.
Powerful technicalities do not kill the tone, do not destroy the mood, do not tire. This sound is dynamics, space and clarity without sibilants, with nicely drawn vocals, nuances simply rendered in an incredibly revealing way, with pace.
After three months, I consider this signature unique, distinct and still surprising, one that will last for years, and when I add to this the next amplifier modules and the stationary mode, I know that I will not be bored.
I have recently listened to many players, more expensive and cheaper.
I think that anything below this price is a shortcut, above it is an unjustified expense.
It seems like, when first released, some DX340 users felt like the low end frequencies were at least a little light compared to DX320. Is that still the case?... that the sub-lows and lows are maybe not as substantial in DX340 versus the DX320? Really getting interested in DX340 reading all the positive characteristics in the comments here. But if the 340 sub-bass, bass, upper-bass, low-mids really is lighter or less than the DX320, that could be a deal-breaker for me.
I find with stock amp15 what you say to be true until you plug in 12VDCIN and run in Super Gain as low end is a bit lacking in just HG. In this mode the DX340 blows the 320 away. You can use either Stouthart or my tweaks and both improve SQ, depends if you want to root or not. You can also trade a stock amp15 with @Whitigir and get a mod one which if I remember improves low end without using SG. @DAPpower can tell you more details on mod AMP15. The construction and quality of DX340 is much better than DX320. It is built to last. Polished the SS looks so good. It does weigh more though. We don't know what AMP17/18 will bring yet.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.