Smok X Cube II 160watt TC Bluetooth $55.9 coupon

[TheLordWinter]

OK cool. Yeah, the whole app thing is a total disaster. The app itself is pretty crappy, poor quality, untested, but that shouldn't matter. It's just there, a minor bonus for anyone who wants to see their vape numbers on their phone and set the TCR with a slider instead of a mod menu (at least when that works.) A million miles from eScribe, but a little something extra that maybe someone thinks is cool.

That's how it should be. But instead they have made the use of the app - and not just that, the repeated use of the app - a requirement to enable what should now be considered basic features of the mod. And then they used Bluetooth 4 Low Energy for the mod, immediately ruling out a huge swathe of older devices that either don't have Bluetooth 4 chips, or don't have LE support in the software (eg any Android before 4.3). I'm sure they wanted to save battery - fine, implement BT 4 LE, but also provide a fallback profile that is backwards compatible with all other BT chips. Have it as an option in the menu perhaps, default LE, optional Compatible mode.

All that too much work? Totally fine. Just don't then make the app a requirement to get Titanium and SS TC.

The whole thing is fubarred from end to end, at every layer, in every possible way. Even in the smallest possible details, like the one you mention - losing the upgrades every time you apply new FW, so even if you borrow a compatible device you still can't get it working long term without constantly going back to borrow another. Maybe the chip doesn't allow data to be saved between re-flashes, but if so that's just yet another reason not to tie it to the app, or at least not exclusively so. Sell an Always-With-TC version of the mod for $5 more or something. Anything except this!

It's so irritating.

Re the bluetooth dongle, they're incredibly cheap. Here's one I quickly looked up which should be identical to mine, for £3.25 delivered: Mini USB 2.0 Bluetooth CSR V4.0 Dongle Dual Mode Adapter For Windows 7 8 A2DP PC | eBay

You shouldn't have to buy that and you shouldn't have to set up an Android-x86 VM in Virtual Box or VMWare. But if you do, I can at least confirm it will work.

The thing about firmware is that it should not be that difficult to write a couple lines of code into the updater that looks for two "on/off" switches in the firmware that indicate whether the Ti and SS upgrades have been purchased, and migrate those settings to the new firmware that it is installing. The entire process, for a computer, would add mere seconds, if any noticable time increase is observed at all.

So yeah, I'm with you 100%, this makes no sense. The whole situation suggests to me that using Flash-able ROM's in these things is something completely foreign to Smok, and they don't have anyone experienced in-house. These are mistakes that a rookie coder would make. Their saving grace is the constant stream of updates that says "We give a crap and are working to fix most issues" even if they haven't separated the Bluetooth app from the "requirements" column.

 

[JoeBattams]

Glad it's working. But see, this is just so wrong. You say before the update you got no vapour on an SS coil even at 600°F. That's the opposite of what should happen. An SS coil vaped on an Ni200 or Titanium mode should give plenty of vapour - the problem will be it won't limit temperature at all, not that it will limit it too much. It is basically a normal VW vape.

At least that's the case for every other mod, and according to basic principles of 'TC' and 'physics'. What the Smok is doing, I don't yet know. It appears to exist in a parallel universe..

I wonder if it's doing some kind of special check on the coil - checking its resistance rise, operating differently according to what it finds. Though even so, it should be impossible in Ni200 or Titanium mode to tell the difference between an SS coil and a Ni200/Titanium coil - all it knows is the resistance has only risen a little bit, but it can't know if that's because it's SS which won't rise much, or because it's an Ni200/Ti coil that has only been heated a little bit.

I don't know, maybe it has hardcoded rules? On initial resistance reading of coil, apply X watt of power, expect resistance to rise at least 0.YYΩ? But then that will vary according to whether the coil is wicked/juiced or not. And why even do that? It's not like it then auto-detects the TC mode.

Then there's the on-screen resistance rises that don't match reality, and which for SS (in all TC modes) indicated heating to 900°C or so when it had barely applied any power at all.

I'm determined to get to the bottom of this, as annoying as it is.

Yeah I agree, it's mystifying, when it took 600F to produce a little bit of Vapour that was 1.091, and the better result was 1.092.

