Status Update
Comments
ma...@gmail.com <ma...@gmail.com> #2
Not sure why this code is doing:
val child2binding = ChildInsideBinding.bind(inside.findViewById(R.id.inside_child))
instead of
val child2binding = ChildInsideBinding.bind(inside)
inside.findViewById(R.id.inside_child)
returns
<LinearLayout
android:id="@+id/inside_child"
android:layout_width="match_parent"
android:layout_height="match_parent">
<TextView
android:text = "I'm child"
android:layout_width="match_parent"
android:layout_height="match_parent"/>
</LinearLayout>
but the binding expects:
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
android:layout_width="match_parent"
android:layout_height="match_parent">
<LinearLayout
android:id="@+id/inside_child"
android:layout_width="match_parent"
android:layout_height="match_parent">
<TextView
android:text = "I'm child"
android:layout_width="match_parent"
android:layout_height="match_parent"/>
</LinearLayout>
</LinearLayout>
We needed to make
I'm guessing this code val child2binding = ChildInsideBinding.bind(inside.findViewById(R.id.inside_child))
is like that for the purposes of repro. Can you add more details on what you are trying to achieve?
ViewBinding is generated per layout hierarchy when it happens to work w/ a different layout, it is more of a luck (unreliable) than desired behavior.
jo...@nordprojects.co <jo...@nordprojects.co> #3
sm...@google.com <sm...@google.com>
ch...@fendt.nom.fr <ch...@fendt.nom.fr> #4
that seems like a different problem with caching. If you can reproduce it, that would be great.
bo...@gmail.com <bo...@gmail.com> #5
ph...@gmail.com <ph...@gmail.com> #6
Can you add more details on what you are trying to achieve?
Sorry for late reply.
To help my colleagues understand, I've already shared the following snippet:
As I already commented, this is a breaking change, and IMHO, this should be announced on release notes.
nh...@myfairpoint.net <nh...@myfairpoint.net> #7
I agree, this should've been covered in the release notes. Apologies.
It is not a breaking change as in API guarantees (we almost never allow that) but it is a breaking undefined behavior change that does require updating release notes.
I was wondering, what is the use case for doing this? I understand it used to work but it is basically passing ViewBinding a totally different view (while there is a 1-1 mapping between layout files and view binding). So it was not intended to work for that case. e.g. in data binding, we update layout files in the pipeline to avoid this but in view binding we don't (has additional cost but data binding needs it for other stuff) which allowed this to happen even though it was not designed for.
ga...@gmail.com <ga...@gmail.com> #8
am...@google.com <am...@google.com> #9
We are currently evaluating this support internally and the timeline for when this can be available. Please subscribe to this bug for updates.
li...@gmail.com <li...@gmail.com> #10
ga...@gmail.com <ga...@gmail.com> #11
wa...@googlemail.com <wa...@googlemail.com> #12
sh...@gmail.com <sh...@gmail.com> #13
di...@gmail.com <di...@gmail.com> #14
supporting pi 3 b+ is the most expected.
specially for hobbyist.
ac...@gmail.com <ac...@gmail.com> #15
bo...@gmail.com <bo...@gmail.com> #16
kh...@sycomore.vn <kh...@sycomore.vn> #17
ch...@fendt.nom.fr <ch...@fendt.nom.fr> #18
this means (with housing, carrier board, ...) devices >= $200 !!!!!
What a crap .... :-(
ga...@gmail.com <ga...@gmail.com> #19
ro...@gmail.com <ro...@gmail.com> #21
My company has developed an Android Things based product with a retail point of under $150. Production was planned to begin once Android Things was production ready for delivery prior to this Christmas season. Glad to see Android Things 1.0 is out and production ready, but sadly, without a $30 SoM like the RPi 3, RPi3+ or RPi Zero, the product is sunk.
ch...@fendt.nom.fr <ch...@fendt.nom.fr> #22
It is good to know that “we are still working on it internally”... but the “security” requirement on the production HW won’t be fulfilled by the R-Pi 3+ !
Muss we understand that the R-Pi 3+ will only be (later) available for dev/ tests ? Because it won’t help to reduce the entry ticket!!! A computer for $30 and a SOM for $130 it is a big big difference!!! It the base system has its cost multiply by 5, I think that the platform looses a lot of its interest!
ga...@gmail.com <ga...@gmail.com> #23
ji...@gmail.com <ji...@gmail.com> #24
mu...@gmail.com <mu...@gmail.com> #25
sw...@gmail.com <sw...@gmail.com> #26
[Deleted User] <[Deleted User]> #27
be...@gmail.com <be...@gmail.com> #28
pe...@163.com <pe...@163.com> #29
ma...@gmail.com <ma...@gmail.com> #30
ma...@gmail.com <ma...@gmail.com> #31
al...@gmail.com <al...@gmail.com> #32
I am willing to have AoT soon for Raspberry PI 3B+
jm...@gmail.com <jm...@gmail.com> #33
mj...@gmail.com <mj...@gmail.com> #34
er...@gmail.com <er...@gmail.com> #35
rs...@gmail.com <rs...@gmail.com> #36
ch...@fendt.nom.fr <ch...@fendt.nom.fr> #37
No the problem is the support!!!!
We need an official support as “production platform” for the raspberry 3 (+) !
ra...@gmail.com <ra...@gmail.com> #38
zo...@gmail.com <zo...@gmail.com> #39
Please give this a higher prio. Thanks.
[Deleted User] <[Deleted User]> #40
ha...@gmail.com <ha...@gmail.com> #41
kn...@gmail.com <kn...@gmail.com> #42
While the documentation clearly states that the R-Pi 3 B is supported, I think it would make sense to temporarily add a warning that the R-Pi 3 B+ is NOT yet supported.
li...@gmail.com <li...@gmail.com> #43
cf...@gmail.com <cf...@gmail.com> #44
rz...@gmail.com <rz...@gmail.com> #45
gu...@gmail.com <gu...@gmail.com> #46
pa...@gmail.com <pa...@gmail.com> #47
we...@gmail.com <we...@gmail.com> #48
[Deleted User] <[Deleted User]> #49
ch...@fendt.nom.fr <ch...@fendt.nom.fr> #50
This board has an ArM v6 abi, not v7! This implies a lot of rework... on the other side, the difference between the PI 3 B and 3 B+ are very very small. The 3B+ support must be very very easy !
If google don’t do it, It means that the raspberry platform will be completely abandoned in a near futur... :-(
[Deleted User] <[Deleted User]> #51
sc...@onyxtop.com <sc...@onyxtop.com> #52
jo...@gmail.com <jo...@gmail.com> #53
[Deleted User] <[Deleted User]> #54
ga...@linklabs.io <ga...@linklabs.io> #55
le...@google.com <le...@google.com>
[Deleted User] <[Deleted User]> #56
[Deleted User] <[Deleted User]> #57
ch...@fendt.nom.fr <ch...@fendt.nom.fr> #58
I expect a release with an official support soon!!!
(And please, not only développement platform!!! Please, please, please...)
64...@gmail.com <64...@gmail.com> #59
Dear Google,
Every one is desperately waiting for a Raspberry Pi production device for
AndroidThings :D
On Tue, 19 Jun 2018, 1:06 pm , <buganizer-system@google.com> wrote:
sm...@gmail.com <sm...@gmail.com> #60
ro...@gmail.com <ro...@gmail.com> #61
ja...@gmail.com <ja...@gmail.com> #62
de...@gmail.com <de...@gmail.com> #63
lo...@gmail.com <lo...@gmail.com> #64
ad...@gmail.com <ad...@gmail.com> #65
ca...@gmail.com <ca...@gmail.com> #66
ca...@gmail.com <ca...@gmail.com> #67
ke...@gmail.com <ke...@gmail.com> #68
in...@gmail.com <in...@gmail.com> #69
li...@gmail.com <li...@gmail.com> #70
b-...@web.de <b-...@web.de> #71
jo...@hex-factory.de <jo...@hex-factory.de> #72
sw...@gmail.com <sw...@gmail.com> #73
Please provide support for Raspberry pi 3b+ board.
ca...@gmail.com <ca...@gmail.com> #74
ra...@gmail.com <ra...@gmail.com> #75
bm...@gmail.com <bm...@gmail.com> #76
ya...@gmail.com <ya...@gmail.com> #77
do...@gmail.com <do...@gmail.com> #78
de...@onsolution.com.au <de...@onsolution.com.au> #79
pa...@avtechcorp.com <pa...@avtechcorp.com> #80
ga...@gmail.com <ga...@gmail.com> #81
gz...@gmail.com <gz...@gmail.com> #82
yu...@gmail.com <yu...@gmail.com> #83
bo...@gmail.com <bo...@gmail.com> #84
st...@gmail.com <st...@gmail.com> #85
sa...@gmail.com <sa...@gmail.com> #86
co...@gmail.com <co...@gmail.com> #87
mr...@gmail.com <mr...@gmail.com> #88
da...@googlemail.com <da...@googlemail.com> #89
rf...@gmail.com <rf...@gmail.com> #90
da...@gmail.com <da...@gmail.com> #91
se...@orange.fr <se...@orange.fr> #92
ch...@gmail.com <ch...@gmail.com> #93
bo...@gmail.com <bo...@gmail.com> #94
vi...@spotify.com <vi...@spotify.com> #95
ch...@gmail.com <ch...@gmail.com> #96
[Deleted User] <[Deleted User]> #97
- Everybody following this thread for insightful responses will receive an email from you.
- A junk comment thread like these often results in Google locking the thread such that nobody can share useful comments.
- Fluff comments are useless; in the ten years using Google's issue tracker, frequent commenting on issues has never affected the prioritization and triage of issues.
Please be courteous and star the issue instead.
As of this writing, Raspberry Pi 3 B+ is not one of the supported devices, although Google has been looking into supporting it "in the future". For a complete list of supported Android Things devices, see this issue:
ar...@gmail.com <ar...@gmail.com> #98
je...@gmail.com <je...@gmail.com> #99
rg...@bitib.cl <rg...@bitib.cl> #100
ra...@gmail.com <ra...@gmail.com> #101
ng...@gmail.com <ng...@gmail.com> #102
to...@gmail.com <to...@gmail.com> #103
yu...@gmail.com <yu...@gmail.com> #104
sa...@getparking.in <sa...@getparking.in> #105
aj...@gmail.com <aj...@gmail.com> #106
th...@gmail.com <th...@gmail.com> #107
ka...@gmail.com <ka...@gmail.com> #108
ma...@gmail.com <ma...@gmail.com> #109
da...@gmail.com <da...@gmail.com> #110
Please be courteous and star the issue instead.
As of this writing, Raspberry Pi 3 B+ is not one of the supported devices, although Google has been looking into supporting it "in the future". For a complete list of supported Android Things devices, see this issue:
ip...@gmail.com <ip...@gmail.com> #111
Support Raspberry Pi 3 B+ Board, please!!!
ne...@google.com <ne...@google.com>
iq...@google.com <iq...@google.com>
di...@lightning.istanbul <di...@lightning.istanbul> #112
el...@gmail.com <el...@gmail.com> #113
le...@gmail.com <le...@gmail.com> #114
ha...@gmail.com <ha...@gmail.com> #115
le...@wearemobilefirst.com <le...@wearemobilefirst.com> #116
mi...@schomaecker-gmbh.com <mi...@schomaecker-gmbh.com> #117
m9...@gmail.com <m9...@gmail.com> #118
ch...@fendt.nom.fr <ch...@fendt.nom.fr> #119
Is blocked by another issue without external visibility...
No production platform available (since May, we got only the coming soon... one SOM was planned for delivery end of June, and now is coming soon...), the i.MX6 platform is not supported anymore...
Last news on the official website: 1.0 release (May 2018)...
We are now in November, no official news about the support, the Pi3+ is available since more than 7 months: I think we can all understand that we will get nothing this year (i’m not sure we get something!)
:-(
mi...@gmail.com <mi...@gmail.com> #120
ir...@gmail.com <ir...@gmail.com> #121
ki...@gmail.com <ki...@gmail.com> #122
wa...@gmail.com <wa...@gmail.com> #123
ky...@gmail.com <ky...@gmail.com> #124
ow...@googlemail.com <ow...@googlemail.com> #125
mi...@gmail.com <mi...@gmail.com> #126
mi...@gmail.com <mi...@gmail.com> #127
al...@gmail.com <al...@gmail.com> #128
kh...@gmail.com <kh...@gmail.com> #129
ko...@gmail.com <ko...@gmail.com> #130
rb...@gmail.com <rb...@gmail.com> #131
I can not buy B, only B+
bp...@gmail.com <bp...@gmail.com> #132
al...@gmail.com <al...@gmail.com> #133
da...@gmail.com <da...@gmail.com> #134
lu...@gmail.com <lu...@gmail.com> #135
ma...@gmail.com <ma...@gmail.com> #136
gr...@gmail.com <gr...@gmail.com> #137
mi...@gmail.com <mi...@gmail.com> #138
11...@life.hkbu.edu.hk <11...@life.hkbu.edu.hk> #139
kp...@gmail.com <kp...@gmail.com> #140
ph...@gmail.com <ph...@gmail.com> #141
ch...@fendt.nom.fr <ch...@fendt.nom.fr> #142
6 months after release, the “coming soon” production platform are still not available. Even worrth : the SDA212 “learn more” link is now pointing to a 404 http error page!
Since my post one month ago, nothing has changed!
No visibility, no production platform, no communication, no roadmap...
It’s more and more frustrating!
Do we have to consider alternative?
kn...@gmail.com <kn...@gmail.com> #143
me...@gmail.com <me...@gmail.com> #144
pa...@gmail.com <pa...@gmail.com> #145
ry...@gmail.com <ry...@gmail.com> #146
an...@gmail.com <an...@gmail.com> #147
de...@gmail.com <de...@gmail.com> #148
gi...@gmail.com <gi...@gmail.com> #149
ts...@gmail.com <ts...@gmail.com> #150
ma...@gmail.com <ma...@gmail.com> #151
tr...@gmail.com <tr...@gmail.com> #152
b....@gmail.com <b....@gmail.com> #153
eh...@gmail.com <eh...@gmail.com> #154
ma...@gmail.com <ma...@gmail.com> #155
ma...@gmail.com <ma...@gmail.com> #156
[Deleted User] <[Deleted User]> #157
yu...@hotmail.com <yu...@hotmail.com> #158
sd...@googlemail.com <sd...@googlemail.com> #159
I guess it is time to search for a more maintained Plattform
fs...@gmail.com <fs...@gmail.com> #160
It's a shame. People can do great things with this devices. I don't know wich "more maintained platform" to migrate to.
gi...@gmail.com <gi...@gmail.com> #161
ga...@gmail.com <ga...@gmail.com> #162
mr...@neotel.com.ar <mr...@neotel.com.ar> #163
r....@gmail.com <r....@gmail.com> #164
ra...@gmail.com <ra...@gmail.com> #165
44...@gmail.com <44...@gmail.com> #166
ma...@gmail.com <ma...@gmail.com> #167
ke...@gmail.com <ke...@gmail.com> #168
[Deleted User] <[Deleted User]> #169
It is still more robust that Windows on the RPi 3b, but Windows10 IoT now
has support for the 3b+. I'm not sure if there is an official build yet
but I have successfully loaded a preview release on it (from Windows
Insiders).
Matthew Monacelli
Senior Software Developer
Vertique
115 Vista Blvd.
Arden, NC 28704
matthew.monacelli@vertique.com
(828) 654-7500 x152 office
(828) 654-8908 fax
On Mon, Jan 7, 2019 at 6:46 AM <buganizer-system@google.com> wrote:
pa...@gmail.com <pa...@gmail.com> #170
jr...@gmail.com <jr...@gmail.com> #171
jc...@gmail.com <jc...@gmail.com> #172
al...@gmail.com <al...@gmail.com> #173
aj...@gmail.com <aj...@gmail.com> #174
ad...@gmail.com <ad...@gmail.com> #175
and it is almost a year
st...@gmail.com <st...@gmail.com> #176
"Given the successes we have seen with our partners in smart speakers and smart displays, we are refocusing Android Things as a platform for OEM partners to build devices in those categories moving forward. Therefore, support for production System on Modules (SoMs) based on NXP, Qualcomm, and MediaTek hardware will not be made available through the public developer platform at this time."
"Android Things continues to be a platform for experimenting with and building smart, connected devices using the Android Things SDK on top of popular hardware like the NXP i.MX7D and Raspberry Pi 3B. System images for these boards will remain available through the Android Things console where developers can create new builds and push app updates for up to 100 devices for non-commercial use."
ga...@gmail.com <ga...@gmail.com> #177
64...@gmail.com <64...@gmail.com> #178
ga...@gmail.com <ga...@gmail.com> #179
ch...@fendt.nom.fr <ch...@fendt.nom.fr> #180
Or something like this...
Please make it official that this becomes clear for all...
This adventure was a waste of time... back to Debian... I need infrastructure for the deployment of my app, but I won’t be disappointed anymore...
->
m9...@gmail.com <m9...@gmail.com> #181
I guess we should all use this issue to share alternatives now. Anybody tried Ubuntu IOT?
Description