Talk:Libhybris
| This is the talk page for discussing improvements to the Libhybris article. This is not a forum for general discussion of the article's subject. |
Article policies
|
| Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
 | This article has not yet been rated on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||
| ||||||||||||||||||||||||
Adoption on the desktop
[edit]- Android's "no GPL or even LGPL in user-space" is childish; seeing that OpenWrt uses uClibc and runs quite well on 32MiB of RAM e.g. on the Ben NanoNote, cf. comparing OpenWrt to Android makes Google's claims, that libbionic has technical reasons and is not only about the darn license, rather questionable. However the problem with libbionic is not the license, but the fact that it does not aim to be compatible with glibc or uclibc and artificially and willingly introduced a serious incompatibility to the Linux kernel-based family of operating systems. So somebody felt obliged to write libhybris to work around this. oFono, the telephony stack adopted by Tizen and Ubuntu Touch is GPLv2 (only, no dual-license)
- E.g. the software CPU-Z was ported to Android but not to Linux. By installing libhybris on Debian, Fedora, Arch Linux, etc. CPU-Z and basically any Android-software that does not require the Android-kernel features binder, pmem, ashmem, etc., should just work, correct? User:ScotXWt@lk 13:17, 5 July 2014 (UTC)
- Interesting, but not the source is (currently) wrong about Replicant and hybris (not sure it was ever true..). And probably the reason OenWrt uses less memory is not (just) the C library but that Android needs memory for a big "GUI"/frambuffer (and OpenWrt non-GUI?). comp.arch (talk) 22:16, 5 June 2015 (UTC)
example for device drivers and libraries
[edit]Are there concrete examples for libraries and device drivers? User:ScotXWt@lk 08:17, 8 July 2014 (UTC)