Feedback for v1.15

  • Vendor Name: Xiaomi
  • Device name: Mi MIX 2
  • Device CodeName: chiron
  • Version of /e/OS or Stock which existed previously: /e/OS Android 12/S 1.14
  • Is the device Rooted: no

Successfully upgraded to /e/OS Android 13/T 1.15, using sideload method & TWRP :smiley_cat:

Big thanks to /e/ and Murena !

  • Vendor Name : Xiaomi
  • Device name: MIA1
  • Device CodeName:tissot
  • From version /e/OS: 1.14
  • Device is Not rooted

Works fine. First time root beer test says not rooted without build.props modification.Thanks!

Vendor Name : Xiaomi

  • Device name: Redmi note 9 pro
  • Device CodeName:joyeuse / miatoll
  • From version of /e/OS: 1.11
  • Device is Not rooted

SaftyNet passed. Root Beer passed. Execellent work!

Vendor Name: Motorola
Device name: Moto X 2014
Device CodeName: victara
Version of /e/OS existed previously: 1.14-r
Version of /e/OS after upgrade: 1.15-r-20230916331434-dev-victara
The device is Not rooted

Mic input volume is still too low on my device. Up until now, I could modify the /system/vendor/etc/mixer_paths.xml file and ramp up some values. Now that debugging has been removed, I cannot enable usb root access anymore.
How can I fix it again?

> ~/P/a/victara-low-mic-volume diff mixer_paths.xml mixer_paths-new.xml                    23:46:00
42,51c42,51
< 	<ctl name="DEC1 Volume" value="84" />
< 	<ctl name="DEC2 Volume" value="84" />
< 	<ctl name="DEC3 Volume" value="84" />
< 	<ctl name="DEC4 Volume" value="84" />
< 	<ctl name="DEC5 Volume" value="84" />
< 	<ctl name="DEC6 Volume" value="84" />
< 	<ctl name="DEC7 Volume" value="84" />
< 	<ctl name="DEC8 Volume" value="84" />
< 	<ctl name="DEC9 Volume" value="84" />
< 	<ctl name="DEC10 Volume" value="84" />
---
> 	<ctl name="DEC1 Volume" value="95" />
> 	<ctl name="DEC2 Volume" value="95" />
> 	<ctl name="DEC3 Volume" value="95" />
> 	<ctl name="DEC4 Volume" value="95" />
> 	<ctl name="DEC5 Volume" value="95" />
> 	<ctl name="DEC6 Volume" value="95" />
> 	<ctl name="DEC7 Volume" value="95" />
> 	<ctl name="DEC8 Volume" value="95" />
> 	<ctl name="DEC9 Volume" value="95" />
> 	<ctl name="DEC10 Volume" value="95" />
  • Vendor Name: Samsung
  • Device name: Samsung s9+
  • Device CodeName: star2lte
  • Version of /e/OS or Stock which existed previously: /e/OS Android 10/S 1.14
  • Is the device Rooted: no

Successfully upgraded to /e/OS Android 13/T 1.15-Dev
Working fine

Samsung Galaxy S9+ (1st Android 13 /e/OS-T)

Vendor Name: Samsung
Device name: S9+ Exynos SM-G965F/DS
Device CodeName: star2lte
Version of /e/OS which existed previously: e-1.14-q-20230815320612-stable-star2lte
Version of Recovery which existed previously: recovery-e-1.14-q-20230815320612-stable-star2lte
The device is: Not rooted


Clean install of SHRP_v3.1_stable-Official_star2lte-1675556930-2023-02-05
Clean install of /e/OS-T e-1.15-t-20230918331436-dev-star2lte

:white_check_mark: The first impression is positive.
:new: BlissLauchner 1.14.0


Note for Samsung DeX Station EE-MG950

:white_check_mark: HDMI to TV
:white_check_mark: HDMI to PC Monitor (Note: Touch PC Monitor: Touch without function)
:white_check_mark: 2x USB 2.0
:white_check_mark: Ethernet RJ45 ~ wired LAN
:white_check_mark: USB-C charging


Note for Samsung DeX Cable EE-I3100

:white_check_mark: USB-C to HDMI ~ TV + PC Monitor


Strange; I can’t edit my own posting :frowning:
Confirm: Austrian easybank app works now with 1.15-r: install, register, app PIN, …
Austrian easybank secTAN app seems to install & start too - though haven’t registered its use yet