I noticed something interesting when I did the firmware upgrade the first time- the microprocessor (Nuvoton nuc220le3an) in the Xcube 2 is identical to that in the XPro M80 plus (going by screenshots and video's of that devices upgrade process on youtube), so I can't see how a code-fiddling on their part can possibly make it in the same league as the YiHi devices for example, since they are using a SoC that Nuvoton's website suggests should be used in things such as 'security alarm', wheras, if i'm not mistaken YiHi actually manufactures their own PCB's and chips (though I really could be wrong), with the sole intended purpose of them being vaping. Whereas Smok are just re-using the same SoC that was used in the M80 Plus.

I'm a bit suspicious and am wondering if the SS mode is just 'emulating' TC like the M80 Plus did, though tests (e.g. by Dirk Oberhaus) have shown that it is actually regulating temp (though not very well!) with Ni 200...

The product page is:

Cortex,Microcontroller,MCU,M0,32-bit,NUC1,Mini5,NUC0,Nano1 - NUC120 USB Series

 

[TheLordWinter]

Yeah I agree, it's mystifying, when it took 600F to produce a little bit of Vapour that was 1.091, and the better result was 1.092.

I noticed something interesting when I did the firmware upgrade the first time- the microprocessor (Nuvoton nuc220le3an) in the Xcube 2 is identical to that in the XPro M80 plus (going by screenshots and video's of that devices upgrade process on youtube), so I can't see how a code-fiddling on their part can possibly make it in the same league as the YiHi devices for example, since they are using a SoC that Nuvoton's website suggests should be used in things such as 'security alarm', wheras, if i'm not mistaken YiHi actually manufactures their own PCB's and chips (though I really could be wrong), with the sole intended purpose of them being vaping. Whereas Smok are just re-using the same SoC that was used in the M80 Plus.

I'm a bit suspicious and am wondering if the SS mode is just 'emulating' TC like the M80 Plus did, though tests (e.g. by Dirk Oberhaus) have shown that it is actually regulating temp (though not very well!) with Ni 200...

The product page is:

Cortex,Microcontroller,MCU,M0,32-bit,NUC1,Mini5,NUC0,Nano1 - NUC120 USB Series

Well, while I can see your point on the microprocessor, you should not forget that these devices are not as complex as the calculations involved may make them seem. It's entirely likely that the processor needed only a new set of firmware to become a completely new machine. Not an uncommon occurrence in electronics these days thanks to modern computer technology.

 

[Mad Scientist]

Yeah I agree, it's mystifying, when it took 600F to produce a little bit of Vapour that was 1.091, and the better result was 1.092.

I noticed something interesting when I did the firmware upgrade the first time- the microprocessor (Nuvoton nuc220le3an) in the Xcube 2 is identical to that in the XPro M80 plus (going by screenshots and video's of that devices upgrade process on youtube), so I can't see how a code-fiddling on their part can possibly make it in the same league as the YiHi devices for example, since they are using a SoC that Nuvoton's website suggests should be used in things such as 'security alarm', wheras, if i'm not mistaken YiHi actually manufactures their own PCB's and chips (though I really could be wrong), with the sole intended purpose of them being vaping. Whereas Smok are just re-using the same SoC that was used in the M80 Plus.

I'm a bit suspicious and am wondering if the SS mode is just 'emulating' TC like the M80 Plus did, though tests (e.g. by Dirk Oberhaus) have shown that it is actually regulating temp (though not very well!) with Ni 200...

The product page is:

Cortex,Microcontroller,MCU,M0,32-bit,NUC1,Mini5,NUC0,Nano1 - NUC120 USB Series

The processor runs at 50 MHz, has 128kb of flash and 16 kb RAM. Simple tiny monochrome SPI display, no animation or graphics. They have way (way, way) more than enough of a microcontroller to run this mod. They need someone to actually design the thing, not a better processor lol. This is high school level trial and error coding masquerading as production code on a finished product. Hire some experienced software engineers and the issues would evaporate. The product is not that complex. PID controller 101.

 

[JoeBattams]

Well, while I can see your point on the microprocessor, you should not forget that these devices are not as complex as the calculations involved may make them seem. It's entirely likely that the processor needed only a new set of firmware to become a completely new machine. Not an uncommon occurrence in electronics these days thanks to modern computer technology.

True!! It would be really interesting if someone with a bit of SoC programming could have a go at writing their own version of the firmware - Though unfortunately the Xcube 2 is not popular/ interesting enough I guess to warrant such people's attention...

 

[TheBloke]

True!! It would be really interesting if someone with a bit of SoC programming could have a go at writing their own version of the firmware - Though unfortunately the Xcube 2 is not popular/ interesting enough I guess to warrant such people's attention...

That crossed my mind - we have access to a tool that can flash anything we like to the mod. We could reverse engineer the FW. But it'd all be in assembler and personally I'm not really sure it's worth the bother trawling through mountains of assembler to improve a basic mod I suppose we might be able to convert automatically to C, but same applies: lots of work, for what?

If the mod was better to start with it might be more interesting - unlocking a full TCR scale, adding new presets for different wires, that sort of thing. But on mod that's so broken to start with, it could be a pretty thankless task - having to first fix their stuff before thinking of adding new things.

And as you say, unlikely to be enough interest to build up a community around it.

Open source/hackable mods definitely are very interesting, and if/when we get a decent base platform it'll be awesome. Hopefully Cloudmaker and their Ares OS might provide that.

 

[TheBloke]

The thing about firmware is that it should not be that difficult to write a couple lines of code into the updater that looks for two "on/off" switches in the firmware that indicate whether the Ti and SS upgrades have been purchased, and migrate those settings to the new firmware that it is installing. The entire process, for a computer, would add mere seconds, if any noticable time increase is observed at all.

So yeah, I'm with you 100%, this makes no sense. The whole situation suggests to me that using Flash-able ROM's in these things is something completely foreign to Smok, and they don't have anyone experienced in-house. These are mistakes that a rookie coder would make. Their saving grace is the constant stream of updates that says "We give a crap and are working to fix most issues" even if they haven't separated the Bluetooth app from the "requirements" column.

Yeah. Or perhaps even better, have the upgrade tool log into the Smok account and a) let you pay for the upgrades from any PC, b) check what upgrades you already have and apply that to the FW. So there is no requirement on the app at all.

As you say, it all comes down to Smok approaching this thing with absolutely no planning and foresight, almost no testing, and making the most basic of errors. It's unfortunate. I think maybe they just have a completely different mindset. It's about volume, and if it works for enough people to make a profit, that's all the need. That still doesn't excuse putting out stuff that blatantly doesn't work - in which case they may as well not put it out until it does - but there we go.

 

[JoeBattams]

That crossed my mind - we have access to a tool that can flash anything we like to the mod. We could reverse engineer the FW. But it'd all be in assembler and personally I'm not really sure it's worth the bother trawling through mountains of assembler to improve a basic mod I suppose we might be able to convert automatically to C, but same applies: lots of work, for what?

If the mod was better to start with it might be more interesting - unlocking a full TCR scale, adding new presets for different wires, that sort of thing. But on mod that's so broken to start with, it could be a pretty thankless task - having to first fix their stuff before thinking of adding new things.

And as you say, unlikely to be enough interest to build up a community around it.

Open source/hackable mods definitely are very interesting, and if/when we get a decent base platform it'll be awesome. Hopefully Cloudmaker and their Ares OS might provide that.

Yep, am really looking forward to it, and reading their updates with anticipation- pre-ordered the DNA200 Whiteout about a month ago- was my vaping budget for quite a few months all in one go!!! Figured though that it's better to spend a chunk on a decent device than a handful of cheap Chinese mods that disappoint... (Actually it was Evolv's interactive eScribe Website that swayed me- it's really really well done) Am spending so much more money recently on vaping gear, I could have probably bought a small tobacco plantation! :/

 

[TheLordWinter]

Hey Bloke, what programs are you using for the Android app on PC, and how did you get the app downloaded to your PC?

I'm getting a bluetooth dongle today so that I can start hammering at my issues myself instead of depending on loaners for app access.

Edit: NVM, just re-read where you mentioned the shell application. Got the names. TY! Still wondering how you got the app downloaded, though.

 

[Croak]

Smok is using the app as a gateway to advanced features as a form of "copy protection", because their initial plan was to be able to charge to even enable Ni200 TC on base units, and of course the charge for every additional wire type they decide to support. To make that work, they needed to lock it down against hackers/pirates (China knows all about that!), and the best way is to do all the validation off the device and outside the app.

With that in mind, you can see why they make you go through the pain to to enable features after a firmware flash, and why the app behaves the way it does when it can't connect to Smok to verify you're a legit user, and/or verify what features you've paid for.

That said, if they abandon the whole in-app purchase scheme and just offer up updates, they could easily add the various TCR settings as default firmware options, no app necessary. But somebody there wants to keep flogging the app purchase scheme.

 

[TheLordWinter]

Yeah. Or perhaps even better, have the upgrade tool log into the Smok account and a) let you pay for the upgrades from any PC, b) check what upgrades you already have and apply that to the FW. So there is no requirement on the app at all.

