Forum Diskio Pi

All the Open Source in one device.

You are not logged in.

#1 English forum » Diskio Pi, an HD touch screen (kit) compatible with Raspberry Pi » 2018-11-17 10:56:26

Replies: 0

The project has attracted a lot of interest and specialist press articles since 2017. A prototype was already funded last year by Ulule. This article tells how the idea grew and developed into today's crowdfunding.


The idea

The idea of the Diskio Pi came to me in 2015, with the purchase of an Orange Pi board (SoC A20). The novelty of the time was the possibility to install Android, something impossible on Raspberry Pi (1) B. But the proposed Android didn't handle touch, I had to compile the sources myself.

The first prototype, in 17", was big enough for me to insert all the boards and batteries. It was from the second prototype that the size of 13'3 was chosen. But the too thick design of this version 2 was to be reviewed, as well as its price.


It is therefore this third prototype that is currently being proposed, still in 13'3. Unfortunately, all parts will be manufactured in China (except perhaps the packaging), a prerequisite for offering an acceptable selling price. The name Diskio (δισκίο)comes from the modern Greek word "tablet" in English.) comes from the modern Greek word "tablet" in English.

Later, I realized that it could be interpreted as disk I/O, and it fits the project well ! The logo was quickly found thanks to an online logo generator. Don't bother with that. Basically, a hexagon (like France map) with squares representing the different compatible machines.


Many of you are curious to know how I managed to make the prototypes. In this article, I try to briefly explain the main stages of development.

From the idea of design to prototyping, there is only one step. But how do we do that? What are the mistakes to avoid? Here is a brief summary of the main steps and difficulties I encountered. First of all, there is the screen part. And it's pretty simple, though. Here is a 16/10 screen recovered from an old laptop to make a secondary screen; manufactured 3 years ago, it still works:


There are many online vendors who offer display controller boards. By noting the reference of the screen, it’s easy to find the corresponding boards. Then, the most appropriate one is chosen, depending on the project and the type of video input desired. In general, it is VGA, sometimes HDMI or DVI. The salespeople are usually very cooperative and will help you. Do not hesitate to write to them for details and advices.

The 0.1 prototype

The first prototype of the Diskio Pi is the continuation of this screen design, with the integration of an Orange Pi and a battery. Here's what it can be:


As a case, I used a laptop cooler chassis, removing the fans, and planing anything that exceeded. The top frame is printed in fablab. In the end, we get a happy bazaar:


The principle of this prototype is the same as on the last one: a general power supply, a buck that converts 12V (or 9V) to 5V, batteries that charge to 12V and deliver 5V. All this with a powered HUB and the video board, itself connected to the PC board via HDMI (here, we have an extra VGA stage).
For the battery, an external battery for laptop dismantled is fine. Be careful with the PCB balance so as not to create short circuits! LiPos are quite sensitive, and can catch fire. The idea of the mouse dismounted for the home button was abandoned on prototype 0.3.

The prototype 0.2

This version already looks better:


There is one of the two brackets of the screen, the screen board (HDMI this time, the VGA connector being unsoldered), and a drawer with a backplane connector. This idea was also abandoned for economic reasons. Same thing for the audio amp, the screen board has an integrated amp, why not use it? This has been done on prototype 3.

This time the case is printed in 3D by a professional for a budget of about 250€. All that remains is to sand and coat it with a resin to obtain a smooth finish. For the HUB, it's always recovery, at least an existing board. The boards that collect the HDMI and USB signals from the nano PC are designed by an electronics engineer (with Kicad software) and then soldered by hand. As prototypes are made, they are manufactured, improved and sometimes repeated...
This prototype suffered from a thickness that was too visible and a design that was too massive. It was necessary to start from scratch to imagine the third prototype.

The prototype 0.3


Standard electronic components are not so expensive, but as soon as you want to have custom-made products manufactured, even a cable sample costs a minimum of 100€. To finance this prototype, we used crowdfunding. The cost of the case exceeding my personal budget (about 300€), the challenge is not to make too much mistake about the 3D drawing. To do this, look around you: all plastic objects have been studied, tested and approved. By dismantling laptops, you can get inspiration and take a caliper, measuring thicknesses, diameters, how reinforcements are placed,
etc. It is in a way a reverse engineering work that I applied to plastics processing, in addition to the advice of Chinese suppliers (who are ready to do anything to help and win a potential market).


For the CAD, each part is modeled with 1/10 mm accuracy. Electronic boards and their main components are also modeled. The result is a virtual assembly that must be manipulated and visualized from all angles, without forgetting anything. And it takes a long time. All options should be thought in advance, and if possible options that are not thought out. That's why I placed 4 PCB screwing pads above the L board, to have all the available surface area "just in case".

The CAD was then sent to a plasturgist in China for manufacture. To save as much as possible, I chose to make it in white ABS, and then paint it with acrylic paint.


