Feedback for v1.16

Oneplus
9 pro
lemonadep
e-1.16-t
bootloader unlocked
A13 eos sideloaded via e-os recovery

I am having huge warm up and battery train after installing e-1.16-t-20231018342574-dev-lemonadep update via OTA does anyone encounter same problem? I charged 3 times in one day yesterday.

  • ASUS
  • Asus Zenfone Max Pro M1
  • X00TD
  • e-1.15-t
  • Not rooted

Updated OTA easily and really fast. My only issue is that the Wi-fi/Mobile data signal is very weak, but I think is a hardware level problem. Aside from this is working fine.

  • Xiaomi
  • Mi A2
  • jasmine_sprout
  • 1.15-r
  • Not-Rooted

I’ve tried to update this morning via OTA. After the reboot, it got stuck in the Recovery screen. I restarted the device a couple of times but no luck.

To fix it, I tried to update via adb. No luck either.

Then I tried to downgrade to the 1.15 version. The problem still persisted.

I managed to boot back to the OS by booting into the 1.15 recovery mode, loading the OS and then turning off the device. After powering it on, everything went back to normal.

I’ll wait a couple of days to try updating again. Let me know if I can assist doing some testing on my end :slight_smile:

  • Vendor Name : motorola
  • Device name : moto g7 power
  • Device CodeName : Ocean
  • Version of /e/OS or Stock which existed previously : 1.15
  • Is the device Rooted / Not rooted: Not rooted

The download and installation went very well. As for the operation general after the installation and restart have been excellent, so far I have had no problems of any kind, everything is going great.

And as usual I want to thank the team that has developed this version.
Team have done a great job!!!

  • Vendor Name : Google
  • Device name : Pixel 4a
  • Device CodeName : sunfish
  • Version of /e/OS or Stock which existed previously : 1.15-r-stable
  • Is the device Rooted / Not rooted: Not rooted

I have updated my device manually by flashing dtbo.img and the custom recovery. Then I sideloaded the 1.16-t-dev. No issues detected so far.

  • Motorola
  • One Action
  • troika
  • previously /e/OS 1.8.1 R
  • device rooted
    After upgrading to /e/OS 1.16 T (from /e/OS 1.8.1 R) per adb sideload, device get stuck in boot screen / menu. Nevertheless Recovery can be started and downgrading back to 1.8.1 R works and brings 1.8.1 R up again. All S and T versions end up in boot screen as described above. Has anybody else the same issue and a solution? Thanks!

System details:
(bootloader) version: 0.5
(bootloader) version-bootloader[0]: MBM-2.2-troika_retail-6a359c146ce-21
(bootloader) version-bootloader[1]: 0316
(bootloader) product: troika
(bootloader) board: troika
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 2
(bootloader) storage-type: ufs
(bootloader) ufs: 128GB SAMSUNG KLUDG4U1EA-B0C1 FV=0800
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=01 M8=12
(bootloader) cpu: Exynos9609
(bootloader) serialno: ZY326PLNM7
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) meid:
(bootloader) date: 09-08-2019
(bootloader) sku: XT2013-2
(bootloader) carrier_sku: XT2013-2
(bootloader) battid: SB18C43602
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: “Sat Oct 28 12: 6:58 UTC 2023”
(bootloader) ro.build.fingerprint[0]: motorola/troika_retail/troika_spro
(bootloader) ro.build.fingerprint[1]: ut:10/QSBS30.62-29-11-10/d2a947:us
(bootloader) ro.build.fingerprint[2]: er/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.samsung: 20190525
(bootloader) version-baseband: S337AP_TROIKA_SGCS_QB3620772
(bootloader) kernel.version[0]: Linux version 4.14.113-user+ (nobody@and
(bootloader) kernel.version[1]: roid-build) (Android (4691093 based on r
(bootloader) kernel.version[2]: 316199) clang version 6.0.2 (and
(bootloader) kernel.version[3]: roid.googlesource.com/toolchain/clang 18
(bootloader) kernel.version[4]: 3abd29fc496f55536e7d904e0abae47888fc7f)
(bootloader) kernel.version[5]: (https://android.googlesource.com/toolch
(bootloader) kernel.version[6]: ain/llvm 34361f192e41ed6e4e8f9aca80a4ea7
(bootloader) kernel.version[7]: e9856f327) (based on LLVM 6.0.2svn)) #1
(bootloader) kernel.version[8]: SMP PREEMPT Wed Jun 23 01:02:21 CDT 2021
(bootloader) bootloader.git: MBM-2.2-troika_retail-6a359c146ce-210316
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 7

