XPost: alt.home.repair, comp.mobile.android
From: nuh-uh@nope.com
On 2023-12-25 12:38, Wally J wrote:
> Roger Mills wrote
>
>> Since you were asking about *Android* OBDII software, the issue of
>> whether or not it works on Apple devices is completely irrelevant
>
> True. It was Steve (as I recall) who brought up iOS devices, not me.
> I knew that all iOS devices are crippled by Apple from the start.
Steve hasn't posted in this thread at all that I can see.
>
> However I did duly respond to what Steve brought up, so I apologize.
> If you want to get something done, Android is always the way to go.
Show the posting id of the post and a quote.
>
> I've nixed a few of the Android apps in the original list already, mostly
> for requiring a login account (what for?) but also for language issues.
>
> An OBDII app is worthless (to me anyway) if it doesn't support (almost) all
> ELM327 devices and bluetooth protocols as there's no need for having to
> deal with proprietary anything and whatever bluetooth that Android supports
> is what EVERY OBDII app should support (it's fine if the OBDII device
> additionally has Wi-Fi but if a setup requires Wi-Fi devices, it's garbage,
IMHO).
>
> Some even "seem" to require their own ELM327 OBD brand, which is crazy.
>
> The OBDII setup should just work with just about everything out there.
> Anything else is crippled from the start.
>
> Moving forward, so that everyone always benefits from every action, I ran a
> few tests - which require me to be near the car & away from the PC, so
> they're not finished yet - but here is the preliminary test result...
>
> 1 requires account (strike 1, you're out)
Because making an anonymous account ID is SO hard...
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