Placing the elements on the framework went as planned, despite deformation of the parts due to heat during transport (it was in June). After a short hot water bath of the deformed parts, the first assembly worked the first time.


The daughter board had to be pre-prototyped before being manufactured in its own right. The electronics engineer took care of the welds and the first tests before sending it to me. So I made the final adjustments and replaced some component values to get what I wanted.
Then, I ordered the corrected PCBs and soldered the final prototype board (exceptsome CMS components, which were not equipped).


For the mechanical side, the main one worked. The hinge to close the cover is very practical, it can be opened and closed quickly with 3 screws. The removable and reversible stand is also functional, although an improvement will have to be made to remove it by hand, and to allow the GPIO tablecloth to pass through (see below).

However, the clips on the side did not work. I have to tilt them to apply a spring effect, and enlarge the hooks. All this without it being too fragile. Some other details need to be improved, such as the fixing of the Raspberry Pi plate on the main frame.
In general, I wasn't too wrong.
For version 1.0, other prototypes (0.3.1 and 0.3.2) must be manufactured before serial production. For the manufacture of this one, I did not encounter too many difficulties, thanks to Benjamin for his ideas. Apart from the unexpected heat stroke, all the suppliers played along and delivered what we had agreed by exchanging emails. The
battery supplier also has some merit because we spent a lot of time and dozens of emails before I ordered 5 packs with PCM board... But so that in the end the batteries are the right size and with a very correct capacity.

When it comes to traps when drawing, it's always wanting lots of features, and sometimes it's limitless. You have to try to balance ergonomics and economy, because sometimes it is feasible but too expensive, or it prevents another feature from working properly. Nevertheless, we must think of all the eventualities, a little bit when programming a script: if we multiply the functionalities, we must also multiply the eventualities of use.

The product offered for pre-sale

The final product will be a kit, with all the parts needed to manufacture a 13'3" high definition touch screen, compatible with nano PC boards such as Raspberry Pi or Odroid. The kit will be composed of boards already populated, no soldering will be necessary for the assembly.

Why a kit?

Several reasons have guided me towards this solution:
Potential buyers already know the development boards, so they are able to assemble their own devices. It is also a game for some of us!

For a paradigm shift. We all know that most disboarded electronic products pollute. If the user knows how to assemble a device, he will be able to dismantle it, and thus repair it more easily if an element is damaged. Therefore, only the element that is obsolete or broken is replaced.

In order to save money: the assembly of our devices has a cost, which would then be saved (although partially offset by packaging).

The final device will therefore be a desktop-tablet hybrid, ready to accommodate Raspberry Pi 1/2/3 B/B+ or Zero, but also Odroids C1+/C2/XU4. Any other board with the Raspberry Pi form factor is also compatible, if its power supply does not exceed 5V and 4A.
The Diskio Pi can also be used as an independent display for a laptop or game console, with a resolution of 1920x1080.


The assembly

The assembly will not require any special knowledge, no welding (except in extreme cases), no glue. You will need a pair of scissors, a cutter and tape. The kit will be delivered with a small screwdriver and a double-sided roller for the assembly of the screen (composed of the screen itself and the touch glass).
The gluing of the screen will be precise, as it is guided by the placement of the plastic frame on the frame. If necessary, you will need a mini drill for the VESA options (coming soon) and to place the OSD buttons at the front: useful if the device is recessed.

An accurate assembly booklet will help you through all assembly steps, with supporting diagrams (at LEGO).

Here are the main parts (off screen):


Each cable has a different coding for added security. For example, 9V, 7.4V and 5V power supplies will have a different connector. Here, we see 2 battery packs. Each pack being composed of 2 cells, the 4 cell version will be composed of 2 packs, and the 6 cell version of 3 packs.

What is Open Source, what is not

The question of Open Source did not arise, it is the cornerstone of the project. For a hardware development like this one, you have to make do with what you have. Being neither a training software developer nor an electronics engineer, while searching on the Internet I learned and found many things. Then, it requires funds to have everything studied from A to Z. This is why some boards are purchased ready-made (screen controller, touch controller), and are not open source.
The supplier will be able to program and then send me the custom firmware (with the addition of the logo at startup for example), but I doubt he will want to provide me with the sources. To be seen later....

On the other hand, all the studies that have been carried out specifically for the project will be put online. This includes:

• the daughter board;
• the L board;
• the button board;
• the charger/balance board.

The community is free to improve, propose, manufacture.
For the case, its complexity does not allow it to be printed in 3D. Only the internal parts (the screen brackets and the nano PC board support plate) will be printed, and it will be possible to download and print special trays to adapt exotic boards. The brackets are removable, to allow greater screen compatibility, in case the original reference is no longer manufactured and all stocks are exhausted. The community will then be able to exchange its files and propose new versions.

