Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 19, 2020 20:12:21 GMT
Firstly I should preface this thread with the fact that I have been comparing IOS dev vs Android dev and complaining about the differences.
So to this thread about Long Coding
Below you will see the screen shots of Android and IOS.
Android has two screens, Frstly a OBD11 Shortcut screen, Secondly the Byte and Bit screen I love that includes the Byte, Bit, Hex data along with (IMPORTANT) User descriptions in different languages.
The IOS Screens have three screens, The Shortcut screen, Secondly the Byte Bit screen (BUT IMPORTANTLY NO Description data) and Thirdly the Description data but no link to Byte Bit.
Now i am very happy with change if it helps me but the IOS Screens in my view do not help me they hinder me.
But I am old and got used to the old ways.
What do people thing about the new IOS Screens as these will in time be the Android screens.
Support response when I said I did not like them and preferred the old Android Screens.
The long coding will keep as it is on IOS and in the future you may expect eh same on Android too. Descriptions of dev for longcoding, live data, adaptations will be added in teh near future.
This thread is not a pop at OBD11 Dev I just want people to agree or disagree with my view (keep it as Android) that the New IOS Screens are not what people want.
If you dont agree with me that is fine, it just means I am out of touch and have no problem just want to make sure
IOS Screens
UPDATE: Support have now confirmed to me that the Byte Bit screens will be updated to show description data. |
|
|
|
Post by dv52 (Australia) on Jun 20, 2020 0:13:43 GMT
tester: thanks for starting the thread - but I'm still not sure what the third screen does on iOS? I had always thought (and I'm probably wrong - I am often wrong) that the first screen displays data that came from the module itself (I get the same descriptors if I use VCP, or the "yellow" long code helper screens on VCDS) and the third screen simply translates the first screen entries into the language that the user sets on her/her account.
Or perhaps the third screen is the data that users have provided - if it is and given that the module info on the first screen is more authoritative - I suggest that it shouldn't be used at all and that the third screen should become the translated data !! As for the absence of the Byte/Bit information on these screens - I agree that it's a retrograde step. I see no reason why the Byte/Bit information can't be added to the description screen - and if this is done, the Byte/Bit screen (on both OSs) can be deleted entirely! Keep up the good work - you are a valuable resource for us mere mortals in identifying these issues to the OBD11 deities!!  Don |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 20, 2020 8:49:26 GMT
Thanks for the kind words,
The screen with the car is Descriptions are provided by vehicle manufacturer
The screen with people is the Descriptions are provided by OBD11 Community etc, Untested, dont rely on them etc etc
The screen with 010101 is the Raw data and does not provide any descriptions, Long coding can be changed in raw bytes/bits format.
Feedback I got from my Friends in Spain is the same and like me whilst the new IOS Screens may look pretty they do not offer as much info on the screen as the Android equiv one's. Enough Moaning by me I have given my feedback to obdeleven dev team@obdeleven and we will have to wait and see if they change.
|
|
|
|
Post by Thirsty on Jun 20, 2020 10:37:14 GMT
@testeronline i think you've tagged the wrong "OBDeleven" user  And a little reminder on the quote function ( read more here): "07. It is generally forbidden to QUOTE the message immediately above yours, use the REPLY button to keep the Topic cleanest and fastest to read.
QUOTE function can be used to reply to older messages or to multi reply." |
|
