Timeline for Why is the FrameBuffer missing on some Android devices?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 27, 2021 at 12:00 | history | tweeted | twitter.com/StackAndroid/status/1354398803516923908 | ||
| Jan 10, 2021 at 22:28 | vote | accept | Yuuta Liang | ||
| Jan 10, 2021 at 13:56 | history | edited | Andrew T.♦ | CC BY-SA 4.0 |
copyedit, removed fluff
|
| Jan 10, 2021 at 13:17 | answer | added | peterh | timeline score: 3 | |
| Jan 7, 2021 at 22:05 | comment | added | Yuuta Liang | @IrfanLatif Thanks! This helped a lot. | |
| Jan 7, 2021 at 16:51 | comment | added | Irfan Latif |
Android's hardware implementation is totally vendor specific. There's no standardization. Many OEMs don't expose standard Linux interfaces in /dev, /sys, /proc, /config etc. Many syscalls don't work either. Instead OEM's closed-source HALs interact with hardware through different IPC's particularly Binders.
|
|
| Jan 5, 2021 at 4:40 | review | First posts | |||
| Jan 10, 2021 at 13:19 | |||||
| Jan 5, 2021 at 4:35 | history | asked | Yuuta Liang | CC BY-SA 4.0 |