20.xhtml 19 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211
  1. <?xml version="1.0" encoding="utf-8"?>
  2. <!--
  3. h t t :: / / t /
  4. h t t :: // // t //
  5. h ttttt ttttt ppppp sssss // // y y sssss ttttt //
  6. hhhh t t p p s // // y y s t //
  7. h hh t t ppppp sssss // // yyyyy sssss t //
  8. h h t t p s :: / / y .. s t .. /
  9. h h t t p sssss :: / / yyyyy .. sssss t .. /
  10. <https://y.st./>
  11. Copyright © 2016 Alex Yst <mailto:copyright@y.st>
  12. This program is free software: you can redistribute it and/or modify
  13. it under the terms of the GNU General Public License as published by
  14. the Free Software Foundation, either version 3 of the License, or
  15. (at your option) any later version.
  16. This program is distributed in the hope that it will be useful,
  17. but WITHOUT ANY WARRANTY; without even the implied warranty of
  18. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
  19. GNU General Public License for more details.
  20. You should have received a copy of the GNU General Public License
  21. along with this program. If not, see <https://www.gnu.org./licenses/>.
  22. -->
  23. <!DOCTYPE html>
  24. <html xmlns="http://www.w3.org/1999/xhtml">
  25. <head>
  26. <base href="https://y.st./en/weblog/2016/08-August/20.xhtml" />
  27. <title>Not a good day &lt;https://y.st./en/weblog/2016/08-August/20.xhtml&gt;</title>
  28. <link rel="icon" type="image/png" href="/link/CC_BY-SA_4.0/y.st./icon.png" />
  29. <link rel="stylesheet" type="text/css" href="/link/basic.css" />
  30. <link rel="stylesheet" type="text/css" href="/link/site-specific.css" />
  31. <script type="text/javascript" src="/script/javascript.js" />
  32. <meta name="viewport" content="width=device-width" />
  33. </head>
  34. <body>
  35. <nav>
  36. <p>
  37. <a href="/en/">Home</a> |
  38. <a href="/en/a/about.xhtml">About</a> |
  39. <a href="/en/a/contact.xhtml">Contact</a> |
  40. <a href="/a/canary.txt">Canary</a> |
  41. <a href="/en/URI_research/"><abbr title="Uniform Resource Identifier">URI</abbr> research</a> |
  42. <a href="/en/opinion/">Opinions</a> |
  43. <a href="/en/coursework/">Coursework</a> |
  44. <a href="/en/law/">Law</a> |
  45. <a href="/en/a/links.xhtml">Links</a> |
  46. <a href="/en/weblog/2016/08-August/20.xhtml.asc">{this page}.asc</a>
  47. </p>
  48. <hr/>
  49. <p>
  50. Weblog index:
  51. <a href="/en/weblog/"><abbr title="American Standard Code for Information Interchange">ASCII</abbr> calendars</a> |
  52. <a href="/en/weblog/index_ol_ascending.xhtml">Ascending list</a> |
  53. <a href="/en/weblog/index_ol_descending.xhtml">Descending list</a>
  54. </p>
  55. <hr/>
  56. <p>
  57. Jump to entry:
  58. <a href="/en/weblog/2015/03-March/07.xhtml">&lt;&lt;First</a>
  59. <a rel="prev" href="/en/weblog/2016/08-August/19.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2016/08-August/21.xhtml">Next&gt;</a>
  61. <a href="/en/weblog/latest.xhtml">Latest&gt;&gt;</a>
  62. </p>
  63. <hr/>
  64. </nav>
  65. <header>
  66. <h1>Not a good day</h1>
  67. <p>Day 00532: Saturday, 2016 August 20</p>
  68. </header>
  69. <p>
  70. Google locked up my new Google account today.
  71. They won&apos;t allow me to log into it from any device, instead insisting that I go through recovery options.
  72. However, the only recovery option (despite the fact that I have a recovery email address set up) is to go through a form that submits to what I believe to be human reviewers.
  73. This form asked for the month and year that I created the account and the month and year that I started using Google&apos;s email service on that account, both which of course were this month of this year.
  74. They also asked for who my frequently-contacted people were (the only people that I&apos;d contacted through the account were myself (for testing) and my mother) and the date of the last time that I&apos;d successfully logged into the account, which was yesterday.
  75. They keep rejecting my attempts to recover the account though.
  76. I decided just to ignore the account and create a new one, as there wasn&apos;t anything else that I could do.
  77. However, Google wouldn&apos;t allow me to create the new account.
  78. As usual, Google demanded a telephone number for &quot;verification&quot; (read: Google demanded a telephone number to be nosy and over-controlling), so I provided the only number that I have.
  79. Google rejected this number, saying that it&apos;d been used to &quot;verify&quot; too many accounts already.
  80. So I guess that two accounts is the limit, (The first account that I &quot;verified&quot; with that number, I later deleted that same day).
  81. Google is such a pain.
  82. Why did they lock up the account in the first place?
  83. </p>
  84. <p>
  85. While trying to get Google to actually function, which I never managed to do,my Wi-Fi card gave out on me.
  86. That was frustrating.
  87. I needed to monitor my temporary inbox for letters from Google&apos;s team to get my account back, but I couldn&apos;t reach the Internet without my mobile.
  88. Rebooting the machine a few times didn&apos;t restore functionality to the Wi-Fi card, but with some help from someone on <a href="ircs://irc.oftc.net.:9967/%23Debian">#Debian</a>, I finally found a working solution.
  89. They said to turn off the machine and take the battery entirely out for a minute, then put it back in and try again.
  90. I never did figure out why my Wi-Fi card went out on me in the first place, but the power in the battery must have caused some internal state of the machine to not fully reset, causing the Wi-Fi card issues to be persistent.
  91. </p>
  92. <p>
  93. FedEx sent me an alert that they planned to deliver my FreedomPop <abbr title="subscriber identity module">SIM</abbr> card &quot;tomorrow&quot;, on 2016-08-20.
  94. However, <strong>*today*</strong> is 2016-08-20! I&apos;d say that the alert must have come from another time zone, but FedEx is a United States-based company and the alert happened too late in the day to have been correct in another time zone of this country.
  95. Later, I received another letter from them saying that the card had been delivered, so I went outside to check; it wasn&apos;t there.
  96. I went to the tracking page (FedEx, unlike the United States Postal Service, does <strong>*not*</strong> maliciously discriminate against <abbr title="The Onion Router">Tor</abbr> users), and found a surprise there.
  97. It said that the package had been delivered by the <abbr title="United States Postal Service">USPS</abbr>! Why did the <abbr title="United States Postal Service">USPS</abbr> deliver a FedEx shipment? Alternatively, how was a <abbr title="United States Postal Service">USPS</abbr> shipment tracked on the FedEx website? I walked down to the mailbox to investigate.
  98. Sure enough, the <abbr title="subscriber identity module">SIM</abbr> card had arrived, as did the GT-i9100, both a bit ahead of schedule.
  99. </p>
  100. <p>
  101. With the <abbr title="subscriber identity module">SIM</abbr> card in hand, I now looked into canceling my FreedomPop service.
  102. I tried to cancel the <abbr title="subscriber identity module">SIM</abbr> card order as soon as I found out that their service wasn&apos;t as advertised, but FreedomPop support took so long to get to me that they&apos;d already sent the card.
  103. First, I turned off the paid plan for the account, which FreedomPop puts you on (with a one-month gratis trial) by default.
  104. They probably hope that you&apos;ll forget to turn it off in time and end up having to pay for it; they don&apos;t give you the option to opt out of the trial when buying the <abbr title="subscriber identity module">SIM</abbr> card or allow you to automatically revert to the gratis plan when the trial is over.
  105. It&apos;s a bit sneaky.
  106. Next, I tried to disable automatic top-ups, which cause FreedomPop to charge you as soon as you get near the end of your data limit, then use that money to pay for any extra data that you might or might not actually use.
  107. They should instead simply cut off your data when you hit your limit, but they&apos;d rather do things the underhanded way.
  108. However, they charge a five-dollar fee for turning automatic account top-ups off! As the <abbr title="subscriber identity module">SIM</abbr> card won&apos;t be in a device anyway, I just left it alone instead of paying the fee.
  109. I can&apos;t go over if the <abbr title="subscriber identity module">SIM</abbr> card isn&apos;t powered on and connected to a radio.
  110. Next, I tried to cancel my plan and deactivate the <abbr title="subscriber identity module">SIM</abbr> card.
  111. I couldn&apos;t find a way to directly do that though.
  112. I can deactivate the account itself, but if I do that, there&apos;s a $20 <abbr title="United States Dollars">USD</abbr> fee if I ever want to come back to FreedomPop.
  113. If FreedomPop cleans up their service, I might one day want to come back, so I decided not to deactivate the whole account.
  114. I found some information that hints that if I don&apos;t use the <abbr title="subscriber identity module">SIM</abbr> card at all for about a month, they might <a href="https://support.freedompop.com/app/answers/detail/a_id/2046/kw/deactivate">deactivate the <abbr title="subscriber identity module">SIM</abbr> card themselves</a> though, so I guess that I&apos;ll just wait for that.
  115. </p>
  116. <p>
  117. The first thing that I did with the GT-i9100 was check behind the battery for the model number.
  118. Would it be another GT-I727? No! The model number was clearly GT-i9100 as ordered, or at least it seemed that way at first.
  119. As the device was second hand, I wanted to be sure that it would actually connect to the towers, so I moved my <abbr title="subscriber identity module">SIM</abbr> card to the device and booted it.
  120. Much to my confusion, the boot screen informed me that this wasn&apos;t a GT-i9100, but a GT-i9100G.
  121. THat is a GT-i9100G? Is it the same thing as a GT-i9100? Will it run the necessary operating system? As it turns out, no, no it is not and no it will not.
  122. THe <a href="https://en.wikipedia.org./wiki/Samsung_Galaxy_S_II#Galaxy_S_II_-_Model_GT-I9100G">GT-i9100G</a> has a different chip set as the <a href="https://en.wikipedia.org./wiki/Samsung_Galaxy_S_II#Model:_GT-i9100">GT-i9100</a> and cannot run the same system images.
  123. It sounds like this version of the device might even be a bit easier to develop on in freedom than the GT-i9100, but as the Replicant team is under-staffed and under-funded, this hasn&apos;t happened yet.
  124. Why do these models have confusingly similar model numbers though? The fact that the product was incorrectly labeled as a GT-i9100 might have been an honest mistake even, caused by Samsung&apos;s similar model numbers and the incorrect model number being listed behind the battery.
  125. The similar model numbers don&apos;t end there though.
  126. It seems that the <a href="https://en.wikipedia.org./wiki/Samsung_Galaxy_S_II#Bell_Mobility_-_Models_GT-I9100M_and_SGH-I757M">GT-i9100M</a> might in fact have identical hardware as the GT-i9100, differeing only in default software.
  127. It&apos;s said that it can run system images designed for the GT-i9100 because of the identical hardware.
  128. Likewise, the <a href="https://en.wikipedia.org./wiki/Samsung_Galaxy_S_II#Europe_-_Model_GT-I9100P">GT-i9100P</a> is supposed to be nearly identical to the GT-i9100, differing only in that it has <strong>*extra*</strong> hardware.
  129. Supposedly, this device can run system images meant for the GT-i9100 as well, though as these images aren&apos;t designed to use the extra hardware, that extra hardware becomes unusable, basically turning it into a regular GT-i9100.
  130. We also have the <a href="https://en.wikipedia.org./wiki/Samsung_Galaxy_S_II#Telstra_and_Vodafone_Australia_-_Models_GT-I9100T">GT-i9100T</a>.
  131. Wikipedia doesn&apos;t have much information on this device, staring that it&apos;s &quot;functionally equivalent&quot; to the GT-i9100.
  132. WHat does that mean? Does it mean that it can run the same system images? If not, that&apos;s hardly equivalent, but if so, it should be stated as such.
  133. Lastly, there might even be a <a href="https://redmine.replicant.us/boards/3/topics/12009">GT-i9100I</a>, though Wikipedia doesn&apos;t seem to have any information on it, assuming that it really exists.
  134. I&apos;ve asked if the GT-i9100M can really <a href="https://redmine.replicant.us/boards/3/topics/13509">run the Replicant system image</a> just to be sure, but I&apos;m not sure that I&apos;ll receive a response, as it&apos;s not one of the most popular mobile systems and people might not have tried it.
  135. </p>
  136. <p>
  137. I reported the device to the seller as not being as listed, requesting a refund.
  138. They responded telling me that my request will be granted and to send it back.
  139. I won&apos;t be able to do that tonight, as the post office has already closed, or tomorrow, as they won&apos;t be open that day.
  140. I&apos;ll try to get it sent on Monday.
  141. Unlike the last seller, this one didn&apos;t supply postage, but did say that they&apos;d refund any postage fees that I paid.
  142. Furthermore, they said that if the post office won&apos;t allow me to send the battery, to remove the battery and send back the device.
  143. I don&apos;t anticipate such a problem, but I suppose it&apos;s always good to walk in prepared.
  144. </p>
  145. <p>
  146. I found a new mobile listed online as being a GT-i9100, though in the information about the device&apos;s condition, it says that it&apos;s really the GT-i9100M.
  147. Assuming that Wikipedia is correct, a device of either model should suffice, so I&apos;ve ordered it.
  148. Unfortunately, with each try, the device gets more expensive.
  149. This time, it cost me $100 <abbr title="United States Dollars">USD</abbr>.
  150. Hopefully this time, I&apos;ll get what I actually paid for.
  151. If not, I might give up and choose an easier device to get ahold of.
  152. Last time, I had less idea of what I was doing and I still managed to get a <strong>*GT-i9300*</strong> on the first try.
  153. That might be a good device to try to reacquire, though it will also be more expensive and potentially less functional.
  154. The GT-i9100 is stated to be the most featureful Replicant device.
  155. </p>
  156. <p>
  157. About two days overdue to get started, I dived into this week&apos;s <a href="http://www.uopeople.edu/">University of the People</a> orientation material.
  158. Trying to make sure that my late start didn&apos;t cause any issues later in the week, I made sure to finish today as well.
  159. Besides, I needed something to do while I waited for Google to respond to my attempts to get back into my account.
  160. Unfortunately, it seems that the school library is hidden behind a CloudFlare <abbr title="Completely Automated Public Turing test to tell Computers and Humans Apart">CAPTCHA</abbr> wall, so I suppose once school starts, that&apos;ll be something that I need to complain about, at least once per course, but probably not more than on a weekly basis.
  161. It would be nice if they got that fixed, though I need to make sure not to be annoying about it, so I&apos;ll probably lean closer to the once-per-course frequency.
  162. The school also mentioned a school-specific social network that they have for students, faculty, and former students, though they didn&apos;t at all mention where it was or how to find it.
  163. I wrote to my program advisor to ask about it, though admittedly, half the reason that I asked was just to make contact and show that I&apos;m really here and did receive their initial email to me.
  164. The assignment for this week was to mark a few dates on whatever calendar system we each use.
  165. Unfortunately, my calendar is down when my server&apos;s down, so I won&apos;t be able to do that until we once more have a home Internet connection.
  166. I went to their list of dates to copy them into a plain text file for now, but their dates are displayed in the form of an image.
  167. Really? What is the point of that? I&apos;ve saved the image for now.
  168. I&apos;ll type the dates into the calendar when can.
  169. In particular, the school wanted me to note the following dates:
  170. </p>
  171. <ol>
  172. <li value="0">The first day of the term</li>
  173. <li value="1">The Course Drop deadline</li>
  174. <li value="2">The Course Withdrawal deadline</li>
  175. <li value="3">The beginning and end dates for registration</li>
  176. <li value="4">When final exams begin</li>
  177. <li value="5">When final exams end</li>
  178. </ol>
  179. <p>
  180. Looking for a Google-free solution to my <abbr title="Short Message Service">SMS</abbr> problem, I tried out a service called <a href="https://textfree.us/">TextFree</a>.
  181. They&apos;re Web-based, so they lack the email integration that Google Voice has, but if I could get their system to work, it&apos;d be better than nothing.
  182. During registration, they asked me for an email address but not a telephone number, but then after verifying my email address, they blindsided me by demanding that I verify the account again by verify a telephone number, a Google account, or a Facebook account! That was not happening.
  183. I tried reloading the page though, and that seemed to work.
  184. My log in credentials work anyway, though I can&apos;t seem to actually send <abbr title="Short Message Service">SMS</abbr> messages.
  185. After submitting one, the page just sort of hangs and the message doesn&apos;t get through.
  186. Furthermore, every time that I log in, my <abbr title="Short Message Service">SMS</abbr> number changes.
  187. That won&apos;t at all work for conversing with my mother, which is the only thing that I need <abbr title="Short Message Service">SMS</abbr> messaging for.
  188. Maybe I can find another solution elsewhere.
  189. </p>
  190. <hr/>
  191. <p>
  192. Copyright © 2016 Alex Yst;
  193. You may modify and/or redistribute this document under the terms of the <a rel="license" href="/license/gpl-3.0-standalone.xhtml"><abbr title="GNU&apos;s Not Unix">GNU</abbr> <abbr title="General Public License version Three or later">GPLv3+</abbr></a>.
  194. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  195. My address is in the source comments near the top of this document.
  196. This license also applies to embedded content such as images.
  197. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  198. </p>
  199. <p>
  200. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  201. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F08-August%2F20.xhtml"><abbr title="Extensible Hypertext Markup Language">XHTML</abbr> 5.1</a> specification and uses style sheets that conform to the <a href="http://jigsaw.w3.org./css-validator/validator?uri=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F08-August%2F20.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  202. </p>
  203. </body>
  204. </html>