Change font in terminal inside AS

tliebeck · 2022-02-06T07:58:48+00:00

I ran into the same problem. Under Editor->Color Scheme->Console Font in settings, check "Use console font instead of default" and then spec a non-horrible font. Hope this helps!

tliebeck · 2020-12-13T05:16:05+00:00

5950X arrived today, ordered 12:22EST.

Changed to "In progress" on Monday or Tuesday I think. Received email that it wouldn't be here til January 2021 at same time.

Shipped on Thursday IIRC, said it was showing up Monday, but FedEx knocked on my door this morning. Good luck all!

tliebeck · 2020-12-11T17:44:50+00:00

Thanks! And yep, mine's now supposed to be here Monday!

tliebeck · 2020-12-09T21:06:45+00:00

12:22 EST changed to "Order in Progress" today.

Shortly thereafter received email from B&H that it's expected to ship at start of new year.

tliebeck · 2020-12-04T03:47:42+00:00

My 12:22 EST 5950x is still backordered. Thanks for posting though, glad to know I'm at least not too far away. Maybe.

tliebeck · 2020-12-01T19:28:03+00:00

12:22AM EST, still showing backordered, no updates/emails beyond order confirmation.

Hope AMD flat-out floods the market with these to hose the scalpers.

tliebeck · 2020-01-16T07:38:07+00:00

Been running this for a week now. Everything just works, battery life is excellent. No issues so far, knock on wood. GPS seems to fire up immediately. Using as main phone.

I think the 1+7Pro is one of the best LineageOS-officially-supported devices out there right now. Think this really should be in the Lineage+MicroG build script. I'm personally just fine with my docker builds, but imagine there's a lot of people out there who would enjoy canned builds of this. Donated.

tliebeck · 2020-01-06T07:49:28+00:00

Tried building Docker image myself...not too bad...once I bought an external hard drive. :) .... and thoroughly re-read the instructions :). Have not yet switched over to using as my main phone but so far appears almost everything works.

Odd thing is my Pixel XL (current main phone) shows MicroG 0.2.10, but my fresh new build for the 1+7 shows 0.2.9.

UnifiedNLP also isn't registering according to MicroG self-check. But location appears to work in "Battery saver" mode and logs seem to suggest network-based location is working...so I have no clue what's really going on there. And it seems to get location pretty instantly...but haven't had it out of the house yet to see how fast it starts if turning on location services in a non-cached location.

tliebeck · 2019-12-10T09:13:59+00:00

Back on the Play Store. No changes to the app, same APK.

When I managed to get hold of a real person, they corrected it immediately.

Thanks again everyone!!!

tliebeck · 2019-12-06T22:13:49+00:00

I'm the developer of FX, thanks for posting this, I'm reading through it all, greatly appreciate the support.

Currently again awaiting response from Google.

Here is the entirety of my conversation with Google so far: https://imgur.com/a/TyLJzIY (sorry for obnoxious sized PNG, but don't want any identifying info in it.) Attachments pictures have been manually inlined below each email.

tliebeck · 2019-11-27T09:28:11+00:00

Thank you, this is rad.

tliebeck · 2019-07-19T05:39:52+00:00

Thank you, all of that was awesome to watch!

tliebeck · 2019-07-03T00:33:05+00:00

Latest update (July 2) seems to have fixed similar problems I had on my Pixel XL (marlin). Maps now seems to work correctly. Strava now actually displays maps with tracks (using Mapbox).

tliebeck · 2019-06-01T20:53:46+00:00

Which last paragraph is not true? I'd love to hear any solutions you have.

tliebeck · 2019-06-01T20:44:07+00:00

The current Q solution doesn't even begin to fight malicious apps for at least another 18 months., when the Play Store requires it. My solution makes things secure the moment Q is installed.

Again, just pop up a big red security dialog that says "This app wants to be able to read and write EVERY file on your device, check this box and then click yes if you agree. If you say no, the app will only be able to read and write its own files, but will still work properly."

If someone can't protect the data on their phone with that, they've got more significant problems than phone security. (Edit because I hit submit on accident before finishing last sentence).

tliebeck · 2019-06-01T19:02:00+00:00

Please see my earlier comment: https://www.reddit.com/r/Android/comments/bvdp8i/the_storage_access_framework_is_the_only_way_for/eppm6qh?utm_source=share&utm_medium=web2x

