All Activity

Hi Yeah I have highquality cables since Im working at Ericsson develop datacenter. And yeah I have changed themes with escribe. I tested the update today again and....IT WORKS now! Now I only need to wait for my replacement screen. It died this weekend after have used my Rift since januari 2025.

2 more things and thanks for the clarification. Have you ever successfully connected to escribe in the past? In your Help Desk ticket you can post a link back to this post if you didn't post these images. First time I'm seeing these cascading errors.

Have you tried using a different cable?

Nr 3 should be first and it unpacks and after trying to update the "command failed, AbiQuery P0! shows up. And it finds the device but dont want to update it. Done an Help desk ticket. Kinda hoped anymore here have had this problem Tried old versions of escribe to since it seems to be no firmware at all left on my device. Google search came up nothing...

Are your images in the order that these errors occured? At any point did you click that link by the lightbulb 💡? Other than trying again, you might need to open a 'Help Desk' ticket. Link in my signature line.

Hi New here.. First my screen died and now It does now it does not work I try to update firmware thru Escribe and these comes up... See attached. It REFUSE to work...Is there a way to FORCE some firmware on it? Its a RIFT AIO

The "Protect Pod" and corresponding sensitivity is self explanatory. It means it is the adjustment for the conditions in which the device will deem the pod in danger and take necessary action to protect it. Realistically, you can think of it as sensitivity for the auto dry hit protection. High/low sensitivity. It is not the same as fill pod warning on The One.

I completely feel your frustration; dropping premium money on a high-end device only to have it turn into a paperweight after a few weeks is incredibly infuriating. You aren't crazy at all, but the blame here actually lies with the mod manufacturers rather than the DNA chip itself. In tight AIO devices like the Rift, the delicate screen ribbon cable is often aggressively bent or pinched against the internal housing, making it highly susceptible to glitching and dying if even a tiny bit of inevitable juice condensation seeps into the frame. Since you've only had the Rift for a month, definitely contact the maker or vendor immediately for a warranty repair—for that price tag, they absolutely owe you a fix, though nobody could blame you if you decide to wash your hands of these devices entirely!

I ran into a similar problem with my vape a while back, thinking my pod was faulty when it started giving me "fill pod" warnings even though it was still full. Turned out it was all about the wattage and airflow like others mentioned. Once I dropped the wattage and opened up the airflow a bit, the errors basically stopped, so now I always adjust those two when I change pods or flavors.

https://www.thingiverse.com/thing:4351429 Not my idea, but useful.

It does indeed sound better. One improvement, e.g. via a firmware update, would be to have the ability to power it off/on. So far I haven't found a way to do that. It's always on I guess until the battery is empty. Otherwise, definitely happy with it so far 👍🏼

In short, this scenario you explained should never occur in the first place on The One. It give no fill pod msgs unless the pod is legitimately in need of filling.

Honestly they aren't very comparable in the direct sense, as oxva has a design language, as does Evolv; That really becomes apparent when you go hands on with The One. It's the type of device that any "Lay" person could intuitively figure out with literally a few presses of the two buttons. There are pop up prompts or hints as to what it thinks you're trying to do, and will help. For instance, Replay activation is double pressing the lower button. If you press and hold or even just press it once, but not that second time, you'll see a little arrow pointing to the button and saying "×2" telling you that you need to hit it twice to activate then you get visual confirmation via a nice bright green sequence on the LED bar. Every other setting is acceptable by double pressing the fire or upper button opening the scrolling menu system. Also, since this was fully made by our guys, there's no broken wording or double meaning mess that came with the oxva. It's also vastly more intentful with it's warning and error screens.It won't just tell at you to "Fill Pod" and when it eventually does remind you that you should probably refill, in my case, it's always been correct. I have yet to catch a single unwarranted message since release. Nothing to worry about, anyone regardless of knowledge or know how, will be able to easily use this device even without documentation. Also, I'm sure documentation will accompany the US release of it. It's kind of the magic of this whole premise...the device does all the decision making based off your settings. It's very much a set and forget pod & absolutely nothing goes wrong because the device won't allow it to go wrong. It catches problems before the issue is even perceived by us so I recommend keeping the comparison to the other model to a minimum. Let it release domestically and see what happens.

If I remember correctly for material files, on the left window you'll see all available (from all your mods) and the right window is what's on an individual mod. *You can't delete a material file from a mod if it'a assigned to a profile* So they'll work the same on all mods. If you use multiple vendors or never changed yours, you might as well live with the evolv default. Otherwise it's under 'Mod' battery.

If I just load the TС profiles (Nife30, nife48, ss316L) instead of the standard ones, will they work the same way? Or do I need to load the "materials" separately as well? That’s so inconvenient... Also, how do I load a separate battery curve? Thanks for the answer!

That's right. You can save profiles from one and move to the other individually. Same for a battery curve and material profiles.

Hi all! I have a nice Cento theme for the DNA100C and want to install it on a DNA75C mod. I can only install the theme file (.theme), but not the settings file (.settings)—which contains the profiles, configurations, etc.—because I get a "DNA100C mod not connected" error. Is there a way to get around this? I’ve shown the issue in the photo.

These colour screens are very delicate and more care is required when installing them, right down to the routing when attached to the board. They are tested before being boxed but a ham handed installation will show up down the road. Also, not a warrantable item but you could open a ticket at Stealthvape and ask if they'd replace the screens for you.

The quality control on any DNA device is shockingly bad for what you pay, both the pixel stabwood AIO I had previously and now my current DNA60 Rift AIO I'm using have broken within a few months of use with no damage occurring to them, either stop detecting atomisers or the display starts glitching before becoming broken and unusable. The display on the Rift AIO I've only had for about a month has started going very pixelated randomly before flickering and totally blank now. This has happened with every device that has a DNA board I've bought no matter what, you'd expect with a premium price tag these devices would last but no; never buying these over priced garbage devices again.

Evolv/James has added a 'loop checker' in escribe SP77 that checks the theme installed on a mod when one does 'upload settings to mod'. This stops the upload, describes the error and causes the user to have to install a 'clean' theme before continuing. James' words 'That error is because I added a loop checker, which detects if a screen jumps to another screen that jumps back to the previous screen, all using "Go To Child Screen", which can run out the screen stack.' Because of this, and how the user interacts with the theme, it can cause 'menu error' or that other oddity 'press left' due to a stack overflow. Read the 'error' carefully and follow the instructions to fix it. You have 2 choices. Either test your own theme now by simply using SP76 and trying to install then upload to your mod or if a user gets the error, we will hide your theme until it is fixed and tested by you. Of course we will send you an email when we hide your theme.