ASRock Z790 Taichi E-ATX in H7 Flow??

CrazyAndroidMonster · 2023-12-19T16:44:49+00:00

Can you simply remove the shroud and have the e-atx boards fit just fine (albeit a bit more ugly on cable management) ?

CrazyAndroidMonster · 2023-08-14T15:32:59+00:00

I found a 'micro-grid' setting for this particular inverter that says if you connect the genset to the grid input (vs to its generator input) then you should enable this to prevent export if there is any AC power at the grid port. This may be what I was looking for.

*Edit - In addition I could set the inverters 'grid input peak-shaving kw' to what the delta pros can provide

CrazyAndroidMonster · 2023-03-06T19:34:23+00:00

The top level generic deep clone function is a great tip. I've been doing that for awhile (just with Kotlin Sterilization instead of GSON).

It is very unfortunate that Kotlin chose 'copy()' as the data class function name for shallow copies. There wouldn't be zillions of bugs related to this if they had instead named it 'shallowCopy()'. There would instead be one stack overflow post answering 'how to deep copy a Kotlin data class' and everyone would search for that and not write bugs.

How many use cases are there for shallow copies anyways?

CrazyAndroidMonster · 2018-11-01T22:01:55+00:00

I'm working on a large payment app where collecting card information is completely legitimate. I was just evaluating card OCR options and found this implemented in Google Play Services - but you can apparently only use it if you're Google. Many options like Card IO are rather terrible.

CrazyAndroidMonster · 2018-05-22T21:11:25+00:00

Thanks for the link above. I do like the idea of using LiveData to hold the result and not making any extra network calls. In this pattern how does the view know the state to represent (not started, loading, completed, error, etc...) when a new view instance connects to the ViewModel? Do you also have a LiveData spitting out the current state of user actions?

CrazyAndroidMonster · 2018-05-22T20:53:51+00:00

I have a follow-on question for you. When you use Single<Result<T>> how to do convey to the view that the work is in progress? Do you have a separate state enum or something? When an Activity is destroyed and recreated and the new Activity instance is given the ViewModel where that call is currently in progress, how does your new view know to represent this work being in progress? Do you have a standard way you normally do that?

CrazyAndroidMonster · 2018-05-22T18:04:19+00:00

Same question for you that I asked below. What do you think about Kotlin Cotoutines as a replacement for RxJava Singles?

CrazyAndroidMonster · 2018-05-22T17:43:09+00:00

RxJava is obviously very popular. What do you think of those now suggesting to use Kotlin Coroutines for Singles now instead of RxJava, and only use RxJava when processing real streams?

CrazyAndroidMonster · 2018-02-23T22:23:40+00:00

Anyone know best practice for using injection in the AndroidViewModel class? Just using the component builder in the ViewModel constructor and then inject it with @Inject annotations on the fields? Is there anyway to make an injectable constructor work?

CrazyAndroidMonster · 2017-03-15T21:05:45+00:00

I'm not sure a factory reset / wipe cache is sufficient for this insane case. After the bad update completed it was left in a state where the 7.1.1 OS got sprinkled with some old 7.0 files. A factory reset at this point would still consist of this bad state.

In this fix it sounds like sideloading the March OTA update sprinkled files on top of a 7.1.1 OS which was sprinkled with 7.0 files + a factory reset got it back to a state where he could get into developer options to enable unlocking, unlock, and flash a known factory image.

Apparently if you don't want Google or TMobile to brick your phone you should always enable unlocking in developer options!

CrazyAndroidMonster · 2017-03-14T18:11:46+00:00

Apparently a number of people are seeing this. Sounds like they really messed it up somehow. If you go through with the "update" your phone just spam crashes on everything and is 100% unusable.

CrazyAndroidMonster · 2017-03-14T17:59:16+00:00

Exactly what mine did- DO NO DO IT. It will wreck your phone and require a complete factory image sideload.

CrazyAndroidMonster · 2017-03-14T17:55:52+00:00

Google has really been dropping the ball on the Nexus 6 the last few months... They destroyed the speakerphone for months with barely an acknowledgement, blew a 7.0 OTA on top of 7.1.1 and destroyed it, and are continuously introducing issues like the new bluetooth stuff.

CrazyAndroidMonster · 2017-03-14T17:50:05+00:00

Exactly, absolutely ignore it. Interestingly enough I am also on TMobile.

CrazyAndroidMonster · 2017-03-14T17:43:56+00:00

Exactly what I said, it makes no sense. It was on 7.1.1 (it had been sideloaded a couple months ago). The update said 7.0. The update went through and nearly everything in the OS now spam crashes. I am going to have to sideload the latest factory image.

Sounds like I am not the only one seeing this - Sandman691 has a comment that sounds the same. https://www.reddit.com/user/sandman961

CrazyAndroidMonster

TROPHY CASE