As you say, it all comes down to Smok approaching this thing with absolutely no planning and foresight, almost no testing, and making the most basic of errors. It's unfortunate. I think maybe they just have a completely different mindset. It's about volume, and if it works for enough people to make a profit, that's all the need. That still doesn't excuse putting out stuff that blatantly doesn't work - in which case they may as well not put it out until it does - but there we go.

The enormity of planning and foresight just sank in and... yeah, it's VERY obvious that the program wasn't flowcharted before coding.

 

[JoeBattams]

Hey Bloke, what programs are you using for the Android app on PC, and how did you get the app downloaded to your PC?

I'm getting a bluetooth dongle today so that I can start hammering at my issues myself instead of depending on loaners for app access.

Edit: NVM, just re-read where you mentioned the shell application. Got the names. TY! Still wondering how you got the app downloaded, though.

You should be able to find the .apk file to download at one of the 'alternate' app repositories, if you google smok bec apk you should be able to find it! Can't quite recall if you can rip from the Play store with a Chrome extension, it's been a while, but am sure TheBloke will be able to help!

 

[TheBloke]

Hey Bloke, what programs are you using for the Android app on PC, and how did you get the app downloaded to your PC?

I'm getting a bluetooth dongle today so that I can start hammering at my issues myself instead of depending on loaners for app access.

