I AM your target demographic. Listen up.
People actually buy from eBay? Gross.
Sick of sifting through hundreds of eBay results in Google Shopping? Append -site:ebay.com to your search.
There you go, no more questionable eBay garbage when you’re trying to shop from reputable merchants.
Thanks jscher2000 for the tip!
Of course you want to return to TouchWiz to fix a problem. Ha, no you don’t.
Note: if you’re not running a custom ROM – i.e. you’re running stock TouchWiz – and need to do this, see Phase 4 only. You’ll need to be rooted.
If you’re running a custom ROM on your S5 and GPS can’t get a fix despite rebooting, battery pulling, flashing new builds, and using all of GPS Status & Toolbox‘s tricks, chances are you’ll need to do rebuild the GPS NVRAM. Here’s how.
Instructions (which assume you use TWRP) in Phase 9 here.
If you don’t already have one of those, here’s how to get one. If you’re setting up a rooted TouchWiz ROM for the 1st time then you don’t have to restore anything because it’ll already be running, so you can proceed to the next phase.
Otherwise:
Same process as Phase 2.
Same process as Phase 3, but with the custom ROM backup instead.
GPS should be back to working now. I have no idea what causes this problem, but so far this is the most involved custom ROM-related fix I’ve had to do.
If you’re reading this, you’re probably trying to solve a frustrating problem. Relax, I’m here to help.
The following are prerequisites for this to work:
Steps:
And that’s it. This will give you a fully stock, rooted Lollipop ROM you can boot right into.
If you run custom ROMs, the stock ROM is pretty useful to keep handy as some troubleshooting methods (especially advanced ones involving the baseband) work on it only. As such, it’s a pretty good idea to back it up so you can restore it as needed. Instructions found in Phase 9 here.
Microsoft won’t tell you how; they’d rather you buy a new headset.
Note: I can personally verify this works for the Xbox Wireless Controllers with built-in 3.5 mm stereo headset jack only. I don’t know how it works with other 1st party controllers, though the post below indicates that it should.
Basically you need a 2.5 mm TRS female to 3.5 mm TRRS male adapter. The headeset microphone does NOT work with regular 2.5 mm female to 3.5 mm male adapters.
Per thornierbird on Reddit:
More background information on headset compatibility with the Xbox One, including different 3.5 mm specs, is available from Xbox Support.
Why write complete documentation when you can just confuse users instead?
If you reboot your PC after a Linux Mint version update (e.g. 17.3 to 18) and find things to be a bit wonky, you’ll need to power cycle the PC. The reason for this is there may have been a kernel version update, and Linux Mint always boots into the latest kernel installed. However, it does this only if the PC is power cycled. If it isn’t, the new Linux Mint build will boot using the old kernel, which causes the problems you may be experiencing.
You’d think this would be in the official version update instructions, but this is Linux, and so caveats are left to unlucky users to discover for themselves.
It’s easier and less complicated than it sounds.
Radio logcats are useful for troubleshooting network connectivity, especially on modded (rooted &/or custom ROM) devices. If you’re reporting such an issue it’s often useful to provide the radio logcat in addition to the regular logcat to help the developer resolve the problem.
There are 3 ways to get a radio logcat:
This is the easiest method.
logcat -b radio > /sdcard/radio_logcat.txt – This dumps the logcat file radio_logcat.txt at the root of your SD card. logcat -b radio works too, but I have no idea where it puts the file and have never tried it myself.While I know this method exists, I’ve never used it. The command to enter is adb logcat -b radio, and adb logcat -b radio > /sdcard/radio_logcat.txt probably works too.
Alternative title: How to get FlashFire working on CyanogenMod 13
The best app for this is SELinuxModeChanger (SELMC). You can sideload it, but it’s best to get it via the F-Droid marketplace app.
SELMC enables use of apps such as FlashFire – which needs either permissive SELinux or SuperSU – on CyanogenMod (which is incompatible with SuperSU).
Don’t forget to set SELinux back to Enforcing after you’re done using Permissive, as it’s a really important part of Android security.
The above worked on a Samsung SM-G900V running the kltevzw build of CyanogenMod 13.
Google’s dogmatic view of how people (should) communicate puts Allo firmly on the path to failure.
Android Central asks:
What if there was an app that had the simple appeal of Apple’s iMessage, but was available for every person using an iPhone or an Android?
My response:
Rooted or got an unlocked bootloader? You’re good to go.
NOTE: If you run CyanogenMod 13+ Nightly, you probably don’t need to do this.
Although Google has done a great job maintaining some Android features as standalone apps, fonts – which contain emoji – are still delivered via OTA updates. Android’s well documented slow (carrier device) OTA update rollout process is frustrating for those who want to use the latest emoji, ergo here’s how to do the latter.
The following process worked on a rooted Verizon Samsung Galaxy S5 (SM-G900V) running CyanogenMod 13 (Android 6.0.1) and TWRP recovery, but it should work on any Android 6.0+ device. Since the flashing process occurs entirely in the recovery environment, your device may not have to be rooted for it to work.*
This post uses and recommends the open source, very actively developed, and beautifully minimalist EmojiOne emoji, but can probably be used for other emoji sets too.
And that’s it! You should know have the custom emoji of your choosing installed to your device.
For convenience, I’ve uploaded a flashable .zip containing the latest EmojiOne .ttf here. I’ll try to keep it updated as new versions (RSS feed) come out.
Want these emoji on Windows? Instructions here.
*An alternative method of updating emoji is to manually replace the corresponding system file. However, this requires both root access and manually setting the correct permissions for the new .ttf file, and the device still has to be rebooted afterwards. Flashing a .zip as described here is far simpler and there’s less that can go wrong.
If only it were this easy in Android.
Like Android, Windows emoji are updated along with the OS. However, installing new emoji on Windows is much easier because Windows provides a GUI method for installing fonts within the OS itself. Here’s how to do it:
And that’s literally it. I used the above method on Windows 10; your mileage may vary on other versions.
Want those emoji on Android? Do this.
Unfortunately the article’s premise works only if Allo ships pre-installed on devices. Even if Google does that for Android, Apple would never allow it for iOS. This would leave Allo with the same need for manual installation as other 3rd party messengers, except those other messengers are already far more successful.
There’s an existing case of this: Hangouts. Hangouts was preinstalled on Android devices and worked automagically via Android’s Gmail account prerequisite. Yet it never took off on any other platform (except perhaps the desktop) and isn’t even in the top 5 messaging apps.
Facebook handled this challenge in a completely different manner: they simply opened up Facebook Messenger to use by anyone with a phone number. BOOM: Messenger is now the world’s #2 messaging app despite needing manual installation on all platforms.
I think it’s hilarious how every Android (fan)blog conveniently ignores that iMessage also has a desktop component that Allo doesn’t. So does Facebook Messenger and Whatsapp, which are available on all platforms, thus enabling them to span form factors.
Another mistake here is the extreme iMessage tunnelvision. iMessage may be big in the US where iOS rules, but Android rules the rest of the world. If Allo is indeed the anti-iMessage, that would make it a narrow and incomplete solution that addresses only one market.
Even Microsoft haven’t been as disingenuos as Google. Say what you will about Skype, but at least Microsoft haven’t pushed a completely incompatible service that no one has any real reason to use.
The market failure of Google Talk, Google Voice (as a messaging solution), and Hangouts shows that Google still doesn’t fundamentally get how people actually communicate. They think they can sell every feature/application solely on ideological purism. That doesn’t work in the real world.