How exactly? I’m asking because related questions came up in the /e/ forum: FP3 + encryption
1 Like
Since I use MyPhoneExplorer for syncing stuff to and from Android anyway, I also use it to copy the whole Internal Storage to the computer, because it can do that and because it can do that via WiFi, which is a lot faster than via USB.
Else I would simply connect the phone via USB to the computer when Android is running, enable data transfer, and copy everything to the computer a file manager (e.g. Explorer on a Windows computer) presents as “Internal Storage” on the phone (which requires MTP to work correctly on the computer side).
If the bootloader of the phone is unlocked already before any current backup attempt, it could also be done when TWRP is booted. TWRP enables MTP once it gets access to the data partition (i.e. once the user supplied the correct unlocking PIN/password/pattern equivalent for TWRP to decrypt the data partition), so Internal Storage can be copied via USB then, too.
1 Like
Doesn’t unlocking the bootloader wipe data?
When I was beta testing, unlocking with fastboot and not wiping the data led to a bootloop.
But then I didn’t try booting TWRP after unlock and before wipe, maybe that would have worked.
2 Likes
It does … but my bootloader is unlocked already.
Good point, I’ll edit to clarify.
2 Likes
Vendor security patch level on “dev” is “5 August 2018”?
Is that different on “test”?
No, it’s the same on test as well.
Hope it’s okay to pitch in here and add to your lists?
What works for me (in addition to Ingos list):
/Apps/
- DB Navigator - there were issues on the FP1 & FP2 if no google services where available, so I had to downgrade the App)
- Sonos
- Several apps that use GPS to find “places nearby” - FP1 & FP2 same as DB Nav
- Nextcloud (Client)
- UniFi
- Several bookkeeping/tax apps
Default apps I replaced:
- Camera: The standard Camera app seemed very slow to me (compared to the default FP3 app) --> get the “Simple Camera” from F-Droid, works much better
- Calendar --> if you integrate multiple webDAV calendars you might wanna consider “Simple Calendar” instead of the default; I couldn’t find a way to highlight the appointments in different colors (depending on which calendar it belonged to)
- edit: please note: /e/ ships with a fork of DAVx integrated so you don’t need to install DAVx separately (I did and it crashed several times)
Slight issues:
- Launcher: I couldn’t find a properly working launcher to replace the default /e/ “Bliss Starter” --> can’t get used to the default /e/ widgets
- Bluetooth headset: I tried several, they all work; however small stuff like “Incoming call” -> “activate headset” usually means the phone recognizes the active headset (when paired before) and accepts the call. Half the time this accepts the call but the audio in and out is lost and stays lost even if you switch back to speakers -> hang up, call back
Other than that it works like a charm. Very happy here 
2 Likes
The test channel received an update today: 0.9-p-2020050352464-test-FP3
Now working: LiveDisplay
4 Likes
Please define “properly working” … and which launchers did you try?
I tried Lawnchair, OpenLauncher, LaunchTime, Zim Launcher and the Fairphone 2 Launcher.
(F-Droid only)
Most crashed when I tried to add Widgets, customize any icon or when adding several icons together into a collection/box.
I’m using Lawnchair with Widgets and customised icon shape and size without a problem.
1 Like
Interesting.
It crashed every time I long-tap the screen > Widget > when I scroll down to select one.
I just realized it crashed everytime the scroll reached the “Simple Calendar widget”
I uninstalled SC and now it now it works, even after I reinstalled the same App… last time installed SC before Lawnchair.
Thank you!
1 Like
Have the impression that /e/ consumes much less energy than the stock Rom.
Furthermore, I am astonished that GPS runs very good and finds connection within seconds.
Anyway, I am very happy with /e/
1 Like
I know that, after a real initial problem, my /e/ installation drains the battery a bit more than my stock installation did, but it’s currently not so much that I would go back to stock.
Hey there!
I think it’s really great, that we finally have a Google-free phone.
I have two really weird problems in WhatsAppt though and I don’t know whether they are related to each other:
-
There is no sound in WhatsApp calls and the problem also occurs with headphones or a bluetooth headset. The microphone works, the other person can also hear me and I also can open other apps that play sound while having a WhatsApp call. Calls in other messenger apps like Telegram work fine.
-
Also during a WhtasApp calls the screen turns black and usually I cannot switch it on anymore during the call, not with any key or going away from the proximity sensor. When the WhatsApp call ends the screen turns on again. Sometimes I can switch the screen once with a key, but if I try a second time it doesn’t work.
These problems only occur on /e/, on Stock Rom everything was fine. Anyone having an idea or has the same problem?
I have installed Magisk and Xposed, but I don’t think that it is related to the problem.
Have a look at this ticket, might be your 1.
2 Likes
Hi Ingo, yesterday I installed the latest /e/update - works fine on FP3.
1 Like
@Chris4 There is an OTA update to address the issue of audio calls with apps like Whatsapp, Telegram, etc., it seems to be fixed now.
1 Like
Yes, I already updated and now everything works. Thank you!
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.