As for the internal cables, I used very common connector references (JST) so that the equipped user could manufacture his own cables. The basic version will be delivered with all cables to adapt all Raspberry Pi models (except the compute module), as well as the Odroid C1+ and C2. For XU4 and UP Board boards, other cables are to be expected: either buy them on the website for a few euros, or manufacture them yourself with the connector references I would make available.

Upgrade your machine


The basic version includes an L-shaped board with an Ethernet connector and an audio output. To adapt the case to this board, a removable part is provided for possible changes. These changes will be possible as the project develops. This L board can be replaced by a new one, for example with a dual SD board reader or a 5Ghz Wifi receiver
connected to the motherboard via USB 3.0 - the removable part can also be replaced, to allow the antennas to leave the case.
But this L board could also be an audio amplifier, an RS232 board, or a video output! Of course, each board will have to be studied individually, which will take time and require funding. The idea is that this L board is the equivalent of a PCIe board on a classic PC.

The software part

The distributions:
The Diskio Pi project is 100% hardware. No proprietary software is required to run it. All Raspberry Pi distributions are therefore installable, even if some (Recalbox for example) are not compiled with touch drivers. For the moment, only one distribution is ready to work in touch "out of the box": it is LibreElec (download to come). For the others, whether it's Raspbian or Ubuntu, the drivers are pre-compiled, there's nothing more to do than choose the most recent kernel.
The Android versions distributed by Hardkernel (Odroid) are fully compatible with touch.

Hardware-OS connections

When designing the project, we chose to completely separate hardware and software. This has advantages, but also disadvantages. For example, in the battery gauge: the advantage is that it works all the time with all OSes; the disadvantage is that it cannot display the battery icon on the screen. It is of course possible to provide a connector on the charger/balance PCB to the Raspberry board, and to communicate via I2C. The problem is that it will be necessary to add cables, and especially to develop (or adapt) a software in Raspbian. A software development under Android will also have to be carried out.
So I think we're going to plan the link on the PCB, but it's going to take a while for the community to help us develop software. The plastic improvements that will be made for V 1.0

GPIO access

I finally solved this problem that had been bothering me for months! I have indeed thought long and hard about making the GPIO spindles accessible. A tablecloth can easily be flexible on its axis, but not laterally, making it impossible to access outside the board axis.
Proof that the simplest solution is sometimes the one you don't think about: a pre-cut on the top of the housing in the axis of the GPIO (Raspberry Pi 3) will be added, it will have to be cut with a cutter (without cutting your finger) to insert an IDE type cloth.


This involves modifying the design of the stand by opening the upper part.

The design of the stand


In addition to this notch to allow the GPIO tablecloth to pass through, another modification will be necessary to easily remove the stand from its lugs. To do this, I added two fingerprints on each side of the pin so that I could leverage with my fingers and detach each "strap".


I hadn't thought at all about how to remove the stand! It has been done.

The gauge

The PCB charger / scale / gauge still needs to be developed, of which only one RGB LED will indicate the battery charge rate (blue to red). The test button, common to all versions, will be molded on the case and placed at the top of the screen:


As you can see, there is still a lot of room for improvement. That's why the delivery time is for August 1019, the time to manufacture two more prototypes, test them and validate all the features.

By whom, for whom?

A brief computer history of the creator
My passion for computers goes back a long way (yes). My first user experience was around an Amstrad 464 cassette, where you had to wait a good 5 minutes (sometimes 10) before you could see the menu of a game appear. The floppy drive changed things, but it wasn't until after the Amiga 500 came along that everything started. At that time I was already starting to use 3D software while waiting for one night to see the rendering of my drawing appear... A lot of mythical games have been played on my screen: Dune II, Xenon II, the Gobliiins series, and so on. In short, I've been a gambler since childhood, but not only that. Tinkering with a SCART socket to finally adapt the Amiga to the TV, I did. And it was working! smile

Little by little I switched to the PC, with a 100 MHz, then a 500 MHz... Until today :
I switched to Linux (Ubuntu) quite recently. My first version is 11.04 it seems to me. I discovered Python, HTML, CSS, various compilations,... Until I came across these Raspberry Pi boards. Is it slow? No slower than my old 500 MHz! And there are many things you can do with it. The Diskio Pi project was almost born, with my screen shots
here and there.
Personally, I have never been equipped with a touch pad. Too closed, no freedom. There is nothing that can satisfy my desire for change with a classic device. And I think there are many of us in this case: who want material that can be controlled and that can really meet our expectations. If you're like that, then Diskio Pi is for you. Sometimes a screen, sometimes a tablet, sometimes a desktop. The choice of use in a single device is useful.
The playful and educational side of Diskio Pi In France, IT innovation since MO5 and minitel is almost non-existent. It is time to react.
Our education system does not really promote new technologies, even if things are moving a little. But nothing to do with the United Kingdom, where all students are introduced to computers in a fun way. The Diskio Pi project is finally an alternative and a material proposal "Made in France" for all teachers who wish to introduce their
students to the programming.
It is a long-term challenge, and an expensive initial investment for an institution, but one that would be profitable for everyone, and that would address various topics related to IT in general. One can even imagine providing a Raspberry Pi Zero to each student when they enter fourth grade, which they would connect to a Diskio Pi in the school for practical work, and take home.
For the software side, Primtux is already available on Raspberry Pi. Financing a project also means investing for the future It is often thought that crowdfunding sites such as Kickstarter are only used to sell a product. But it is much more than that. As an investor, if you believe in the project, you are a direct actor in its development. The power is on your side. In addition, you give it visibility and the chance to succeed. Without you, the project dies and the idea stays in a box. That's why even a donation of 5€ for a free project is important!
Thank you for taking the time to read this article, and I hope to see you soon.


