Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Ehm... Just ranting, not really expecting anyone would "solve" these - just don't like the direction it's headed in, that's all (purely subjective, I know). And most of it is caused by management's orders not seeming possible without working around how apps work in Android somehow (basically guarantee a perfect BLE connection ALL THE TIME, regardless of conditions; Ever tried reading data from a closed socket...? They don't care. Just do it.). BTW, is it guaranteed that manufacturers won't change the source so much as to make debugging basically impossible (with what we have in the SDK)? I know the debugger connects to the device, but what if the code you put a breakpoint on doesn't exist on the device, for example (talking about stepping through SDK methods, not libs) or is just plain different? Fortunately never happened to me (afaik), just asking. Just mad as hell, consistency not found...
@gitpush The newest one available yesterday (don't know if it was 9 or 8.1, don't have... -
Oh, and we have to use OTG USB in a way that is not possible when targetting Android 8+, afaik (BroadcastReceiver listening to attach, asking user for permission then proceeding to work with it via another receiver for said permission)...
Anyone has any idea how to do it right? It says in the docs that it can't be done (that particular broadcast - USB_DEVICE_ATTACHED), however I somehow failed to find alternatives. So far sticking to targetSdkVersion 23, everything works even on newer droids. Company doesn't particularly want to go on Google Play, so...
Related Rants
It all makes sense now...
Bloody fucking Android! Updates, updates and more updates! My development Nexus 5X won't allow me to sideload apps since it updated... Hello, printf debugging! Goodbye, profiler and debugger!
My hate for Android grows with each version after 4.0.$something... 2 was shit, I missed 3, 4 was OK, and since then it's going steeply down.
And don't get me started on Material Design...! Good luck figuring out what's a button and what's a label...
And what's up with the "let's keep all apps running all the time to save a few ms on start" philosophy!? Who thought that is a good idea!? Yeah, System.exit(0) works, but... Is it so hard to determine when it's not needed anymore (has no services running etc.)? Why should a web browser (for example) stay in memory after I quit? Minimize is a thing (Home button), why make it so confusing?
Another thing - feedback-less async tasks - why? I like to know when it is working in the background... How the hell am I supposed to find out if it is supposed to do this or if it is frozen?
And Android deciding to kill your process whenever it pleases without any callback... Happened to me once with an Activity in the foreground (no exceptions anywhere in my app, it just quit). How do you do IO properly? It seems you can't guarantee some file or socket or something that must be closed doesn't stay open (requiring to restart Bluetooth 'cause the socket wasn't closed, for example)...
rant
android