AN Adonay Felipe Nogueira
- Login: adfeno
- Registered on: 06/23/2019
- Last sign in: 03/15/2026
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 2 | 0 | 2 |
Projects
| Project | Roles | Registered on |
|---|---|---|
| Replicant | Developer, Wiki author | 08/25/2019 |
| libsamsung-ipc | Developer, Wiki author | 10/05/2020 |
Activity
04/10/2025
- AN 12:49 AM Replicant Issue #2354 (New): Fix small typo on vendor_replicant-scripts/networking/usb/usb_networking_device.sh
- In Replicant 6.0, the reverse tethering script refers to a non-existing @$iface@ variable. Here follows the patch to use @$USB_IFACE@.
03/13/2025
- AN 10:54 AM Replicant Wiki edit: People (#117)
- Minor device correction.
03/01/2025
- AN 12:54 AM Replicant Replicant usage: RE: Galxy Tab 2 10.1: How to enable graphics accelaration _only_?
- John R wrote:
> Hi,
> ...
According to [[Graphics]], depending on the Replicant version being run, libagl or llvmpipe may be in use.
The same page has a guide on how to do the switch.
12/12/2024
- AN 10:34 PM Replicant Wiki edit: People (#116)
- Minor device correction.
09/19/2023
- AN 10:22 AM Replicant Wiki edit: People (#109)
- Update the device that adfeno owns.
02/24/2020
- AN 07:28 PM Replicant Wiki edit: PromotionalMedia (#8)
- Added anchor to my own name from the list of project contributors.
- AN 07:06 PM Replicant Wiki edit: People (#89)
- Added myself.
12/27/2019
- AN 05:13 PM Replicant Wiki edit: GalaxyNote2N7100Installation (#11)
- Add senson fix instructions.
08/24/2019
- AN 10:55 PM Replicant Issue #1948: Document how to install and run Replicant in a virtual machine
- I noticed that the author of the first link and repository (second link) actually did an entire new QEMU. I don't know the reason for that, but I wonder if that was really needed.
In order to not ask meaningless question, I think that...
08/23/2019
- AN 03:50 PM Replicant Issue #1949 (In Progress): Make web browser and email client support TLS 1.2
- To take an example website, https://www.hyperbola.info/ is now accessible only if the web browser supports TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 and `TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256`.