Tried to manually according to instructions for kiev. Error 7 which is a common error. Have to flash stock and then flash /e/os…annoying, but doable.

When sharing your feedback or issues, Please add the following details

Vendor Name Motorola
Device name Moto G 5G / Motorola One 5G Ace
Device CodeName kiev
Version of /e/OS or Stock which existed previously 1.15
Is the device Rooted / Not rooted not
  • Vendor Name: Asus
  • Device name: Zenfone 8
  • Device CodeName: sake
  • Version of /e/OS or Stock which existed previously: /e/OS 1.15 S
  • Is the device Rooted / Not rooted: not rooted

Upgrade to 1.16 S went fine - no issues yet. Thanks again for the good work!

Gigaset
GS-290
v1.15-s
Not rooted

In the release notes for 1.16-t, there is no mention of a fix for being unable to send SMS messages. Does 1.16 fix this issue?

  • Vendor Name : Samsung
  • Device name: S8
  • Device CodeName: dreamlte
  • Version of /e/OS or Stock which existed previously: 1.15-r dev
  • Is the device Rooted / Not rooted: not rooted

Everything seems fine…

  • Vendor Name: Samsung
  • Device name: Galaxy S10e
  • Device Code name: beyond0lte
  • Version of /e/OS which existed previously: 1.15-s-dev
  • Not rooted

No issues. Thanks to the team!

I also have the dual-sim H8324. I’m definitely unable to control call volume at all presently, while I was able to prior to T. @Manoj, any advice how to proceed?

  • FP4
  • 1.15-s stable
  • Not rooted

Updated to 1.16-s, very fast! No new problem so far, thanks to the team.

Still have the Mail notification issue, which actually is a problem of the Mail app not being able to run in the background.

1 Like

You can raise an issue in Gitlab if not already done. Pl share the issue ID with me on this thread once done. The developers may want to see some logs to debug the issue which could be shared in the gitlab issue.

  • FP3
  • 1.16-s stable
  • not rooted

CacheCleaner 1.8.2 seems to have problems now. It starts but stops then after two or three apps, hangs for a minute (or so) and then terminates silently.

Update: SD Maid SE does work.

1 Like

Vendor Name: Samsung
Device name: S7
Device CodeName: SM-G930F
Version of /e/OS: 1.15-20230913330637
(q, stable, herolte)
Not rooted

Works fine, another big thanks to the team keeping this hardware alive so well!

2 Likes
  • Vendor Name: Fairphone
  • Device name: FP3
  • Device CodeName: FP3
  • Version of /e/OS or Stock which existed previously: /e/OS-1.15-stable
  • Is the device Not rooted

I received the OTA update yesterday evening. Everything is working smoothly.
Thank you for your good work!
I will continue supporting you.

1 Like

. Vendor Name: Fairphone
. Device name: Fairphone 4
. Device CodeName: FP4
. Version of /e/OS or Stock which existed previously: /e/OS-1.15-stable
. Is the device rooted: Not rooted

Updated yesterday to /e/OS-1.16-Stable. Still on Android 12 though.
Everything’s well so far. “Tout nickel!” Thank you!

1 Like

Vendor Name: Samsung
Device name: Samsung S8 SM-G950F
Device CodeName: dreamlte
Version of /e/OS or Stock which existed previously: 1.11-r-20230509288096-stable-dreamlte
Version installed now : 1.16-r-20231017342509-stable-dreamlte
Is the device Rooted / Not rooted: Not rooted

Big improvement on GPS !! I used to have to turn it on and off several times before it would show any sign of life. Now it works every time.

Issues experienced :

  • The “finishing the installation” notification does not disappear despite multiple reboots.
  • Notifications are no longer displayed, at least for Signal and Messenger
  • The GPS compass is of by 90°

Other than that, everything works great ! Well done :slight_smile:

. Vendor Name: Fairphone
. Device name: Fairphone 4
. Device CodeName: FP4
. Version of /e/OS or Stock which existed previously: /e/OS-1.15-stable
. Is the device rooted: Not rooted

Updated yesterday to /e/OS-1.16-Stable.
No Problems so far.
Thank you team.

1 Like