Profile cover photo
Profile photo
Gyuri Grell
2,191 followers
2,191 followers
About
Gyuri's interests
View all
Gyuri's posts

Post has shared content
Makers! Help us help you.

Google wants to create smart tools for Makers, so we're asking you to fill out this survey to tell us what you'd find helpful.

We'll also share they survey findings back to the community

https://google.qualtrics.com/jfe/form/SV_3yMNYryaP4WsCwJ?Source=RETO

Post has attachment
Trolololol
Photo

Post has attachment

Post has shared content
You're searching for Android developers or want to advertise your product/service which helps Android developers in their daily business? Post a job or a sponsored post in the Android Weekly newsletter and reach more than 48500 Android developers!
http://androidweekly.net/jobs/new/

Post has attachment
For a few heady days in the autumn of 1956, Hungarians rose up and retook the streets from their Soviet hegemon. Soviet troops eventually reentered Budapest and crushed the uprising. But despite their eventual defeat, the Hungarian rebels of 1956 inflicted what would come to be known as "the first tear" in the Iron Curtain. Today, the exact locations of many of the most iconic photographs of the uprising can be determined, revealing that while politics have changed, the historic streets of Budapest remain remarkably similar.

Soooo... My stock, locked Nexus 6P with Nougat (final, via beta test) was sitting on my desk, plugged in, recharging, when all of a sudden it rebooted. Now it's stuck in a boot loop not getting past the initial display of "Google" (no colorful animation). Sigh. Tried re-applying Nougat OTA, thinking it might recover and issues, didn't help.

Is it pretty much try and wipe it at this point?

Post has shared content
On vacation for a week, Android Weekly is still published! (Thanks to +Sebastian Deutsch and +Martin Gauer)

Post has shared content
I've seen a few postings from Android Wear developers asking about problems with some users having devices where Google Play Services on the Android Wear device is out of date (typically version 8.x instead of 9.x).

You can determine your version on Android Wear by going to Settings ... About ... Versions ... Google Play Services. It should start with a 9, and not 7 or 8. If it is 7 or 8 you have a stuck device.

I'm trying to understand what the cause of this problem is, so we can get it fixed. Most developers don't have the problem on their own devices, but occasionally they are being contacted by users of their apps who are reporting problems. If you hear from a user with a problem, I would like to get a bug report from them so we can analyze and then help fix it.

We need bug reports captured from both the phone and wearable side. So if you have a USB cable and watch cradle, you can run "adb bugreport > phone.txt" with the phone plugged in, and "adb bugreport > wear.txt" with the wearable plugged in. There is also a bug report mechanism which can work over Bluetooth, outlined here: http://www.androidpolice.com/2014/08/27/android-wear-app-update-adds-a-confusing-way-to-report-bugs-to-app-developers-support-for-ambient-light-sensors/

Once you have a bug report, please send them to me directly, do not share them in public since they might have private information in them. Ping me on hangouts and I'll send you my email address. The quicker I get reports, the quicker I can work on getting a solution for this. Thanks!

Post has shared content

Post has shared content
Wait while more posts are being loaded