Who are we? Who are we?

My name is Guillaume Debray, I have a BTS in optical eyewear. I didn't develop with the optician's profession, that's why I stopped everything to devote myself first to travel, then to IT, my lifelong passion. I have been working full time on the Diskio Pi project for about two years. I learned about python by offering Dpluzz+, an open-source software for downloading television programs. I put this project aside to devote myself fully to Diskio Pi.

In the course of the project, Benjamin offered to help me draw version 3, but his company taking up a lot of his time, he agreed to let me set up all the crowdfunding. It therefore remains in the background for the time being.
All electronic engineering is carried out by Nicolas Macé, from Mace Robotics. His knowledge of Raspberry Pi is very useful to the project, and he will continue to develop the boards for Diskio Pi.

Going further

The Kickstarter webpage
The project webpage
The first crowdfunding, to fund the prototype 0.3

#2 General use with the Raspberry Pi 2/3 » [Tutorial] Two finger touch for right click on Raspbian (2018 update) » 2018-08-06 09:34:38

Replies: 0

Credit goes to @gadgetoid for finding the method, testing it, and confirming that it works in this thread. … 2&start=25 I'm just adding some polish.

Tested with a Raspbian fresh install, 2018-06-27-raspbian-stretch and the 3rd prototype of Diskio Pi with ILITEK Multi-Touch-V3000 touch screen (13'3 capacitive)

It should work with other brands with some little modifications.

1) install twofing

mkdir ~/temp
cd ~/temp

That should report that "twofing-0.1.2.tar.gz" was saved.

Now we'll add some needed packages, if any of these are already installed it's OK. We'll update first, and then install them with the following commands.

sudo apt-get update
sudo apt-get install build-essential libx11-dev libxtst-dev libxi-dev x11proto-randr-dev libxrandr-dev

Now that those are in place we can extract the downloaded file and compile the binary using "make".

tar -xvzf twofing-0.1.2.tar.gz
cd twofing-0.1.2

Now copy "twofing" to /usr/bin

sudo cp twofing /usr/bin/

2) Next we need to create a .rules file in "/etc/udev/rules.d"

sudo nano /etc/udev/rules.d/70-touchscreen-ilitek.rules

SUBSYSTEMS=="usb",ACTION=="add",KERNEL=="event*",ATTRS{idVendor}=="222a",ATTRS{idProduct}=="0001",SYMLINK+="twofingtouch",RUN+="/bin/chmod a+r /dev/twofingtouch"
KERNEL=="event*",ATTRS{name}=="ILITEK Multi-Touch-V3000",SYMLINK+="twofingtouch",RUN+="/bin/chmod a+r /dev/twofingtouch"

3) Install some packages to auto calibrate

sudo apt install xserver-xorg-input-evdev xinput-calibrator

4) Add an X configuration

sudo nano /usr/share/X11/xorg.conf.d/90-touchinput.conf

Section "InputClass"
    Identifier "calibration"
    Driver "evdev"
    MatchProduct "ILITEK Multi-Touch-V3000"
    MatchDevicePath "/dev/input/event*"
    Option "Emulate3Buttons" "True"
    Option "EmulateThirdButton" "1"
    Option "EmulateThirdButtonTimeout" "750"
    Option "EmulateThirdButtonMoveThreshold" "30"

5) install udev rules :

sudo nano /etc/udev/rules.d/ 99-input-tagging.rules

ACTION=="add", KERNEL=="event*", SUBSYSTEM=="input", TAG+="systemd", , ENV{SYSTEMD_ALIAS}+="/sys/subsystem/input/devices/$env{ID_SERIAL}"

6) Application on startup :

nano ~/.config/lxsession/LXDE-pi/autostart


7) reboot

sudo reboot

test :

twofing --debug

or via SSH :

export DISPLAY=:0 && twofing --debug

You should see

pi@raspberrypi:~ $ export DISPLAY=:0 && twofing --debug 
twofing, the two-fingered daemon 

