csh
/
y.st.
派生自 y.st./y.st.


			
				
					
						
						
							123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151
							<?xml version="1.0" encoding="utf-8"?>
<!--
                                                                                     
 h       t     t                ::       /     /                     t             / 
 h       t     t                ::      //    //                     t            // 
 h     ttttt ttttt ppppp sssss         //    //  y   y       sssss ttttt         //  
 hhhh    t     t   p   p s            //    //   y   y       s       t          //   
 h  hh   t     t   ppppp sssss       //    //    yyyyy       sssss   t         //    
 h   h   t     t   p         s  ::   /     /         y  ..       s   t    ..   /     
 h   h   t     t   p     sssss  ::   /     /     yyyyy  ..   sssss   t    ..   /     
                                                                                     
	<https://y.st./>
	Copyright © 2016 Alex Yst <mailto:copyright@y.st>

	This program is free software: you can redistribute it and/or modify
	it under the terms of the GNU General Public License as published by
	the Free Software Foundation, either version 3 of the License, or
	(at your option) any later version.

	This program is distributed in the hope that it will be useful,
	but WITHOUT ANY WARRANTY; without even the implied warranty of
	MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
	GNU General Public License for more details.

	You should have received a copy of the GNU General Public License
	along with this program. If not, see <https://www.gnu.org./licenses/>.
-->
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
		<base href="https://y.st./en/weblog/2016/10-October/11.xhtml" />
		<title>Something is seriously wrong with my GT-i9100M. &lt;https://y.st./en/weblog/2016/10-October/11.xhtml&gt;</title>
		<link rel="icon" type="image/png" href="/link/CC_BY-SA_4.0/y.st./icon.png" />
		<link rel="stylesheet" type="text/css" href="/link/basic.css" />
		<link rel="stylesheet" type="text/css" href="/link/site-specific.css" />
		<script type="text/javascript" src="/script/javascript.js" />
		<meta name="viewport" content="width=device-width" />
	</head>
	<body>
		<nav>
			<p>
				<a href="/en/">Home</a> |
				<a href="/en/a/about.xhtml">About</a> |
				<a href="/en/a/contact.xhtml">Contact</a> |
				<a href="/a/canary.txt">Canary</a> |
				<a href="/en/URI_research/"><abbr title="Uniform Resource Identifier">URI</abbr> research</a> |
				<a href="/en/opinion/">Opinions</a> |
				<a href="/en/coursework/">Coursework</a> |
				<a href="/en/law/">Law</a> |
				<a href="/en/a/links.xhtml">Links</a> |
				<a href="/en/weblog/2016/10-October/11.xhtml.asc">{this page}.asc</a>
			</p>
			<hr/>
			<p>
				Weblog index:
				<a href="/en/weblog/"><abbr title="American Standard Code for Information Interchange">ASCII</abbr> calendars</a> |
				<a href="/en/weblog/index_ol_ascending.xhtml">Ascending list</a> |
				<a href="/en/weblog/index_ol_descending.xhtml">Descending list</a>
			</p>
			<hr/>
			<p>
				Jump to entry:
				<a href="/en/weblog/2015/03-March/07.xhtml">&lt;&lt;First</a>
				<a rel="prev" href="/en/weblog/2016/10-October/10.xhtml">&lt;Previous</a>
				<a rel="next" href="/en/weblog/2016/10-October/12.xhtml">Next&gt;</a>
				<a href="/en/weblog/latest.xhtml">Latest&gt;&gt;</a>
			</p>
			<hr/>
		</nav>
		<header>
			<h1>Something is seriously wrong with my GT-i9100M.</h1>
			<p>Day 00584: Tuesday, 2016 October 11</p>
		</header>
<img src="/img/CC_BY-SA_4.0/y.st./weblog/2016/10/11.jpg" alt="City plantlife" class="weblog-header-image" width="811" height="480" />
<p>
	Current countdowns:
</p>
<ul>
	<li>6 days until my old domain registrar can no longer counter my charge dispute</li>
	<li>12 months worth of weblog entries to correct misuse of the <abbr title="Extensible Hypertext Markup Language">XHTML</abbr> <code>&lt;q/&gt;</code> tag in</li>
	<li>249 scheme-specific <abbr title="Uniform Resource Identifier">URI</abbr>-parsing classes to write and add to <a href="https://git.vola7ileiax4ueow.onion/y.st./include.d">include.d</a></li>
