I didn’t update to pre2 yet (still pre1). Did someone have any trouble with the general reaction speed of the system? When i used to play Pokemong Go before the ban of rooted devices i was thinking my OS is slower because of Pokemon Go. But even after not using Pokemon Go anymore i feel like the system is palpably slower. Also firefox is crashing quite often on several websites (even facebook). I don’t think i read about one of these problems before. Are there some fixes in pre2?
While it is possible that some of the other stuff we have been working on, fixes some isssues, we did not know about the issues you describe and haven’t looked into them specifically.
It would be great if you could update to pre2 and send me adb bugreports if you encounter the issues again.
1 Like
I think this is related to Pokemon Go (or microG, did you use it or do you have Google Play Services installed?). On my phone Firefox also crashed every time, when there is a Google map embedded somewhere on a website. I think this is an aftermath of having used Pokemon Go and/or microG. I uninstalled both and still have the issue.
Hello, I’ve been using my Fairphone (first with pre1, now with pre2) as my daily smartphone for some months. This are the bugs that I’ve found:
- After you turn off the GPS, it appears as on (but it’s off) in the battery usage.
- The LED notification only works when the battery level is low. No LED Notifications for whatsapp messages or missed calls.
- To enable GPS properly, it seems that the 3g data must be off. Once the GPS signal is OK, you can enable 3g data again.
- This summer I travelled from Spain to Portugal. All was OK except that I had to reboot my phone during the trip and when the phone was ON again, an error message appears (sorry, I didn’t jot down the error message). I think it’s because the phone was started with a roaming network. That happened with the pre1 version, not tested with pre2.
- When you switch from WiFi to 3G, the 3G lasts 5 seconds (more or less) to connect.
That’s all that I can find for now. Whenever I can I will install pre2 from scrath (wipe data and cache).
2 Likes
Weird but I don’t have battery problems anymore…
I have speaker problems though… As with FP2 when phone is set to speaker mode nothing changes, volume is the same as on usual mode.
Enhancement: SMS to MMS threshold is back to 3. Should be at least 10 or infinity. (SMS are mostly gratis while MMS are expensive.)
1 Like
Hello, I don’t think that I’ve a software bug but I still mention it. My pre2 phone just started flickering (turning darker and brighter but gradually getting darker) the screen and it turned black. I currently try to reboot it but it stays black and as I can not input the encryption key, I can’t access it using adb or other tools. It currently click for my attention because it’s not unlocked and typing blind is not really a good thing.
I’ll try to check the hardware later, but @jftr was something changed with the brightness and pre2?
i didn’t use microG, only google play. also no magisk or something like this.
will the update erase my data? do i have to reinstall and backup everything like when i installed the pre1 or will it only update the OS with all my data untouched?
After waiting for a while with the battery removed I was able to see the boot animation but the brightness went down again during it with flickering. At the point where I have to enter the decryption code the screen was completely black again.
I have trouble with synchronization… phone’s connected but messages or other doesn’t load… I don’t know if it’s OS related…
Nope, nothing changed in that regard. It’s a real bummer to hear that. My hardware colleagues tell me that it is not a hardware issue they have seen before.
What happens if you boot into recovery? Does that work?
If it’s really only the screen, you could also try to use a USB on-the-go (OTG) adapter and connect a keyboard. The ROM includes drivers for USB keyboards. This might also work when entering the decryption password.
It will only update the system partition. Your data will not be touched.
Do you use GApps? What apps do not load properly?
1 Like
@ilaz, thanks for the useful debugging.
It could be that the OS and battery needed some calibration first. Did you change anything else?
Is it possible to just set this to a high number? I assume there are protocols and standards to be adhered.
I use OpenGapps. Gmail doesn’t synchronize as it should but also whatsapp… I receive messages long after they are send and I don’t always get notifications either…
With Gmail, I see the title of the message but when I try to load it it won’t always load.
No I didn’t change anything…
Is it possible for you to install the GApps package that we provide next time you update? I cannot give support for OpenGApps but would hate to have the same issue in the GApps package we provide.
I think some of these problems are also just on Google’s side. I know similar issues also exist on other phones.
(I assume your connection is fast and stable when you test this).
Sure thing… but I need min gapps and I don’t like having all the useless apps on my phone… that is why I use OpenGapps.
The FP2 doesn’t have this problem though (lots of others but not this one!) 
Maybe we can make a list of apps that I can remove from our package? Which ones do you think are superfluous?
Reg. SMS to MMS conversion: Emoticons - Convert SMS to MMS at a price! . Apparently this has been changed before.
1 Like
I’ve let it sit without a battery over the weekend and was able to boot it up this morning. Although the brightness is on it’s highest level, the screen is barley lit. It looks as if the brightness is degrading the longer it is turned on. I hope to be able to record that behaviour as a video tomorrow.
I’ve just tried to see something with adb logcat and got many messages regarding the backlight. Small extract:
D/PowerManagerDisplayState( 1590): mTask: on = true, mActualOn = true, backlight = 50, mActualBacklight = 50
D/PowerManagerDisplayState( 1590): setScreenBrightness: brightness=47
D/PowerManagerDisplayState( 1590): Requesting new screen state: on=true, backlight=47, mChangeInProgress=false
D/PowerManagerDisplayState( 1590): on mTask
D/PowerManagerDisplayState( 1590): mTask: on = true, mActualOn = true, backlight = 47, mActualBacklight = 50
D/PowerManagerDisplayState( 1590): mTask: on = true, onChanged = false, backlightChanged = true, backlight = 47
D/LightsService( 1590): setLight_native: light=0, colorARGB=0xff2f2f2f, flashMode=0, onMS=0, offMS=0, brightnessMode=0
D/lights ( 1590): write_int open fd=261
D/MessageMonitorLogger( 1590): Monitor message handler is null
D/PowerManagerDisplayState( 1590): mTask: on = true, mActualOn = true, backlight = 47, mActualBacklight = 47```
I try to log more and provide that log to you - I still hope it's not a hardware issue.
At the last moments of the lock the screen went completly black and I tried to get it responding using the power button.
I'll try booting into recovery soon and report back.This is strange, mainly for the reason that it is supposed to be enabled already:
From the source code:
// This flag is somewhat confusing. If mEnableMultipartSMS is true, long sms messages are
// always sent as multi-part sms messages, with no checked limit on the number of segments.
// If mEnableMultipartSMS is false, then mSmsToMmsTextThreshold is used to determine the
// limit of the number of sms segments before turning the long sms message into an mms
// message. For example, if mSmsToMmsTextThreshold is 4, then a long sms message with three
// or fewer segments will be sent as a multi-part sms. When the user types more characters
// to cause the message to be 4 segments or more, the send button will show the MMS tag to
// indicate the message will be sent as an mms.
private static boolean mEnableMultipartSMS = true;
But, I can confirm the behavior, and the threshold is set to 4 (which matches the limit of max 3 SMS before it gets converted that you found).
private static int sSmsToMmsTextThreshold = 4;
We will discuss this and include it if it makes sense for most of our users.
Good to hear that you got it booting again.
If possible, it would be great, if you could also record adb bugreport which includes logcat but also many other useful logs.
Before turning off your phone, make sure to have backed up any data that is important for you.
1 Like