Hi, I find the Sony Smartwatch 3 mostly works ok for compass but not that reliably, here a fragment of a GPS NMEA log from a Sony Smartwatch 3 with some custom sensor messages injected (the $PRHS messages) -
$PGLOR,1,FIX,1.0,1.0*20 $GPRMC,072428.00,A,3425.691647,S,15051.743203,E,000.8,272.9,050315,,,A*46 $PRHS ,RMC,20150305072427985*55 $PRHS ,GYR,0.0,0.0,0.0,20150305072428247*4D $PRHS ,ACC,9.952756,0.37819514,1.3165021,20150305072428436*44 $PRHS ,LAC,0.23899937,0.009213656,0.02143073,20150305072428437*46 $PRHS ,MAG,47.183502,-51.789,-2.7145,20150305072428614*41 $PRHS ,ORI,187.86511,-2.1546898,-82.405205,20150305072428614*53 $PRHS ,COM,238.09642,16.275442,82.198425,20150305072428824*43 $GPGGA,072429.00,3425.691623,S,15051.743187,E,1,07,3.2,25.0,M,17.8,M,,*43 $PGLOR,6,STA,072429.00,0.001,0.000,473,1,32,1,P,D,L,0,C,2,S,0002,589,5,R,33F4,TPEF,25,1784039,LC,,*58 $PGLOR,1,UNC,072429.00,0.041,32.0,11.7,1.04,180.00,29.0,13.6,-11.6*3C $PGLOR,2,SAT,2,1,G18,020,1F,G21,012,30,Q01,023,1F,R04,025,1F,G22,028,1F,G15,011,30*34 $PGLOR,2,SAT,2,2,R19,030,1F,G27,020,1F,G16,012,1F*03 $PGLOR,2,SIO,TxERR,0,RxERR,0,TxCNT,340,RxCNT,4224,MLFRMPKT,0,DTMS,1003,DTIN,30,46,DTOUT,178,955,HATMD,-119*32 $PGLOR,2,SIO,TxERR,0,RxERR,0,TxCNT,340,RxCNT,4224,MLFRMPKT,0,DTMS,1003,DTIN,30,46,DTOUT,178,955,HATMD,-119*32 $PGLOR,3,PWR,mA,33.6,RFTm,1002,OscTm,1000,MeasTm,1000,UTC,072429.00*39 $GPGSV,3,1,11,18,74,239,21,21,66,133,12,22,41,287,28,15,40,118,11*71 $GPGSV,3,2,11,27,25,223,21,16,20,259,12,29,23,027,,26,11,142,*7E $GPGSV,3,3,11,13,10,142,,14,07,348,,24,03,066,*45 $GLGSV,2,1,07,68,50,305,25,83,29,210,30,82,81,118,,67,66,168,*6E $GLGSV,2,2,07,81,32,043,,66,14,146,,69,02,318,*5C $QZGSV,1,1,01,01,64,269,23*5B $BDGSV,2,1,07,208,76,247,,201,47,342,,206,43,298,,203,32,304,*64 $BDGSV,2,2,07,209,14,306,,212,11,220,,202,07,281,*69 $GPGSA,A,3,16,18,22,27,,,,,,,,,9.4,6.6,6.7*35 $GNGSA,A,3,16,18,22,27,,,,,,,,,9.4,6.6,6.7*2B $GNGSA,A,3,68,83,,,,,,,,,,,9.4,6.6,6.7*25 $QZGSA,A,3,01,,,,,,,,,,,,9.4,6.6,6.7*23 $IMGSA,A,3,,,,,,,,,,,,,9.4,6.6,6.7*2D $BDGSA,A,3,,,,,,,,,,,,,9.4,6.6,6.7*2F $PRHS ,GYR is the gyroscope it values are usually all 0 (but sometimes it has non zero values present) I find the Gyro returns non zero values until the GPS gets a valid fix then the gyro values are always zero (???) $PRHS ,COM show compass values - in landscape device orientation (!) using the old deprecated sensor values method. $PRHS ,ORI shows compass values - in portrait device orientation (!) using a sensor fusion method based on the accelerometer ($PRHS ,ACC) & magnetometer values ($PRHS ,MAG) The GPS receiver is ok I suppose, not that sensitive & a little laggy. I use my Smartwatch 3 as a digital GPS speedometer with track & sensor log recorder for bike riding. It works ok but it requires an external power supply as I use a wake lock to force the screen on all the time, consequently the device runs hot but thats ok as its mounted on handle bars. Regards On Thursday, March 5, 2015 at 6:08:07 AM UTC+11, Nathan wrote: > > I was thinking of offering this as an alternative= to customers. > > > http://www.amazon.com/Sun-DC204WB-Slip-On-Wrist-Compass/dp/B001949J1W/ref=sr_1_1?ie=UTF8&qid=1425488514&sr=8-1&keywords=slip+on+wrist+compass > > Less battery drain, and probably more reliable. ;) > > I tried forcing it to use these two sensors: > Sensor.TYPE_ACCELEROMETER > Sensor.TYPE_MAGNETIC_FIELD > > Before that, it was defaulting to a RotationVectorSensor if one exists. > I thought, at least in the phone world, that was preferable where it > exists. > > On Sony Smartwatch 3, it does exist but apparently not preferable. I don't > know about the other devices. > > Anybody else have secrets to contribute? > > Nathan > > On Tuesday, March 3, 2015 at 3:42:44 PM UTC-8, Nathan wrote: >> >> I implemented code that finds the compass direction. >> >> It uses Sensor.TYPE_ROTATION_VECTOR. >> >> The same code works fine (or at least, as usual) on the phone using >> Android 4.4. >> >> I've tried it out on my Sony Smartwatch 3 and it works - a small minority >> of the time. >> >> I have found that if I look at the compass needle I placed on North, >> Sometimes it points North. >> Sometimes it points West >> Sometimes it points East. >> Sometimes it points South >> Sometimes it points some other >> Sometimes it moves When I rotate the watch. Sometimes it doesn't feel >> like it. >> >> Calibrating (in other words, twisting my arm around violently), did not >> consistently help. >> >> Is my experience typical? >> >> Before I spend a lot of time trying to figure out if there is something >> weird with the code, I wanted to know how many have tried and are there any >> secrets. >> Maybe I should drop the idea of apps using compass sensors if they are >> just going to annoy end users who will send me hate mail. >> I've read things on the internet that indicate the Moto360 does not have >> the right sensors for compass rotation but it guesses anyway. >> >> Besides this device, I only have experience with the Gear Live. It had >> some funny compass directions sometimes too. The funniest part (ha ha) was >> once in a while, the compass sensor, plus all other motion sensors, just >> stopped working at all for a week or two. >> Sometimes they came back, but it happened enough that I returned that >> unit. >> >> Nathan >> > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
