Skip to content

Commit 77ffba3

Browse files
malysclaude
andcommitted
release: EVABRPUploader 2.1.8 — the weather answers were arriving, and being discarded
EVHardware 1.6.0 settles what 2.1.7 timed the map query to find out. The reply parcel was read one int too early: a nullable parcelable argument is written as a presence flag and then the object, so every field landed in the next one's place, the payload's type tag no longer matched, and an answer that had arrived was reported as unreadable. The service was bound, the query was answered, and the reading was thrown away on the way back — which is exactly the map=bound with nothing behind it that the log kept showing. So ext_temp now has a source that does not depend on catching a broadcast at the moment the weather app happens to refresh. The broadcast path stays where it is, ahead of the query: it is free when it has a reading, and the two disagreeing would itself be worth seeing in the log. Nothing in this app changed but the submodule pointer and the version. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
1 parent 33839ab commit 77ffba3

3 files changed

Lines changed: 15 additions & 3 deletions

File tree

‎CHANGELOG.md‎

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,18 @@ All notable changes to this project are documented here. Format follows
44
[Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versions follow
55
[Semantic Versioning](https://semver.org/spec/v2.0.0.html).
66

7+
## [2.1.8] - 2026-08-26
8+
9+
### Fixed
10+
11+
- **The weather answers arrived all along; they were being thrown away.** EVHardware read the
12+
reply parcel one int too early — a nullable parcelable argument is written as a presence flag
13+
and then the object, so every field landed in the next one's place, the payload's type tag
14+
never matched, and a reading that had arrived was reported as unreadable. That is precisely
15+
the `map=bound` with nothing behind it that 2.1.7 timed the query to explain. Tracking
16+
EVHardware 1.6.0 fixes it, and `ext_temp` has a working source that does not depend on
17+
catching a broadcast at the right moment.
18+
719
## [2.1.7] - 2026-08-26
820

921
### Fixed

‎app/build.gradle‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,8 +34,8 @@ android {
3434
applicationId "com.evsuite.abrp"
3535
minSdk 27
3636
targetSdk 36
37-
versionCode 15
38-
versionName "2.1.7"
37+
versionCode 16
38+
versionName "2.1.8"
3939

4040
testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
4141
}

0 commit comments

Comments
 (0)