evpuneq
Mbps Experimental Acoustic Through-Tissue Communications: MEAT-COMMS
Implementations of cat(1) from various sources
Checklist for projects that have promised to liberate software in the future
Dell Foundation Services Remote Information Disclosure
The World We Leave Our Children: How I Became a Free Software Extremist
A 22-year-old anti-Nazi song tops German charts again – to welcome refugees
IBM Watson Personality Insights
Project Seen
Release extravaganza: CM 11.0 and 12.0 Final
Remember broken Nexus telephony? This is how Google treats it's customers
Re:121 Megapixel true color photo of Earth from Japan's new Himawari-8...
on Monday January 05, 2015 @03:50PM (#8841061)
More information: http://www.jma.go.jp/jma/jma-eng/satellite/news/himawari89/2...
121 Megapixel true color photo of Earth from Japan's new Himawari-8 satellite
Re:Google broke telephony for many Nexus users
on Monday January 05, 2015 @02:18PM (#8840555)
The services probably just trigger an error deeper in the call stack like in Qualcomm's proprietary binary blobs. Perhaps they received a new version from Qualcomm.
Re:Google broke telephony for many Nexus users
on Monday January 05, 2015 @10:50AM (#8839364)
This issue also affects users of CyanogenMod 11 which is currently based on Android 4.4.4 (https://jira.cyanogenmod.org/browse/CYAN-5728). The same thing happened to the HTC One M7, but HTC fixed it quickly with an OTA update (http://venomroms.com/venomhub-fix-no-sound-calls-htc-one-m7). All in all it looks like the malfunction is caused by an automatic update of the Google Play Services framework. Not reacting at all so far is definitively not a good move of Google.