[00:20:27] *** Quits: Horwitz (~mich1@p200300EC9BC22F00022268FFFE64E7C4.dip0.t-ipconnect.de) (Ping timeout: 240 seconds) [00:33:48] *** Joins: Horwitz (~mich1@p200300EC9BC1B800022268FFFE64E7C4.dip0.t-ipconnect.de) [00:33:48] *** ChanServ sets mode: +o Horwitz [04:50:15] *** Joins: xenos1984 (~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120) [04:50:15] *** ChanServ sets mode: +v xenos1984 [05:00:53] <03mike> How cheap is that? [05:00:57] <03mike> XD [05:30:49] *** Quits: Navit (~Navit@ec2-34-214-224-248.us-west-2.compute.amazonaws.com) (Remote host closed the connection) [05:31:15] *** Joins: Navit (~Navit@ec2-34-214-224-248.us-west-2.compute.amazonaws.com) [05:31:15] *** ChanServ sets mode: +v Navit [05:50:47] *** Quits: Navit (~Navit@ec2-34-214-224-248.us-west-2.compute.amazonaws.com) (Remote host closed the connection) [05:51:03] *** Joins: Navit (~Navit@ec2-34-214-224-248.us-west-2.compute.amazonaws.com) [05:51:03] *** ChanServ sets mode: +v Navit [09:49:01] *** Joins: thoms (c2fa06b2@gateway/web/freenode/ip.194.250.6.178) [12:43:16] *** Quits: thoms (c2fa06b2@gateway/web/freenode/ip.194.250.6.178) (Quit: Page closed) [13:21:09] *** Quits: xenos1984 (~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120) (Quit: Leaving.) [13:37:03] hi there [13:37:16] Mike : $15 including shipping [13:53:52] <03mike> Hello [14:10:32] kazer: did you say you will also get a tomtom? [14:11:40] <03mike> He ordered one i guess [14:13:53] <03mike> Im trying to get my tomtom to boot [14:27:34] jkoan: yep. I ordered a device that should be similar to Mike's device (Start / Ease). I should get it in a few days [14:28:05] mike : i haven't seen anything, but i've never seen a device that allows you access to its system memory. So whatever we broke yesterday can be fixed [14:28:06] <03mike> Kazerrr [14:28:18] <03mike> I fixed it [14:28:23] nice :) [14:28:24] <03mike> Well kind of [14:28:26] what was it? [14:29:07] <03mike> Actually when ever i was supposed to connect it to pc. I used to connect it and restart device (while its connected to pc so it would boot in usb mode) [14:29:30] <03mike> I connected it to pc and kept pressing power button ever few seconds [14:29:48] <03mike> And the windows did a plud in sound [14:30:54] <03mike> Then it mounted the drive in. And added its original files. The main logo is gone but device works now [14:31:37] <03mike> Now device is in its original shape [14:32:53] <03mike> I made a mistake last night. I formated it and disconnected it letting it turn off fully. :D [14:48:22] *** Joins: xenos1984 (~xenos1984@74d2-56b9-8dc3-291b-8780-87e7-07d0-2001.dyn.estpak.ee) [14:48:22] *** ChanServ sets mode: +v xenos1984 [14:50:34] <03mike> Kazer [14:53:13] *** Quits: xenos1984 (~xenos1984@74d2-56b9-8dc3-291b-8780-87e7-07d0-2001.dyn.estpak.ee) (Ping timeout: 276 seconds) [14:54:13] *** Joins: xenos1984 (~xenos1984@169-100-191-90.dyn.estpak.ee) [14:54:13] *** ChanServ sets mode: +v xenos1984 [14:56:42] kazer: do you know if you also have a docking port? [14:57:25] <05jkoan> BTW Kazer, finished the PC yesterday :) [15:09:16] mike: nice. we can resume troubleshooting if you want, or we can wait until i get my device. up to you [15:09:45] jkoan: i don't believe that this one has a docking port. But it's possible that it has the pins on the PCB like on your device [15:10:04] so, does that new PC compiles code much faster? :) [15:10:45] Probably yes, it's a 6 core cpu (ryzen 2600) but I haven't tested do far [15:10:48] *so [15:11:30] Kazer, mike: what's the current problem? Gltt? [15:19:19] current problem is that this device uses a different gps hardware than the one we tested so far. /proc/barcelona/gpstype returns 130 which is currently unhandled by our gps startup script [15:19:39] it's probably just a matter of testing if it needs different parameters than 128 or 129 [15:29:04] <05jkoan> 130 sounds familiar to me, but I can't test in the coming days [15:32:52] no worries [16:35:15] <03mike> We can continue if you want :) [16:35:36] <03mike> Jkoan same problem as before [16:35:58] <03mike> The map wouldnt follow devixe [16:36:33] <03mike> Then did some changes and the ttconsole stopped working [16:36:43] <03mike> It would not open [16:50:03] so mike did you get ttconsole to work again? [16:51:22] <03mike> Not yet. I just restored it to its original firmware [16:54:10] ok. so next step is probably to reinstall navitom and get a ttconsole session so that we can troubleshoot [16:55:00] <03mike> Ok [17:02:41] <03mike> Console doesnt work [17:07:54] same as yesterday? [17:08:00] blinks but doesn't start? [17:09:12] <03mike> Yes [17:09:24] <03mike> Is terminal different from console? [17:17:14] <03mike> I guess ttconsole never worked. I opened terminal and thought it was the console [17:45:31] ha! what do you call terminal? [17:46:50] <03mike> https://cdn.discordapp.com/attachments/500190750085087235/573928464407592971/20190503_224610.jpg [17:46:53] <03mike> That [19:23:52] oh that should work [19:25:36] let's try this : gltt -baud 115200 -periodic 500 -fix_start normal -rftype HH_4L_INT_ON [19:28:11] <03mike> Type that? [19:33:43] <03mike> https://cdn.discordapp.com/attachments/500190750085087235/573955364819697664/20190504_003226.jpg [19:44:23] ok we just need to find where your gltt binary is stored [19:44:27] try "mount" [19:45:48] <03mike> https://cdn.discordapp.com/attachments/500190750085087235/573958405371461632/20190504_004514.jpg [19:48:06] ok so probably /mnt/sdcard/bin/gltt -baud 115200 -periodic 500 -fix_start normal -rftype HH_4L_INT_ON [19:51:03] <03mike> https://cdn.discordapp.com/attachments/500190750085087235/573959730167545856/20190504_005030.jpg [19:53:05] <03mike> https://cdn.discordapp.com/attachments/500190750085087235/573960237640450058/20190504_005229.jpg [19:58:18] <03mike> That didnt give any error [20:59:48] ok that's probably a good sign :) [20:59:53] ps -ef|grep gltt [20:59:57] to check if it's still running [22:07:19] *** Quits: xenos1984 (~xenos1984@169-100-191-90.dyn.estpak.ee) (Quit: Leaving.) [23:50:34] *** Joins: Navit1 (~Navit@ec2-34-214-224-248.us-west-2.compute.amazonaws.com) [23:50:34] *** ChanServ sets mode: +v Navit1 [23:51:04] *** Quits: Navit (~Navit@ec2-34-214-224-248.us-west-2.compute.amazonaws.com) (Remote host closed the connection) [23:51:27] *** Navit1 is now known as Navit