Smok X Cube II 160watt TC Bluetooth $55.9 coupon
- Thread starter vapee
- Start date
- th_trl_thread_readers 0
- Status
Adding my recent experiences in as well. As I said before, I have a clone velocity and 30 ga steel wire that is hard to capture with my janky clone set screws, so when I do get weirdness, it's hard to tell if it's the xcube, or my rda, although I do also have SS Triton coils and nickel OBS T-VCT coils to play with as well.
My upgrade process was:
Tried the beta tool, got a pass message, turned on the xcube, got an error message about a bad passkey? Then it reset to my prior version.
Saved the .hex update file it had downloaded, took batteries back out, plugged in usb, opened the old update tool while Windows installed some driver it thought was appropriate for the device.
Turned ON the xcube (keep in mind, batteries are out, only power is from usb,) went to settings, download, yes, then held the fire bar and didn't let go.
After lights were out on the device, told the update tool to connect, did the update from the .hex file.
After update, I disconnected from update tool, let go the fire bar, loaded batteries, turned the xcube on.
Turned Bluetooth on, loaded the app on my phone, connected, did upgrade to ti and ss mode.
Had to turn back off, then back on the xcube before those options showed on the device.
Then began the tinkering.
I have no ti, so I can not speak to ti usability.
With my Triton coils, I got an ok tc vape at 460 F at tcr 0.00090 in SS mode. Temp was still jumping around a bit more than I'd like, but it was working and temp controlling when I fired the coil dry.
Nickel coils worked fine at default settings.
I know for sure that the same tcr setting in SS versus TI modes was giving different results, they are NOT just applying a standard TCR adjustment. Smh.
The velocity took me several tries before I could simultaneously a) not lose contacts with the leads, I REALLY have to crank my set screws down b) not under wick, I basically have to let my coils deform as I stuff my wicking into super thin, spaced coils, then use the wicking to deform the coils back into place and c) not get horrible hot legs, this mostly consists of dry pulsing before wicking to check, a lot of praying that it doesn't occur after wicking, and cursing while ripping the build out if it does occur after wicking.
Once all that came out ok to a 0.59 build... my SS coils worked fine about 20 degrees F higher than the Triton coils wanted.
I HAVE found that if I don't tighten my atomizer on firmly enough, the xcube just never applies more than 0.3Volt, and no vapor. I have also found the xcube starts out at some preset wattage based on hard/soft/etc, and in about 1 second climbs to a temp protect, and THEN starts actually regulating the power based on readings... unless my atomizer isn't on tight enough and it gives me the no explanation low power bit again.
My upgrade process was:
Tried the beta tool, got a pass message, turned on the xcube, got an error message about a bad passkey? Then it reset to my prior version.
Saved the .hex update file it had downloaded, took batteries back out, plugged in usb, opened the old update tool while Windows installed some driver it thought was appropriate for the device.
Turned ON the xcube (keep in mind, batteries are out, only power is from usb,) went to settings, download, yes, then held the fire bar and didn't let go.
After lights were out on the device, told the update tool to connect, did the update from the .hex file.
After update, I disconnected from update tool, let go the fire bar, loaded batteries, turned the xcube on.
Turned Bluetooth on, loaded the app on my phone, connected, did upgrade to ti and ss mode.
Had to turn back off, then back on the xcube before those options showed on the device.
Then began the tinkering.
I have no ti, so I can not speak to ti usability.
With my Triton coils, I got an ok tc vape at 460 F at tcr 0.00090 in SS mode. Temp was still jumping around a bit more than I'd like, but it was working and temp controlling when I fired the coil dry.
Nickel coils worked fine at default settings.
I know for sure that the same tcr setting in SS versus TI modes was giving different results, they are NOT just applying a standard TCR adjustment. Smh.
The velocity took me several tries before I could simultaneously a) not lose contacts with the leads, I REALLY have to crank my set screws down b) not under wick, I basically have to let my coils deform as I stuff my wicking into super thin, spaced coils, then use the wicking to deform the coils back into place and c) not get horrible hot legs, this mostly consists of dry pulsing before wicking to check, a lot of praying that it doesn't occur after wicking, and cursing while ripping the build out if it does occur after wicking.
Once all that came out ok to a 0.59 build... my SS coils worked fine about 20 degrees F higher than the Triton coils wanted.
I HAVE found that if I don't tighten my atomizer on firmly enough, the xcube just never applies more than 0.3Volt, and no vapor. I have also found the xcube starts out at some preset wattage based on hard/soft/etc, and in about 1 second climbs to a temp protect, and THEN starts actually regulating the power based on readings... unless my atomizer isn't on tight enough and it gives me the no explanation low power bit again.
If you double the legs over, life with the Velocity gets much easier. To double the legs, just leave them long, then fold them so that the ends are about half a millimeter from the coil, or trim them so they are if you get the bend a bit wrong and the ends end up too close to the coil.
Doing this doesn't add any resistance (you're cutting the wire when you trim the other side so it doesn't increase functional leg length), but it makes trapping the legs SO much easier and SO much more secure.
And it makes them much less likely to be cut by the screws (particularly useful with Ni200).
I do that on all my Velocity coils, Kanthal, titanium, or Ni200, even with 26ga.
Doing this doesn't add any resistance (you're cutting the wire when you trim the other side so it doesn't increase functional leg length), but it makes trapping the legs SO much easier and SO much more secure.
And it makes them much less likely to be cut by the screws (particularly useful with Ni200).
I do that on all my Velocity coils, Kanthal, titanium, or Ni200, even with 26ga.
Bad passkey message is normal, I got it as well and Smok have posted to say that it is expected to be seen after the upgrade is finished .
The reset to prior version - or rather, simply not putting on the new version - is what happened to me as well.
This is what I did as well. Next time I'm going to try a couple of other ideas mentioned earlier in the thread, such as A) Going to Settings->Download On, and B) Just trying the new tool more times
OK glad it's working for someone! I have a Triton and one SS coil so I will give that a go as well.
Can you elaborate? The TCR ranges are:
- Ni200: 0.008 - 0.004
- Titanium: 0.005 - 0.0015
- SS: 0.0005 - 0.002
Yes this matches what I'm seeing - the pre-heat seems to be applied almost regardless. Huge peaks at the start of a vape and then down from there. I'll post some graphs soon.
Regarding the atomizer not being on tight enough - does this result in a change in the base resistance reading, higher than it should be?
That means that the tc isn't very good though, doesn't it? Preheat should not make the device overshoot the set temperature ever, particularly not so far that the coil fuses.
Sent from my C6903 using Tapatalk
Not necessarily, since by design its supposed to STOP the pre-heat at a resistance that equates to about 100F below your set temperature.
But Smok (or anyone else) can't account for all the vagaries in coil design, especially with the mass produced pre-builts. It's like blaming the light fixture maker when a GE bulb burns out. Usually it's not the fixture maker's fault.
There's not a single pre-built Ni200 head on the market I'd trust for reliability or longevity. They're still trying to stuff nickel builds in heads designed for NR-R-NR Kanthal. The legs are too long, the connections are weak press fits, etc.
Ordered my black xcube today with matching tfv4 kit be a good while before it gets here but one day I'll have happy vape mail .
.
Holy crap -- they came out with another version of this thing?! I think they should take care of their existing customer base before growing it even bigger. I guess the good news is they are throwing more eggs in their xcube basket. Will likely get continued support. The bad news is they now have two devices to support with the software and I predict plenty of new issues with which version is ending up updating what device.
While I can (thankfully) no longer participate in the horror show I'm reading about here, I'd like to see Smok get this thing right, if for nothing more than for the benefit of everyone who paid good money for it and expect it to do what's advertised.
SMOK is going hard for peoples $$$ this summer. New mods, tanks, 54 different coils for their tanks.
No problem because Smok's QC dept is doing the testing with different coil builds and heads. Same QC dept as the one that tests their software
I have to say, I'm actually quietly impressed with the 1.092 update after some other basic tests- I got a Uwell Crown after all the rave reviews and know that it uses a stainless steel coil. Before the update it was unusable in TC mode with this- giving out no vapour at even 600F, however now with 1.092, am getting a good, comfortable and above all, consistent vape, when I select SS, DC and use default TCR for SS. I ususally vape at around 420-450F and it feels like it's definitely in that range.
New tank and some new coil heads. Did notice that there are no stainless steel heads announced. Must be somthing to do with the fact that TC with SS on the Xcube DOSE'NT F-CKING WORK.
I'm curious about something. I'm having problems getting the upgrades for Ti and SS to install. My buddy was able to get me vaping on the Ti under the Ni settings, but I'd like to get this thing upgraded properly. What version of the firmware did you fellas, who already have the upgrades installed, purchase the upgrades for? I'm willing to go back to a previous version if that's what it takes, and I can find said version.
I first added Titanium on 1.07 then re-added it on 1.08 and again on 1.092 (has to be done again after every upgrade.) SS first on 1.092.
No problems paying for the upgrades (no technical problem anyway ), nor re-applying them - at least once I was able to login to the app, which didn't work for 12 hours or so after I upgraded to 1.092.
No problems paying for the upgrades (no technical problem anyway
), nor re-applying them - at least once I was able to login to the app, which didn't work for 12 hours or so after I upgraded to 1.092.
Hiya, I think it may be due to the app being used rather than the firmware? I recall there were issues initially with Android whereas iOS seemed to be fine. I'm using iOS and the only issue I run into is that it takes an inordinately long time to log in.
The 'Vapor Up-Gradation' (their words!) seemed to work fine on all firmwares apart from 1.90, which is why they hurriedly released 1.91 to address this.
Basically if you've already purchased the unlock for the newer wires, then when you update the firmware on the device, you'll need to go back and link to it in the companion app, and re-apply both the titanium and SS upgrades.
After doing this, they will be select-able on the device and in the iOS app.
Mine is working fine with these now on 1.092
I've got the older firmwares on my home PC- more than happy to email them to you if you need them...
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.
Last edited:
The Android app is working fine for me (albeit in a virtual machine on my PC, not on an actual phone or tablet as I don't have one that's compatible). But yes you have to re-apply the updates every time you upgrade FW.
I assumed that was what Lord Winter was having problems doing? Maybe I misunderstood. Anyway yeah, after every FW upgrade it's necessary to login to the app (either Android or iOS), then re-do the Vapour Upgradation thing. For me that's worked every time, including re-applying the Titanium update twice (first applied on 1.07, then re-applied on both 1.08 and 1.092). At least it works so long as I can login to the app, which did stop working for a while.
No misunderstanding, Bloke. You're correct, it's the Vapor Up-Gradation from the app. Still waking up here, I apologize. I'm on 1.092 and it wouldn't take the updates from the Android app. I'll have to try it again. I don't have a bluetooth dongle or I'd use an Android emulator, myself. As it stands now, I'm at the mercy of friends with Android compatible devices. The guy at my vape shop is happy to help, but we couldn't get the profiles to install. I still have the 1.091 firmware file, so if that one is a known quantity, I'll use it for now for trying to get the first install of the up-gradation. Thanks for the offer Joe, I'll get in touch with if I need the older versions. I think at most, I might have to backtrack to version 1.08, but I'm hoping it won't take all that.
Edit: That's actually something they need to add, an entry in the firmware for these upgrades that carries from upgrade to upgrade without the need to constantly re-enable.
Last edited:
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.
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.
- Status
Similar threads
