The drop down is NOT showing up and I guess this might be because the USB connection is not active to ask for any selection. In Developer Options, the default for USB is set to file transfer, but when connecting the cable, the same error message is shown in dmesg output.
I only see the normal charging message, at the bottom of the screen.
1 Like
Vendor Name: Fairphone
Device name: Fairphone 3
Device CodeName: FP3
Version of /e/OS or Stock which existed previously: /e/OS 2.6.3-t-20241219455848-community-FP3
Is the device Rooted / Not rooted: Not rooted
No issue with updating, now on 2.7-t-20250112460980-community-FP3.
The following things work for me:
- Call / be called
- Send SMS / receive SMS
- Notification LED
- Alarm
- Internet via Wi-Fi
- Internet via mobile network
- Wi-Fi hotspot
- Location
- Settings - System - microG - Self-Check: all ok, including location permissions
- Settings - System - microG - Location - Wi-Fi location - Request from online service: enabled
- Settings - System - microG - Location - Wi-Fi location - Request from Hotspot: enabled
- Settings - System - microG - Location - Wi-Fi location - Remember from GPS: enabled
- Settings - System - microG - Location - Mobile network location - Request from online service: enabled
- Settings - System - microG - Location - Mobile network location - Remember from GPS: enabled
- Settings - System - microG - Location - Location server - Use /e/OSâs location system: enabled
- Settings - Advanced Privacy - Geolocation: Exposed
- Settings - Advanced Privacy - Geolocation - Use my real location
- Settings - Location - Use assisted GPS: enabled
- Settings - Location - Location Services - Wi-Fi scanning: enabled
- Settings - Location - Location Services - Bluetooth scanning: disabled
- Settings - Location - App location permissions - âAllowed only while in useâ: Apps are listed
- Compass
- Screenshot
- Main camera (original FP3 Camera module, not +) photo + video
- Selfie camera (original FP3 Top module, not +) photo + video
- USB connection to PC / MTP
- MyPhoneExplorer 2.2
- Bluetooth (music playback, data connection)
We are proud to deliver the /e/OS 2.7. Enjoy all the new features and improvements it embeds!
We embedded some improvements!
Galaxy S20, S20+ and S20 Ultra are now available with /e/OS
When and where are the community ROMs available for download?
OTA or installation from scratch ?
Wonât have a stuck in setup wizard again.
OTA for S5e. No problems so far.
Update to /e/OS 2.7-t without any problems. All used apps perform as expected. With the new microG, even Parco app (paying street parking in Germany) is now working using mail registration (i.e. without Google).
Big thanks to the devs!
I upgraded my FP3 to 2.7 and itâs fine day to day. 2.7-t-20250111460957-official-FP3
Brivo Mobile Pass app is complaining that the device is rooted. I havenât rooted it.
I have recently updates to 2.7 but eversince data roaming doesnât work anymore. Is anyone else experiencing this problem. If yes wat can I do about it ? I already tried resetting mobiel network to no luck.
- Vendor Name : google
- Device name : Pixel7a
- Device CodeName : lynx
- Version of /e/OS: 2.7 U
- Is the device Rooted / Not rooted : Not rooted
Vendor Name: Fairphone
Device Name: Fairphone 3
Device CodeName: FP3 (+)
Version existing previously: e-2.6.3-t-20241219455848-community-FP3
Device: Not rooted
Did the Upgrade as explained by @piero at this link by sideloading (dirty Upgrade).
Up to now, no problems detected. âUâ seems to be more stable.
Many thanks to the Team for your good Work.
I dirty flashed my FP3 from 2.6.3-t to 2.7-u (both community)
There were two problems:
SystemUI chrashes when playing media in work profile (Shelter). That is an upstream bug from lineage. It is described and solved here the fix worked for me.
Something was draining the battery. It turned out to be AdvancedPrivacy. Clearing Storage and cache fixed the problem.
2 Likes
Itâs not possible to install v2.7 on my device Google Pixel 8 Pro - recovery: error 21.
- Vendor Name: Google
- Device name: Pixel 8 Pro
- Device CodeName: husky
- Version of /e/OS: 2.7 u
Android 14 was installed on the phone when it was new. I had to update it to Android 15 to be able to activate the Enable OEM unlock in the Developer options.
After than I followed the Intall-Guide in Install /e/OS on a Google Pixel 8 Pro - âhuskyâ and everything worked quite well so farâŠ
After I had unlocked the bootloader and flashed the additional partitions, the next hurdle for me was to switch to recovery mode. After
entering fastboot --set-active=a
I switched to boot__a and then I also entered recovery mode.
I carried out the factory reset together with the format data.
When executing adb sideload <downloaded_file_name>.zip, the program aborted at 47% with the following error message:
Error: recovery : Signature verification failed
Error: recovery : error: 21
Install from ADB completed with status 2.
Installation aborted
I wonder if Iâve done something wrong.
Has anyone had similar experiences?
What can I do now?
- Vendor Name: Gigaset
- Device name: GS290
- Device CodeName: GS290
- Version of /e/OS or Stock which existed previously: Not sure
- Is the device Rooted / Not rooted: Not Rooted
Everything seems to be working fine, apart from âWallpaper and Stylesâ in Settings which instantly crashes on opening.
I had the home screen and lock screen set with different wallpapers prior to the update, now theyâre both showing the home screen one. Not the most serious of problems, to be fair.
It does not work to use /e/ to downgrade Android version. To install Android 14 (U) the device should be on manufacturer Android 14 ⊠is mentioned in install page âŠ
Tip: Before installing /e/OS on the Google Pixel 8 Pro husky for the first time, install the latest stock OS version 14 build on the device
AdvancedPrivacy is draining my battery as well. Which cache did you wipe? Is it of a specific app?
Yes, but how does that work?
I had to update it to Android 15 to be able to enable the OEM unlock option in the developer options. This option was grayed out in version 14. I donât see how I could have done it any other way.
It may be best to start a new thread to get specific support. A few possibilities crop up in an online search, subject husky OEM Unlocking âgreyed outâ or Solved! OEM Unlocking greyed out
Depends on the background of the device; sometimes contact with the manufacturer update service can release OEM unlock.
Storage and Cache of AdvancedPrivacy.
Press Settings â Apps â See all apps â Three dots in top right â Show system â Scroll to AdvancedPrivacy and click it â Storage and Cache â Clear Storage
2 Likes
Thanks! Havenât recognised the three dots at all ever since. Wiped storage and cache of AdvancedPrivacy and will inspect battery draining.
vendor: FairPhone
Phone: FP4
Problem
I lost my esim with v 2.6.3 and v2.7 solved this huge problem. Thanks the developers.
Unfortunately, v 2.7. didnât fix an other huge problem. I have 1 physical sim (work) and 1 esim (personal). Both cannot work together. I opened an other topic (https://community.e.foundation/t/problem-esim-and-physical-sim-on-fp4/60822 about this problem but i only met people with the same problem.
When can we hope to solve it? Thanks
First of all, thank you very much for the valuable information!
I have downloaded the following image: Nexus ć Pixel èźŸć€çćșćæ ć | Google Play services | Google for Developers 14.0.0 (AP2A.240905.003, Sep 2024) fĂŒr âhuskyâ for Pixel 8 Pro. This would give me the latest Android 14 version.
In the current state of the smartphone, can I flash the image according to the Google instructions or do I have to do or consider anything else with regard to the actions already successfully performed: âFlashing additional partitionsâ and âInstalling a custom recovery using fastbootâ from the /e/os instructions?