Input device name: "ILITEK Multi-Touch-V3000" 
XInput device id is 8. 
XInput device id for calibration is 8. 
Start calibration 
No calibration data found, use default values. 
Calibration: MinX: 1; MaxX: 16384; MinY: 1; MaxY: 9600 
Invert X Axis: No 
Invert Y Axis: No 
Swap Axes: No 
Calibration Matrix:     1.000000        0.000000        0.000000 
                       0.000000        1.000000        0.000000 
Grab Result: 0 
Reading input from device ... (interrupt to exit) 
Current window: 'pcmanfm' 
Use default profile.

and the menu appears.
[Ctrl]+[C] to interrupt.

Sources : … p?t=138575 … uchscreen/

#3 Re: Other OS » How to install Android on Raspberry Pi (1920x1080 resolution) » 2018-04-03 07:12:58

Ah ok, I havn't tried via another Pi.
Maybe you can try to install phablet-tools, like it says !
Be also sure about the IP adress of the second Pi.

About the screen, no idea, I'm sorry !

#4 Re: Other OS » How to install Android on Raspberry Pi (1920x1080 resolution) » 2018-04-02 17:29:40

The script must be execuded on a Linux PC, not on the Pi.
You must install the package android-tools-adb on the PC, and lunch the script with the Pi, connected via wifi or ethernet

#5 Re: Other OS » How to install Android on Raspberry Pi (1920x1080 resolution) » 2018-02-05 10:53:13

Here will be soon a complete tutorial to install LineageOS with gapps.
LineageOS is an Open Source fork of Android, based on the 7.1 version.

- A Linux system, tested on x64. Should work also with x86
- A Raspberry Pi 3 ! (with power, screen etc)
- SD card, class 10 / 8Gb or 16Gb, 32Gb is perfect to install many apps


1.1) The best way to burn images is Etcher
Install it (with adding the repo, or only the package)

1.2) Download the latest LineageOS image.

1.3) Please note the number version! Today, it's 20180118. We will need it later.

1.4) Unzip the archive, and use Etcher to burn it on your SD card.
When it's done, put the SD card in the Pi and boot it.
Setup the wifi or ethernet with the interface.


2.1) Developer mode:
Settings -> About tablet -> Click ‘Build number’ several times

2.2) Root access:
You need to enable root access under Settings -> Developer options -> Root access

2.3) Note the IP adress:
Settings -> About tablet -> Statut


3.1) On your Ubuntu PC, create a folder:

mkdir ~/lineageos
cd ~/lineageos

3.2) Click on this link (on a new tab):
Copy the contents and paste in a new file, named
The script is based on the AndroidRT script, a little modified.


3.3) Now, you must modify the script with adding the corresponding version number like this: (tested 16/08/2018)

Version of Lineage OS      ->    Version of the GAPPS to setup in the script
20180118                                20180203

Same for the IP adress (192.168.1.xx) of the Pi like this:



When ok, save ([ctrl]+[o]) and quit ([ctrl]+[x])

3.4) Make it executable and launch the script:

chmod +x ~/lineageos/

Install the dependancies if needed

If the script is blocked here

restarting adbd as root

You can do [ctrl][c] and

sudo adb kill-server

Then restart the script.

3.5) Wait for the reboot of the Pi, and enjoy !

Here is the result:

Optional: install SuperSU from the Play Store, and an app to reboot/shutdown !

Source: … pberry-pi/

If you liked this tutorial, take a look at our crowdfunding, we need your support to build the third prototype of the ultimate open source tablet ! Thanks smile

#6 Re: Avant de démarrer... » Welcome » 2017-10-24 12:54:33

Hello RoDus,
Thank you !
The internal HDD is planed to be an option, the case is already designed to receive a 2'5 SDD or HDD, as long as the disk is not higher than 5V 1A. (some old disks will not start)

#7 Re: Utilisation du Dikio Pi, avec ou sans SBC » A propos du protoype v0.2 » 2017-06-18 10:39:13


L'idée première de cette tablette était de proposer un kit prêt au montage, avec toutes les fonctionnalités intégrées et évolutives. Les cartes à assembler fesait partie du plan initial, avec des connexions par broches, ou avec des câbles.

Après avoir discuté avec le bureau d'étude, il a été décidé de tout rassembler sur une seule carte, pour une raison très simple: le prix de production.
Il faut en effet réduire au maximum les opérations manuelles (soudure traversantes, soudures de câbles), sans compter le découpage des PCBs qui doit être le plus simple possible.
C'est pour cela qu'il n'y aura qu'un nombre minimum de PCB (2, sans compter le SBC) à l'intérieur de la tablette.

Pour les produits Adafruit, c'est en effet une idée qui peut être creusée. Mais cela pourrait peut-être freiner certains débutants de devoir commander à plusieurs endroits les éléments, Diskio ne pouvant pas approvisionner cette marque pour le moment. Il faut aussi essayer de ne pas trop dépendre de telle ou telle marque, car leur amplis peuvent changer de dimension du jour au lendemain.
La dépendance des produits de la fondation Raspberry ou de Hardkernel étant déjà indispensable.

