Vik

my best guess would be “cat related things”

don’t ask

Someone suggested to me the other day that safetynet was now (or will soon be) deprecated. I’m not sure what the situation is with regards to attestation, though I sort of dread to think about what will replace it.

I’m also experiencing this intermittently with a pixel 7 and android 14.

Stacktrace

java.lang.NullPointerException: Attempt to invoke virtual method ‘java.lang.Class java.lang.Object.getClass()’ on a null object reference at androidx.compose.ui.graphics.layer.LayerManager.persistLayers(Unknown Source:118) at androidx.compose.ui.graphics.AndroidGraphicsContext$componentCallback$1$onTrimMemory$1.onPreDraw(Unknown Source:16) at android.view.ViewTreeObserver.dispatchOnPreDraw(ViewTreeObserver.java:1176) at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:4029) at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:2718) at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:9937) at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1406) at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1415) at android.view.Choreographer.doCallbacks(Choreographer.java:1015) at android.view.Choreographer.doFrame(Choreographer.java:945) at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1389) at android.os.Handler.handleCallback(Handler.java:959) at android.os.Handler.dispatchMessage(Handler.java:100) at android.os.Looper.loopOnce(Looper.java:232) at android.os.Looper.loop(Looper.java:317) at android.app.ActivityThread.main(ActivityThread.java:8592) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:580) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:878)

END of stacktrace

Thread info

Name: main ID: 2 State: RUNNABLE Priority: 5 Thread group name: main Thread group parent: system Thread group active count: 40 Thread time: 0 hr 2 min, 25 sec

END of thread info

Device info

Report ID: ba4f523e-a62e-4f16-9748-641ba37e3b34 Device ID: 98bcbcd13ed07858 Application version: 69 Default launcher: com.android.settings Timezone name: Greenwich Mean Time Timezone ID: Europe/London Version release: 14 Version incremental : 24508000 Version SDK: 34 Board: panther Bootloader: cloudripper-14.5-11677884 Brand: google CPU ABIS 32: N/A CPU ABIS 64: arm64-v8a Supported ABIS: arm64-v8a Device: panther Display: AP2A.240605.024.24508000 Fingerprint: google/panther/panther:14/AP2A.240605.024/11860263:user/release-keys Hardware: panther Host: tuotanto.eu.calyxos.net ID: AP2A.240605.024 Manufacturer: Google Product: panther Build time: 1718293084000 Build time formatted: 13-06-2024 16:38:04 Type: user Radio: g5300q-240308-240517-B-11857457,g5300q-240308-240517-B-11857457 Tags: release-keys User: cdesai User IDs: N/A Is sustained performance mode supported: No Is in power save mode: No Is in interactive state: Yes Is ignoring battery optimizations: No Thermal status: STATUS_NONE Location power save mode: MODE_NO_CHANGE Is device idle: No Battery percentage: 32 Battery remaining time: N/A Is battery charging: No Is device rooted: No CPU Model: N/A Number of CPU cores: 8 Up time with sleep: 76 hr 9 min, 36 sec Up time without sleep: 25 hr 12 min, 37 sec

END of Device info

Exit reasons

Exit reason #1 Description: crash Importance: FOREGROUND Reason: CRASH Timestamp: 22-06-2024 21:27:36 END of exit reason #1

Exit reason #2 Description: REMOVE TASK remove task Importance: CACHED Reason: USER_REQUESTED Timestamp: 22-06-2024 14:59:49 END of exit reason #2

Exit reason #3 Description: crash Importance: FOREGROUND Reason: CRASH Timestamp: 21-06-2024 23:02:27 END of exit reason #3

END of exit reasons

Application info

App name: Jerboa Version code: 69 Version name: 0.0.69 Package name: com.jerboa Short package name: jerboa Flavor: N/A Signatures: KvQuis6lLSzWNkzLFfVFwtoVsyk= Is debuggable: No First installed: 05-09-2023 18:30:11 Last updated: 14-06-2024 19:00:56 Requested permissions: android.permission.ACCESS_NETWORK_STATE, android.permission.INTERNET, android.permission.READ_MEDIA_AUDIO, android.permission.READ_MEDIA_IMAGES, android.permission.READ_MEDIA_VIDEO, com.jerboa.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION, android.permission.READ_MEDIA_VISUAL_USER_SELECTED Default prefs: N/A Default prefs: N/A

END of Application info

Currently running foreground/background processes

N/A

END of running foreground/background processes info

There’s also the handy public instance https://send.vis.ee

holy damn I just realised how long my block list is.

Appreciate the update

None whatsoever. You’re good to use heliboard with the gesture input library. There is also the FUTO keyboard, which somehow has a gesture input library built in. I would presume theirs is FOSS but I’ve not done my homework on this.

E: as someone else mentioned, you can deny network permission for gboard with ROMs like LineageOS, GrapheneOS, CalyxOS etc. This is what I did for many years until heliboard came along.

That works. Which service do you use ooc?

Ordinarily I’d agree, but for now, WhatsApp is tied to your phone number. I’m not sure if you can use some kind of service to create alias numbers but for many people, that’s a big blocker when it comes to making another account following any kind of infraction.

I don’t think meta would shift in requiring a phone number per account either,

It is to

A: the continuity of said project (DMCA) and B: to the individual end users.

You can use FOSS clients for things like Discord or the Google play store but you still run the risk of getting banned.

Yes, I already aluded to this. Point being, I don’t think you’ll find a viable FOSS front end since it would violate their TOS.

I see, fair enough. I don’t know if you’ll have any luck with a FOSS third party client which does t violate their TOS. There was something on fdroid years ago, a wrapper that effectively allowed you to use WhatsApp Web on another phone (or perhaps even the same one), but it ultimately requried the use of the official clients

Signal I suppose would be the closest analog

That’s fair enough, though one of the characteristics I had in mind was also battery life (that said, it would be at a given level of performance so either way).

Also definitely not thrilled about things like ME, Pluton and so on.

We’re a ways away from reaching equivalent performance characteristics of the currently available options they have with RISC V, but I would also love to see that as well.

here’s hoping. would be a nightmare if it somehow reached the healthcare industry

big fan of Hulshult’s work on IDKFA, DUSK and Prodeus. Would love to see them directly involved with DOOM.

Appreciate the insight

It’d be telling if later iterations of idtech (should it continue to develop) switch away from Vulkan on desktops.

Would be a difficult move considering how ruthlessly performant it is at present.

God damn I didn’t expect to ever see that again. Brill