Edit: NVM, just re-read where you mentioned the shell application. Got the names. TY! Still wondering how you got the app downloaded, though.

I am using Android X86 - so I have a full installation of Android, GUI and everything. So I just download Smart Bec from the Google Play store on the Android install, exactly like one would with a phone or tablet.

To get Androidx86 running on a PC, which can be done under any of Windows, Mac or Linux, you need virtualisation software. I tried VMWare Workstation first, but had problems getting the GUI to come up, so I switched to VirtualBox. Later I believe I found and fixed the issue in VMWare, but VirtualBox is free so you'd almost certainly want to use that anyway.

You download an ISO file for Android x86 and install it into a new VM in VirtualBox - VM type is Linux, SATA hard drive, a couple of gig of ram, and the networking in Bridged mode. You then also assign your USB BT dongle to the VM.

When you're ready I can just send you a VirtualBox definition file to make all that a lot easier.

Then you go through the Android x86 installation process which takes a few minutes. There's one particular step you need to know about regarding configuring the hard drive, which I can let you know when you're ready to do it.

Once you've done all that, you've got a perfectly normal Android 4.4 install. You install Smart BEC through Google Play store like on a normal phone/tablet, and any other apps you want - should there be any Android apps you desperately want to try

in VirtualBox you can hit Control-I to give you a simulated mouse pointer, as Android doesn't provide one as it expects you to be using fingers. When you click into the VBox window it will "lock" your mouse/keyboard, so inputs are only sent to the OS running in VBox. To unlock it and get control back to use other programs on your PC, press the right-hand Control key on your keyboard.

There's one further problem: Android phones/tablets can display in either portrait or landscape, and normally they auto rotate as you move the device. The Androidx86 install on a PC will always be landscape. But the Smart Bec app automatically rotates the screen into portrait every time - regardless of whether Screen Rotation is enabled or disabled in the Android OS.

Most android apps are designed to run in either mode, but Smok's forces you to always be in portrait, even though it looks just fine in Landscape. More great design - who cares if the user might have a 12" tablet and holding it portrait is daft? Anyway, the result is that the app will be 90° rotated which is somewhat hard (read, near impossible) to use VirtualBox doesn't have an option to rotate the virtual display.

Fortunately, rather than physically rotating your monitor, or craning your neck, there's a quick solution: there are a number of free "screen rotation lock" apps on the Google Play store. I installed one of those and told it to lock the screen in landscape, and to auto start when Android starts. That prevents Smart Bec from rotating the screen. You can see the name of the app I used in the screenshot below, and I can send you a Google Play link later if needed.

I tried several versions of Androidx86, because unfortunately the latest one, 4.4 release 3, did not seem to work properly with BT 4 LE - it couldn't find the Smok, either in their app or in the general Bluetooth list. I tried r3 again later and I think I did get it working. But the one I carried on using is 4.4 r2, so that's the one I can easily recommend. It can be downloaded here: http://sourceforge.net/projects/android-x86/files/Release 4.4/android-x86-4.4-r2.iso/download

 

[JoeBattams]

I am using Android X86 - so I have a full installation of Android, GUI and everything. So I just download Smart Bec from the Google Play store on the Android install, exactly like one would with a phone or tablet.

