Project

General

Profile

Graphics » History » Version 32

dl lud, 01/24/2020 07:59 PM
Rewrite as it is somewhat possible to use GPU an software rendering at the same time (for different apps/components).

1 1 Wolfgang Wiedmeyer
h1. Graphics
2
3 26 Denis 'GNUtoo' Carikli
h2. History
4 1 Wolfgang Wiedmeyer
5 32 dl lud
Replicant doesn't rely on the dedicated graphics processor (GPU) for accelerated graphics rendering. Instead it uses the CPU with a technique known as software rendering. Software rendering is the reason why Replicant devices appear slow at times and is responsible for a lot of crashes that can happen during usage.
6 26 Denis 'GNUtoo' Carikli
7 32 dl lud
At the beginning of Replicant, using the GPU required non-free software on all of the supported devices. As of today free-software replacements exist for some (but not all) the GPUs used in Replicant compatible devices, but the drivers are not ready yet for Replicant.
8 26 Denis 'GNUtoo' Carikli
9 32 dl lud
These drivers implement a subset of the OpenGL ES (GLES) API, and don't support Vulkan, which is now the default for the latest Android versions. They still need to be integrated in Replicant in a way that doesn't make things worse. For instance, due to their incomplete implementation of GLES, it may be needed to configure Replicant to use software rendering for specific apps or system components.
10 26 Denis 'GNUtoo' Carikli
11 32 dl lud
There are more details on the various options we are considering in the [[GraphicsResearch]] and [[GraphicsReplicant9]] wiki pages. 
12 26 Denis 'GNUtoo' Carikli
13
h2. Using llvmpipe
14
15 18 dl lud
Until [[Images#Replicant-60-0003-images|version 6.0 0003]], Replicant used the [[GraphicsResearch#Android-software-renderer|Android software renderer]], also known as libagl. libagl is fast, but [[Graphics#Known-issues-with-libagl|caused several issues]] due to lack of OpenGL ES (GLES) 2.0 support.
16 16 doak complex
17 18 dl lud
As of "Replicant 6.0 0004 rc1":https://ftp.osuosl.org/pub/replicant/images/replicant-6.0/0004-rc1/, [[GraphicsResearch#Mesas-llvmpipe|llvmpipe]] is used as the default software renderer. llvmpipe has a more complete GLES implementation than libagl (see #705), so more apps work with it, like Firefox-based browsers or more recent WebViews (see #1780). Unfortunately, llvmpipe is too slow for certain system components, which may also be true for some apps. Furthermore, certain apps still crash with llvmpipe, although less frequently. Usually the screen stays black if an app does not work with llvmpipe.
18 16 doak complex
19 1 Wolfgang Wiedmeyer
To cater for these issues, Replicant 6.0 0004 includes a "mechanism to choose between llvmpipe and ligagl, on a per process basis":https://lists.osuosl.org/pipermail/replicant/2019-August/002054.html. Such mechanism is "actually used":https://lists.osuosl.org/pipermail/replicant/2020-January/002421.html on the Replicant 6.0 0004 images to force some system components (bootanimation, SurfaceFlinger and system_server) to use libagl.
20 17 dl lud
21 26 Denis 'GNUtoo' Carikli
h3. Methods to choose the software renderer
22 1 Wolfgang Wiedmeyer
23
For all the methods bellow you must have [[ADB]] installed on your computer. Make sure that it can access the device's [[ADB#Accessing-root-shell|root shell]] and that the [[ADB#Modifying-the-system-partition|system partition is mounted as writable]].
24 19 dl lud
25 27 Denis 'GNUtoo' Carikli
h4. Choosing the default software renderer on Replicant 0003
26 17 dl lud
27 1 Wolfgang Wiedmeyer
The following command switches between llvmpipe and libagl:
28
<pre>
29
adb shell "grep -q "ro.libagl=1" /system/build.prop && sed "s/ro.libagl=1/ro.libagl=0/" -i /system/build.prop || sed "s/ro.libagl=0/ro.libagl=1/" -i /system/build.prop" 
30 17 dl lud
</pre>
31 1 Wolfgang Wiedmeyer
32
Then reboot the device. To switch back to previous renderer, run the above command again and reboot the device.
33 27 Denis 'GNUtoo' Carikli
34
This method works on both Replicant 6.0 0003 and 0004. Do note that: on 0003 you will start with libagl by default, whereas on 0004 the default is llvmpipe.
35
36
h4. Choosing the default software renderer on Replicant 0004
37
38
The following command switches everything back to libagl:
39
<pre>
40
androidsw.sh
41
</pre>
42
43
And to switch back to the default (libagl for some system components, and llvmpipe for all the rest)
44
<pre>
45
llvmpipe.sh
46
</pre>
47
48
Then the device will reboot.
49 20 dl lud
50 18 dl lud
This method works on both Replicant 6.0 0003 and 0004. Do note that: on 0003 you will start with libagl by default, whereas on 0004 the default is llvmpipe.
51 19 dl lud
52 26 Denis 'GNUtoo' Carikli
h4. Choosing the software renderer for a specific app
53 18 dl lud
54 19 dl lud
# Find out the app ID. Example: @org.gnu.icecat@
55 18 dl lud
# Force the app to always use libagl by creating empty file named @libGLES_android@ on it's data directory (e.g. @/data/data/org.gnu.icecat/@). Example command:
56 1 Wolfgang Wiedmeyer
<pre>
57 18 dl lud
adb shell touch /data/data/org.gnu.icecat/libGLES_android
58 19 dl lud
</pre>
59 24 dl lud
To force llvmpipe instead, use a file named @libGLES_mesa@.
60 19 dl lud
# Restart the app. For instance: kill it and open again.
61 1 Wolfgang Wiedmeyer
# Get back to the default renderer by removing the file. Example command:
62
<pre>
63
adb shell rm /data/data/org.gnu.icecat/libGLES_android
64
</pre>
65
66
This method only works for Replicant 6.0 0004.
67
68 26 Denis 'GNUtoo' Carikli
h4. Choosing the software renderer for a system component
69 1 Wolfgang Wiedmeyer
70 28 Denis 'GNUtoo' Carikli
The following method only works for Replicant 6.0 0004.
71
72 1 Wolfgang Wiedmeyer
System components usually lack a directory in the data partition. Thus, another method must be used to switch their software renderer.
73
74 28 Denis 'GNUtoo' Carikli
# Find out the process name. This can be done by getting the process pid with @ps@ or @pidof@ and then looking at /proc/<pid>/cmdline. 
75
76
For instance for surfaceflinger:
77 1 Wolfgang Wiedmeyer
<pre>
78 28 Denis 'GNUtoo' Carikli
shell@i9300:/ $ pidof surfaceflinger
79
1984
80
shell@i9300:/ $ cat /proc/1984/cmdline ; echo                                  
81 1 Wolfgang Wiedmeyer
/system/bin/surfaceflinger
82
</pre>
83 28 Denis 'GNUtoo' Carikli
Here the process name is @/system/bin/surfaceflinger@.
84
85
or for system_server:
86 1 Wolfgang Wiedmeyer
<pre>
87 28 Denis 'GNUtoo' Carikli
shell@i9300:/ $ pidof system_server
88
2362
89
shell@i9300:/ $ cat /proc/2362/cmdline ; echo                                  
90
system_server
91
</pre>
92
Here the process name is @system_server@.
93
94
# Force the component to always use libagl by creating an empty file at @/system/etc/libGLES_android/<process_name>@.
95
96
For surfaceflinger:
97
<pre>
98 1 Wolfgang Wiedmeyer
adb shell mkdir -p /system/etc/libGLES_android/system/bin
99
adb shell touch /system/etc/libGLES_android/system/bin/surfaceflinger
100
</pre>
101 28 Denis 'GNUtoo' Carikli
Or for system_server:
102
<pre>
103
adb shell mkdir -p /system/etc/libGLES_android/
104
adb shell touch /system/etc/libGLES_android/system_server
105
</pre>
106
107 1 Wolfgang Wiedmeyer
To force llvmpipe instead, create the file under @/system/etc/libGLES_mesa/@.
108 19 dl lud
# Reboot your device, or restart the specific system component individualy (if possible).
109 28 Denis 'GNUtoo' Carikli
# Get back to the default renderer by removing the file.
110
111
For surfaceflinger:
112 1 Wolfgang Wiedmeyer
<pre>
113
adb shell rm /system/etc/libGLES_android/system/bin/surfaceflinger
114
</pre>
115 19 dl lud
116 28 Denis 'GNUtoo' Carikli
For system_server:
117
<pre>
118
adb shell rm /system/etc/libGLES_android/system_server
119
</pre>
120 19 dl lud
121 1 Wolfgang Wiedmeyer
h2. Known issues with libagl
122 16 doak complex
123 14 doak complex
* Selecting the third option besides photo and video (Panorama mode) will crash the Camera app.
124
* Video playback in the browser does not work. (issue #1533)
125
* Screenshots do not work. (see [[Screenshots]] for a workaround)
126 1 Wolfgang Wiedmeyer
* Selecting wallpapers from storage does not work.
127
* Screen content is sometimes shortly visible before unlocking. (issue #1275, happens with llvmpipe as well)
128
* Previews of the windows in the tasks switcher are missing.
129
* Switching between apps, apps and the launcher or different views inside an app is sometimes slow and the device may seem unresponsive.
130
* There are issues with using folders with the Trebuchet launcher. (issue #1790, happens with llvmpipe as well)
131 14 doak complex
132 19 dl lud
h3. Popular apps from F-Droid that do not work with libagl
133 14 doak complex
134 16 doak complex
* All Firefox-based browsers like "IceCatMobile":https://f-droid.org/repository/browse/?fdfilter=icecat&fdid=org.gnu.icecat and Orfox
135 1 Wolfgang Wiedmeyer
* "Document Viewer":https://f-droid.org/repository/browse/?fdfilter=document+viewer&fdid=org.sufficientlysecure.viewer
136
* "LibreOffice Viewer":https://f-droid.org/repository/browse/?fdfilter=libreoffice&fdid=org.documentfoundation.libreoffice
137 16 doak complex
* "RedReader":https://f-droid.org/repository/browse/?fdfilter=redreader&fdid=org.quantumbadger.redreader cannot display images ("upstream bug":https://github.com/QuantumBadger/RedReader/issues/279)
138 2 Wolfgang Wiedmeyer
139 19 dl lud
h2. Known issues with llvmpipe
140
141
* Too slow to use in SurfaceFlinger (screen compositor).
142
* If SurfaceFlinger uses llvmpipe, Gallery and Orbot render some GUI elements are visible while the main screen is black. The GUI of Simple File Manager works as long as no image is viewed in fullscreen.
143
144 8 Denis 'GNUtoo' Carikli
h2. See also
145 9 Denis 'GNUtoo' Carikli
146 19 dl lud
There is a page about [[GraphicsResearch]] that gathers information to improve graphics support.