Google Pixel 4a (Sunfish)

  • Vendor Name: Google
  • Device name: Pixel 4a
  • Device CodeName: Sunfish
  • Version of /e/OS which existed previously: e-1.14-s-20230819321663-dev-sunfish
  • the device is Rooted

OTA Update went smoothly. Everything works (first short tests).
I’m eagerly waiting for the upgrade to T !

THX for your great work!

Samsung Galaxy S10

Vendor Name: Samsung
Device name: G973F

after update to v1.15 S, problems with bluetooth disappeared. previously I couldn’t connect to my speaker

1 Like
  • Vendor Name: Samsung
  • Device name: Samsung s9+
  • Device CodeName: star2lte
  • Version of /e/OS or Stock which existed previously: /e/OS 10/Q v1.15 dev
  • Is the device: Not rooted

I tried upgrading to T, which didn’t work: sideload was successful but after rebooting the phone I got stuck on the /e/ logo. I downgraded to Q and then successfully upgraded to R.

Hi, does the heartrate sensor works by you?

1 Like

Have you tried “magisk” ?

OnePlus 7T Pro (1st Android 13 /e/OS-T)

Vendor Name: OnePlus
Device name: 7T Pro - Mod. HD1911
Device CodeName: hotdog
Version of CustomROM which existed previously: lineage-20.0-20230919-nightly-hotdog-signed
Version of Custom Recovery which existed previously: lineage-20.0-20230919-hotdog-recovery
The device is: Not rooted


After the month-long fiasco since upgrade Android S e-1.9-s-20230312268558-dev-hotdog, I was excited to see the first /e/OS-T upgrade.


First I unzipped e-1.15-t-20230917331436-dev-hotdog.zip, then unzipped the payload.bin file it contained, which in turn contained recovery.img (v.1.15) among other things. The next step was the installation of e-Recovery (v 1.15) via fastboot. Afterwards the successful installation of e-1.15-t-20230917331436-dev-hotdog.zip via adb sideload.

Clean install of /e/OS e-1.15-t-20230917331436-dev-hotdog
Clean install of /e/OS V1.15 Recovery

:white_check_mark: The first impression is positive.
:white_check_mark: BlissLauchner 1.14.0
:white_check_mark: eApp Lounge 2.6.3
:white_check_mark: e-Camera 1.15.1 e-Camera 1.15.1 with working Motorized pop-up Camera


Do you have any idea why you fail to upgrade to T ? Apparently some other user succeed.

Updated my Fairphome 3+ to eOS 1.15-s-stable. No issue so far.

  • Vendor Name Fairphone
  • Device name Fairphone 3+
  • Device CodeName FP3
  • Version of /e/OS or Stock which existed previously eOS 1.14-s-stable
  • Is the device Rooted / Not rooted
1 Like
  • Vendor Name Fairphone
  • Device name Fairphone 4
  • Device CodeName FP4
  • Version of /e/OS or Stock which existed previously IMG-e-1.14-s-20230816320616-stable-FP4
  • Is the device Rooted / Not rooted

The device is in boot loop. I’m not able to start the phone. Is there a way to boot into the previous version (Slot A/B)?

  • Vendor Name Gigaset
  • Device name ** Gigaset GS290**
  • Device CodeName GS290
  • Version of /e/OS or Stock which existed previously IMG-e-1.14-r-20230815320614-stable-GS290
  • Is the device Rooted / Not rooted

So far everything is working

Which app should I try? Samsung health not working if you know another app lemme know

  • Vendor Name Fairphone
  • Device name Fairphone 3
  • Device CodeName FP3
  • Version of /e/OS or Stock which existed previously eOS 1.14-s-stable
  • Is the device Rooted / Not rooted

Updated the device without any issues, it continues working flawlessly.

3 Likes

good question, that would be the next question for me.
I’ll to make some investigation.

Did you tried other apps? if yes which one ?

1 Like

Vendor Name : Sony Xperia
Device name : Z5 Companct
Device CodeName : suzuran
Version of /e/OS or Stock which existed previously : e-1.14
Is the device Rooted / Not rooted : Not rooted

Everything looking good so far, thanks!
A new behavior I see though that there is a pin needle in the status bar every now and then with a very short notification that says something about “account manager is active” (“Kontenverwalter” in German).
Any ideas what it means?