<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>solution &#8211; TOMASZ &quot;CeDeROM&quot; CEDRO (SQ7MHZ)</title>
	<atom:link href="https://www.tomek.cedro.info/tag/solution/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.tomek.cedro.info</link>
	<description></description>
	<lastBuildDate>Wed, 11 Aug 2021 14:21:18 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>BSD Chromium Audio/Mic</title>
		<link>https://www.tomek.cedro.info/bsd-chromium-audio-mic/</link>
		
		<dc:creator><![CDATA[CeDeROM]]></dc:creator>
		<pubDate>Mon, 09 Aug 2021 17:45:41 +0000</pubDate>
				<category><![CDATA[computers]]></category>
		<category><![CDATA[FAQ]]></category>
		<category><![CDATA[BSD]]></category>
		<category><![CDATA[chromium]]></category>
		<category><![CDATA[freebsd]]></category>
		<category><![CDATA[microphone]]></category>
		<category><![CDATA[problem]]></category>
		<category><![CDATA[sndio]]></category>
		<category><![CDATA[sndiod]]></category>
		<category><![CDATA[solution]]></category>
		<guid isPermaLink="false">https://www.tomek.cedro.info/?p=1871</guid>

					<description><![CDATA[If you encounter a problem with microphone in Chromium on FreeBSD (and other *BSD), this is because it uses sndio audio backend and probably default microphone is not the one you want to use. In my case /dev/dsp0 is the HDMI input/output thus no audio input. There is no need to start system wide sndiod. [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>Google Hangouts related feedback</title>
		<link>https://www.tomek.cedro.info/google-hangouts-related-feedback/</link>
		
		<dc:creator><![CDATA[CeDeROM]]></dc:creator>
		<pubDate>Wed, 10 Aug 2016 16:09:01 +0000</pubDate>
				<category><![CDATA[bugs]]></category>
		<category><![CDATA[computers]]></category>
		<category><![CDATA[electronics]]></category>
		<category><![CDATA[mobile]]></category>
		<category><![CDATA[android]]></category>
		<category><![CDATA[bug]]></category>
		<category><![CDATA[chat]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[hangouts]]></category>
		<category><![CDATA[idea]]></category>
		<category><![CDATA[lg]]></category>
		<category><![CDATA[smart]]></category>
		<category><![CDATA[solution]]></category>
		<category><![CDATA[talk]]></category>
		<category><![CDATA[video]]></category>
		<category><![CDATA[voice]]></category>
		<category><![CDATA[wine]]></category>
		<guid isPermaLink="false">http://www.tomek.cedro.info/?p=1207</guid>

					<description><![CDATA[I have just reported several issues and ideas related with this nice Google Hangouts Android application: The name Hangouts is not popular and hard to remember. Abandoning &#8220;Google Chat&#8221; or &#8220;Google Talk&#8221; was a bad idea. People tend to remember short names and popular words such as &#8220;Skype&#8221; or &#8220;Viber&#8221;. This may be funny but [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>Google Android Nexus Device Un-Brick</title>
		<link>https://www.tomek.cedro.info/google-android-nexus-device-un-brick/</link>
					<comments>https://www.tomek.cedro.info/google-android-nexus-device-un-brick/#comments</comments>
		
		<dc:creator><![CDATA[CeDeROM]]></dc:creator>
		<pubDate>Thu, 21 Jan 2016 13:08:06 +0000</pubDate>
				<category><![CDATA[computers]]></category>
		<category><![CDATA[electronics]]></category>
		<category><![CDATA[FAQ]]></category>
		<category><![CDATA[modifications]]></category>
		<category><![CDATA[science]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[android]]></category>
		<category><![CDATA[bootloader]]></category>
		<category><![CDATA[brick]]></category>
		<category><![CDATA[debrick]]></category>
		<category><![CDATA[firmware]]></category>
		<category><![CDATA[fix]]></category>
		<category><![CDATA[flash]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[logo]]></category>
		<category><![CDATA[loop]]></category>
		<category><![CDATA[nexus]]></category>
		<category><![CDATA[problem]]></category>
		<category><![CDATA[rom]]></category>
		<category><![CDATA[solution]]></category>
		<category><![CDATA[unbrick]]></category>
		<guid isPermaLink="false">http://www.tomek.cedro.info/?p=1149</guid>

					<description><![CDATA[If you happen to brick your Google Nexus device you can always use stock ROM images [1] to revert it to a default and operational state. Package contains not only OS but also bootloader and radio firmware images! I have bricked my device by installing custom firmware that messed partitions layout inside a Flash Memory. [&#8230;]]]></description>
		
					<wfw:commentRss>https://www.tomek.cedro.info/google-android-nexus-device-un-brick/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
	</channel>
</rss>
