• 0 Posts
  • 12 Comments
Joined 1 year ago
cake
Cake day: April 5th, 2024

help-circle



  • Compared to the Fairphone 5 it has some improvements but also a few downsides:

    Pro:

    • It’s a bit smaller (~4mm) and lighter (~20g)
    • Slightly better camera (future tests will tell how much better)
    • 120 Hz display
    • More RAM and storage (although I feel that the previous 6GB/128GB option was also sufficient for most users)
    • WiFi 6E Tri-Band (however you will likely never need this speed)
    • Bluetooth 5.4
    • Slightly larger battery

    Con:

    • Backpanel now requires a screwdriver
    • Display has less resolution/PPI
    • Performance of processor will likely be nearly identical to predecessor (however it’s more efficient and modern)
    • Downgrade to USB 2
    • 600€

    My conclusion: Overall the improvements are ok, however just releasing the Fairphone 5 with a newer SoC might have been the better/more cost effective choice. Sacrificing display resolution for 120 Hz feels also quite wrong. 600€ is very pricy for a phone like this. Cutting some premium features away like the 120 Hz display or a bit of RAM and storage (that you can extend anyway with an SD card) might have saved enough to get the launch price down to somewhere near 500€ which would make it accessible for a wider audience.





  • Whilst I get the idea the implementation is currently unusable:

    So I filtered for “Battery user-replacable” and found 117 smartphones (out of ~500). This is a straight up lie because all these phones are glued together (nearly all are IP68) meaning that you need some special tools.

    It lacks a lot of phone models. I couldn’t find any Google Pixel or Fairphone.

    The “Battery endurance in cycles” (number of charge/discharge cycles a battery can withstand until its usable electrical capacity has reached 80 % of its rated capacity) attribute is completely broken: It never seems to exceed 15? I had phones for years that withstood hundreds/thousands of battery cycles and the battery still nearly behaved like it’s new and you’re telling me the maximum number is 15??? Did you guys just stop testing after 15?

    Also “with regard to energy labelling” what is this labelling about? Energy? Ok then why are there values about the phones “Repeated free fall reliability” or IP protection inside there?

    The whole thing looks way to intransparent and useless for the average phone buyer and definetly needs some improvement…

    General labelling about repairability/phone lifetime (e.g. receives updates for X years, replacement parts are avilable for X years, can install another OS, can replace battery without external tools, etc) without a overall score that merges all aspects would be a lot better and useful IMHO.




  • You can already do that:

    Get-AppxPackage "Microsoft.XboxApp" | Remove-AppxPackage
    Get-AppxPackage "Microsoft.XboxIdentityProvider" | Remove-AppxPackage -ErrorAction SilentlyContinue
    Get-AppxPackage "Microsoft.XboxSpeechToTextOverlay" | Remove-AppxPackage
    Get-AppxPackage "Microsoft.XboxGameOverlay" | Remove-AppxPackage
    Get-AppxPackage "Microsoft.XboxGamingOverlay" | Remove-AppxPackage
    Get-AppxPackage "Microsoft.Xbox.TCUI" | Remove-AppxPackage
    Set-ItemProperty -Path "HKCU:\Software\Microsoft\GameBar" -Name "AutoGameModeEnabled" -Type DWord -Value 0
    Set-ItemProperty -Path "HKCU:\System\GameConfigStore" -Name "GameDVR_Enabled" -Type DWord -Value 0
    If (!(Test-Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\GameDVR")) {
    	New-Item -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\GameDVR" | Out-Null
    }
    Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\GameDVR" -Name "AllowGameDVR" -Type DWord -Value 0
    

    You’re welcome