. | Timestamp | How did the course meet your learning objectives? | How was the duration of the course? | Comments and suggestions | Comments and suggestions | How helpful 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 well did the instructor answer questions from the audience? | 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 | An extra session? | 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 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? |
. | 1/17/2013 13:33:30 | 3 | 4 | Sometimes more details or even the correction for the exercises could be useful | 5 | 5 | 5 | 5 | 5 | 5 | 3 | Computers were provided by our company and were definitively too slow... compilations took years! | 4 | 5 | 4 | 5 | 6 | 4 | Porting Android to a custom made board from scratch instead of using a clone-config of a board that is already supported by Android | 4 | Availability for on-site sessions, Not applicable - My management made the decision | Free Electrons chosen by my management | Board Support Package development: make Linux / Android support your new hardware, Boot time reduction, Root filesystem design and development | 5 | 5 | 3 | 3 | From a foreign country | ||||||||||||||||||||||
. | 1/17/2013 14:27:00 | 1 | 3 | 3 | 4 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 2 | 4 | First Android compilation need a lot of time, this time should be used for anything else. This course subject is very wide, so it's hard to fully understand all the details. In only 4 days is not enough and the covered subject too wide. | 6 | 5 | yes, anything interesting in this field of knowledge | 5 | Missile launcher :-) | Not applicable - My management made the decision | Free Electrons chosen by my management | Board Support Package development: make Linux / Android support your new hardware, Real-time: implementation and bug fixing | 5 | 4 | Sometimes labs were too well explained (like a todo checklist), and sometimes not enough (don't know how to reach goal at all, even after checking the lecture) | 4 | 3 | From less than 100 km / 60 miles | |||||||||||||||||||||
. | 1/17/2013 16:42:02 | 4 | Not enough time to see application part. dommage | 3 | It's too messy to have example useful. | 3 | 4 | 5 | 4 | We had one issue with a exercise (same for every one) and we spend to much time to fix it. The instructor didn't know this problem. | 4 | 4 | the laptop was too slow. take to much time to compile | 1 | 3 | not enough clear with the break (time and when) | 4 | 3 | 3 | 4 | 4 | the training was well but the compilation time was very bad | 3 | - | - | Not interested | 2 | 4 | 3 | 3 | From less than 100 km / 60 miles | |||||||||||||||||||
. | 1/17/2013 16:42:20 | 4 | Not enough time to see application part. dommage | 3 | It's too messy to have example useful. | 3 | 4 | 5 | 4 | We had one issue with a exercise (same for every one) and we spend to much time to fix it. The instructor didn't know this problem. | 4 | 4 | the laptop was too slow. take to much time to compile | 1 | 3 | not enough clear with the break (time and when) | 4 | 3 | 3 | 4 | 4 | the training was well but the compilation time was very bad | 3 | - | - | Not interested | 2 | 4 | 3 | 3 | From less than 100 km / 60 miles | |||||||||||||||||||
. | 1/17/2013 16:53:53 | 4 | labs are sometimes a bit long. They could be shorter if more precisely directed not to let us search too long for solutions to some basics need (like .mk files options or syntax issues). | 4 | Something like an index or a quick reference is missing (during the labs, we could refer to reference instead of digging into the slides) | 5 | 5 | 4 | 4 | Questions were clearly answered. Speaker goes a bit to fast and monotonic like a recitation. He's a very a good speaker but his teacher skills can still be improved. | 5 | 5 | equipment (our equipment) was not efficent enough (old pcs) | 1 | Insist more on customers to have powerful computers | 5 | 4 | 1 | 5 | 5 | 2 | - | 5 | labs | having the spaeker speaking fast while displaying the slides | Availability for on-site sessions | Free Electrons chosen by my management | Not interested | I guess all the same question always arise. They could be compiled in a kind of answer book, or a reference guide | 2 | 5 | This is the most valuable part of this course, by giving us insight to android. but could be improved as explained earlier. | 3 | 4 | From less than 100 km / 60 miles |