Feedback for v1.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

Hi,

vendor name: Fairphone
device name: FP3
OS-Version: 1.12.3-s-20230615299639-stable-FP3

Update broke usage of bike-rental app. Used Donkey Republic Bike-App, but App isn’t working since the update. Might have to do with the change in location-settings? App support couldn’t help (“we don’t plan to have support for alternative location services other than the official Google one”). :confused:

Hi,

vendor name: Fairphone
device name: FP3+
OS-Version: 1.12.3-s-20230616300623-dev-FP3

I did a fresh install and most of the things seem to be working fine…
But I have a obvious battery drain problem, that shortens battery life a lot compared to 1.11-r-stable I was running before.
In Settings → Battery it showed that the Mail App was using 137% of battery, followed by Android System. Mail is just receiving in the backgroud (3 mail accounts), sometimes reading a bit, but no different usage than before on 1.11-R

Update: I also use murena cloud and saw that it uploaded my Music folder, which had a couple of GB, but not sure what this has to do with the mail app. Where can I uncheck the upload of music into cloud ?

Update2: Seems that music sync cannot be independently switched off. Can I control what backs up/syncs to Murena account - #9 by ywo4d
I will monitor battery usage, without massive cloud syncs in the backgroud.

Same here, also on Redmi Note 8T. But it seems like it’s not the only model affected.

I’ll keep this short because there is nothing new to report. Gigaset GS-290, not rooted. Update as usual without problems, everything works as before.

I’m finding that the Seek app is actually able to determine location for the first time in a while on my FP3 and link it to an observation.

However, what’s strange is that, having identified a plant with its location, if I then try to view the observation while GPS is still active the app crashes. If I view the observaion while GPS is off it works fine.

The app also behaves strangely if I try to manually select location while GPS is off. Occasionally it works, most of the time the typing box and map flicker wildly then settle on a location miles away from the one I typed in.

I don’t know if this is a Seek app issue or related to the new location set-up.

I have the same with the Tesla app. GPS on - crash. GPS off - it works.

Regarding Seek and Tesla just mentioned above. This may fit with a difference between “GPS from the device” and a thing which seems odd to me; the app may acquire “GPS though Google Play Services” as this is a feature highlighted to app developers – the thought being that a Google phone can deliver this more efficiently than rely on the device sourced GPS.

It seems from my reading that micro-G may well handle “GPS though Google Play Services” just fine (mostly !).

Hi,
for me nothing works well with Seek.
iNaturalist works well but the Seek app does not.
More, it crash when I try to enter the location with the last updated version (2.14.10 on my S9+).
I tried with and without GPS with the same results.

The only time I’ve found that Seek crashes is when trying (with location enabled) to access a page which contains a map, for example an individual recorded observation.

Otherwise it all seems to work OK, it determines location correctly and includes this information when saving a record.

Did you need “Lenovo Smart & Rescue Assistant”?
It’s only supported for Windows…
Made some prep on my Linux, but need to fully understand this concept before commencing.
Did you ran the remove dm verity?

Thanks

Oneplus
Oneplus 8 (IN2013)
instantnoodle
From Stock OxygenOS 12.1 IN2013_11_C.36
not rooted

No touch screen. Cannot do anything once flash complet

Perhaps you can find something here …

Vendor Name: Google

Device name: Pixel 4a

Device CodeName: sunfish

Version of /e/OS or Stock which existed previously: /e/ 1.11 “S” DEV
note: Stable R with factory android 11 modem only works with Edge on Mint/T-Mobile, no LTE. S Dev works with LTE on factory android 12 modem with Mint/T-Mobile USA.

Is the device Rooted / **Not rooted**: NOT rooted

install was flawless. Phone works… except MMS broke with update (worked with 1.11 S Dev) reset and re-entered APN for Mint Mobile (T-Mobile mvno). Stock messenger not working. Also Google messenger has same issues. regular texting works, can not send it receive any pic attachments - fail to send on my end.

/e/ OS version 1.12.3-s-20230617300623-dev-sunfish.

Update 07 July 2023, Still no go, What was done:

factory reset /e/ , manually re-flashed 1.12.3-s-20230628304336-dev-sunfish
set APN again (same as what works on a second factory google Pixel 4a android 13 known/proven functional)
used stock Messenger, also installed and tested SMS Messenger from F-Droid - both send SMS, fail on MMS

APN Settings located at https://www.mintmobile.com/help/how-to-configure-android-settings/

Captured logcat when trying to send an MMS from the /e/ stock messenger