To get Androidx86 running on a PC, which can be done under any of Windows, Mac or Linux, you need virtualisation software. I tried VMWare Workstation first, but had problems getting the GUI to come up, so I switched to VirtualBox. Later I believe I found and fixed the issue in VMWare, but VirtualBox is free so you'd almost certainly want to use that anyway.

You download an ISO file for Android x86 and install it into a new VM in VirtualBox - VM type is Linux, SATA hard drive, a couple of gig of ram, and the networking in Bridged mode. You then also assign your USB BT dongle to the VM.

When you're ready I can just send you a VirtualBox definition file to make all that a lot easier.

Then you go through the Android x86 installation process which takes a few minutes. There's one particular step you need to know about regarding configuring the hard drive, which I can let you know when you're ready to do it.

Once you've done all that, you've got a perfectly normal Android 4.4 install. You install Smart BEC through Google Play store like on a normal phone/tablet, and any other apps you want - should there be any Android apps you desperately want to try

in VirtualBox you can hit Control-I to give you a simulated mouse pointer, as Android doesn't provide one as it expects you to be using fingers. When you click into the VBox window it will "lock" your mouse/keyboard, so inputs are only sent to the OS running in VBox. To unlock it and get control back to use other programs on your PC, press the right-hand Control key on your keyboard.

There's one further problem: Android phones/tablets can display in either portrait or landscape, and normally they auto rotate as you move the device. The Androidx86 install on a PC will always be landscape. But the Smart Bec app automatically rotates the screen into portrait every time - regardless of whether Screen Rotation is enabled or disabled in the Android OS.

Most android apps are designed to run in either mode, but Smok's forces you to always be in portrait, even though it looks just fine in Landscape. More great design - who cares if the user might have a 12" tablet and holding it portrait is daft? Anyway, the result is that the app will be 90° rotated which is somewhat hard (read, near impossible) to use VirtualBox doesn't have an option to rotate the virtual display.

Fortunately, rather than physically rotating your monitor, or craning your neck, there's a quick solution: there are a number of free "screen rotation lock" apps on the Google Play store. I installed one of those and told it to lock the screen in landscape, and to auto start when Android starts. That prevents Smart Bec from rotating the screen. You can see the name of the app I used in the screenshot below, and I can send you a Google Play link later if needed.

I tried several versions of Androidx86, because unfortunately the latest one, 4.4 release 3, did not seem to work properly with BT 4 LE - it couldn't find the Smok, either in their app or in the general Bluetooth list. I tried r3 again later and I think I did get it working. But the one I carried on using is 4.4 r2, so that's the one I can easily recommend. It can be downloaded here: http://sourceforge.net/projects/android-x86/files/Release 4.4/android-x86-4.4-r2.iso/download

Crikey, that's an incredible amount of useful information- thank you for writing all that!! Let alone on a vaping forum with nothing to do with virtualisation!

I've used VMware for years when not running Linux natively, but have never even thought of running an android VM- virtual box does seem to crop up a lot when researching it- I'll bookmark this for future reference- thanks again from me!

 

[TheBloke]

Pleasure! Yeah I hadn't thought about running Android in a VM either. When I first realised I couldn't run the app on my phone, I Googled for "android emulator with bluetooth" and apparently that can work, but with no GUI (so it would involve manually downloading the APK, as LordWinter feared he was going to have to do) and lots of messing about. Fortunately most of the answers to similar questions all pointed to the Android x86 distro, so I found that quickly and that was much nicer.

It works really well actually! And although it was rather more effort than one should have to go to in order to run an app, now that I've done it I do much prefer having the app usable on my PC, where I can leave it displayed on a separate monitor and access it with a mouse, rather than fiddling about with my phone

 

[TheLordWinter]

I am using Android X86 - so I have a full installation of Android, GUI and everything. So I just download Smart Bec from the Google Play store on the Android install, exactly like one would with a phone or tablet.

To get Androidx86 running on a PC, which can be done under any of Windows, Mac or Linux, you need virtualisation software. I tried VMWare Workstation first, but had problems getting the GUI to come up, so I switched to VirtualBox. Later I believe I found and fixed the issue in VMWare, but VirtualBox is free so you'd almost certainly want to use that anyway.

You download an ISO file for Android x86 and install it into a new VM in VirtualBox - VM type is Linux, SATA hard drive, a couple of gig of ram, and the networking in Bridged mode. You then also assign your USB BT dongle to the VM.

When you're ready I can just send you a VirtualBox definition file to make all that a lot easier.

Then you go through the Android x86 installation process which takes a few minutes. There's one particular step you need to know about regarding configuring the hard drive, which I can let you know when you're ready to do it.

