A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | AA | AB | AC | AD | AE | AF | AG | AH | AI | AJ | AK | AL | AM | AN | AO | AP | AQ | AR | AS | AT | AU | AV | AW | AX | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Timestamp | How did the course meet your learning objectives? | How was the duration of the course? | Comments and suggestions | Comments and suggestions | How useful was the lecture document? | Comments and suggestions | Will you recommend this document to others? | Comments and suggestions | If you have Linux / Android project opportunities, will you use this document again in the future? | Comments and suggestions | How knowledgeable was the instructor? | Comments and suggestions | Did instructor oral explanations add value to the lecture materials? | Comments | How much value did the instructor add to lecture materials? | Suggestions and comments | Was the instructor helpful with practical labs? | Comments and suggestions | How do you rate the training equipment (mainly computers)? | Comments and suggestions | How well was the course organized (program, registration, schedule...)? | Comments and suggestions | How much did you learn? | Comments and suggestions | How useful should this course be in your daily job? | Comments and suggestions | Would you recommend this course to others? | Comments and suggestions | Overall rating | Comments and suggestions | Further training needs? | Comments | How did the course meet your learning objectives? | What part(s) of the course did you like most? | Comments | What part(s) of the course did you like least? | What reasons prompted you to choose Free Electrons? | How did you first learn about Free Electrons? | Interested in other types of embedded Linux / Android engineering services? | Comments and expectations | Comments and suggestions | How do you rate training conditions (room size, equipment, environment)? | How useful were the training labs? | Comments and suggestions | Comments and suggestions | How difficult were the training labs? | Was enough time dedicated to practical labs? | Comments and suggestions | How far do you come from? |
2 | 6/11/2015 14:13:44 | 3 | 4 | 5 | 5 | 5 | 4 | 3 | 4 | 3 | 6 | 3 | 4 | Open training materials that can be checked in advance, Language | Course recommended by previous participants | Build environment deployment and support, Root filesystem design and development | 5 | 5 | 4 | 4 | From a foreign country | |||||||||||||||||||||||||||||
3 | 6/11/2015 14:14:53 | 3 | 5 | 4 | 4 | 5 | 5 | 5 | 4 | 4 | 6 | 4 | 5 | Open training materials that can be checked in advance, Hardware giveaway (public sessions only), Access to full feedback from participants to previous sessions | Course recommended by previous participants | Board Support Package development: make Linux / Android support your new hardware | 5 | 5 | 3 | 3 | From more than 100 km / 60 miles, same country | |||||||||||||||||||||||||||||
4 | 6/11/2015 14:18:03 | 3 | 5 | 4 | 4 | 5 | 5 | 5 | 4 | 5 | 6 | 4 | 5 | The kernel relqted part | Geographical proximity (public sessions only), Open training materials that can be checked in advance, Language, Hardware giveaway (public sessions only) | Course recommended by previous participants | Not interested | 5 | 5 | 3 | 5 | From a foreign country | ||||||||||||||||||||||||||||
5 | 6/11/2015 14:18:24 | 4 | 4 | 5 | 4 | 5 | 4 | 5 | 5 | 2 | 7 | 5 | 5 | Availability for on-site sessions, Trainer, Open training materials that can be checked in advance, Hardware giveaway (public sessions only), Access to full feedback from participants to previous sessions | Course recommended by previous participants | Technical support, Consulting in technology selection and methodology | 5 | 5 | 4 | 3 | From more than 100 km / 60 miles, same country | |||||||||||||||||||||||||||||
6 | 6/11/2015 14:22:13 | 4 | 5 | 4 | 4 | 5 | 5 | 4 | 4 | 2 | 6 | 5 | Yocto Buildroot | 4 | AOSP full images generation from scratch | high level / java part | Trainer, Open training materials that can be checked in advance | Technical resources on the Free Electrons website | Board Support Package development: make Linux / Android support your new hardware, Technical support | 5 | 4 | More precisions/guidelines should be added on several labs to avoid loss of time | Not difficult if students already have linux experience. Probably a lot more for those who don't => insist on the prerequisites | 3 | 5 | From more than 100 km / 60 miles, same country | ||||||||||||||||||||||||
7 | 6/11/2015 14:24:26 | 2 | 1 extra day would give more time to finalize without rushing. | Main goal was learn about Android structure, how to recompile Android and kernel. So expectations fully met. | 3 | 4 | 3 | 5 | 5 | 5 | 4 | 5 | 5 | Very good training. Maybe too much time on labs. | 5 | Linux kernel and driver development | 5 | Kernel and Android modification/configaration and recompilation. | Fixing bugs for libusb | Not applicable - My management made the decision | Internet search engines | Board Support Package development: make Linux / Android support your new hardware, Boot time reduction, Investigating and fixing bugs | 5 | 3 | 4 | 4 | Maybe too many compile issues to solve on the lab of libusb. | From a foreign country | ||||||||||||||||||||||
8 | 6/11/2015 14:25:41 | 2 | We do not reach the end of the slides and labs. | 4 | 4 | 4 | 4 | 4 | Lot of time is spent in compilation. So maybe more powerful computers could save some times. | 5 | 4 | Not able to finish all slides and labs. | 4 | Maybe split the training in 2 parts (introduction and advanced) | 5 | 1 | 4 | Good structure of the training (from basic to more complicated topics) | Compilation time too long. Differences between the lab slides and the real labs. Training going too slowly. Some prerequisites needed (git) 1st day could be skipped. | Already did some trainings with free electrons | Can't remember | Not interested | 5 | 3 | The training labs do not correspond to the slides as, to avoid downloading sources code was already available on the computer. But it leads to confusion when you read the lab slides. | 3 | 5 | Problem is that labs relies on some git knowledge, Linux knowledge that not all participants have. It leads to some people going fast and some others going slowly but due to technical issues not related to Android knowledges. | From more than 100 km / 60 miles, same country | |||||||||||||||||||||
9 | 6/11/2015 14:29:50 | 2 | 4 | 5 | 5 | 4 | 4 | 5 | 4 | 3 | 6 | Nice training, good job ! | 4 | 4 | JNI | system customization / overlay | Geographical proximity (public sessions only), Open training materials that can be checked in advance, Hardware giveaway (public sessions only), Cost | Course recommended by previous participants | Real-time: implementation and bug fixing, Technical support, Investigating and fixing bugs | 4 | 5 | 3 | 3 | From more than 100 km / 60 miles, same country | ||||||||||||||||||||||||||
10 | 6/11/2015 14:38:35 | 2 | Pour ce genre de sujet, c'est toujours trop court :-) | Le résultat final est que j'ai une compréhension et une approche globale et relativement détaillée d'Android. Néanmoins, l'aspect touffu du sujet va me demander encore un certain temps pour assimiler tout cela. Il manque alors peut-être une sorte de résumé du cours qui permettrait de tout reprendre plus aisément. | 4 | Ils sont bien mais un peu trop "bullet points". J'aurais préféré une approche plus didactique qui commence par une vison d'ensemble (de quoi est fait un système Android, de quoi est fait le kernel, etc.) Pour ce cours, c'est une approche incrémentale qui a été choisie (construire petit à petit), ce qui est très bien mais peut être déroutant si l'on a pas tous les concepts initiaux bien en main. | 5 | Aucun problème de ce côté là : toujours disponible, très patient et très au fait du sujet. | 4 | C'est probablement le point le plus faible : les cours en bullet points font que l'instructeur passe trop de temps à nous lire ce qu'il y a à l'écran. A la limite, on devrait nous dire de lire le cours avant, puis avec d'autres slides, plus légers, plus graphiques, voir ce qui est expliqué dans le cours. On aurait alors un véritable engagement intellectuel des deux côtés (enseignant et étudiant) plutôt qu'une lecture commune ponctuée par des commentaires et des questions. | 5 | Conditions de rêve. N'ayons pas peur des mots | 4 | Bon évidemment, on rêve toujours de plus puissant. Mais du i5 c'est déjà pas mal. | 5 | Rien à dire de ce côté là. | 4 | J'ai beaucoup appris, mais avec l'impression que la quantité d'informations donnée est un peu désordonnée et qu'il faut que j'y remette de l'ordre. Je vais donc tout refaire une fois rentré chez moi en priant pour ne pas bloquer trop et trop longtemps. | 3 | Encore trop tôt pour le dire. Mais le savoir acquis n'est jamais perdu (oui, je sais, c'est beau...) | 6 | Je pense qu'un petit sondage ou un questionnaire avant la formation pour connaître le niveau de connaissances pré-requis serait pas mal. | 5 | 4 | Tout ce qu'on a appris en général. | L'aspect un peu "chasse au trésor" parfois. J'étais venu pour comprendre et apprendre, pas pour deviner où se trouve tel fichier, quoi mettre dedans et faire des recherches Google. | Open training materials that can be checked in advance, Hardware giveaway (public sessions only), Access to full feedback from participants to previous sessions, Seul formation système Android disponible en France ? | Internet search engines | Not interested | Rien à dire si ce n'est bravo. Antoine a pris le temps de me débrouiller mes problème, y compris le soir après la journée de cours de façon à ce que je puisse reprendre le lendemain sans courir après la suite de la formation. | 5 | 3 | A la fois bien et pas bien. On met les mains dans le cambouis, et c'est très bien. Par moment on nous demande de chercher ou deviner des trucs, alors que j'ai eu l'impression que ça ne nous donnait pas vraiment une valeur ajoutée dans l'apprentissage. Le document de training labs est parfois trop imprécis et/ou n'insiste pas assez sur certain point. Par exemple, bien précisé les environnements spécifiques à tel ou tel build, bien expliqué la démarche et la rigueur nécessaire pour avancer les builds ou d'autres choses. | Voir commentaire précédent. Je rajouterai, il manque : - indiquer dans les prérequis : git et ses aspects branching, remote, etc. - une explication plus pragmatique de la partie download (avec vision d'ensemble) | 4 | 3 | Bien équilibré à mon sens. | From more than 100 km / 60 miles, same country | ||||||||||||
11 | ||||||||||||||||||||||||||||||||||||||||||||||||||
12 | ||||||||||||||||||||||||||||||||||||||||||||||||||
13 | ||||||||||||||||||||||||||||||||||||||||||||||||||
14 | ||||||||||||||||||||||||||||||||||||||||||||||||||
15 | ||||||||||||||||||||||||||||||||||||||||||||||||||
16 | ||||||||||||||||||||||||||||||||||||||||||||||||||
17 |