Yes, same coil head.Same coil head?
It's the one that came with the TFV4. It vapes fine in Watt mode.Is your tricoil nickle, or the one that came with your TFV4?
Does the four coil that comes with the TFV4 a TC coil?There is the problem. The tricoil that comes with the TFV4 is not a TC coil. The TF-T3.is a Kanthal coil, and incapable of Temp Control. The new firmware must be acting differently than before, but rest assured that you never had temp control operating on that coil. The only mod that does TC (of a fashion) is the Asolo.
Thank you. This forum is great! Does Smok make a TC coil for the TVF4?BTW, welcome to VU, and no, it does not do TC.
TF-Q4 (quadruple coil)
•Patented Quadruple Coil Head
•High Quality Kanthal
•More E-liquid Delivery Efficiency
•Work with 100% VG
•0.15Ω (40w-140w)
Which isn't temp control, it's dry hit prevention.There is the problem. The tricoil that comes with the TFV4 is not a TC coil. The TF-T3.is a Kanthal coil, and incapable of Temp Control. The new firmware must be acting differently than before, but rest assured that you never had temp control operating on that coil. The only mod that does TC (of a fashion) on Kanthol is the Asolo.
Which isn't temp control, it's dry hit prevention.
The change in resistance in kanthal is MUCH less than any TC wire, by far. Also that change is not linear to temperature. The only true TC for kanthal is innokin with its proprietary rda with the sensor, but that is measuring ambient temperature in the rda not wire temp.There are a couple of temp control heads for that tank but I don't think the Triple is one of them.
TC uses wires which rise in resistance when heated... much faster than Kanthal.
That's how TC do what it do.
I suspect when the mod does not see that res rise, it's programming knows it's not a TC head and kicks out of TC Mode.
Some mods do this all the time, some allow Kanthal in TC (though there's no temp control actually happening). I haven't looked for a pattern, but that may be why the xCube is kicking the triple.
Lmfao, nooooo! Let's forget the assholio was mentioned. We don't need that thread to spread!"Taste Control" man... it's "Taste Control". LOL
Haha, yes where it belongs!Beating the glowing red eyed monster of a previous thread back into its proper place in the closet with an aluminum ball bat.....
3. One to hold it, two to turn. Lolhow many asolos doe sit take to screw in a light bulb?
HahaDrops bat and runs.....
Trick question ... none, because it isn't temperature controlled ... erm ... I mean taste controlled ... erm ... I mean both!how many asolos doe sit take to screw in a light bulb?
I'm guessing someone who thought he was an expert got in an argument about TC and thought it meant taste control. But that's my best guess. LolTotally lost at this point lol
I have this issue, whenever I put in fresh batteries, I have to connect my device to my phone, and upgrade to TI and SS to be able to select them from my device again. Luckily I do not have to pay, it just says upgrade and I click them both, then they are on my device.That is very strange, I know some people had to buy it again after upgrading but if you can apply it I don't know why it's disappearing from the device. Hopefully onebadwolf can help
Jim, Do you have a copy of the HEX file for 1.08? As thats what mine come as, and seemed to work better on that firmware.I've got all 5 "hit" settings, love that feature.
Lock... check.
Any specifics on TC issues. I understand they fixed the dry burn issue a revision or two earlier (I've got 1.08).
I have this issue, whenever I put in fresh batteries, I have to connect my device to my phone, and upgrade to TI and SS to be able to select them from my device again. Luckily I do not have to pay, it just says upgrade and I click them both, then they are on my device.
Also slightly annoying as I like my lights set to change colour during use and my screen rotated 180 so I can see it during inhaling, and I have to do that each time I change the bloomin batteries lol.
Think I might reflash the device to 1.091 and downgrade it.
I recommend using the firmware/installer from smoks website. It ran fine for me zero issues.If you downgrade below 91 you WILL lose TC on SS and TI. 92 runs stable for me. Try putting 92 on again, but when you do, erase the old firmware. When did your mod begin doing this?
As soon as I installed 1.092. I think I will stick at 1.091 for now, it seems to work the best for me, I tried a reflash of 1.092 with the same issues.If you downgrade below 91 you WILL lose TC on SS and TI. 92 runs stable for me. Try putting 92 on again, but when you do, erase the old firmware. When did your mod begin doing this?
I actually prefer the old installer though lol. It gives you more options to flash to whatever version you want, not just updates.Try going to 92 again, it sounds like maybe the flash is being installed over the old version, instead of erasing the old version, and cleanly installing the new one. Here is an exellent vid. Follow it exactly. Also, I've heard the new installer is fixed, and working properly now. perhaps try it again.
But I will try it in half hour
Well, the beta installer does now work. It is version 09B instead of 09A, so a later revision. edit; come to think of it, It might of been version 0.9b before, this is just a tweaked version of that. My memories not that good as you know.I'm using the same 92 firmware, and as a rule, I don't leap the the newest firm ware for anything until other poor sould have beta tested it. 92 though really is an improvement, and I'm using the same hex file as you are, and I have not had the problems you are describing. I've been looking ver the firmware, and it appears that the chip on the Smok has several different memory locations, if not perhaps physical memory locations.
Waiting to hear the result.
Can I ask you what you find better about 1.092? As 1.091 changes the coeficcient correctly on my device on 1.091, and hear that is the only benefit of 1.092? As i can't really tell a difference, apart from 1.092 being buggy as hell on my Xcube lolI'm using the same 92 firmware, and as a rule, I don't leap the the newest firm ware for anything until other poor sould have beta tested it. 92 though really is an improvement, and I'm using the same hex file as you are, and I have not had the problems you are describing. I've been looking ver the firmware, and it appears that the chip on the Smok has several different memory locations, if not perhaps physical memory locations.
Waiting to hear the result.
No it doesn't, everything is literally reset to the beginning. You can understand that is quite annoying, so would rather stick with the 1.091 for now.I find the TC on SS to be very much improved on 92. It was really choppy on 91. I am sure there must be a hardware hard reset for for the X Cube 2, I just havn't found it yet. It must be a combination of hard keys or the fire bar or both, likely at startup. That might cure your problem. There is obviously some memory retention, because as I recall, I didn'y have to set the clock again after the firmware upgrade. I may be wrong, I just don't remember for sure. I have only use the app to do the SS and Ti upgrade, as I don't own a device that will run the app. Check all the nooks and crannies of the app for a hard reset.
As far as future updates, who knows. Apparently Smok is far too grand these days to respond to anything. It has been about a month since I emailed support about an issue, and have not heard a single thing from them. What we need is a tame vaping uber geek from hell, to reverse engineer their firmware, and put out an opensource interface. I know there was a petition organized to try to get Smok to make the source public for the M80 since its TC was such a fail, but I've heard very little of that as of late.
Does you time remain set when you change the batts?
The 1.93 is out, with 180w upgrade and a couple of stability fixes.
those batteries were TrustFires
Haven't done any of it yet.
Bluetooth is backwards compatible. And the X Cube II only requires kit-kat 4.4 I believeIf its an Android tablet make sure it has Bluetooth 4, and is lollypop OS. If you want to use the old updater, and would like the hex file for .91, 92, or 93 let me know. As I wrote above, I also have the APK for older versions of Android.
FWIW, I put the X Cube up agains 2 other mods today, and I have no doubt its actually putting out 180 watts.
Bluetooth is backwards compatible. And the X Cube II only requires kit-kat 4.4 I believe
I meant with Bluetooth 3 and up also EDIT: 4.3+ is the required of (per smoks site)None of my bluetooth devices that are V2 or less even see the X Cube. The full implementation may be backwards compatible, but the Android implementation relys on the chipset Mfr. supplying a new stack, or upgraging to a higher version of of Android that has native BT4 support. My Samsung s-7560M On 4.04 will not see my mod BT,or run the new version of the app>My tablet on 4.04 will not load the new app, or see my mod on BT. The S-7560m will load the old versoin of the app, which I have as a APK, since Google Play only has the new app. Believe me, I have checked.