Je comprend bien que cette première version n'est pas parfaite, car il y a des choix qui n'ont pas été faciles à faire.

Ceci dit l'évolutivité du produit est pour le moment disponible avec le processeur ou la RAM (la carte PC), j'espère qu'il en sera de même avec l'ampli si le produit se développe. Mais pour cela il faudra des investissements que je ne peux pas demander à l'utilisateur, ce serait demander trop à la fois!

Dans tous les cas merci pour cette remarque, car je vais totalement dans votre sens. Lutter contre l'obsolescence n'est pas toujours le plus économique, les principaux fabricants l'ont vite écarté...
Mais cela est à mon avis urgent de s'en préoccuper, avec toutefois les moyens dont je dispose.

En espérant que mes choix ne seront pas trop pénalisants pour la suite!

A bientôt,


#8 Linux » How to setup sound using RPi Zero on Raspbian Pixel » 2017-05-16 12:02:45

Replies: 0

This tutorial will help you to enable sound on Diskio Pi using Raspberry Pi Zero (USB device)

1) Listing of USB devices


The USB sound device should be displayed here

2) Listing of sound devices

cat /proc/asound/modules


0 snd_bcm2835
1 snd_usb_audio

3) Modify alsa configuration file:

sudo nano /usr/share/alsa/alsa.conf

Look at these lines, and change 0 to 1:

defaults.ctl.card 1 # was 0
defaults.pcm.card 1 # was 0

Save with [ctrl]+[o]
Quit nano with [ctrl]+[x]

4) Restart alsa:

alsactl restore

5) Done !
You can now listening audio files with Diskio Pi & Raspberry Pi Zero.

Sources: … audio.html

#9 Re: Avant de démarrer... » Welcome » 2017-04-11 13:17:50

Hi hmpff,

Thanks for your post!
The project go forward slowly, but I do my best !
Soon the prototype will 100% work, with sound and buttons, after I will look for the wall mounting.

See you in June smile


#10 Re: Utilisation du Dikio Pi, avec ou sans SBC » projet vivant, cout, usb3 » 2017-04-11 13:14:27

Bonjour humpff !

Il y a encore des tas de choses à faire, mais je serais prêt pour Juin !
Pour la question du prix, c'est encore un point qui m'est impossible de répondre précisément, car il me manque des devis.
Malgré tout, il faudra compter environ 350€ TTC pour la tablette sans les batteries, et sans le nano-PC.
Les batteries (6 cellules) seront vendues à environ 40€.
Les 100 premiers bakers pourront bénéficier des batteries offertes (du moins l'équivalent), c'est à dire 10% de remise sur le prix de la tablette.

A propos de l'USB3, les ports seront disponibles en interne (avec l'utilisation de l'Odroid XU4), directement sur la carte. Le coût de l'étude pour les intégrer dans la carte mère (le HUB notamment) n'étant pas une priorité, j'ai préféré garder l'USB2. C'est n'est pas figé bien sûr, mais je vais prévoir un pré-perçage dans le rack pour faire passer un câble, qu'il sera possible de découper au cutter. Un petit passe-câble à cliper sera livré par défaut.

A bientôt,

#12 Re: Avant de démarrer... » First preview of the assembly guide » 2017-03-26 09:59:33


1) Ces pieces sont à assembler sur la coque principale, elles sont le support de l'écran.
1) These parts are the screen's support

2) Les pièces assemblées, la coque peut recevoir l'écran.
2) The parts are assembled.

3) Poser l'écran dans l'empreinte, puis décoller le film de protection
3) Put the screen in the mark, then remove the plastic film.

4) On utilise le même adhésif sur l'écran, en faisant tout le tour.
4) Here, use the same tape (as the step 1), all around the screen.

5) L'étape la plus délicate: glisser le connecteur du verre tactile sous l'écran, pluis poser le dessus de la coque (voir étape 1) sur la coque principale. L'écran se collera sur le verre tactile à la position exacte.
5) This is the most delicate step: pose the top of the case on the screen, the tape will paste the screen on the touch screen at the exact position.

6) Vérifier que le dessus de la coque se place bien !
6) Verify that the top is well positionned

7) L'écran est collé, il ne bougera plus, sauf si on doit le remplacer !
7) You can remove the global screen, done !

#13 Avant de démarrer... » First preview of the assembly guide » 2017-03-26 09:59:02

Replies: 2

This is the first preview of the assembly guide, as I have thought the process. The assembly is simple, don't need much tools, and will allow fast and easy open/close of the tablet.

Here is the first step, the assembly of the touchscreen with a special tape (special for touch screens). The tape will be provided with the kit.


