angealvape

Create a ticket directly to Evolv - I had to send my device to replace the ship on warranty.

I don't want to be rude but let's try to be professional here. I know about this option - been using DNA & Escribe since the very 1st that came out. This does not solve the issue as the issue is probably coming for the malfunction of the board itself. Evolv Support provided me also extremely useful information which was to connect to the escribe and set to "removable batteries" ... which is kind of an obvious thing you do once you receive a device which I did long time ago and also is not a solution.

yes, well... I a, waiting for quite sometime for a reply from them.... lots of tickets it seems.

no worries about your english - its perfect I am using ThinkVape 250C. And I followed your recommendation. 1. I applied Service Pack 2. I uploaded default.ecig for ThinkVape 3. I tried waiting with batteries nothing works

I did bro, did not work still got the clock error crap. I tried looking for clock settings in Escribe but seems nothing there

Also interested what might be a solution as I have same issue

Have the same issue... any fixes yet?

ok, I changed the coils to another company ones. Now I have a question - so the ohm goes .1 to .15. So those temp sensing coils. as per the replay it self, when you're looking for your vape - does the Save Puff option appear to you after each and every puff even when you chainvape or it has to be set when the coil is at its' lowest ohms.?

spaced fused SS316L - Dual coil . .13 cold ~.15 haven't checked that in normal TC though if I leave replay it does vape like normal.

Hi guys, I am using DNA 250C since yesterday and I got only one issue, while replay sometimes works perfect (I am using the 316L) sometimes it does not fire and on screen there is error message "check atomizer". When I let it sit for a couple of seconds it starts working again as if it needed to cool down. Is that a correct funcionality - I mean you cannot chainvape on it? Anyone had that issue and knows what might be causing it?