James

I've posted it. I updated the version number to SP77 as well, because yesterday's SP76 was missing a few files. Definitely let me know how it works for you! Thanks! God bless. James

I've posted SP76, which adds support for DNA One devices.

I've posted SP77. It includes support for DNA One devices, as well as bug fixes. (As an aside, these devices have a much more powerful Theme Designer, if you're interested in customizing your device in that way.) Enjoy God bless. James

EScribe Suite 2.0 SP77 For US-based customers (Windows): https://downloads.evolvapor.com/SetupEScribe2_SP77_US_ServicePack.exe For US-based customers (Mac): https://downloads.evolvapor.com/SetupEScribe2_SP77_US.pkg For international customers (Windows): https://downloads.evolvapor.com/SetupEScribe2_SP77_INT_ServicePack.exe For international customers (Mac): https://downloads.evolvapor.com/SetupEScribe2_SP77_INT.pkg For customers using Linux, see the beta thread. --- DNA One --- Added support for DNA One pod device. --- Theme Designer --- Added support for DNA Pod devices of various screen sizes. --- EScribe Suite --- Miscellaneous bug fixes and improvements.

In Theme Designer, go to Appearance -> Fonts and select a font that has the characters you want to use. The default theme uses the Built font, which has a limited character set, but you absolutely can choose a different font. (You can also add a secondary font if you want, if you want to use a font with limited character set, but have another font be used if the character is missing from the primary font.)

Are you using the Oxva Edition or standard EScribe? As I recall, Evolv's version of EScribe (which can still talk to the Oxva) gives access to many more of the options.

Great! Out of curiosity, why did your system not already have pkexec? I had thought it was standard on nearly all Linux distributions. Is it a new install?

Normally, Linux EScribe will ask "Would you like to grant permission?". It won't do this if certain things are missing, but they shouldn't be missing... Do you have /usr/bin/pkexec? Is your user in the "plugdev" group? (Does the group exist on your PC?) Does /etc/udev/rules.d exist? If so, is 60-dimension_engineering.rules present? If so, it's a text file. What does it look like? Essentially, EScribe uses /usr/bin/pkexec to prompt for a root password, and then adds your user to plugdev and writes the .rules file into /etc/udev/rules.d. It does this because on Linux, by default, a USB HID device can only be written to by the root user. If /usr/bin/pkexec isn't present on your system, I'd be curious as to why. If there's a solid reason I can write fallback code. Thanks! God bless. 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