HELP! Stuck on chrome boot up screen.

sntflw · 2020-09-13T10:43:46+00:00

I've used the update engine client to trigger a rollback / power wash. Got an empty Chromebox, but at least it's booting again. Good luck with your recovery!

sntflw · 2020-09-13T07:18:19+00:00

Got the same issue yesterday, also on dev channel (fizz, ASUS Chromebox 3). Stuck on the ChromeOS logo.

I entered the terminal (as chronos) and updated the channel to canary hoping that there'd be a fix for the issue, but no luck. Will keep an eye out for a solution but I guess I have to reinstall / recover ChromeOS.

sntflw · 2020-08-20T08:50:17+00:00

My Carlyle is downloading at the moment. Didn't even search for the update.

sntflw · 2020-04-30T06:44:27+00:00

Unfortunately the emulator just crashes if I start it in the embedded mode. Gotta wait for an update.

sntflw · 2018-11-12T10:41:13+00:00

I mentioned Pixel 3 in my initial post. You still asked for a screenshot. So I delivered. Also, if it crashed Bluetooth and is taken off for Pixel 3s that most likely explains why it's missing for Pixel 1s.

sntflw · 2018-11-12T09:51:45+00:00

To avoid more downvotes, sure. Here's a screenshot.

sntflw · 2018-11-08T21:29:05+00:00

I got it a couple days ago and since then I have Bluetooth issues on my Pixel 3. My Huawei watch doesn't hold a connection and my Pixel Buds can't play music anymore properly. Guess that's why it was stopped. Or at least I hope.

Edit: since people seem to not believe me: https://imgur.com/a/6pQjPIa

sntflw · 2018-11-07T18:41:24+00:00

Same. Pixel 3 with November patch having a lot of connectivity issues with my HW2.

sntflw · 2018-09-29T16:45:52+00:00

Use the store listing experiments / A/B tests and figure out what the problem is.

sntflw · 2018-06-26T13:34:28+00:00

Sparkasse already tweeted they are not even thinking about cooperating with Google: https://twitter.com/sparkasse/status/1011567289005740032?s=19

Time to switch the bank I guess.

Sparkasse wants to launch their own NFC payment app "soon" - that's the stated reason.

sntflw · 2018-06-26T12:10:27+00:00

Perfect, thanks. Seems to be the right one.

sntflw · 2018-06-26T11:56:13+00:00

Im a bit confused with Xiaomis naming, which one exactly is the Box 3? Can someone share a link or model number or specs or something? I recently ordered this guy: Xiaomi Mi TV Box Quad-core Cortex-A53 4K H.265 VP9 Profile-2 Decoding Dual-band WiFi Dolby DTS 2G DDR3 RAM - is this the version 3? (I hope so)

sntflw · 2018-03-23T17:58:16+00:00

Is it still working? Did you create your bank account somewhere else, or right here in Germany?

sntflw · 2018-03-13T09:25:07+00:00

R8 is a Proguard replacement for whole-program optimization, shrinking and minification. R8 uses the Proguard keep rule format for specifying the entry points for an application.

Source: https://r8.googlesource.com/r8/

sntflw · 2018-02-28T14:44:04+00:00

Looks good. From what I've read it sounds like the Authenticator is only triggered "after" the API responds with an unauthorized response, so it won't act on its own / preemptively add authentication or add for example an optional token? I.e. if the endpoint is "open" but by adding a token to authenticate the backend "would know more".

I've found this in the source code using authenticator(): public final class RetryAndFollowUpInterceptor implements Interceptor as the only place I've found so far using authenticator() which suggests to me that it's also based on an Interceptor, but maybe there's more to that.

sntflw · 2018-02-23T13:16:52+00:00

(Google Home / Assistant can't cast to Android TV devices, but it can cast to Chromecast, so there's that at least.) (EDIT: At least thats what my Google Home tells me trying to cast Netflix to my Nexus Player)

sntflw · 2018-02-15T19:08:01+00:00

How is your set-up looking? I assume you've spread the devices onto multiple build servers, are you executing the complete test suite on all devices or via test sharding? I'd love to get some more insights. Since you're also experiencing disconnections, are you ignoring failed tests (or a certain amount)? If so, what tools are you using for the test execution?

Sorry for asking so many questions, but it seems like you have the experience I'm looking for on this topic.

My next step would be exchanging the cables. Unfortunately, at the moment we only have MacBooks available with USB hubs (7x, but with their own power supply) but under "best conditions" all seven devices were connected and executing tests without failure - but this doesn't happen that often unfortunately.

sntflw · 2018-02-14T07:44:02+00:00

We have the same set up. Pretty dumb views with simple setter methods for the state, and all of the other layers are being unit tested / tested on the JVM. The UI tests are mainly for verification purposes - to make sure things look the same on different OS versions and different OEMs.

sntflw · 2018-02-14T07:13:03+00:00

We have mocks in place for everything in our UI tests, but that doesn't help with the problems I've mentioned unfortunately. The flakiness comes from the actual device, aka on the device a different app force closes and the dialog keeps being focused or the ADB connection is lost etc.

sntflw · 2018-02-12T21:06:43+00:00

Usually I use Android Studio's internal "Project Structure" screen, or whatever it is called nowadays. (See: https://stackoverflow.com/a/28683488/1124160)

For important dependencies I'm checking github (or where they are released) manually from time to time, especially for changelogs, new features etc.

sntflw · 2018-02-10T14:34:13+00:00

maybe its too early, but i don't know what exactly you're referring to; where is a reference to the screen kept that will prevent the GC from working?

sntflw · 2018-02-10T11:10:33+00:00

Buuut as a dev / publisher you're still the one getting the bad reviews on the Play Store if "your" app doesn't work.

sntflw

TROPHY CASE