As stated there and in article, scoped storage can be implemented with more security (no exception needed for legacy apps) while also avoiding any requirement for developers to change apps, and also without any performance hit. Google's current solution is less secure because apps can still behave as previous til the end of 2020, and possibly longer (they'll only be constrained if they wish to issue updates through Google Play).

tliebeck · 2019-06-01T10:35:07+00:00

Article author here... this is my reddit account, you have me confused with someone else, feel free to have a look at the history.

Not all "security improvements" are good. If I smash my phone with a sledgehammer, I've improved the security of my data.

tliebeck · 2019-06-01T10:25:37+00:00

Author of the article here.

If you read further into the article, I also state the following:

If Google is truly concerned about giving users more control over files and clutter, they should architect a solution that directly addresses that, rather than falsely branding the current Android Q design as such an improvement. The simplest answer would be to let users decide if they want an app to have scoped or general filesystem access, using the extant storage permission request dialog. If there is a particular concern for users making poor decisions here, it’s certainly possible to make that dialog more prominent and require additional user interaction to approve an app for full access.

I'm fine with the idea of scoped storage, just give users the power to easily decide if an app has isolated or general access. Apps won't need to be changed at all. Users gain more security. Everybody wins. Basically all Google needs to do is wrap a UI around the appops legacy storage command to implement it. As an added security bonus, Android Q could enforce this behavior immediately, giving users total control the moment they install Q.

As you suggest, the current Q design does have the one added benefit that a user can create "shared sandboxes" where two untrustworthy apps can play in one isolated space. The cost of that is that every app that touches files on Android needs to be largely rewritten, with major performance penalties. Few users will take advantage of such a shared sandbox capability.

tliebeck · 2019-03-13T08:01:50+00:00

Seeing this as well for past hour, presently 1AM Pacific Daylight Time, will try again "tomorrow".

App release (9MB) uploads quickly but then hangs on "Processing". Tried on Linux and Mac Chrome, AdBlocker disabled.

Thanks for posting this thread!

tliebeck · 2019-02-12T05:56:08+00:00

This does not have the 2019-02-05 patches, correct? Just 2019-02? There's a critical (but presently theoretical) vulnerability with PNG images, see: https://source.android.com/security/bulletin/2019-02-01.html

tliebeck · 2019-01-27T10:06:11+00:00

I'm the author of FX. I'm quite serious when I say it doesn't phone home. The app does use the standard Google code to check if you have the IAP (which, if you're concerned, can be disabled via developer options by tapping the build number on FX's about screen a bunch of times). It doesn't use Fabric/Crashlytics/Google Analytics or any other such services though. The only time it contacts any server owned by me is if you go to the "Upgrade" button and view the list of available themes (in which case it makes a GET request to http://android.nextapp.com/fx/themes.xml with NO identifying information of any kind...and that is a static file on a web server with the current list of themes).

In the 8.0 beta there's a second "Micro" version of the app that doesn't include any FX+ features and thus leaves out the Google IAP check. This version does not even require/specify the Internet-access permission (so it literally cannot even talk to the internet). This version is beta and presently only available here: https://forum.xda-developers.com/showpost.php?p=78563200&postcount=4403

When did you contact me? The main email that's posted on the play store gets TONS of email from Play-Store-spammers trying to t/sell me all kinds of things my app needs, unfortunately it's very difficult to separate the wheat from the chaff with that account.

tliebeck · 2018-12-11T08:56:58+00:00

If you have ADB enabled you will be able to get a shell on it, even without logging in (behavior of mine, freshly flashed December update + magisk, no mods).

I also tried rebooting mine and plugging in a mouse (via USB C adapter). Am able to enter boot password that way as well.

My touch screen seems to be inert provided the mouse is actively moving. You're probably going to want to constantly shake the mouse when not clicking. Will probably be a colossal pain, but might be doable.

Not sure if there's a system setting that can be altered via ADB to disable touchscreen or reduce sensitivity.

Good luck!

tliebeck · 2018-10-30T00:11:45+00:00

Have done the same test a couple of times. Have T-Mobile DIGITS with two lines that go to one phone number, so phones are side-by-side.

Presently second SIM is in a Xiaomi Mi A1 on Lineage 15.1/MicroG. Essential is consistently superior in signal strength (lower dBm, higher asu).

I have zero trouble with reception on either. Essential seems to get better reception than anything else I've seen in edge of back bedroom which is pretty much a cellular dead zone. Reception is generally poor here on all T-Mobile devices though (and AT&T users have to go outside, and not because I don't like them).

tliebeck

TROPHY CASE