07-07 10:34:32.939 2714 5962 D TelephonyProvider: match current APN size: 2
07-07 10:34:32.939 2714 2714 D PhoneSwitcherNetworkRequstListener: got request NetworkRequest [ REQUEST id=136, [ Transports: CELLULAR Capabilities: MMS&NOT_RESTRICTED&TRUSTED&NOT_VPN Specifier: <TelephonyNetworkSpecifier [mSubId = 2]> Uid: 1001 RequestorUid: 1001 RequestorPkg: com.android.mms.service] ]
07-07 10:34:32.939 2714 5962 D TelephonyProvider: match MVNO APN: 1
07-07 10:34:32.939 2714 5962 D TelephonyProvider: match carrier id APN: 0
07-07 10:34:32.940 2714 5962 I MmsService: [SendRequest@ec6d7ca {x-message-id:0}] No match with APN name: Wholesale, try with no name
07-07 10:34:32.940 2714 5962 I MmsService: [SendRequest@ec6d7ca {x-message-id:0}] Loading APN using name null
07-07 10:34:32.940 2714 5962 D TelephonyProvider: Using old permission behavior for telephony provider compat
07-07 10:34:32.946 2714 5962 D TelephonyProvider: match current APN size: 34
07-07 10:34:32.947 2714 5962 D TelephonyProvider: match MVNO APN: 1
07-07 10:34:32.947 2714 5962 D TelephonyProvider: match carrier id APN: 0
07-07 10:34:32.948 2714 5962 D MmsService: [SendRequest@ec6d7ca {x-message-id:0}] MmsNetworkManager: release, count=0
07-07 10:34:32.948 2714 5962 E MmsService: [SendRequest@ec6d7ca {x-message-id:0}] APN failure
07-07 10:34:32.948 2714 5962 E MmsService: com.android.mms.service.exception.ApnException: Can not find valid APN
07-07 10:34:32.948 2714 5962 E MmsService: at com.android.mms.service.ApnSettings.load(ApnSettings.java:116)
07-07 10:34:32.948 2714 5962 E MmsService: at com.android.mms.service.MmsRequest.execute(MmsRequest.java:213)
07-07 10:34:32.948 2714 5962 E MmsService: at com.android.mms.service.MmsService$2.run(MmsService.java:581)
07-07 10:34:32.948 2714 5962 E MmsService: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
07-07 10:34:32.948 2714 5962 E MmsService: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
07-07 10:34:32.948 2714 5962 E MmsService: at java.lang.Thread.run(Thread.java:920)
07-07 10:34:32.948 1663 2239 D ConnectivityService: releasing NetworkRequest [ REQUEST id=136, [ Transports: CELLULAR Capabilities: MMS&NOT_RESTRICTED&TRUSTED&NOT_VPN Specifier: <TelephonyNetworkSpecifier [mSubId = 2]> Uid: 1001 RequestorUid: 1001 RequestorPkg: com.android.mms.service] ] (release request)
07-07 10:34:32.950 2714 5962 I MmsService: [SendRequest@ec6d7ca {x-message-id:0}] processResult: failure(2) handledByCarrierApp: false mLastConnectionFailure: 0
07-07 10:34:32.950 2714 5962 I MmsService: [SendRequest@ec6d7ca {x-message-id:0}] MMS failed with error: 2 httpStatus:0
07-07 10:34:32.953 2714 5962 D MmsService: addToRunningRequestQueueSynchronized mRunningRequestCount=0
07-07 10:34:32.953 2714 5962 D MmsService: Move pending requests to running queue mPendingSimRequestQueue.size=0
07-07 10:34:32.953 4412 4412 V MmsSentReceiver: MMS sending result: 2
07-07 10:34:32.953 4412 4412 V MmsSentReceiver: content://mms/10
07-07 10:34:32.953 4412 4412 V MmsSentReceiver: MMS has failed to send, marking it as so in the database
07-07 10:34:32.956 966 966 I netd : networkSetPermissionForNetwork(100, 1) <7.03ms>

I have to add: After restarting the mobile phone, app permissions are resetted again. VPN permission has to be given again as well as installation permissions for F-Droid

Hi all,

Since v1.12.3 that I installed a week ago on my FP4 (1.12.3-s-20230615299639-stable-FP4) I find often that when I charge the phone before night, unplug it at 100%, put it in flight mode and open it in the morning the battery has lost 1.6%/h. Here are BetterBatteryStats reports that seem to indicate wakelocks activity but I’m not sure how to interpret them. Could anyone help? Thanks in advance.




What stands out for me from you log is

I MmsService: ... No match with APN name: Wholesale, try with no name
E MmsService: [SendRequest@ec6d7ca {x-message-id:0}] APN failure
E MmsService: com.android.mms.service.exception.ApnException: Can not find valid APN

The leading I is for Info; E is for Error.

So it seems the published APN contain an error. Other threads on the forum on the subject have the hashtag apn ← is a link !

There was a recent forum thread, Can't remove an APN from previous carrier, causing SMS failures where the published ANP worked with errors, but in the end on contacting the carrier, a slightly different APN was offered which fixed the problem.

I think contact your carrier is the way forward.