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.
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.
Follow these instructions to set Terminal Emulator to start with root permissions.
Start Terminal Emulator.
Enter 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.
Reproduce this issue you’re getting the logcat for.
When you’re done with Step 5, close Terminal Emulator.
Navigate to the root of your SD card to find the file there.
Using ADB on your PC
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.
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.
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.
*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.
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:
Donald Trump’s blowout win in the Hoosier State spurred talk of third-party runs and internal revolt, though in truth the shock has not worn off enough for them to think clearly. Cruz’s unlikely Indiana denouement gave frontrunner Trump a clear path to the GOP nomination, suggesting there is no way to stop him from amassing the 1,237 delegates needed for a first-ballot nomination. […] supporters like Wright have said they will try to be elected as delegates to the national convention in Cleveland in hopes of continuing the battle in an intramural arena. Early media reports that the tea-party movement might support an independent bid for the White House was just talk, movement leaders say, but they agree there is no enthusiasm for Trump among those who paved the way for the raft of “outsiders” who have ousted longtime establishment Republicans around the country. Despite their dismay that Cruz was unable to stem Trump’s rise, they would not support any sort of “parachute candidate” offered by Republican leaders as a last-ditch alternative at the national convention, Myers said. Cruz’s strategy of using tea party support to stay in the race as other candidates fell, gaining victories where he could, especially in states that awarded more delegates through caucuses and grass-roots selection processes, was going according to plan. Trump was able to capture that share of the voting public that was voting for a person or for ‘anti’ rhetoric, rather than for policy and principles. While Cruz unquestionably was the tea party favorite among the dozen-plus GOP candidates, opinion polls showed that for voters self-identifying as tea partiers, the preference was not so clear. Trump actively courted well-known tea party activists, continuing a dalliance that started when he was considering a run for the presidency in 2012. Cruz’s beliefs may mirror those of the tea party perfectly on an ideological basis, but Trump succeeded in tapping into frustration and disappointment at a gut level.
Develop its own chips. This may not solve the issue of backwards compatibility, but it would give Microsoft more freedom to work through the problem. Developing chips, however, is costly, time-consuming, and not something Microsoft has much expertise in.
The above article says the Surface Phone is in serious trouble because Intel killed its mobile x86 CPUs. At least one comment has suggested Microsoft should buy AMD to fix this. I disagree:
As much as I’d like MS to buy AMD, I don’t think that would solve *this particular problem.* AMD has no mobile x86 chips, & has been sucking at low power/high efficiency x86 for a while. Optimistically it would take 1 to 2 years to get an x86 SoC out of the AMD purchase, by which time UWP should (hopefully) be a sufficiently viable alternative to Win32 anyway.
A better option would be to push UWP and Centennial as hard as possible while maintaining Continuum and optimizing W10M for the Snapdragon 830.
That said, Surface tablets could use some AMD help. Adopting AMD’s APUs would fix the Surface line’s well documented GPU issues, at the expense of battery life (again, Intel rules at the latter).
Quick Charge users don’t have to worry about USB compatibility.
Benson Leung, a Google engineer, has been testing USB Type-C cables across the market to verify they meet the USB Type-C spec. He’s succeeded in getting some poor quality items off Amazon, which is very helpful to consumers.
In November he said Qualcomm’s Quick Charge (QC) technology couldn’t coexist with USB Type-C on the same connector because the latter violates the former’s spec:
While he’s certainly correct that QC violates the USB spec, the situation is lot more nuanced than that, and some of what he said is unfortunately incorrect.
I replied directly to that post, and some of the content of those replies follows.
Let’s get a few things straight about QC first, and then review Benson’s assertions using them:
Unlike the status quo for USB†, OEMs actually have to go through a UL (a worldwide saftey certification organization) certification process for QC, detailed in this Test & Certification Application (PDF). Per page 3 shown below, devices must maintain “the plug-and-play ease of use of USB connectors” to pass certification. This implies that there is no data transfer use case in which a QC device would behave any differently from a non-QC one and certainly none in which the QC device’s behavior would be unpredictable.
For all non-QC use cases, QC devices behave like any other normal USB device. Per page 3 above, QC certified devices must support “Conventional USB charging,” defined as “1A at 5V” (though I’m not sure how they get 15W from that. P = IV, so power should be 1A * 5V = 5W).
UPDATE: I contacted Qualcomm about this and got this useless reply:
Any information other than what is listed on our website (URL listed below for your reference) is Proprietary to Licensees.
Unfortunately we are unable to assist with your inquiry. However, we keep a list of compatible devices at Qualcomm.com/quickcharge. Hopefully this has the answer to your question.
Otherwise, we recommend you follow-up with a vendor that carries this product and seek their feedback on your technical questions.
Please note, Qualcomm is the technology provider, not a manufacturer of consumer products and therefore we are unable to answer your product specific question. We hope this direction helps.
Thank you for your inquiry,
Qualcomm Technologies Inc.
FWIW, in my experience QC (2.0) chargers slow charge non-QC devices and don’t (can’t?) fast charge them.
It follows from points 1 and 2 above that QC uses USB data lines for power only when connected directly to an A/C adapter, which has no use for a data line anyway.
While I can’t find any publicly available definition of the QC spec, it’s based on a patented technology called HVDCP (High Voltage Dedicated Charging Port). The “Dedicated Charging Port” detail name implies the tech works for ports that do nothing else but provide power and doesn’t work for data ports. Here’s the patent (which I haven’t read).
Fairly detailed implementation info can be found by searching “HVDCP” on Google. Here’s a very detailed product preview (PDF) by ON Semiconductor for their NCP4371 HVDCP controller.
Points 1 to 3 disprove Benson’s claim that the “Type-A port can’t be used to communicate to your PC at the same time you fast charge” via QC, as QC devices would fail the certification requirements if that were the case. In addition, implementing QC on a PC Type-A port would be disingenuous as it would disable data transfer for QC devices, thus killing most of the Type-A port’s functionality. No PC OEM in their right mind would do that.
The HTC 10, LG G5, and all other Quick Charge 3.0 and lower devices will work just like every other Type-C compliant device for every use case except when connected to a QC charger, in which case they behave like a QC device.
You’re probably wondering how we got to the current charging standards mess. I’ll probably explain that in a later post.
*I suspect the main reason for this is Android doesn’t handle user/administrator/root accounts in the same manner desktop Linux does. On Android every app is a user in Linux parlance, while Android users are something else entirely.