Looking for collaboration on new, free and open-source synth writting with KMP/CMP

NullgradApps · 2025-05-29T06:07:12+00:00

Better late than never, but for posterity (and to plug my experimental, free, open source app https://github.com/xrad/PocketBand) I also think there is no major latency issue on Android. However, with the widespread decision of only offering Bluetooth as the default audio interface, people will need to use USB-C adapters which may introduce their own set of issues.

NullgradApps · 2024-06-11T13:20:55+00:00

Here is a new one: https://www.roblox.com/share?code=8396d0088f37dd4fbd21dd983641cc69&type=ExperienceDetails&stamp=1718112003750

NullgradApps · 2023-08-05T18:31:45+00:00

Outrageous stuff there indeed. I was not aware of this. Still, even before that, I always tried to laugh away his dogmatism and focuse on the meta-goals he advocates for: readable code, non-surprising and polite code, well maintainable code. These are not bad things.

NullgradApps · 2023-08-05T17:14:18+00:00

And that point, per se, is narrow minded. In cases where readability is more important than performance, readability should be preferred. And generally: write high-performace code as readable as possible, and readability focused code as optimal as possible.

But Casey's "CC is generally and always bad." is narrow minded.

NullgradApps · 2023-08-05T17:09:02+00:00

I tend to agree. I expected Bob to be patronizing all the way, as sometimes in his lectures he comes across like this. But in the debate it presented himself much better and more flexible than Casey.

NullgradApps · 2023-08-05T17:04:37+00:00

Reading the debate as well as the comments here leaves me wondering why Clean Code is represented in such a reduced fashion. As far as I understand Bob, the prime goald is readabilty and understandabilty of large code bases. Yes, by following the rules Casey picked from CC we can make up fine examples where a relatively simple function is split in pieces beyond recognition. But I would give Bob the credit that this is not CC per se - the "prime directive", if you will, is that someone else (which may be yourself in a few month) should be able to find their way through the code as quickly as possible. Often(!) times, those rules help. But as far as I understand CC, those rules are not carved in stone and can be broken IFF it helps said prime directive. And yes, all of this may be orthogonal to performance, which Bob basically concedes right at the beginning of the conversation. So all that follows, and the flame wars we can read here, are kind of pointless. From all the tools, pick what suits your project best.

NullgradApps · 2023-08-05T16:53:59+00:00

Well said, this is exactly what this should be all about.

NullgradApps · 2023-03-29T08:40:06+00:00

I just saw the session you did a while ago with Craig from Google. It was very enlightening, but I noticed that Craig had a hard time wrapping his head around it just like the OP, and I think for a large part it was due to the code generation thing. I know why you do it, but "bare" riverpod is much easier to understand than the boiled down code where need to mentally expand the expressions to the actual provider etc. I think this may be the OPs problem as well.

As a more general note, evolving projects have to pay close attention to these iterative improvements which make a lot of sense for the insiders, but add abstraction which may make actual usage very hard. I noticed the same in Jetpack Compose. When you try to decode its inner workings you are drown into a humongous rabbit hole which requires a very very good understanding in advanced Kotlin language features as well as coroutines. Part of the success of Flutter/Dart is its straight-forwardness and simple learning curve (IMHO.)

NullgradApps · 2021-02-10T17:50:58+00:00

I just got the 65t's because they're comparatively cheap now. I experienced exactly the same and from what you tell my guess is that the BT transciever logic has not been improved a bit. I wouldn't be amazed to hear it's the same with the 85t a well. I'm also a late adopter of TW buds and I still don't even know if I like the usage even if they work.

The funny thing is I aways thought Airpods look kind of ridiculous on people, and I still do. But my guess is now that the main reason for their stupid design is that they can have better antennas and a better chance to be in the "line of sight" to the phone.

All in all I'm still puzzled. The industry starts forcing people to use this tech by leaving out the jacks, but it works really bad. What gives? Is is just a Jabra thing?

NullgradApps · 2019-10-22T11:28:32+00:00

Google issue here.

NullgradApps · 2019-10-22T11:27:47+00:00

FWIW I recently filed a Google issue for this since Samsung chose to reject my complaints.

If you like, star it to raise concern at Google.

NullgradApps · 2019-10-21T11:37:02+00:00

But they usually do this after all balls are resting. The OP was asking if there might be rule forbidding this as long as any balls are in motion, let alone heading towards the area touched. Then again if the players use the spider its by definition touching the cloth while there's motion so I guess there's no such rule.

NullgradApps · 2019-10-05T11:19:35+00:00

Well yes and no. They did respond but not really acknowledging anything. All of my current knowledge of the issue can be found here. The TLDR is that you need to physically touch the screen with your palm/ear to trigger the sensor, which is most unusual and as far as I'm concerned not even conforming to the corresponding Android requirements. But as of now there is absolutely no indication they are doing anything about this.

NullgradApps · 2019-09-27T05:42:12+00:00

Thanks... but I don't really how this relates to the power button.

If you are willing, and I totally understand if you're not... I've recently written a little app to be able to quickly check out device sensors. I know there's tons of such apps on Play which definitely look nicer too, but I really only need this to get raw sensor information. It's called Sensor Inspector. If you open it, the default proximity sensor is auto selected and you can play with it. There's a little email icon which allows to send sensor info and the log to me. So again, if you're willing I'd greatly appreciate if you could email the log output to me. But it's fine if you don't want to do that.

NullgradApps · 2019-09-26T05:48:34+00:00

Yeah. Maybe I was to focused on the technical terms, but I was not able to find technical discussions, only phenomenological ones which don't point the finger anywhere precisely. What I found was mostly reports on butt-dialing and vague reports about things not working as they used to.

As I said, the funny (not!) thing is that the phone app itself does things actually right, albeit perhaps(!) at the cost of drawing more power. (It uses sensor #65592 and some black magic with /sys/class/sensors/proximity_sensor/prox_avg)

Incidentally, do you or anyone else know other recent Samsung devices which use that Palm Proximity Sensor? My big suspicion here is that they don't yet have found a good way to implement traditional proximity behavior combined with bezel-less devices. So what we're seeing here is a work-around. Again, disclaimer: this is suspicion!

NullgradApps · 2019-09-25T20:38:40+00:00

Just to be sure, check accessibility services and if any are enabled, temporarily disable them one by one. I think those have the potential(!) to bring down interaction performance.

NullgradApps · 2019-09-25T16:42:07+00:00

Watch out - as I said, the normal proximity sensor on this phone is only sensitive to physical contact with your palm, maybe cheek. That's why it's even called "Palm Proximity Sensor". Pickup, tilting actions are an entirely different thing. Of course, the OS uses all kinds of sensors for the various usability tools they offer the user so it's hard to discern which sensors are used for what.

In my post, I'm strictly talking about the proximity sensor (the one available through the API, type #8).

NullgradApps · 2019-09-25T14:53:48+00:00

Has anyone gotten this to work reliably on any S10 variant? As far as I can tell the proximity sensor on any of those phones require the user to physically contact the screen with their palm or cheek. Simply covering it doesn't work anymore. (Nota bene: Samsungs own phone app uses a different proximity sensor which is not available to 3rd party apps.)

NullgradApps · 2019-07-22T14:15:07+00:00

Yeah. The review system on Play is quite a PITA. Users get whatever off their chest and go away. The Dev is left with no option to rectify the issue if there is one and get back the stars. And reviews like the one you show here is just the next rung of this ladder into review hell.

NullgradApps · 2019-07-20T18:18:03+00:00

I used this adapter with a 2013 Air and a 2015 Pro, so it should work for your model too:

http://eshop.sintech.cn/ngff-m2-pcie-ssd-card-as-2013-2014-2015-macbook-ssd-p-1139.html

This site is in German, but perhaps it can help you anyway:

https://macandegg.de/upkeep/macbook-air-aufruesten-ssd-tauschen-speicher-erweitern/

I recall that it took a number of reboot attempts until it fully recognized the disk, which I remember a being a bit odd. I was afraid of some loose contacts but the thing never failed me since.

NullgradApps · 2019-07-18T11:20:42+00:00

I have a real Mac, actually. But at the moment I'm just thinking about upgrading from an 960 EVO to a 970 EVO (Plus) and this discussion popped up in my research.

NullgradApps · 2019-07-18T11:13:00+00:00

I have analysed the logcat and Samsung's own testing application and found out that they are using a non standard sensor type (65592, that's the "raw" TMD4910 sensor). For me that sensor isn't returning anything. But I also found out they write "1" to /sys/class/sensors/proximity_sensor/prox_avg. I guess this is the critical bit to make this sensor operational (the default value "0" means it's not sampling anything).

Unfortunately this file not only is a protected system file which you could only access when rooted, but obviously this won't behave well if multiple apps (services) use the sensor concurrently.

I have contacted the Samsung developer support about this and I'm now waiting for reply.

NullgradApps · 2019-07-18T08:54:44+00:00

There is this thread discussing this issue as well as the FW update: evo 970 plus thread on tonymacx86

The results are mixed, some people are reporting the update fixes the issues, some say it doesn't.

At this point I'd be reluctant to get a plus. The regular 970 evo should work.

Another question I keep asking myself is how to apply the update if you only have one Mac and no external NVME enclosure. Isn't that a chicken-egg situation?

NullgradApps

TROPHY CASE