Below are my notes regarding every question asked and answered, covering both sessions.
While the 1st session's audio is lost to time, I have a full recording of the second session.
Stream and download the MP3 here: https://nc.dj.je/s/9FZAqbs9LwcSnio
(I'm looking for a better way to host the file, perhaps I might upload the next one to archive.org)
NOTE: The transcription of questions and answeres may contain errors, take it all with a grain of salt.
1yr, all defects replaced.
Setback: Having a shaky team. Win: Being able to update firmware directly on the device
Likely through authorized re-shippers Q3 or Q4
Potentially, though GPIO may not be fast enough.
Version 1.0.0, ETA is Q3-Q4
It's being worked on and will be release in the near future
- There will be an official "gallery" for apps
- You provide source code (no closed-source) and the apps are automatically compiled
- Likely coming to mobile apps
- There will be no paid apps.
It's complicated, transferring large files can be error-prone.
A lot of the supporting behind-the-scenes code exists, it is theoretically possible to implement.
Yes, they will be vastly improved before firmware 1.0, but currently it's hard to keep up with the constant beta firmware changes.
Currently not directly. User-focused docs are the main focus now, while developer docs will come later.
It was done in order to heavily improve user experience. This extra functionality will be brought back eventually in a separate menu within the NFC app.
- Felica and NFC-V are being looked into
While not textured, there are exact models available on GitHub: https://github.com/flipperdevices/flipperzero-3d-models
It majorly depends on the type of card, among many other factors. Generally speaking: 125khz RFID no, NFC yes.
They will work fine, but you'll have a lot of wasted space.
A good place to start is https://blog.flipperzero.one/rfid/. Beyond there, look up "Intro to NFC" on YouTube.
Officially, no. The firmware comes with a lightweight radio driver that doesn't support BLE scanning. A full driver exists, however it takes up a lot more (internal) storage, meaning certain applications would have to be removed and others rewritten to support the different API's.
It's still being worked on and will eventually be used in "online" attacks where the reader is present.
Approximately 6-7 working on firmware, others work on mobile apps, testing, docs, etc. Teams work in 2-week sprints.
(marketable?)
No, it has been resolved.
- Previously there were 3 models of Flippers being produced, one per region.
- The goal is to have one where location info is provisioned before shipping.
- RPC API is coming for applications, making it easier to control the device with mobile companion apps.
- It's summer for the Flipper team, and some of the members are on vacation. PR's will be merged when they're back.
Yes and no. Flipper is not SDR, and part of the transmission would get cut off if it only started recording after a certain RSSI is reached.
- Use https://my.flipp.dev plotter. Eventually it will be able to split and save segments
It depends on the provider and shipper.
- Flipper's screen is produced exclusively for the device
It's possible, but editing the file directly on the Flipper can be challenging given the limited screen space. Ideally this would be done by the mobile companion apps.
Yes, eventually.
Currently it only supports adding complete applications, not tapping into existing apps. (Eg. Adding a new Sub-GHz protocol)
- There's no technical limitations preventing the ability to extend existing apps, but lack of dev interest means it isn't being worked on. Alternatively you could recompile the entire apps
- External apps are linked in a special way meaning not all app-specific API's will be accessible
Flipper will not be able to TX until you apply a firmware update* for the first time. Then, your region info will be sent to Flipper servers and a profile will be generated on your device. This profile is also stored on the flipper and dictates which frequencies can be TX on.
Flipper interfaces with MicroSD via SPI, which is much slower but more power efficient than normal SD. While it's possible, proofs of concept have shown transfer speeds are extremely slow and thus won't be implemented.
Due to legal regulations, this can not be done by the Flipper team.
Yes, it's being worked on right now.
It's being prototyped to improve upon everything Flipper Zero has. It's still being decided whether or not it will use commonly available hardware (Such as RPi) or more custom hardware (to enable features like an SDR).
Docker still works, however FBT is preferred. https://github.com/flipperdevices/flipperzero-firmware/blob/dev/documentation/fbt.md
Yes, there will be small updates to certain hardware components.
Yes, it's great for determining demand levels.
- It will be launched with working prototypes
It's not possible. Card chips are very secure, and the private keys required to authorize transactions never leave the card.
- Even if it was possible, Flipper team is not interested in implementing it.
Yes, you'll need to buy a new device.
Binary files can be difficult to interface with for humans. Most flipper files are meant to be human readable.
There's a dedicated documentation writer on the Flipper team currently working on the wiki. Feedback can be given via GitHub issues, and the ability for users to contribute is being worked on.
The plastic screen is bound to the casing, thus this is impossible to do without destroying the casing as well.
It's very difficult to do this on the device due to limited resources, however it will be added to mobile companion apps eventually.
Yes, it will be worked on within the next couple of sprints.
It's not that straightforward, but there are third party firmwares compatible with the dev board that can do this to a degree.
BLE is embedded in Flipper's microcontroller, and it's a highly locked-down core. While it should be possible, it's not officially supported by the chip manufacturer. It would be required to "jailbreak" the chip in order to drive such functionality.
While there are hardware-accelerated encryption API's on Flipper, full disk encryption will not be implemented due to high computational resource requirements.
Auto lock with PIN is something that will be added.
Swapping SD cards is much faster for large files, but both should work without error.
If the firmware is small enough, it can be loaded in RAM theoretically (yet to be implemented). Alternatively, you can load multiple firmwares on your SD card and they can be flashed directly on the device itself.
It should be possible.
Yes, definitely.
It's theoretically possible, but there's a delay that can cause issues for certain use cases.
There's a possibility it will be added, but it's not top priority.
Yes, a GPIO API is accessible to apps.
Without using the existing API, it will be difficult.
- Separate API may be added to directly communicate with screen
- Max FPS without artifacts is 15-20
Choice of chipset (Specifically STM WB*) has caused a lot of pain. On the other hand, everything else was great.
The Flipper Team is looking for help from the community with this.
This would have to be implemented in a third-party app.
Yes
Yes, it should be possible.
No, it will use an LCD.
It relates to the capabilities of the BLE core. Lite excludes a bunch of uncommon functions
There WILL be a limited transparent series, however there's no word on black case production.
In theory it's possible, but flippers processor is pretty slow for this.
Button pins aren't exposed, interrupt controller is.
Flipper One will definitely use SDIO.
Probably 60 MHz to 60 GHz.
This can be done with a third party application, the hardware has 2 RTC alarm clocks.
Yes, though more planning is needed. If your idea is fully developed, you can reach out and the Flipper Team will help provide resources.
No, it won't damage the device. If reading raw, make sure your SD card is big enough/
- and eventually which peripherals would be currently unused and free to directly be used from apps ? There's no complete documentation currently available, but apps will have certain hardware and subsystem APIs.
- https://miro.com/app/board/o9J_l1XZfbw=/?share_link_id=606281650151
Yes
There's no emulator, though it's planned after 1.0. Contributions can be made on GitHub
Yes, there's a pull request currently waiting to be merged that will add support for alternative keyboard layouts.
- Should arrive in next sprint or two
- Person in charge of BadUSB is on vacation
If they get invited, why not?
A lot of hardware changes had to be made to prototypes as production was being planned.
- STM WB series contract was secures long before shortage, while others simply disappeared one day.
Yes, additionally widgets are planned to be added.
Format it with Flipper for best results.
- Flipper can not verify integrity of filesystem
FAT32.
Updated version: https://github.com/flipperdevices/flipper-questions-and-answers/tree/dev/2022_08_06_QnA_Discord