Building a real Thermal Imaging addon for Android Smartphones - General Accessories

Hi everyone,
Thermal imaging has been a long-time dream for me, and I guess for many other as well. However, even the most simple TI cameras tend to be too expensive to justify if you want then just for private use.
It seems like their might be a way out of that now...
A Company called Melexis has released a cheap and low-resolution Thermopile Array (Melexis MLX 90620), that could be the ideal base for an extremely basic Thermal Camera. It's 16x4 Pixel Sensor won't win any prizes for building inspection or detailed thermal analysis, but it is cheap (if you buy a single unit it's around 60$ from Digikey or Futureelectronics, should be in stock this week at Futureelectronics according to Melexis) and comes complete with built-in signal amp, RAM, EEPROM and digital I2C output.
I came across this idea through the Kickstarter Project "Sensordrone" that gives you an easy way to hook up Sensors to your Smartphone via Bluetooth. They are planning to build this TI Sensor as an addon Module to their Sensordrone, but they need somebody to help build the app that turns the raw data coming from the sensor into colourful pixels...
Connecting the Thermopile Array to the Sensordrone is as easy as connecting the 4 pins to the Addon Connector pins. Adding a simple Silicon Diode to reduce the power from 3.3v down to the recommended 2.6v is the only additional step.
You could also hook the Thermopile Array up to a standard Arduino or the Android ADK board I guess if you don't want to go for the Sensordrone.
So it all comes down to Software, and this is where I hope somebody in this fantastic community might help. If you would like to see this happen and (unlike me) have the required coding skills, just go ahead, contact the Sensorcon Team (developers of the Sensordrone) or build your own ADK kit with Thermal Imaging.
TecSpecs for the Melexis MLX90620 can be found on their website together with a demo video. The Sensordrone can be found on Kickstarter (just enter the name) and specs for their unit are available there or on the Sensorcon forums.
I hope somebody takes this up and makes my (and I hope many others') long time dream real! Once the cheap and low-res version works, going for the more high-resolution Heimann Thermopile arrays with 32x31 and 64x62 might be the next step to an affordable Smartphone Thermocam.

I had the same idea and ordered the sensor a few days ago.
Got a message from Future electronics that they get the sensor on the 23rd and than it will take 5 to 7 days for me to receive it.
So I will have to wait a little bit longer and than start programming.
I have some ideas to combine it with the phone camera to make it a real thermographic camera.
I don't know if i will use the Sensordrone or a standalone bluetooth solution. With the later I have more control over the firmware.

Thanks for replying Mardaso.
The idea of combining it with the smartphone cmos camera is great, I had thought about that as well, but am not sure how it could be achieved. You'd either have to synchronize the FOV, which is pretty much impossible given the parameters of the Melexis module or you'd have to track the area the sensor is "scanning" with the smartphone and overlay the image then. This might work with LEDs or laser dots, but it would be difficult.
But maybe I'm missing something here and it might not be that complicated after all.
My idea for increasing the effective resolution was in using motion sensors and "image stitching" to create a larger and more detailed image with the low-resolution sensor. This would work much like the "panoramic" feature in Android smartphones. It works perfectly for my Nexus. This might be rather challenging to program though...but maybe also worth a try.
I think this would maybe all be relevant for later on if/when the basic functionality is there...
I'm hoping you'll give the Sensordrone a try since I ordered one and would like to see Theraml Imaging on it ASAP...or if you go with a standalone Bluetooth module, would you provide your sourcecodes for the app so that it can be easily adapted for use with the Sensordrone?
The main advantage of the Sensordrone from a dev. point of view is that it takes care of the low-level stuff for you. You'd get the required raw data from the sensor easily and could concentrate on the features of the app...
Maybe you could contact Sensorcon, the creators of the Sensordrone, and see whether you'd like to work with them on this project. They are really nice guys. Are you going to do the initial work on an Arduino based ADK btw?
Whatever you do, I'm glad that you're picking this up. Your work will be useful in bringing a "world's first thermal imaging device" to the Smartphone. Since the Sensorcon folks are also in contact with Heimann Sensors for a later-to-come higher resolution version of the the TI module there is definitely a future for this and your software could be the basis for all that...:good:
I'd like to offer my assisitance, but since I am absolutle yno good at programming I'll probably not be able to do anything useful...

That would be really cool!!!
Can the Bluetooth handle that much data???
Sent from my LG-P999 using xda premium

Bluetooth should not be a problem. Even BT 2.1 has about 3Mbps capacity. With the low resolution of the Thermopile arrays that is a non-issue.
@Mardaso
which FOV option die you order? 40 degree or 60?

CommanderROR said:
Bluetooth should not be a problem. Even BT 2.1 has about 3Mbps capacity. With the low resolution of the Thermopile arrays that is a non-issue.
@Mardaso
which FOV option die you order? 40 degree or 60?
Click to expand...
Click to collapse
I ordered: MLX90620ESF-BAB-000-TU so the 60 degree version. They had only this one listed and the evaluation board.
I want to start programming asap. So when the sensors arrive I will start first with a controller (arduino or pic(32)) sending data serial to a PC.
After that go for bluetooth and an android app.
When looking at the data sheet there is a lot of calculation to be done before you get the actual temperature. These calculations could be handled by the Pic32 processor. But we could always use the sensordrone as a gateway for the serial data.
I want to use the motion sensors from the phone to "stitch" the data.
Maybe we will need some kind of holder to align the thermo sensor and the camera pictures so you won't need an extra laser or manual alignment. Just some thoughts.

Futureelectronics seems to have the 40 deg sensor listed now. I'm not sure, but I think that might be better for image stitching...not sure though.
Aligning the sensor with the phone for motion sensor useage...I'd probably go with a bit of double-sided sticky tape...
At least for initial trials that could work well. It would not overlay the "real" image with the Thermal image but would create a more high-res thermal image. That might be easier as a start.
About the calculations...I read that data sheet too, but I'm not sure what is done in the sensor itself and what you have to do in software. It's rather confusing in some passages...
As far as I can tell, calibration values are stored in the EEPROM and can be changed (but I would leave those well alone) and the 65 data packages are written to RAM from where they can be read. 64 temp readings for T(Object) and 1 for T(Case). I'll try to figure out what I can from the Spec sheet, but it's not exaclty my field of expertise...^^
If it gets really complicated you could always ask Melexis for advice. They are really helpful.
The Output from the Sensor should be handled as I2C, that would be easiest and would also be the way the Sensordrone receives data. I'm thinking about getting an Arduino ADK board and a breadboard so that I can at least help with testing, but I'll wait a bit...not sure whether it's worth the money if the Sensordrone comes in October and can do the same and more...
I just reread the spec-sheet, and it seems that the calculations really are not done internally but have to be performed each time you read data from the sensor.
I'd suggest doing those calculations in the app rather than in the microcontroller since that would make things fully compatible with the Sensordrone which as far as I know only passed the data through.
Btw...have you thought about refresh rates? The default is 1Hz (1fps) which is ok for tryouts, but probably not very satisfying for actual use. I' suggest something like 12Hz for general use, maybe more for "painting" a larger image with the "stitching" method. However, I do not know how much the accuracy suffers then...

OK...the Sensors and Evaluation Boards are now listed "in Stock", so you should receive yours soon.
I'm looking forward to following your progress.
If I understand correctly, you'd need to initiate a PTAT read and a Full Frame read to get the raw data from RAM. In addition, you'd have to read the Constants from EEPROM since you need them for calculation.
One constant is set to 25°C, I'm not sure whether the others have to be read each or if they can be stored somewhere in the app and read from there after the first initialization (since they are constants they should not change).
Values are sotred in two's format, so you have to convert them to "real" numbers before using them...my god this is complicated. I think I'll make lunch and leave the calculating bit to somebody who knows what they are doing...

CommanderROR said:
OK...the Sensors and Evaluation Boards are now listed "in Stock", so you should receive yours soon.
I'm looking forward to following your progress.
Click to expand...
Click to collapse
Yes! got an email that they have been shipped.

Great news!
Post when it arrives, will you? And don't hook it up to 5V...

MLX90620 progress
Its worse than that!
Firstly, the chip is designed to run at 2.6V, despite what is says on some (though not all) of the pages of the manual. So,
you will need to get 2.6V from somewhere - I used a LM317 variable voltage regulator. Then you will need level changers
between the 2.6 and your 3.3 or 5v of your microprocessor.
The first thing to do is to extract the contents of the eeprom that is built into the chip. Not difficult, because it is a
22AA02 Mircochip device.
I was disappointed to find that I couldn't get all the information from the EEPROM which is supposed to be there - notably
the temperature gradient coefficient (TGC) and all the "Ta dependence of IR pixels offset" and the "individual sensitivity
coefficients" which all came out as 0! As the other variables came out, I don't think this is a fault of my code.
I have no confidence in the values I did get out either.... The first thing you need to do is to get the temperature of the
chip itself (Ta), as the 64 pixel readings are relative to that. You read a value called PTAT from the Melexis and run it
through some maths. I did that and got crazy values, even when I put the configuration into a spreadsheet. So, I have put
my Melexis in a temperature controlled oven and taken a number of readings from room temperature up to 60 degrees C to
create my own formula.
The next job is to read the 64 channels and the 'compensation pixel' value. I failed to get these out in one I2C session,
but that might be my code. I get the data pixel by pixel at the moment.
If you had confidence in the configuration variables, you could then start to run this data through the 'maths' that is
well documented in the manual (section 7.4.2). There is no way that I can get that maths to run in my target MCU - when
was the last time you tried to calculate 2 to power of 42 in an 8-bit micro!
Not the easiest thing to program for!
CommanderROR said:
Futureelectronics seems to have the 40 deg sensor listed now. I'm not sure, but I think that might be better for image stitching...not sure though.
Aligning the sensor with the phone for motion sensor useage...I'd probably go with a bit of double-sided sticky tape...
At least for initial trials that could work well. It would not overlay the "real" image with the Thermal image but would create a more high-res thermal image. That might be easier as a start.
About the calculations...I read that data sheet too, but I'm not sure what is done in the sensor itself and what you have to do in software. It's rather confusing in some passages...
As far as I can tell, calibration values are stored in the EEPROM and can be changed (but I would leave those well alone) and the 65 data packages are written to RAM from where they can be read. 64 temp readings for T(Object) and 1 for T(Case). I'll try to figure out what I can from the Spec sheet, but it's not exaclty my field of expertise...^^
If it gets really complicated you could always ask Melexis for advice. They are really helpful.
The Output from the Sensor should be handled as I2C, that would be easiest and would also be the way the Sensordrone receives data. I'm thinking about getting an Arduino ADK board and a breadboard so that I can at least help with testing, but I'll wait a bit...not sure whether it's worth the money if the Sensordrone comes in October and can do the same and more...
I just reread the spec-sheet, and it seems that the calculations really are not done internally but have to be performed each time you read data from the sensor.
I'd suggest doing those calculations in the app rather than in the microcontroller since that would make things fully compatible with the Sensordrone which as far as I know only passed the data through.
Btw...have you thought about refresh rates? The default is 1Hz (1fps) which is ok for tryouts, but probably not very satisfying for actual use. I' suggest something like 12Hz for general use, maybe more for "painting" a larger image with the "stitching" method. However, I do not know how much the accuracy suffers then...
Click to expand...
Click to collapse

Thanks for your input!
getting the voltage down from 3.3v to 2.6 should be easy with at silicon diode, they have a drop of 0.7v built-in and cost less than 1$.
Getting it from 5v would require more work. According to the spec-sheet the sensor should work at voltages between 2.4 and 3.6v (if I remember correctly) but I'd definitely try to run it at it's optimal voltage of 2.6v
The math is indeed strange, there is one step I don't understand where they convert something and I can't figure out what it is they are converting too and from...but I'm not good at math anyway so I guess there'll be somebody out there who gets this...I'll keep looking at it though.
mardaso is the one who plans to write the app for this, if you'd be willing to join in then I'm sure this could go better and smoother. I won't be much help, but I'll try my best to assist...
edit:
This is what I could not work out:
from page 16 in the spec-sheet: 256.26 + 120 = 6776 decimal value
The example hex values convert to 26 and 120 without trouble...but I have no idea how the result of the addition yields 6776
edit2: I figured it out..sort of.
run the results, for examle 6776 trhough this converter http://www.statman.info/conversions/hexadecimal.html and you'll see something interesting about the values...
Doesn't really make sense to me, but it does work...

@cybersteveUK
Could you post the values you get from the sensor and eeprom? Then we can all go through the data together and try to find out how to translate it into useable temp readings.
Thanks.
Sent from my Galaxy Nexus using xda premium

Got the sensors! I hope that I will have some time to test them next week.

another sensordrone backer and mlx90620 owner
Hi there,
I just registered to this forum to let you know that I wish to participate in this effort too. I am also a sensordrone backer on kickstarter, and I just received my melexis mlx90620 sensor. To start with, I plan to use it with my pandaboard, which has more than enough power to handle the math. When I get the sensor working, I will try to register the sensor data with a camera to overlay the thermal data on the rgb image.
I don't own an android phone yet, but I'm planning to get a Galaxy S3 later. For using the sensor with the android phone, I guess I would start by connecting it with the sensordrone via some simple electronics and using sensordrone's bluetooth connection to send the data to the phone for processing. Later a standalone small bluetooth module that could be attached to the phone would be nice.. Registering the sensor data with the camera image would require that the module stays somewhat stationary in relation to the phone's camera.
I don't know yet when I have time to test the module, hopefully in the next couple of weeks. Meanwhile, should we set up a project and some version control in some place like github? It would be good to have some place to store the data we gather, documentation, and the code we write.

Welcome on board!
Feel free to start a project on google code or similar. So far cybersteve seems to have put the most work into this, but he has not replied in this thread apart from his initial post, so I don't know if he is willing to cooperate.

update: Did some first testing. Ram register values looking good but eeprom readings are NOK.
@cybersteveUK Did you get any further? My eeprom readings give all 249(dec) 2s complement => -7 except address 0 = 160 and address 87 = 49. Not something I expected. Tomorrow I will take the logic analyser to see if the I2C eeprom code is ok.

Good and bad news.
The good news is that the code is OK and the bad news is that the eeprom of one sensor is not.
Tried it with the second sensor and all readings are as expected.
At least I can start coding but I have to see if Melexis will exchange the other sensor.

Mardaso said:
Good and bad news.
The good news is that the code is OK and the bad news is that the eeprom of one sensor is not.
Tried it with the second sensor and all readings are as expected.
At least I can start coding but I have to see if Melexis will exchange the other sensor.
Click to expand...
Click to collapse
Getting it exchanged should not be a problem. Futureelectronics should take it back without a problem.
I wonder if cybersteveUK also got a damaged sensor since his readings seemed to be off as well and what that says about the quality if this first batch...

One you get this project working, Are you going to make a YOUTUBE video of it working???
Thanks in advanced.
Sent from my LG-P999 using xda premium

Related

Camera Upgrade

I believe that I have read somwhere in this forum that there is a update/upgrade for the camera on blue angel which helps get clearer pics. I have done a search but can not find it. My actual version is2.21 Build 17084.
http://wiki.xda-developers.com/index.php?pagename=ERK_Patches_13x
So anybody tested them?
Does it make any difference..........i mean, there is from the starting point not so much to expect from a vga camera :?
I currently have 2.21 17084
Thanks for your quick reply! I just don't understand what this means:
"Note this is a higher build than but lower version than"
Which one is the latest/better version. Which one should I get for my blue angel, Fix_camera18157.sa.cab or Camera patch 10080401? I have camera version 2.21 build17084?
Do I just install the cab from the blue angel?
Lio said:
"Note this is a higher build than but lower version than"
Click to expand...
Click to collapse
I suppose it should have said
"Note this is a higher Version than the one above, but a lower build"
And yes, .cab files are just copied to the PPC and executet for installation. Note that the .cab file will delete itself on installation
Thank you! It did help quiet a bit. The pictures are sharper now
Xda II
hey guys.....
is there something like this for xda II as well ?
regards
jeetz
Lio said:
Thank you! It did help quiet a bit. The pictures are sharper now
Click to expand...
Click to collapse
so which cab file you did you get?
I just tested them both.
Now this is a mini test on only a few pics. in bad light, and a minimal difference on the pictures, but i found the 2.11 (Build 18157) to be just a ini mini little bit better, but in no way the same quality as you se on screen.
Anybody got an explanation on why its much better on screen (just with the camera active) than the actual picture that comes out of it??
For me it seems quite unlogical that the lens can capture a much better quality to put on the screen, but ones you take the picture the quality is much whorse.
How does this makes sence?
so which cab file you did you get?
Click to expand...
Click to collapse
I got this cab file: Camera patch 10080401
Anybody got an explanation on why its much better on screen (just with the camera active) than the actual picture that comes out of it??
Click to expand...
Click to collapse
Maybe it's to do with the encoding?
Lio said:
Maybe it's to do with the encoding?
Click to expand...
Click to collapse
Yep, but why the h... not fiks it so it uses the lens full capasati.
Im beginning to get a bit frustrated over using so much money on a device thats not even finished.
I gotta say, that if SonyEricsson comes with a new P900 type of device thats more like the BA, i will consider turning back to Symbian.
Symbian has its own troubbles, but they are very productive when it comes to updates and getting things fixed, which definantly is not the case with HTC/Microsoft and probbably the 5000 companies they outsource to
Well I went form the P900 to the MDAIII, only since I got it free.
The P900 is a VERY nice phone, its small gives you addresses in and not just phone numbers, has a lot of good apps and when I go out I still use it due to the size.
The MDAIII, well its a PPC, and thanks to this forum you can infact fix a few of the issues like the language. Its far form perfect but its one hell of a toy if you want to waste time palying with it and trying to work out how to make it better.
I think it all about maket share, what is the point of having a PDA as a phone with a 5meg camera all in one unit if you can sell all three.
The technolagy is around, look at the Sony cameras. Shame but what can we do as the differences between men and boys remains the price of their toys.
Ha ha ha, I know MDAIIIUser........
It's just that I use it also as a tool in my business.
I have a lot of tools, and if one of them don't work as it's suppose to, it's just right back in their the next second.
I get no mercy when I'm out on a job, everyone don't get any mercy when they are on a job. If it's not finished........Well you simply just don't get the money. If it's not made by the regulations, you get a ticket to the court room, and don't expect it to anything else for you than cost a hell of a lot of money.
So you see, it's bugs me quite a bit that i buy a device at this price that’s not finished. There are major software troubles on it, making the phone part useless from time to time.
It's sold as BT compatible, what BT compatibility are they talking about??? Everyone is having trouble with it no matter what headset they are connecting to.
It don’t even have the most basic function found in every single phone sold world wide, a button lock that actually locks the device. I was sure that it was something I missed, just couldn’t believe that it weren’t in there.
And I don’t care if this is a PDA/Phone and not a Phone/PDA, they can’t be that thick in their heads that they don’t see this.
The hardware is bad, it’s getting more and more loose every day, the sliding keyboard is soon to become an auto sliding keyboard. Just hold it vertical and it will slide down all by itself.
I had the whole outer case replaced because the stylus was sliding out by itself. Now about 3 weeks later it’s so loose that it in the next week or so will be completely loose again. Then it’s in to service once again, me not having my tool which I spend a good amount of money on software for business use. Back to paper and then by hand doing the job in the office.
Now I’m guessing that this will happen again, that being the 3’rd time. Then it’s a full refund by law, and if the software isn’t ready at that time, I will claim a full refund or else ill just hand it over to my attorney. Buy a laptop for the car, a P900 again and then the irritation is over, and I can work in peace and quite.
The screen occasionally makes a high frequent sound when I’m talking in it, making it quite difficult to concentrate on the conversation. Unfortunately they didn’t have any new screens on stock when it was repaired the last time……….
I had absolutely no hopes for the camera when I got it, as I said earlier, what’s to expect of a VGA camera, and I don’t care, even though it would be nice to actually have one that could produce something just a little bit useful.
If I where the IT responsible person in a big company, I certainly wouldn’t recommend the boss to get 50 of these, the work load and support needed is simply just too much.
And all that said, ill properly end up with the MDA IV anyway *LOL* , what an idiot
Hum!!! Got out of bed on the wrong side or did wify have a headache??
Ok I admit the hardware is crap, my keyboard is auto eject at the momnet and the only thing I am REALY happy about is the fact that it has a metel case as I have dropped it (or was it threw it on the floor). My 5 yearl old girl has better developed teath than the BT on this thing. Yellow is a nice color if you realy like it but maybe not on a high depth screen. Don't even let me go down the rest, I will sound like you.
All I can hope for is the MDA 4 and that I get that one free as well. If its only to update wiki. Grin.
Thanks for your post put a big grin on my face.
Once there was a book "101 uses for a dead cat". Maybe we should start a thread for the BlueAngel:
101 uses for a dead BlueAngle
Click to expand...
Click to collapse
and hope that NOBODY postes the paper wheight idea.
Well let’s not take it all out on the phone.
I think it would be more fair to get that book out with the title “101 uses for a BA owners head”.
It’s going to be the worlds most paperless book ever sold :lol:
Well maybe we could get some highly respected brain schrinks expert opinion in there, then it at least would have one page, “I simply do not now”

anyone know of a weight watchers point calculator for WM SP

Anyone know of a spreadsheet or app that can do this?
As long as you are able to browse the net with your phone, just copy this into your phones browser favorites. Works for me.
http://www.webmilhouse.com/pointcalc.php
points = (calories/50) + (fat/12) - (min{fiber,4}/5)
In case you didn't know, "min{fiber,4}" means that you use the lower number. In other words, only the first four grams of fiber count.
You can use this formula in Excel to create your own pointes calculator.
I hope that helps!
Make your own weightwatchers program
So is there a way extract the food database from the WW program so you could add it as a separate spread sheet and search for food pint values? Also does anyone know formula for the exercise points?
excellent response
dewey1973 said:
points = (calories/50) + (fat/12) - (min{fiber,4}/5)
In case you didn't know, "min{fiber,4}" means that you use the lower number. In other words, only the first four grams of fiber count.
You can use this formula in Excel to create your own pointes calculator.
I hope that helps!
Click to expand...
Click to collapse
Thanks for that. I'm not as familiar with Excel as I should be. Any chance you could upload one with that formula already in it?
sorry to bring this back but thought i'd share...
the following formula will work in an excel to calculate points. it will not display any result if there's a number missing (otherwise you get 0.8 displayed in the result because of the fiber calculation), and will around to the nearest whole number (since fractions aren't accounted for in normal ww calculation):
=IF(C2="","",ROUND(((C2/50)+(C3/12)-((MIN(C4,4)/5))),0))
you will need to adjust the cell references to match your layout. in the above formula c2=calories, c3=fat, and c4=fiber.
hope this helps!
Developer one recently came out with a program called ifitone that tracks a lot of fitness info.
http://www.developerone.com/ifitone/screenshots.htm
Love to get my hands on this
i actually worked up an html file that can be used via a browser. same exact idea as plugging in that afore mentioned formula into an excel.
the only problem with this is that i can't figure out how to force the phone to go into number entry mode when inputing the info into the fields... so for the time being you have to hit the alt key for every number you enter. total PITA, so if someone knows how to fix, please do!
Many Thanks!
SirKeats said:
sorry to bring this back but thought i'd share...
=IF(C2="","",ROUND(((C2/50)+(C3/12)-((MIN(C4,4)/5))),0))
c2=calories, c3=fat, and c4=fiber.
hope this helps!
Click to expand...
Click to collapse
Thanks for bringing it back up! first thing I sat down to figure out this morning and you had the formula laid out. I had PointsCalc on my Treo 650 and my wife had gotten dependent on me having it handy when we're shopping. This is even easier to use!
I use Iambic Health and Diet Manager
Lots of options.
I believe you can "try before you buy"
i actually worked up an html file that can be used via a browser ...
Click to expand...
Click to collapse
I actually worked up a sweat reading the formulae.
Still; no pain, no gain.
Sorry I never responded to the request for the Excel file, I don't remember getting an email about a reply.
I wonder how many excercise points for reading the formula? Let's figure it out...
From Starling Fitness » What You Need To Know About Weight Watchers:
Activity Points:
These are harder to calculate. The calculation is based on perceived exertion. Light, Moderate and Heavy. They base the levels on sweating and breathing levels, which leaves asthmatics and heavy sweaters in a strange conundrum.
In January 2005, Weight Watchers released recommendations for Activity Levels based on Heart Rate:
* WeightWatchers.com - Exercise Intensity Levels
They use the typical calculation for Maximum Heart Rate:
Maximum Heart Rate = 220 - Age
They state you can calculate your activity levels based on the following:
* Light is about 40-54% Maximum Heart Rate.
* Moderate is 55-69% Maximum Heart Rate.
* Heavy is equal to or greater than 70% Maximum Heart Rate.
I used much more vigorous percentages in my estimations, so this bit of news made things much easier for me.
Once you’ve calculated how much time you’ve exercised at a certain activity level, here is the registered calculation for Activity Points:
Light Activity Points = Weight X Minutes X .000232
Moderate Activity Points = Weight X Minutes X .000327
Heavy Activity Points = Weight X Minutes X .0008077
You can add Activity Points into your total for the day. The Flex Points plan states that you need to use the Activity Points on the day that you use them. The older plan used to let you Bank a maximum of four Points and save them for up to a week.
Click to expand...
Click to collapse
I also purchased Iambic Health and Diet Manager. It is pretty good. It used to have a desktop client that you could use and sync between the phone and the PC. Then the software was sold to Iambic and now they charge for the desktop version separately. Bummer! It was easier to load up the database with your favorite foods (or at least your most frequently eaten foods [because usually you aren't going to be eating your FAVORITE foods]) using a full sized keyboard.
I made an Excel calculator (using a similar, if not the same, formula) that also had a way to calculate the points for a recipe given the ingredients. I'll see if I can dig it up.
points calculator
kendle said:
As long as you are able to browse the net with your phone, just copy this into your phones browser favorites. Works for me.
http://www.webmilhouse.com/pointcalc.php
Click to expand...
Click to collapse
This is just awesome. Its all you really need.
thanks!
I use a excel spread sheet on my tilt with wm6. I made it and synced it to my phone. Works great in Wal-mart where service can be spotty.

Touch Pro 2 radio

Hi guys
Followed the slightly concerning threads re the radio disappearing from the specs.
It is now back on the specs at Clove and never disappeared from the Expansys ones.
I called HTC UK support yesterday. They said to me that it was all still subject to change (as it would be officially until the shops get it) but their internal current spec still said it had an FM Radio.
Paul.
If that's what the current internal spec is then I'm pretty dang sure it will have it. That means that it's been designed to have it and removing it would just be removing the chip from the board. The chip is probably pretty dang cheap as it is. Then it would just be wasted space.
Specs don't just disappear from web pages for no reason. The main HTC site still shows the FM radio as not being included, when it used to be there. I'm hoping it will continue to be there, but somebody took it down for a reason, even if it wasn't taken down from all sites.
at this point, if they say it still has it, it likely still does. They have to be manufacturing them in mass by now with it being as close to the release as it is (least outside of the US). T-Mobile/AT&T may have the radio removed tho, it wouldn't surprise me for them to remove features (ie cmos camera). But who knows. Either way, i couldn't care less. I don't listen to the radio as it is. Not to say that others wouldn't want to, but technically, this is a business phone so a radio would seem a bit out of its way.
Personally, i would say, if they included a radio, they should also include a 3.5mm jack to Listen to it on.
That's pretty much my point. At this time, they most decidedly are not saying that it has it, when in February they specifically said on the same page that it was included. I hope it was right then and wrong now, but I have my doubts.
Business or phone phone
I do wish people would stop pandering to this rubbish.
No one buys a highend PDA phone (privately) to use it just as a business / organiser device or just as a fun / media device.
It is fair to say that some people won't mind if a radio or tv-out or gfx acceleration or decent camera or 3.5" jack is missing .... but that isn't a justification for HTC or anyone else not to put these things in on expensive new devices.
Most people I know that have a highend device like the HD or TP2 will probably want at some point to dump some movies to it and play it on an hotel TV when they are away with work because they don't have their Archos or ipod with them. This means that TV-Out and support of embedded gfx hardware should be a given.
Most people would prefer a proper wired headphone jack for wired listening of any description.
Many people find themselves on the train, at an airport or in a break and at some point may like to listen to the news. If you live in the UK or a country where most providers insist on realmedia for streaming, Resco News etc is no good ... you need a decent radio. PDA and phone manufacturers have demonstrated that hardware for this sort of thing is typically on chipset anyway and just needs enabling and exploiting in firmware.
HTC very irritatingly artificially leave these things out which makes the device in complete ... for no good reason other than to force people to either get two devices or feel frustrated from time to time (even if rarely) when they want to use things like the above.
The camera situation is the same. 30fps vga video is common place on SE and Nokia ... Apple and HTC should not be forgiven for not including it (yes ... I know the TD2 and TP2 now have it ... at last) ... also ... yes ... you'd expect if you were planning to take holiday snaps you'd take your Pentax or Canon SLR with you .. but often you want to take adhoc pictures .... why shouldn't they be of decent quality ... the technology is there and in mass production SE and Nokia have shown that it shouldn't raise the cost of the devices.
We shouldn't be so accepting about things like this ... it allows HTC to treat us with some contempt and encourages them to continue to do so.
All these devices they are bringing out ... long after the Snapdragon ... but still no sign of official support ... again ... getting people to buy last generation technology today. Are we forced to ... no ... but given their position in the market ... they still have no viable competition on the WM front ... they are exploiting that.
Sorry for the rant ....
Hope this helps...
Some food for though...
If HTC remove the FM radio, at this late stage (after some devices with it have been released) will they keep the chipset's the same?
If so I'm sure some of the guys on here could get the Drivers for it working again...
If such a project is needed, count me in, I'm missing FM radio from my Kaiser
Dave
Speaking of rubbish...
pgamble said:
HTC very irritatingly artificially leave these things out which makes the device in complete ... for no good reason other than to force people to either get two devices or feel frustrated from time to time (even if rarely) when they want to use things like the above.
Click to expand...
Click to collapse
Yes, I'm sure that this is precisely the reason HTC does these things. Market analysis, purchase trends, customer preferences research - all of these things are meaningless next to the opportunity to make their customers irritated and frustrated.
pgamble said:
The camera situation is the same. 30fps vga video is common place on SE and Nokia ... Apple and HTC should not be forgiven for not including it (yes ... I know the TD2 and TP2 now have it ... at last) ... also ... yes ... you'd expect if you were planning to take holiday snaps you'd take your Pentax or Canon SLR with you .. but often you want to take adhoc pictures .... why shouldn't they be of decent quality ... the technology is there and in mass production SE and Nokia have shown that it shouldn't raise the cost of the devices.
Click to expand...
Click to collapse
Define decent quality. I'm not sure what your gripe is here. Lack of a flash? OK, I can see that. But if you are complaining that you're not getting 30 FPS for your ad hoc videos, then HTC is just not the camera for you. Your priorities dictate the purchase of a different device. That's no reason to suggest that HTC is being intentionally annoying. They are making the decisions that will earn the highest sales for any given device in the markets for which they have seen they can effectively compete.
ajbopp said:
Define decent quality. I'm not sure what your gripe is here. Lack of a flash? OK, I can see that. But if you are complaining that you're not getting 30 FPS for your ad hoc videos, then HTC is just not the camera for you. Your priorities dictate the purchase of a different device. That's no reason to suggest that HTC is being intentionally annoying. They are making the decisions that will earn the highest sales for any given device in the markets for which they have seen they can effectively compete.
Click to expand...
Click to collapse
I read HTC somewhere (I forget where) that it will be removed because of battery life performance issues. HTC are still trying to make this a business phone (hence the conference calling and Straight Talk) so it makes sense that a business phone would benefit more from battery life than an FM radio.
Just my 2'cs
Dave
I have to ask this again. Why would a radio chip and software waste battery when it's not on? It just doesn't make sense. Please enlighten me!
any news?
it's weird to see the Radio feature still on the official italian specification web page ...but it's not anymore on the english page
cocoaju said:
I have to ask this again. Why would a radio chip and software waste battery when it's not on? It just doesn't make sense. Please enlighten me!
Click to expand...
Click to collapse
It's Possible the FM radio stuff can cause interference with other devices in such a small space, meaning more power is needed to overcome any distortion.
There might even be a form of idle state it keeps itself in. Take the radio feature on the mp3 player next to me, it doesn't scan through like normal unless you force it to retune. It presets itself stations it can find gets RDS for them and names them and keeps track of it when not using the radio feature and more annoying it will do this when the whole device is in it's standby mode and will do so unless fully turned off.
Personally I believe it's just an oversight when they updated the battery spec on the UK HTC page as mass production is likely to have started and removing it last minuet would have likely been costly.
magius00 said:
There might even be a form of idle state it keeps itself in. Take the radio feature on the mp3 player next to me, it doesn't scan through like normal unless you force it to retune. It presets itself stations it can find gets RDS for them and names them and keeps track of it when not using the radio feature and more annoying it will do this when the whole device is in it's standby mode and will do so unless fully turned off.
Click to expand...
Click to collapse
I understand that if it's on standby mode, it may use up battery life. I mean if you leave software running in the background, it will run down your battery as well. So it's understandable.
But if you fully turned it off, it shouldn't kill battery life, cos it's not on, right? So, again, it doesn't make sense for battery life to lower, with or without the radio.
As you said, it could be HTC updating on the battery life spec because they got it wrong the first time round. And they thought the radio is no longer needed on this phone so they take it off as well.
I think this happened to the Samsung Omnia HD (not out till end of June) as well. GSM Arena just took another preview of it and some specs has changed prior to launch. They took the radio out as well.
So anything can happen until everything is set on launch date.
Just thought of a good reason to keep radio for business - GPS traffic data! GPS software use FM radio to receive the traffic data. if no radio, no traffic for GPS software.
Apart from no Radio, I just saw a couple of videos from you tube on TP2 reviews, it looks like the zoon bar is missing too.
I checked HTC's website and their gallery still shows the zoom bar. The videos were uploaded this week as well. So unless they took the video a while back and just uploaded it now, it looks like we are missing more features.
European Version Video Review
Asia CNET Version Video Review
Hope this is my mistake.
I just watched again and on the start of the video, I think I saw a glimpse of the zoom bar but never again afterwards. Maybe it's just so reflective, that I can't see the zoom bar. Maybe it is really me... being too imaginative
european video at 3.36 min, it's there !!!
Ha! You are correct! I saw the glimpse. Super reflective screen makes it hard to see on the video.
cocoaju said:
Ha! You are correct! I saw the glimpse. Super reflective screen makes it hard to see on the video.
Click to expand...
Click to collapse
which icont is it? i cant easily make out what one is the radio

IWOWN i5+ BLE bracelet teardown with debug programming pins etc

Hey I got one of these to do some hacking on - well, I got several of them, because taking one apart is very much a one-way trip.
As posted elsewhere, it's made of:
A 128x32 white OLED ( cdn-shop.adafruit.com/datasheets/UG-2832HSWEG02.pdf )
NRF51822 BLE chip (16K ram version)
Atmel ATmega16U2 (I assume to read the accelerometer at low power, but it also has USB - which appears to not be connected to the USB port unfortunately)
An accelerometer (STM C3H)
Azoteq IQS263 touch sensor (senses swipes and taps)
24C256 EEPROM connected to the Atmel
75mAh Lipo
..and some other stuff like a Lipo charger, vibration motor etc.
Typical cost is $15-$20 on ebay etc.
The cap-touch screen is quite good - detects swipes and taps reliably.
It's very well sealed - completely closed plastic molding. It looks to be fully waterproof to me.
Well... waterproof until I took a hacksaw to it. There's no way to disassemble it other than to (carefully) hacksaw/dremel the case open. Mine is still working fine, albeit in pieces..
I didn't see many photos of the guts online (just a couple) so or anyone else planning to hack on firmware for it, I found very convenient SWD and UART testpoints (under the OLED)...
Was figuring I might be able to find the time to do some alt firmware for it, because I quite like that Nordic chip, and it's a pretty decent waterproof BLE wrist-display with reasonable battery life (~7days people have said) and touch-sensor at a very attractive price.
I'll let you know what else I figure out about the hardware but first some teardown pics;
FULL PICS:
(oh man **** this forum not letting me post URLs... ok whatever, you figure this out..)
imgur.com/a/qTrSN
Samples images attached...
NOTE that test test points "RESET" and "CLK" are regular Cortex M0 SWDIO and SWDCLK, so just bust out the ST-Link/J-Link and have at it. Nice to have UART TX+RX too. Very civilized.
If I have time to get further into it I'll post more hw details on here.
Cheers,
DrTune
Yep J-Link works fine
Nice, works fine connected to a J-Link, can program it with NRFgo Studio, debug with Keil uVision, etc. Cake.
Ok when I have a sec I'll do some custom firmware for this thing, personally I'm going to use it as a user interface for a GPS+radio project for Burning Man - the I5+ should be perfect for the Playa as it's completely sealed, has vibration, decent battery life, nice OLED.
I really like this bracelet as a programmable toy - nice CPU, great price. I doubt I'll ever get around to programming the Atmel in there or using the accelerometer (it's not what I'm after) but as a two-way messaging device it should fit the bill nicely.
Well done my friend! Can't wait to see what you will come out with! Cheers
Do something perfect ? thank you
Sent from my E2333 using XDA-Developers mobile app
Hm just thinking about it there's quite a lot of fun little things you can do with a cheap watch w/touch sensor that vibrates that are a bit awkward to do with a phone... bear in mind I'm super busy (I do this kinda thing for a living) and the BLE range is probably pretty poor, but...
a) Finder for those absurdly cheap ($3 or so) "finder" keyfobs, just display RSSI (signal strength) and it'd be somewhat useful; at least to give you a "warmer/colder" feedback on your distance to the tag.
b) Vibrate when your friend comes into range (or any BLE device that's advertising) and let you send simple emoticon messages (again the range won't be great, but enough for when you're in a bar or whatever), kinda like a really basic emoticon walkie-talkie. This would suck down quite a lot of battery (b/c of scanning for advertising packets) but it's a thought
c) some sort of basic morse-code style tapping messager
d) unlock your front door (use any old BLE device, e.g. a $4 CC2541 BLE-to-serial dongle hooked up to a FET or a relay)
e) assuming I can sort out reading the accelerometer, you've got basically a button/slider (the touchscreen) plus a very rough motion sensor; maybe make it a GATT HCI device like a mouse or keyboard (not sure what the OS support is like for those but it's doable)
f) You could certainly interface it to a Banana Pi (with a CSR BLE dongle) or a C.H.I.P. (which has built-in BLE)...
g) then there's all the stuff you can do with modern android/iOS phones and BLE; caller ID etc etc - much of this is covered by the current IWOWN firmware... Haven't look at it a huge amount but there's sure to be some fun stuff not yet done by the stock fw...
h) Depending what OSes have HID-over-GATT keyboard support, you could tap your watch to enter passwords (fairly insecurely, but hey it's a fun hack)..
i) Trivial to make the thing act as an Apple iBeacon (or any vendor beacon really, it's just a custom advertising packet) - and that would have excellent battery life. You could make it a beacon detector also but the battery life would suck horribly (I guess you could tap the watch to scan and it could buzz when it found an iBeacon and display some txt from it )
j) BLE scanner, probably most useful to have it scan for specific GATT profiles or ad packets or MAC address ranges or whatever; same battery life caveat applies but there might be a fun application.
...there's a lot of simple projects basically, it's quite a nice toy in some limited ways.... well like I say I don't have time to implement a lot of this but if I can stick some code up on Github maybe people will take the ball and run with it...
drtune said:
Hm just thinking about it there's quite a lot of fun little things you can do with a cheap watch w/touch sensor that vibrates that are a bit awkward to do with a phone... bear in mind I'm super busy (I do this kinda thing for a living) and the BLE range is probably pretty poor, but...
a) Finder for those absurdly cheap ($3 or so) "finder" keyfobs, just display RSSI (signal strength) and it'd be somewhat useful; at least to give you a "warmer/colder" feedback on your distance to the tag.
b) Vibrate when your friend comes into range (or any BLE device that's advertising) and let you send simple emoticon messages (again the range won't be great, but enough for when you're in a bar or whatever), kinda like a really basic emoticon walkie-talkie. This would suck down quite a lot of battery (b/c of scanning for advertising packets) but it's a thought
c) some sort of basic morse-code style tapping messager
d) unlock your front door (use any old BLE device, e.g. a $4 CC2541 BLE-to-serial dongle hooked up to a FET or a relay)
e) assuming I can sort out reading the accelerometer, you've got basically a button/slider (the touchscreen) plus a very rough motion sensor; maybe make it a GATT HCI device like a mouse or keyboard (not sure what the OS support is like for those but it's doable)
f) You could certainly interface it to a Banana Pi (with a CSR BLE dongle) or a C.H.I.P. (which has built-in BLE)...
g) then there's all the stuff you can do with modern android/iOS phones and BLE; caller ID etc etc - much of this is covered by the current IWOWN firmware... Haven't look at it a huge amount but there's sure to be some fun stuff not yet done by the stock fw...
...there's a lot of simple projects basically, it's quite a nice toy in some limited ways.... well like I say I don't have time to implement a lot of this but if I can stick some code up on Github maybe people will take the ball and run with it...
Click to expand...
Click to collapse
Actually i don't think that there will be anyone who doing after you so i ask you to do some of them. Another question the screen has to coler white and blue can we change it i really like white one
Sent from my E2333 using XDA-Developers mobile app
Errrr.. no the OLED is whatever color it is. It's a cheap monochrome OLED. The only way you could change it is to take the device apart and there's no way you can ever put it back together properly again (it's solid molded plastic)
Nice work.
if it's any help.
Softdevice and bootloader i5PLus.
http://www.mediafire.com/download/uc5ugaqrjcg58w3/i5plus_softdevice.hex
http://www.mediafire.com/download/z3oe2544uayec6h/bootloader.hex
thx but the Nordic publicly available stuff is fine. I pulled the firmware etc from mine and reflashed it already. There's nothing difficult or problematic, just a case of finding time to do new fw (and I'm super busy)
There was a distant feature in oldest firmware but they removed many asked to get it back can you do it in your firmware ☺
Sent from my E2333 using XDA-Developers mobile app
by "distant feature" do you mean distance, i.e. it tracked how far you have walked/run? I can see how that would be unreliable, there's just an accelerometer in there and you can't really figure out distance from that. Accelerometers just tell you which way is down (i.e. they measure gravity) plus the acceleration/deceleration as you move it around. So, they're ok for detecting walking, better for running, but not good for figuring out how far you've actually travelled, the best it could really do is just guess from the number of footsteps it detected, which is going to be pretty inaccurate.
In general I'm not planning to do anything with the accelerometer (I doubt I'll have time), I'm thinking about using the I5 for other things like radio messaging and as a phone peripheral.
I don't expect to produce anything that duplicates the current firmware in terms of function, I want to do completely different things. Once I've written some code I'm happy to put it on github (which will have basic stuff like driving the OLED, reading the touch sensor, using the BLE radio etc) and maybe someone else will build some firmware that works as a fitness tracker.
drtune said:
by "distant feature" do you mean distance, i.e. it tracked how far you have walked/run? I can see how that would be unreliable, there's just an accelerometer in there and you can't really figure out distance from that. Accelerometers just tell you which way is down (i.e. they measure gravity) plus the acceleration/deceleration as you move it around. So, they're ok for detecting walking, better for running, but not good for figuring out how far you've actually travelled, the best it could really do is just guess from the number of footsteps it detected, which is going to be pretty inaccurate.
In general I'm not planning to do anything with the accelerometer (I doubt I'll have time), I'm thinking about using the I5 for other things like radio messaging and as a phone peripheral.
I don't expect to produce anything that duplicates the current firmware in terms of function, I want to do completely different things. Once I've written some code I'm happy to put it on github (which will have basic stuff like driving the OLED, reading the touch sensor, using the BLE radio etc) and maybe someone else will build some firmware that works as a fitness tracker.
Click to expand...
Click to collapse
Really it doesn't need any adding or creating for it. Just like calorie and step measure it was measuring km. You just need to get it from old firm and add it to the new one ?
Sent from my E2333 using XDA-Developers mobile app
Right, and without even having seen it I can tell you it won't work very well at all, because (...see above info about accellerometers and distance tracking).
Like I said I'm not planning to support any of this stuff.
If you personally want to "just get it from old firm and add it to new one" go for it!
drtune said:
Right, and without even having seen it I can tell you it won't work very well at all, because (...see above info about accellerometers and distance tracking).
Like I said I'm not planning to support any of this stuff.
If you personally want to "just get it from old firm and add it to new one" go for it!
Click to expand...
Click to collapse
Well done bro thank u for your work i hope to see it soon
Sent from my E2333 using XDA-Developers mobile app
@drtune
The reason why we're "clinging" on you is because you seem to be the only one here who can really play with these things at a developer level. With the Chinese manufacturer not caring about the abroad markets (they did not release the v2.x firmware and the "full" v3 Android app outside of China), we're kinda stuck.
I, for one, do not regret spending $16 on this thing at all. v2.0.1.8 firmware - customly flashed thanks to @roninzgz's thread - brings everything I was hoping for (vertical display and the ability to keep the time synchronized even while turned off), albeit with the trade-off of a slightly less responsive touchscreen. For crying out loud, I have Fitbit sporting coworkers that are envious at what this bracelet can do for its price. Their only hope is that mine will eventually break or fry due to poor manufacturing quality.
With all that going for us, getting you aboard would be a bit too much luck. Thank you for all the research and here's to hoping that someone will pick up from what you will share. *raises beer*
Sure, thanks.
I do this stuff for a living (not actually fitness trackers, but embedded systems hardware/software) so I have all the equipment and experience to make this a fun little project ; on the minus side I have quite a backlog of paying work to finish so taking time off that (and my family) to do this feels like I'm playing hooky from school
Anyway, like I say I have a pet project for this wristband in mind - and it doesn't really involve it doing much of what the existing firmware does - but at least I'm mildly committed to it now (ordered another six I5+'s and have one gutted and wired up for debugging here).
For anyone wanting to play with building new firmware you'll basically just need a hacksawed-open I5+ and a $4 ST-Link programmer; it would be interminably boring trying to debug by downloading new code OTA each time you make a change. Obviously once one has something reasonably ready to test it's easy enough to package it so it can be downloaded by other people with the regular Nordic OTA tool.
I can imagine it'd be possible to have an error in the firmware that bricked a device, but you'd put some reasonable safeguards in there wherever possible - really it's just about doing your best to ensure a user can get it back into an OTA-programmable state again.
drtune said:
Sure, thanks.
I do this stuff for a living (not actually fitness trackers, but embedded systems hardware/software) so I have all the equipment and experience to make this a fun little project ; on the minus side I have quite a backlog of paying work to finish so taking time off that (and my family) to do this feels like I'm playing hooky from school
Anyway, like I say I have a pet project for this wristband in mind - and it doesn't really involve it doing much of what the existing firmware does - but at least I'm mildly committed to it now (ordered another six I5+'s and have one gutted and wired up for debugging here).
For anyone wanting to play with building new firmware you'll basically just need a hacksawed-open I5+ and a $4 ST-Link programmer; it would be interminably boring trying to debug by downloading new code OTA each time you make a change. Obviously once one has something reasonably ready to test it's easy enough to package it so it can be downloaded by other people with the regular Nordic OTA tool.
I can imagine it'd be possible to have an error in the firmware that bricked a device, but you'd put some reasonable safeguards in there wherever possible - really it's just about doing your best to ensure a user can get it back into an OTA-programmable state again.
Click to expand...
Click to collapse
Drtune did you done anything ?
Sent from my E2333 using XDA-Developers mobile app
Not yet have a ton of work on right now and will be busy for a while on that - just very short of time right now.
Honestly don't expect anything useful to you as a consumer any time soon; when I get some code done (which will be for my project and not directly useful to an end-user) I'll post on here and github.
Hi,
Does anyone know if it's possible to customize this device and turn it into a ibeacon?
I'm looking for a wristband that is able to switch between On/Off which enable the device to broadcast iBeacon signal.
I'm looking for somebody who can help me with it, i'm willing to pay a small fee for his expertise
(I'd like to learn how to code a firmware of this device too)
Thanks
What am i trying to do?
I hope to develop a solution where i will like to enable Teens to have a SOS button on their wristband. It would then be able to code a android/iphone app that would listen for such signal, if the ibeacon signal is on their range, it will alert the mobile user that there's a surround person is facing danger.
Current wristband that i found would require user to pair it with a phone, i'm looking at broadcasting feature instead.
If any developer is able to do this for me, please PM me i'd pay a fee for your expertise.
Yes the I5 (or, even cheaper, a TW64 watch) can do simple iBeacon (or similar) advertising, it's not difficult..
However you are making two very common mistakes; scanning for BLE devices uses as lot of power so no mobile OSes will let you do it all the time (for good reason). Everyone overlooks this and it's a huge issue.
Secondly the range of BLE is very limited.
I am not interested in doing this for you (I don't work for small fees) but it's not a difficult task for someone who knows what they're doing.

Any updates or improvements in 3D scans? Anyone one using it to generate 3d models?

The 3D scan capability of the N10+ is what intrigued me most about the phone. However, after release, most tests/examples of scans were disappointing. I read that the software was problematic and expected to be improved. Has this happened? Anyone actually using the phone to create exportable 3d files? If not, is improved 3d tech expected in the next version of the phone?
I tried it a bunch of times and could never get it to work. I mostly gave up since then though I did see that at least a couple of updates to the 3D scanner were released since then. I am yet to try this again.
I see so little about this feature. I really hoped there was more info.
CalypsoDroid said:
I see so little about this feature. I really hoped there was more info.
Click to expand...
Click to collapse
I've tried it a few times, some of them recently. It still works like garbage. It was a really cool idea but the execution has been totally worthless. I think they found the greenest intern they could find and had them randomly copy/paste code from StackOverflow until a program aaaaaaaallllmost formed. Then the intern went back to college and the company janitor took over development. It's just so completely stupid to put a 3D ToF sensor on the phone then totally bork the software and just never fix it. I suppose I shouldn't expect any less from the idiots who built LinuxOnDex then just suddenly aborted development even though it was working perfectly fine. Samsung is the new Google. Never trust anything either of them start. They're 90% likely to never finish it and just discontinue it suddenly.
Collin80 said:
I've tried it a few times, some of them recently. It still works like garbage. It was a really cool idea but the execution has been totally worthless. I think they found the greenest intern they could find and had them randomly copy/paste code from StackOverflow until a program aaaaaaaallllmost formed. Then the intern went back to college and the company janitor took over development. It's just so completely stupid to put a 3D ToF sensor on the phone then totally bork the software and just never fix it. I suppose I shouldn't expect any less from the idiots who built LinuxOnDex then just suddenly aborted development even though it was working perfectly fine. Samsung is the new Google. Never trust anything either of them start. They're 90% likely to never finish it and just discontinue it suddenly.
Click to expand...
Click to collapse
There is so much truth in this it's scary. Samsung Cloud was just going through my head as I was reading this. Launched, billed as the next best thing to happen to Android devices, then failed to roll out with any sort of desktop support, followed by failure to support buying more storage in almost all regions followed by scrapping of the whole thing and some quasi-partnership with Microsoft to use OneDrive. I can think of a bunch more features like this that Samsung devised and that never took off. The fact that the ToF sensor is not being utilized for better photography is also baffling to me. Samsung's default implementation of DoF is absolutely horrible.
A couple of days ago there was a new update. This doesn't make it suddenly scan things properly. I tried several things, mostly stuffed animals / dog toys as those are about the right size and don't move. Still works like crap. It does an OK job sometimes but the 3D sensor is very picky. I tried to scan a very large mug that is plastic and some of the pieces were too shiny and hardly showed up. I tried to scan a rubber dog toy and it kind of worked but the process was irritating. I tried to scan a large stuffed animal chicken. It's probably 3 feet tall, plush, and covered in fake fur (why would a chicken be furry? The world may never know). This worked OK, the model is decent. But, it was tough to keep my phone at the proper distance as I moved around it. That's mostly my problem but the app is super brittle. If you move too abruptly or you accidentally point your camera too far away it just immediately aborts. I've got programs for the PC that use a Kinect sensor from the XBOX to do scanning and those work similarly but generally tell you if you're getting off course and allow you to try to move back into position rather than just suddenly aborting the scan.
Forget trying to scan your pets. Animals move far too much. Probably forget trying to scan a person. It's hard for a person to sit perfectly still for long enough and this software isn't very forgiving. Though, scanning either pets or people does allow for some bazaar lovecraftian horrors to emerge. If you want to transform your pet into the Thing then this is the way to do it.
I think the problem is that they've got too large a mission. The app supports all kinds of dumb stuff like animating your 3D model after you capture it, etc. They really needed to focus on actually being able to capture models reliably before implementing all the cutesy garbage on top of it. The sad thing is that, for all the crap I give them about how bad it is, it's actually almost there. It's just right on the cusp of working. I can capture models of stuff. They're just very difficult to get working and when I do I see some aberrations that shouldn't be there. It's close to working and if they'd just hunker down and fix the weirdness in capture it could be great in short order. But, it seems like development on this is very slow and too spread out across all the other needless stuff it can do. It needs to scan stuff reliably and then they can work on the other gee-whiz features.
For your viewing pleasure, I've attached the best model I've gotten captured so far - the fuzzy chicken. It's large, it's in charge, it worked pretty well. Behold, the best the 3D Scanner on a Note 10+ can do. I attached both the model output from the 3d Scanner app and a picture of the base model (with no texturing) from Blender so you can see the smoothness and detail of the model without the texture obscuring it. I suppose it's fairly decent but I wouldn't directly use it to 3D print something.
Collin80 said:
A couple of days ago there was a new update. This doesn't make it suddenly scan things properly. I tried several things, mostly stuffed animals / dog toys as those are about the right size and don't move. Still works like crap. It does an OK job sometimes but the 3D sensor is very picky. I tried to scan a very large mug that is plastic and some of the pieces were too shiny and hardly showed up. I tried to scan a rubber dog toy and it kind of worked but the process was irritating. I tried to scan a large stuffed animal chicken. It's probably 3 feet tall, plush, and covered in fake fur (why would a chicken be furry? The world may never know). This worked OK, the model is decent. But, it was tough to keep my phone at the proper distance as I moved around it. That's mostly my problem but the app is super brittle. If you move too abruptly or you accidentally point your camera too far away it just immediately aborts. I've got programs for the PC that use a Kinect sensor from the XBOX to do scanning and those work similarly but generally tell you if you're getting off course and allow you to try to move back into position rather than just suddenly aborting the scan.
Forget trying to scan your pets. Animals move far too much. Probably forget trying to scan a person. It's hard for a person to sit perfectly still for long enough and this software isn't very forgiving. Though, scanning either pets or people does allow for some bazaar lovecraftian horrors to emerge. If you want to transform your pet into the Thing then this is the way to do it.
I think the problem is that they've got too large a mission. The app supports all kinds of dumb stuff like animating your 3D model after you capture it, etc. They really needed to focus on actually being able to capture models reliably before implementing all the cutesy garbage on top of it. The sad thing is that, for all the crap I give them about how bad it is, it's actually almost there. It's just right on the cusp of working. I can capture models of stuff. They're just very difficult to get working and when I do I see some aberrations that shouldn't be there. It's close to working and if they'd just hunker down and fix the weirdness in capture it could be great in short order. But, it seems like development on this is very slow and too spread out across all the other needless stuff it can do. It needs to scan stuff reliably and then they can work on the other gee-whiz features.
For your viewing pleasure, I've attached the best model I've gotten captured so far - the fuzzy chicken. It's large, it's in charge, it worked pretty well. Behold, the best the 3D Scanner on a Note 10+ can do. I attached both the model output from the 3d Scanner app and a picture of the base model (with no texturing) from Blender so you can see the smoothness and detail of the model without the texture obscuring it. I suppose it's fairly decent but I wouldn't directly use it to 3D print something.
Click to expand...
Click to collapse
How did you manage to put it in blender?
I played with it but more a curiosity than a useful tool. It really ate cpu cycles/current like crazy though. I guess if I needed a hand warmer I might use it again
may i know how do you scan a 3d model? been finding the app for some time already but cant find it
conanDO98 said:
may i know how do you scan a 3d model? been finding the app for some time already but cant find it
Click to expand...
Click to collapse
Search for "3D Scanner" in the Galaxy Store (not Google Play Store) and download the app.

Categories

Resources