1) Use a flat support to set the case. The game is to paste the tape in the footprint of the case. You can use a little clamp to do it.



2) Remove the film from the tape


3) Place the touchscreen in the footprint. Be careful, the tape is strong. You can also clean the surface with alcohol or a glasses cloth.


4) Done ! The top of the tablet is ready to receive the screen. This will be precised in a next post.


See you soon for the other step !


#14 Other OS » How to install Android on Raspberry Pi (1920x1080 resolution) » 2017-02-17 09:28:38

Replies: 5

This tutorial is available only for Raspberry Pi 3. To run with Raspberry Pi 2, see this link.

Edit 2018:

This tutorial is no longer relevant because AndroidRT is abandonned, but you can still install LineageOS, an Open Source system based on Android 7.1.
A new tutorial to install LineageOS and gapps (google play) is available here -> link


It explains how to install Android with 1920x1080 resolution, works with any full HD screen.

With time, a special image for Diskio Pi will be available.

The version choosen is RTAndroid, it's not an official version from the fundation, but works well and still in development. Thanks to Igor Kalkov for his development.
The touch screen is supported, and the USB DAC too.

- A formated 8Gb SD card, with UHS speed class 4. Class 10 is recommended.
- A SD card adapter
- A linux PC host to burn the SD card. Windows users should use a Live-CD or VirtualBox.
- Gparted if you use Ubuntu, or other partition soft.

1: Download the image.

Go to this page: https://rtandroid.embedded.rwth-aachen. … pberry-pi/ to download the latest image file.

2: Unzip the downloaded package.

cd Downloads
unzip rtandroid-[VERSION]-[DATE] -d .

3: Edit the file "boot/config.txt" for desired resolution. You can find more informations here or here.
For DiskioPi, the screen is 1920x1080. You can run Android with this resolution:


If you prefer run android in 1280x720 resolution, keep


To enable USB sound, add these lines in config.txt:


4: Insert your SD card in your PC.

5: Find the device name of the SD card. Several methods can be used.

- Terminal method:

sudo fdisk -l
and find the letter correspond to your SD card.

- Graphical method:
You can check with Gparted the SD card name. You can also delete all partition already created before.

The name will be /dev/sdX (/dev/sde for example)

Be sure of this name, the next operation will delete all data of the device.

6: Burn the SD card:
On the terminal, run the install script:
Use the "-p" flag to partition your card.
Use the "-f" flag to format your card.

cd rtandroid-aosp-7.1-20170211-rpi3
./ -p -f /dev/sdX

with X your specific letter found in step 5

The script will create 4 partitions and burn the system.
Finally, you should have this:

 * Copying new system files...
   - mounting the boot partition to /media/rpi-sd
   - copying boot files
   - unmounting the boot partition
   - writing the system image
2048+0 enregistrements lus
2048+0 enregistrements écrits
2147483648 bytes (2,1 GB, 2,0 GiB) copied, 234,006 s, 9,2 MB/s

Installation successful. You can now put your sdcard in the RPi.

7: If you have chosen 1280x720 resolution, you can remove your SD card from the PC and put it into the raspberry pi and power it on.
Next step is 9.

8: In the case of 1920x1080 resolution:

Mount the SD card. (I remove the card and re-plug, more easier)
Go to the system partition.

