Gianna,
my tablet has only 2GB RAM. It’s running slow d/t this limitation. Not sure it’s worthwhile doing this jump to e? What do you think?
Have made some initial preparations but not yet sure I can go further yet. Do you have any additional advices/warnings?
FP3: As already mentioned, the App Lounge does not update or install anything. Please help with ideas if possible. Other functions are apparently working fine.
@Hartmut, for App Lounge “stuck” please try
Settings > Apps and notifications > See all … apps > App Lounge > Storage & cache > Clear storage | Clear cache
- Vendor Name: Teracube
- Device name: Teracube 2e
- Device CodeName Emerald
- Previous Version of /e/os: 1.11
- Is the device Rooted / Not rooted: Not Rooted
Apps work, Internet works, Email works, SMS works.
Issues:
- Battery Drain
- Unable to make or receive phone calls
- Unable to access voice mail
Hi,
The Teracube 2e (emerald) update 1.12.3 is no more proposed.
Has it been removed due to phone calls issues encountered by users ?
- Vendor Name: Motorola
- Device name: G7 Play
- Device CodeName: Channel
No v1.12.3 build available.
The latest build at https://images.ecloud.global/dev/channel/ is e-1.8.1-r-20230205.
In the 1.12-beta Test Session gitlab issue, we can see a e-1.12-rc.2-s-20230602295656-dev-channel.zip build, but it has not been released. This device missed out on the 1.9, 1.10, 1.11 builds as well. All the other G7 devices (lake, ocean, river) have up-to-date 1.12.3-s builds available
Reported in the testing Telegram channel. Gitlab issue raised
Pl can you create an issue around this. The same can be assigned to Marvin the microG creator himself.
2 Likes
Fairphone 3+
FP3
From 1.11s stable
Not rooted
I had been concerned about updating to v1.12.3 having read the reports of location issues being experienced by some users.
However, I have now updated and after initial testing all seems to be working well with no location issues noted. Update took slightly longer than usual at 40 minutes (screen on, phone not used). Again no ‘install’ prompt after download, something I first noted in v1.11s update.
I’m pleased that App Lounge now offers the correct version of an app for update (where the installed version is the Play Store version rather than that from F-Droid), and also that there is now an option to stop App Lounge offering to update apps installed from other sources.
However, I believe that it will still not offer a choice of initial installation source where an app is available both in F-Droid and the Play Store (an outstanding issue on Gitlab relates to this).
Although tracker records for all apps were deleted from Advanced Privacy (not an issue for me), the record of the single allowed tracker I have was correctly retained. However, I didn’t like the update re-enabling the Advanced Privacy widget (I’d removed it for a reason!) but that was easily removed (again).
All in all I’m currently very pleased with the update.
Hello,
Vendor Name: Fairphone
Device name: FP4
Device CodeName: FP4
Version of /e/OS which existed previously: 1.11 stable
The device is not rooted
Battery drain issue is resolved.
But had several times that without touching the screen it opened various apps
Now gone again for several days...
Device: Fairphone 3 (FP3)
Previous version: 1.11
Device not rooted
The upgrade went well.
But I see a regression in one app, when it requests geolocation: https://play.google.com/store/apps/details?id=com.micropole.android.tcl_mobile (installed through AppLounge, of course)
Symptom: the app crashes with following adb logcat excerpt, when it tries to find my location:
07-03 18:27:26.674 1665 1665 D AndroidRuntime: Shutting down VM
07-03 18:27:26.674 1665 1665 E AndroidRuntime: FATAL EXCEPTION: main
07-03 18:27:26.674 1665 1665 E AndroidRuntime: Process: com.micropole.android.tcl_mobile, PID: 1665
07-03 18:27:26.674 1665 1665 E AndroidRuntime: java.lang.NullPointerException: Listener must not be null
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at com.google.android.gms.common.internal.Preconditions.checkNotNull(com.google.android.gms:play-services-basement@@18.0.0:2)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at com.google.android.gms.common.api.internal.ListenerHolders.createListenerKey(com.google.android.gms:play-services-base@@18.0.1:1)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at com.google.android.gms.location.FusedLocationProviderClient.removeLocationUpdates(Unknown Source:6)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at com.airbnb.android.react.maps.FusedLocationSource.deactivate(FusedLocationSource.java:70)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at com.google.android.gms.maps.zzs.deactivate(com.google.android.gms:play-services-maps@@17.0.1:1)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at com.google.android.gms.maps.internal.zzj.zza(com.google.android.gms:play-services-maps@@17.0.1:1)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at com.google.android.gms.internal.maps.zzb.onTransact(com.google.android.gms:play-services-maps@@17.0.1:3)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at android.os.Binder.transact(Binder.java:1064)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at com.google.android.gms.maps.internal.ILocationSourceDelegate$Stub$Proxy.deactivate(ILocationSourceDelegate.java:121)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at org.microg.gms.maps.mapbox.SourceLocationEngine.removeLocationUpdates(SourceLocationEngine.kt:41)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at org.microg.gms.maps.mapbox.GoogleMapImpl.updateLocationEngineListener(GoogleMap.kt:423)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at org.microg.gms.maps.mapbox.GoogleMapImpl.setLocationSource(GoogleMap.kt:436)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at com.google.android.gms.maps.internal.IGoogleMapDelegate$Stub.onTransact(IGoogleMapDelegate.java:474)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at org.microg.gms.maps.mapbox.GoogleMapImpl.onTransact(GoogleMap.kt:876)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at android.os.Binder.transact(Binder.java:1064)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at com.google.android.gms.internal.maps.zza.zzc(com.google.android.gms:play-services-maps@@17.0.1:2)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at com.google.android.gms.maps.internal.zzg.setLocationSource(com.google.android.gms:play-services-maps@@17.0.1:3)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at com.google.android.gms.maps.GoogleMap.setLocationSource(com.google.android.gms:play-services-maps@@17.0.1:2)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at com.airbnb.android.react.maps.AirMapView$15.onHostResume(AirMapView.java:400)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at com.facebook.react.bridge.ReactContext$1.run(ReactContext.java:224)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:938)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:201)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at android.os.Looper.loop(Looper.java:288)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7870)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
07-03 18:27:26.674 1665 1665 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003)
I reproduce the same issue after removing the app data. I also reproduce it on another device: Samsung S5 (SM-G900F)
It might be a bug of the app itself, but the fact that it affects geolocation (and that it was working well with /e/ OS v1.11) makes me suspect a regression due to microG upgrade, with its geolocation refactoring.
Workaround: remove app data, and do not use geolocation
Should I create a separate thread? A gitlab ticket?
1 Like
On further testing there still appears to be an issue in App Lounge where apps are available in both the Play Store and F-Droid. Although following the v1.12.3 update I was able to update the Play Store version of an app (for the first time in a while), subsequent searches have produced incorrect results.
So a search for Vespucci (Play Store version installed) incorrectly shows the F-Droid version, while a search for Proton VPN (F-Droid version installed) incorrectly shows a non-F-Droid version.
I’ve opened an issue in Gitlab here https://gitlab.e.foundation/e/backlog/-/issues/7103 .
i appreciate the information but this does not resolve my problem. my APN settings are correct, i verified my settings with the information from my network provider website and with a call to customer service that i had to make with a borrowed phone. my data continues to work but i still do not have voice over LTE, my phone is set for VoLTE calling but i still cannot make or receive calls.
1 Like
For now the fix has gone on the stable builds. Will update when the dev builds will also get this.
1 Like
My Lenovo Smart Tab M10 HD TB-X306FA also has 2/32 GB and works very well with /e/OS GIS ‘Q’ V.12.3.
Cheers Gianna, thanks for the feedback!
Samsung S10
Everythong works so far, but sometimes it seems that Microphone isn’t working. E.G. in BirdNET and Merlin Bird Recognization sometimes no sound is recorded.
Another point is the calendar. In the new built i cannot change the calendar in the appointment, e.g. from personal calendar to family calendar.
Thanks for the great software, especially GPS is working now much better.
Best wishes
Until now i got no update for my Xiaomi MiA2 it is still on v1.11. (https://images.ecloud.global/dev/jasmine_sprout/)
I hope this device will get the update soon.
many thanks for your excellent work
Hi.
Vendor Name: Xiaomi
Device name: Redmi Note 8T
Device CodeName: ginkgo
Version of /e/OS or Stock which existed previously: 1.11
Is the device Rooted / Not rooted: The 1.11 is rooted.
There’s no update available for my phone. The System Updater (“Systemaktualisierungen”) says that the newest eOS-Version is running on my phone. When I tip the update (“Aktualisieren”) button, it says that no new updates could be found.
So what about 1.12? Still not released for the Xiaomi Redmi Note 8T? Has it been forgotten…?
Cheers,
Volker
1 Like