James

@DJT, what are your battery voltages and battery curve? When in removable mode, the percentage it shows is based on the lowest of the battery cells. (If they are imbalanced, it will not show 100% until they are balanced. That may be what you are encountering.)

Go to the Tools menu, Apply Service Pack.

Give the attached test firmware a try if you have the deep sleep wake-up issue. (Don't use it if you don't need it, of course.) We haven't heard anything bad about this firmware so far, but let us know if you run into anything. DNA 250 Color v1_1_SP35_US_SleepTest3.sw-service DNA 250 Color v1_1_SP35_INT_SleepTest3.sw-service

What are all of your battery cells' voltages? What does your battery curve in EScribe (Mod tab) look like?

Gotcha. Definitely let me know if you run into any issues (or in future versions) running in a non-writable global directory. It should work, but isn't something I'm actively testing on Linux. Thanks! On another note, it turns out I accidentally broke moving controls in Theme Designer on Linux SP15.1. Will be releasing a fix this week.

What is the advantage of this over the installer we provide? It will already offer new versions like the Windows and Mac versions.

The DNA 250C is step-down, so if your device takes two battery cells, the output voltage cannot be higher than the battery voltage. (Four cell devices have their battery voltage above 10V at all times while operating, and three cell devices generally do, so you don't run into this. The benefit of the step-down configuration is drastically better efficiency and cleaner signal.)

If it is still showing up on USB, the device is still running. Go to Tools->Update Firmware and choose 1.2 SP6 again manually. It should work.

I mean the power wiring of the battery input (as opposed to the balancer taps).

That is low. On 1.2 SP5.1 and SP6, it should read about 1.1V. The balancer taps appear to be reading, but are you sure the power wires are correct? That number would make sense if the power wires had 3V or so on them for some strange reason.

Try left clicking seven times on the Evolv logo in Help->About of EScribe and then run Device Monitor. What does your Bandgap measurement read?

Does the clicking happen in Power mode, or just Replay or temperature sensing?

Normal is the default if you don't set a color in the theme. Error is Status when there is an error such as Check Atomizer. If the designer of the theme does not override the colors for most fields this makes it easier for folks to customize their colors.

Highlight Read-Only is when you are hovering over a field and the Select button will not work. (If a field has a Status, for example, that can make it highlightable, even if it is not an editable field. Also, some fields are only editable sometimes, which makes them highlightable but not always selectable.) Highlight Selectable is when you are hovering over a field and the Select button will work. Selected is when you are adjusting a field.

EScribe Suite 2.0 SP15.1 For US-based customers (Windows): https://downloads.evolvapor.com/SetupEScribe2_SP15_1_US_ServicePack.exe For US-based customers (Mac): https://downloads.evolvapor.com/SetupEScribe2_SP15_1_US.pkg For international customers (Windows): https://downloads.evolvapor.com/SetupEScribe2_SP15_1_INT_ServicePack.exe For international customers (Mac): https://downloads.evolvapor.com/SetupEScribe2_SP15_1_INT.pkg For customers using Linux, see the beta thread. --- DNA 75 Color (firmware 1.1 SP33.2) --- Replay (International Edition only). To use Replay, keeping your settings: (1) Apply the Service Pack. (2) Choose a profile to put Replay on. Check "Use Replay on this profile", and name it how you like. (For most people, the easiest way to use Replay is to choose a profile whose material is Watts.) (3) Load on a theme with Replay support. (The default theme has Replay support. Go to the Theme tab and click Default Theme, and upload.) To use Replay, resetting the device: (1) Apply the Service Pack. (2) Go to File -> New, select DNA 75 Color, and choose "International Edition (Replay-enabled)". (3) Upload the settings. --- DNA 250 Color (firmware 1.1 SP33.2) --- Minor bug fixes and reorganization. --- Theme Designer --- Double-clicking now works when a control has multiple conditions. The default DNA Color theme now uses 0.5W increments instead of 0.1W increments. --- EScribe --- File -> New now asks questions to avoid some configuration when resetting a device's settings. (This should ease Replay setup on DNA 75 Color.) --- EScribe Suite --- Made tooltips show up on fields now instead of just their labels, and added some new tooltips. Permission errors on save/load are now more descriptive. Upgraded many icons to high-DPI variants. Minor bug fixes, cosmetic, and usability improvements.

Yes, though it appears it isn't in the default theme.. It's in EScribe, on the Display tab. (It operates differently from on monochrome devices -- the screen will turn off any time you fire.)

All power-controlled profiles can do Boost. We created Watt Boost to have one default profile preconfigured with non-zero Boost, nothing wild really.. For a power-controlled coil, the Punch setting controls Boost Punch. For a temperature-sensing coil, it instead controls Preheat Punch. Boost and Preheat are the approaches to getting the coil up to boiling temperature quickly. Punch is on a 0-11 scale. (For Preheat, you can use Temperature instead of Punch.)

One of the legs of a first-revision DNA 200's Fire button is always wired to battery voltage. Something (metal shaving? juice?) must have gotten in between that and the ground and shorted them together.

In the operating manual of a DNA device?

I've posted EScribe Suite 2.0 SP15.1. It contains primarily bug fixes and usability improvements over SP15. Also, the default settings (File -> New) are now separate for US and International Edition DNA 75 Color. Let me know if you run into bugs, etc. Have a good weekend James

That theme will work with firmwares 1.1 SP29 and up. Could you post your .ecig file? Whatever is causing that error may be in your EScribe settings, not your theme. That or it's a bug with the EScribe Suite version you are running. (I'm testing in 2.0 SP15.)

Funny thought I had. If you go into the Mod tab, Battery, what battery type is selected? Is it Lithium Polymer or Lithium Ion 18650? If LiPo, try selecting 18650.

Please make sure it's not just the battery curve being off for your batteries. If it keeps hitting fine below 15%, it's just the percentage being off for your batteries, nothing you need to ruin your device's performance for. See how far you can keep vaping it. It may be absolutely fine. If you limit your DNA to 10A continuous, on the other hand, you're capping it to 60W near low battery and 80W max. That's your business, but it'll only improve your battery life in the same way as 'vaping at lower watts'. Remember there is "Restore Defaults" to get back to a normal configuration....

How far can you keep vaping once you get to 15%? It could be that the battery curve is just off, which is cosmetic. The DNA should not be any more of a drain than any other device at the same power, and you should not have to do any voodoo to make it work right. Do check that the cells are well balanced in Device Monitor. The DNA's meter and Weak Battery function are based on the lowest of the device's cell voltages, so if they are imbalanced that could reduce battery life. The DNA will do its best to balance the cells while (and after completion of) charging. If you have been using them together in other mods that don't balance, they may have started balanced but have diverged. Worth a check anyway. Also, I Googled it a bit and found: https://www.e-cigarette-forum.com/threads/enook-40a-3200mah-18650-bench-test-results-only-10a-shame-on-you-enook.786067/ If those are the batteries in question, according to that review, they may not have as good life if pulsed to higher power (as you would get from a Boost, Preheat or Replay), because they are not actually high current cells. You can see in Device Monitor what the power is doing for your specific vape configuration. Screen brightness shouldn't have much effect on battery life, by the way. There's no need to suffer