James

5V should be fine. If it had put 9V or 12V onto USB (these do exist in the wild, even though they shouldn't), both the screen and FET driver would both be damaged by this. I can't speak for that particular charger, but contact Oxva for a repair/replacement.

The charger you used, what does it say on the label for voltage and current?

If you click the icon to the left of "Puff" to bring up the button simulator, and click Fire, does the screen turn on? That'd tell us if there's an issue with the physical buttons. Also, before you start Device Monitor (make sure it is closed), go to Help->About in EScribe and left click the logo seven times. This will close the window and put the program into Debug mode. Then, start Device Monitor. If you do this, click the "Debug" group on the left to bring it up. What does "Buttons" say? As to 4.16 Ohms, PWM devices like Oxva can't read over 4 Ohm. 4.16 Ohm is probably the 4 Ohms limit with calibration applied. This almost certainly means it's not reading the pod resistance, or the connection has become very bad, but clearly it's detecting that there _is_ a connection, or it wouldn't have tried to measure it at all.

Okay. What lock time are you using? I'd like to try to reproduce this. Also, would you mind saving your .ecig settings file and posting it here? That might help to reproduce the problem. Also, what do you mean by "tests but doesn't work"? Thanks! God bless. James

What lock-out time do you have set? Did you try that newest firmware I posted on November 24?

@Vapors Tongue: The time on the lock screen.... The DNA 60 Color doesn't have a real-time clock, so any clock would definitely have been an estimate from the CPU. I hadn't remembered supporting that, but maybe I did. How accurate did you find the clock to be? What Service Pack did it last work in? Thanks!

I've found the bug that causes conditions to be incorrect on that DNA 60 Color test firmware. I've attached a new test version. Give it a try, and see how it works for you! Thanks! God bless. James 1_1_SP137_INT.sw-service

Thanks @Frank65. I will investigate that on Monday. Despite not showing, is it still temperature-controlling properly for you? (If so, that'd mean it's a bug in the graphics code.) Are you able to see/set your temperature setting correctly in Device Monitor? Have a good weekend! God bless. James

Would you be willing to try an experimental firmware? It may have other bugs, but I'd be curious to know whether it fixes this problem for you. You should be able to apply the attached firmware by downloading it, going to Tools -> Apply Service Pack and clicking File. Then, browse to the file and select it. (It also fixes a startup glitch where it would fade the screen brightness in before the screen had been painted.) Thanks! God bless. James [attached file deleted -- see later in the thread for a newer version]

EScribe Suite 2.0 SP71.1 For US-based customers (Windows): https://downloads.evolvapor.com/SetupEScribe2_SP71_1_US_ServicePack.exe For US-based customers (Mac): https://downloads.evolvapor.com/SetupEScribe2_SP71_1_US.pkg For international customers (Windows): https://downloads.evolvapor.com/SetupEScribe2_SP71_1_INT_ServicePack.exe For international customers (Windows): https://downloads.evolvapor.com/SetupEScribe2_SP71_1_INT.pkg If you would like the Oxva-specific version, https://downloads.evolvapor.com/SetupEScribe2_SP71_1_OXVA.exe For customers using Linux, see the beta thread. --- Oxva Pro 2 DNA --- Added an option in the Safety tab to adjust Fill Pod detection. --- Theme Designer --- Added an "Import Animation Frames" menu option for Meter and Picture controls on devices which support animations. (This saves you the trouble of creating a WebP file.) Fixed a bug introduced in Service Pack 69 which caused some themes (specifically, those with conditioned Labels with padding) to refuse to upload. Fixed a bug which caused some themes (specifically, those using known() and unknown()) to crash on older devices. --- EScribe Suite --- Fixed a crash when downloading settings on DNA Go and Reflex. Fixed a Linux (GTK 3) stability-related bug. Miscellaneous bug fixes and improvements.

Normally, the program will recognize that it lacks the necessary permissions and ask for root access to install that rules file if it needs it.. Does pkexec not work for some reason in the setup you are describing? I've made some effort to not require any command line manipulation whatever. Also, I've updated the installer. It will look for libgtk-3-bin now, and use find instead of locate if it can't find that. (Hopefully.) Thanks! God bless. James

@Magigamix, I'm glad it's working for you! Turns out the bug wasn't Linux-specific, and was a rather serious bug! Thanks for reporting it! @Alessandro D.... Wow, investigating on Debian 13, the installer script is looking for the package libgtk-3-0, which they have renamed libgtk-3-0t64. Also, they've removed the locate program from the default install, which was my fallback in case the package lookup didn't work. I'm not nearly smart enough to understand the wisdom of Debian, but, I'll change the script to look for libgtk-3-bin. That at least does not appear to have changed. Thanks for reporting this. It will be fixed in the next version. For what it's worth it would have also offered to install mono-complete if you hadn't installed it as well. ECigStats still seems to be broken. I'll need to investigate that.

I've posted SP71. It includes a number of bug fixes, as well as Fill Pod adjustments for Oxva Pro 2 DNA. Enjoy God bless. James

I've posted up a version that fixes the bug with DNA Go and Reflex. If that's the problem you were having, it should be fixed now. Let me know God bless. James

@Siebel80... Yes, we have been looking at this. The other devices you mentioned don't have the Fill Pod feature, so it makes sense you wouldn't encounter it. @Cough... Hmm. If you have been using one single pod the whole time, 1000 puffs is on the early side, but if you are using a really high power, really thick juice, or really sugary juice, it's not out of the question. As they clog up, their ability to wick goes down. This is just the nature of pods. If it can't wick, it thinks it's dry. (If this is the entirety of the problem, without the Fill Pod feature, it'd probably be burning on you.) Does lowering your power setpoint make the problem go away? *** THAT SAID... *** While the Fill Pod settings we put on the device seemed to work for many liquids, they may not work for all liquids. And there is the open question: "Are the Fill Pod settings too sensitive, or are the pods just old?". When we looked at ECigStats data, it appeared that Fill Pod was working rather well -- we'd see Fill Pod showing up after about 200 puffs consistently, which is about right for 2 mL. But again, "for many liquids" doesn't mean "for all liquids", and not everyone uses the same power level, etc. *** If you want to try something... *** Here is an experimental EScribe. It's not one of the official versions at this point, at-your-own-risk, etc. But if you want to try it, it includes an experimental Service Pack 130.1. You can upload it to your Oxva Pro 2 DNA. With that Service Pack uploaded, you will be able to use a new setting in the Safety tab -- "Fill Pod Low" / "Fill Pod Off". I would be very curious to know if "Fill Pod Low" solves your problem. (This particular EScribe also unlocks the Fill Pod settings in Atomizer -> Mod, in case you want to experiment with thresholds further.) https://downloads.evolvapor.com/SetupEScribe2_2025-09-25_INT_ServicePack_FillPodTest.exe If you do try this, please let me know what results you get. Thanks! God bless. James