export device properties#383
Conversation
There was a problem hiding this comment.
while you are at it, i would suggest changing the current TOLINO conditions to instead of just DEVICE.contentEquals("ntx_6sl")) to also check for MODEL.contentEquals("tolino") or only MODEL.contentEquals("tolino") (no other conditions)
also would suggest re-using TOLINO for the check for TOLINO_EPOS
for example the Vision5 getprop for ro.prop is
[ro.product.board]: [EVK]
[ro.product.brand]: [RakutenKobo]
[ro.product.cpu.abi2]: [armeabi]
[ro.product.cpu.abi]: [armeabi-v7a]
[ro.product.device]: [ntx_6sl]
[ro.product.display]: [eink]
[ro.product.hardwareType]: [E70K00]
[ro.product.lightGestureEnabled]: [true]
[ro.product.locale.language]: [en]
[ro.product.locale.region]: [US]
[ro.product.manufacturer]: [Rakuten Kobo Inc.]
[ro.product.model]: [tolino]
[ro.product.name]: [ntx_6sl]|
Not sure what your intention is here :/
I won't plan to change that. I'm also won't plan to change any other device check without a device owner reporting the corresponding stuff. And in that case I would add the new condition as an OR and never replace the check because that might screw things on previous devices that are already working fine. |
i though i might as well ask, because this would bring as for updating the conditions on see |
Frenzie
left a comment
There was a problem hiding this comment.
Annoying, but seems sensible enough.
|
Not breaking backward compatibility with brittle crap like this unfortunately trumps coding style ;). |
Same intent as #381 but exporting them all.
It makes possible to have very specific branches to workaround broken aosp devices, like
exports manufacturer, brand, device, model, product and hardware as strings and boolean values for
is_tolinoandis_boyueas both brands use some non AOSP keycodes.This change is