Once you've done all that, you've got a perfectly normal Android 4.4 install. You install Smart BEC through Google Play store like on a normal phone/tablet, and any other apps you want - should there be any Android apps you desperately want to try

in VirtualBox you can hit Control-I to give you a simulated mouse pointer, as Android doesn't provide one as it expects you to be using fingers. When you click into the VBox window it will "lock" your mouse/keyboard, so inputs are only sent to the OS running in VBox. To unlock it and get control back to use other programs on your PC, press the right-hand Control key on your keyboard.

There's one further problem: Android phones/tablets can display in either portrait or landscape, and normally they auto rotate as you move the device. The Androidx86 install on a PC will always be landscape. But the Smart Bec app automatically rotates the screen into portrait every time - regardless of whether Screen Rotation is enabled or disabled in the Android OS.

Most android apps are designed to run in either mode, but Smok's forces you to always be in portrait, even though it looks just fine in Landscape. More great design - who cares if the user might have a 12" tablet and holding it portrait is daft? Anyway, the result is that the app will be 90° rotated which is somewhat hard (read, near impossible) to use VirtualBox doesn't have an option to rotate the virtual display.

Fortunately, rather than physically rotating your monitor, or craning your neck, there's a quick solution: there are a number of free "screen rotation lock" apps on the Google Play store. I installed one of those and told it to lock the screen in landscape, and to auto start when Android starts. That prevents Smart Bec from rotating the screen. You can see the name of the app I used in the screenshot below, and I can send you a Google Play link later if needed.

I tried several versions of Androidx86, because unfortunately the latest one, 4.4 release 3, did not seem to work properly with BT 4 LE - it couldn't find the Smok, either in their app or in the general Bluetooth list. I tried r3 again later and I think I did get it working. But the one I carried on using is 4.4 r2, so that's the one I can easily recommend. It can be downloaded here: http://sourceforge.net/projects/android-x86/files/Release 4.4/android-x86-4.4-r2.iso/download

Thanks from me as well. You just cut down the hunt time for those proggies. On a different note, I finally got my profiles installed and functioning, my XCube 2 is now working wonderfully. The android info is still going to come in handy because I'm not going to run out and spend a couple hundred on an android tablet I have absolutely no need for, just so I can re-install the profiles everytime I update the firmware... I'm a die-hard PC man. VM'ing it is gonna be the way to go for me, Bluetooth dongle and all.

How I got them functioning was through my friend at my B&M shop. I brought over the old firmware update software, and just like others have mentioned... we deleted the old firmware and installed 1.092 clean. After that, the Ti and SS profiles popped straight up and haven't given me problems. That said, I have no stainless wire to test at the moment, though that is expected to arrive Friday. Got 100ft of 316l stainless on order. I'll share more on that when I have the wire. As for Ti wire... loving it now. Absolutely loving it.

 

[TheBloke]

OK that's great it's working now. So what you did to fix it was: used the old FW upgrade tool to first wipe the chip completely, then re-install 1.092?

If so then clearly the new upgrade tool, when it works at all, is able to install a non-working copy at least with regard to the upgrades. They did mention in an earlier blog post, from when they were still providing the old/original FW tool, to first wipe before applying the new update. So maybe they didn't take their own advice and the new tool misses out the wipe step.

 

[TheLordWinter]

OK that's great it's working now. So what you did to fix it was: used the old FW upgrade tool to first wipe the chip completely, then re-install 1.092?

If so then clearly the new upgrade tool, when it works at all, is able to install a non-working copy at least with regard to the upgrades. They did mention in an earlier blog post, from when they were still providing the old/original FW tool, to first wipe before applying the new update. So maybe they didn't take their own advice and the new tool misses out the wipe step.

You are correct good sir. And that's my guess, too... The new tool isn't wiping at all, or isn't doing a complete wipe of the old firmware. After the proper erasure and reflash of the chip, the Vapor-Upgradation as they like to call it, took hold and I got my profiles for Ti and SS.

 

[Toolbox875]

Hi all,
Just received vape mail in the form of a smok x cube2. I have an issue with the firing bar sticking. Is there a fix? Or is it a defect ?

 

[TheLordWinter]

Hi all,
Just received vape mail in the form of a smok x cube2. I have an issue with the firing bar sticking. Is there a fix? Or is it a defect ?

Sticking? Huh... gotta say, that's new. Might want to shoot them an email and look into it. I don't think that particular issue has cropped up yet that I have noticed.