Comment (add #) before this line:

and add these lines:




and comment this line.

The file should be:


Save and close gedit.

Then, the system will start with 1792x1008 resolution.
To have a real 1920x1080 resolution, there's a command to send when Android will be started (see step 10).

You can unmount & remove your SD card from the PC and put it into the raspberry pi and power it on.

9: Gapps Installation:
Gapps is a suite of Android software including Google Play Store.

Your Android is runing on your RPi. You must be connected (wifi or Ethenet)

Settings -> Wifi -> Wifi ON -> Add your passphrase

Then, get the IP adress:

Setting -> About tablet -> Statut

The IP adress is like 192.168.1.xx

With the host PC, open a terminal, then:

Edit the file and find the ADB_ADDRESS="" line.
add your IP adress like this:


Save, close.

and execute the script:

./ -a arm

You must maybe install some package (lzip or other)

Wait until the script end, the Raspberry must reboot.

All done, you should have Google Play Store installed!

10: Set the 1920x1080 resolution:

With the PC host, enter this (the Raspberry Pi must be connected)

To connect your PC with the Android RT,

adb connect 192.168.1.xx

and set the new resolution:

adb shell wm size 1920x1080

Limitations of this method:
At this time, we can not set the build.prop file with 1920x1080 resolution. The resolution is not reconized by the screen.

I will add corrections if I find a better method. (Or if I manage to modify/compile a custom image for Diskio Pi @RPi)

Have fun!


Sources: https://rtandroid.embedded.rwth-aachen. … pberry-pi/ … hd-franais
RT Android Google group:!forum/android-rpi

#15 Re: English forum » Partial result of the poll » 2016-12-15 09:39:54

Thanks, I try to respond a maximum of greetings.

#16 Re: Avant de démarrer... » Welcome » 2016-11-27 20:24:02

Hi Freepix

Thank you for your message, glad you like this project!
A second prototype is on the way, I hope to present it in february.
Don't hesitate to subscribe the newsletter to have unpublished informations !


#17 Re: Utilisation du Dikio Pi, avec ou sans SBC » compatibilité avec boite d'encastrement » 2016-09-26 19:17:25


L'intégration murale fait partie des options du boitier qui sont à l'étude. L'axe principal de réflexion est une fixation par aimant, de telle sorte que l'utilisateur puisse décrocher la tablette de son support en cas de besoin, ou pour la configuration.
La connectivité se fera donc soit par ethernet, soit par wifi.

A propos de l'encastrement au mur, cette option n'est pas encore à l'étude mais il n'est pas trop tard pour y penser,  en sachant que la fabrication plastique coûte relativement cher (voire très cher). Ceci dit, rien n'empêche de placer quelques ergots supplémentaires pour prévoir un encastrement mural "semi-DIY".

Merci pour cette idée,

#18 Re: Android » Main specification of Android OS » 2016-08-01 09:05:12

Hi Chrisatorain,

Android OS system for Odroid machines is available on Hardkernel website.
DiskioPi will use a touchscreen, so the team will compile the source to add the driver in the kernel, and will propose some download links for the users.

#19 Re: Avant de démarrer... » Welcome » 2016-06-07 14:23:08

Welcome GrosDede ! (and sorry for the late  :8 )

#20 Avant de démarrer... » [Test] Bananapi M2+ » 2016-06-07 12:51:48

Replies: 0

This post is a test of the board Banana Pi M2+, a free sample sent by Sinovoip. (Thanks Izzy ! )

I will try to explain pros and cons of this board, even if I must try Android and camera, not done yet.

So the board is based on a H3 quad core, 1Gb DDR3 RAM, a 7Gb eMMC, inboard Wifi + BT.
The complete description is here:


The size of the board could be ideal for Diskio Pi, the chip is not very hot in normal use.

[stress test in progress]

I have tested Debian (Armbian) and Ubuntu 16.04 (BPi official)


Very light distribution, version tested 5.10 but 5.13 available now (here) with Wifi out of the box.

Some modifications to install wifi:
- add the driver bcmdhd in /etc/modules
- download and install AP4212 firmware
BT not tested yet


UBUNTU 16.04:

The image is after dezip 14.8 Go, but can be cloned in the eMMc (7.3Go).
I wonder what was the problem... but no problem.

After a simple

dd if=/path/ubuntu.img of=/dev/mmcblk1 bs=10mb

and a reboot, Ubuntu is loading.
Lots of package are pre-installed, too much. For example, Firefox and Chrome-browser...
So, some clean must be done.

No Mali driver is available at this time, but the window manager is fine.


Just a problem to shutdown. I must to force it because something is wrong with vfe:

[   77.521003] [VFE]vfe_open
[   77.521031] [VFE]..........................vfe clk open!.......................
[   77.521082] [VFE]vfe_open ok
[   77.521500] [VFE_ERR]input index(0) > dev->dev_qty(1)-1 invalid!, device_valid_flag[0] = 0
[   77.531298] [VFE]vfe_close
[   77.531319] [VFE]vfe select input flag = 0, s_input have not be used .
[   77.531347] [VFE]..........................vfe clk close!.......................
[   77.531390] [VFE]vfe_close end


A big problem: I can't start the board with my 2 usb devices plugged, using a 2A power. The startup consumption is about 0.4A.
I must unplugged the mouse to see the screen alight

[post in progress]

#21 Avant de démarrer... » Event » 2016-05-22 06:36:48

Replies: 0

Hi all,

If you live in France, and in particular in Lyon, we will be present at the Mini Maker Faire the may, 28 and 29.
Demos and presentation of the prototype.

All infos here:

Try to come! smile


#22 Re: General use with the Raspberry Pi Zero » Windows IOT » 2016-03-31 21:30:05


Yes, Windows IOT should works, if you use a Raspberry Pi 2 or 3 model.

#23 Re: Avant de démarrer... » Welcome » 2016-03-07 10:36:47

Welcome meumeu34 !
Thanks  wink

Can you tell me if you have received an email for this post ?
I think it doesn't work for me.

#24 Re: Avant de démarrer... » Welcome » 2016-03-03 17:53:28

Welcome Ben, thanks for this first post !
I hope too this project is just a beginning smile

Edit: just added a plugin for bbcodes, I think it works.

sudo apt-get update

#25 English forum » Partial result of the poll » 2016-03-01 15:59:45

Replies: 2


In this post you can see some datas from the poll.
To see details, click on the pics.





Board footer

Powered by FluxBB 1.5.9