</ul>
<p>
	Since I first started using my GT-i9100M, there have been small problems.
	At first, the problems were too small and I was too busy, so I didn&apos;t complain about them.
	I was far behind in my journal entries, so rather than griping about every little thing when I&apos;d write about my day, I kept to the more important aspects of the day and ignore my mobile.
	I also rwote some of the issues off as simply being because I was on a different device than when I was on my old GT-i9300.
	For example, the battery life on my GT-i9100M has been much worse than on my GT-i9300.
	The GT-i9300 needed to be charged before I went to bed, then topped up a bit after I awoke, but the simple fact is that it could stay powered on through the night without major drawbacks.
	However, the GT-i9100M needs to be turned off before I go to bed.
	Otherwise, the battery either completely drains, or if I&apos;m lucky, only reaches critically-low levels.
	Either way, it&apos;s not good for the battery and would cut down on how many years the battery will last, so I try to avoid allowing that to happen.
	Likewise, the GT-i9300 could stay charged throughout the day, but I&apos;ve had to purchase a portable charging pack for the GT-i9100M because it drains its battery so quickly.
	There have also been interface quirks that I&apos;ve chalked up to worse hardware support.
	It&apos;s been hard to get certain parts of the interface to respond correctly when tapped.
	In fact, I found that the way to make one of the interface components function, specifically the one that allows the setting of a data connection usage warning and data connection usage limit, doesn&apos;t function in the intuitive way at all, so I&apos;d been using it wrong.
	In other words, it wasn&apos;t something huge to get upset over, it was just something that I needed to relearn how to use.
	I&apos;ve also had an issue with the battery level indicator.
	It&apos;s unreliable, often reporting a drastically different battery level after rebooting.
	Sometimes the device will seem to gain power, other times it will lose it.
	It even sometimes slowly seems to gain power when not charging, and I think that it&apos;s seemed to lose power sometimes when it is charging.
	The lock screen can also be a pain, not always accepting my taps.
	However, last night, I ran into my first major issue with the device.
</p>
<p>
	Yesterday when I awoke, I found that my GT-i9100M&apos;s battery was completely dead.
	I figured that I must have forgotten to power the device off before I went to bed.
	Now, I no longer think that.
	Last night, when I tried to power off the device, instead of fully powering off, it instead <strong>*rebooted*</strong>.
	It must have done that the night before too, but I hadn&apos;t noticed right away.
	Today, no matter how many times I instructed the device to power down, it immediately powered back up.
	I could find no way around this short of removing the battery so that it was physically incapable of remaining powered on.
	I even tried reinstalling the operating system and wiping the cache, but to no avail.
	After trying to get the device to function all day, the thing went into a stupid reboot loop.
	Even when I wasn&apos;t trying to shut the bloody thing off, it kept restarting.
	I tried formatting the <code>/data</code> partition and reinstalling Replicant again, but the device still refused to power off.
	That did fix the reboot issue that was happening without any attempt to power the device off though.
	It caused a new issue though.
	When the device was plugged in to charge, it would now shut off, though only sometimes.
</p>
<p>
	It&apos;s been recommended to me that I dismantle the device.
	Supposedly, cleaning the contacts on the &quot;lock switch&quot; would potentially fix the problem.
	I think that this &quot;lock switch&quot; is the power button, but I don&apos;t have the correct screwdriver to open up the device.
	I was going to try to get ahold of one tomorrow, but a strange thing happened before my plans were set in stone.
	I&apos;ve taken to adding daily photographs to my journal over the past couple days, so I planned to do that tomorrow as well.
	I couldn&apos;t very well be taking photographs using CyanogenMod instead of Replicant, so I reinstalled Replicant.
	Now my device actually powers off! What in the world is going on!? I&apos;d already tried reinstalling Replicant three or four times before that and it had never fixed the problem ....
	However, now the device won&apos;t show me the internal storage over <abbr title="Media Transfer Protocol">MTP</abbr>.
	It will, however, show me the <abbr title="Secure Digital">SD</abbr> card&apos;s storage over <abbr title="Media Transfer Protocol">MTP</abbr> Something is seriously wrong with this device and I have no idea how to even begin debugging it.
</p>
<p>
	My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
</p>
		<hr/>
		<p>
			Copyright © 2016 Alex Yst;
			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>.
			If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
			My address is in the source comments near the top of this document.
			This license also applies to embedded content such as images.
			For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
		</p>
		<p>
			<abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
			This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F10-October%2F11.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%2F10-October%2F11.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
		</p>
	</body>
</html>