Merci trefix, (un peu confus comme d’habitude avec /e/ … )
there are no wipe for system on my phone recovery, and i’m asking SuzieQ
but i can delete system.
yes twrp. Can i install Android Pie onto Android 11 ? GSI
I have installed Android 12 using that method on Youtube video, but i do it a bit different and there are no option to wipe system on my phone so i delete it different.
Not E-Rom, From Google.
I wish i can get E-rom Pie version but my comes with Android 10
I am using Redmi K30 5G with A/B Arm64. But I am facing bootloop problem with latest /e/ OS GSI (Q).
Details here: Latest GSI Bootloop Issue - /e/ Devices / GSI - /e/ community
Any solution please?
SAMSUNG A8 (2018) ARM64 A/B on latest 3 vendors, starting with [A/B][TREBLE][9.0][A530F/A530W/A730F]SaR patch and kernel for Pie Vendor | XDA Forums .
1 Like
Hello !
After installing an /e/ OS GSI (/e/ image ROM download) on a Sony Xperia X (suzu) (https://github.com/phhusson/treble_experimentations/wiki/Sony-Xperia-X), I was informed that the microphone doesn’t work : during a call, the remote participant is heard just fine, but the local participant is not heard.
Here’s a log after a call using Signal, taken using MatLog :
device_info.txt
dmesg.txt
logcat.txt
I believe the relevant lines start here :
09-04 11:15:38.155 E/audio_hw_utils(16102): send_app_type_cfg_for_device: Could not get ctl for mixer cmd - Audio Stream Capture 16 App Type Cfg
And then :
09-04 11:15:38.157 E/ACDB-LOADER(16102): Error: ACDB get asm topology returned = -8
09-04 11:15:38.159 E/ACDB-LOADER(16102): Error: ACDB get adm topology for acdb id = 4, returned = -8
09-04 11:15:38.160 E/ACDB-LOADER(16102): Error: ACDB_CMD_GET_AUDPROC_COMMON_TABLE_SIZE Returned = -19
09-04 11:15:38.161 E/ACDB-LOADER(16102): Error: ACDB audproc returned = -19
09-04 11:15:38.163 E/ACDB-LOADER(16102): Error: ACDB_CMD_GET_AUDPROC_VOL_STEP_TABLE_SIZE Returned = -19
09-04 11:15:38.164 E/ACDB-LOADER(16102): Error: ACDB AudProc vol returned = -19
09-04 11:15:38.166 E/ACDB-LOADER(16102): Error: ACDB_CMD_GET_AUDPROC_STREAM_TABLE_SIZE Returned = -19
09-04 11:15:38.167 E/ACDB-LOADER(16102): Error: ACDB get audstream table returned = -19
09-04 11:15:38.170 E/ACDB-LOADER(16102): Error: ACDB_CMD_GET_AFE_COMMON_TABLE_SIZE Returned = -19
09-04 11:15:38.171 E/ACDB-LOADER(16102): Error: ACDB AFE returned = -19
09-04 11:15:38.173 E/audio_route(16102): unable to find path 'audio-record-voip'
09-04 11:15:38.178 E/audio_hw_primary(16102): start_input_stream: pcm_prepare returned -1
(Also posted here : https://github.com/phhusson/treble_experimentations/issues/1997)
1 Like
Hello, do you or anyone else know if this project is suitable to install efoundation platform on a Nokia 8? I’am new at this forum and not very technical with this IT stuff yet. I’d like to know if and how I can install e / os on my Nokia 8.
From the initial post, you can read :
For - Nokia 8 - use GSI type “ARM64 A/B”
1 Like
… and for 2021 / 22
Thanks for the links and help. I read that the goal of the use of project treble is for testing, not for normal daily use. I would like to use it for daily use as a ‘normal’ phone user, because I want to degoogle my phone. Can anyone can give an advise if project treble is suitable for me or not? I use a Nokia 8.
So first we check Smartphone Selector, does Nokia 8 feature – not as yet! Do we see it in Search results for '#unofficial Nokia 8' - /e/ community – not today.
GSI is great for experimenters!
Will the Motorola e (2020) be added for use with your OS. I just tried the install and it is not supported. Also if I knew how to code properly I would gladly help your cause but being a 53yr old idiot at times I would not trust myself at times.
Motorola has an irritating variety of models and often several models within a model line. Therefore, as a first step, it is important to identify the model exactly, e.g. Motorola Moto E 2020: XT2052-1, XT2052-2, XT2052-2PP, XT2052-5, XT2052-6 or XT2052-DL.
The most popular model is Motorola Moto E 2020 (codename: ginna) XT2052-1. It comes with stock Android 10 and Dynamic Partition / Super.img.
There are numerous unofficial custom ROMs, for example with LineageOS. I have not found a /e/OS. Therefore the installation of /e/OS ‘Q’ GSI offers itself. As a first installation attempt, I would follow GSI instructions from /e/
I apologize for not listing the complete model type since I just purchased the phone from my carrier Ting Mobile which is run on a T-Mobile platform or main carrier but it is the Motorola e 2020 Model XT2052-1
LineageOS does not work with my phone as well and being on a very limited income I guess I have to be invaded by Google always unless I can use Linux on my phone.
Hi, there!
IMG-e-1.6-q-20221204240086-dev-treble_arm64_bvN worked with a Moto G8 (XT2045-1/RAV), but only when installing from stock Android 10 (I got a bootloop when using Android 11). I think it makes sense, since the ROM is based on Android 10.
It seems to work quite well, and I am very impressed with how the UI and apps are well polished overall. Only the Apps is somewhat sluggish sometimes. I would love to see a filter for searches (like only list Open Source apps, etc), mainly because the sections do not allow searching.
A few suggestions:
- Icons cannot be re-arranged in folders (workaround is moving them out and putting them back in the order you want)
- Please consider adding two system features: quick unlock (screen is unlocked when the correct PIN is entered, no need to hit ENTER) and disable the power menu and quick settings when the screen is locked (Lockdown mode helps, but it could be more “secure” by default)
Two questions:
-
Any reason why the microG build is not the stock one from F-Droid, for instance? I needed a newer version for some app to work properly and I could not updated it, so I cannot keep using /e/, unfortunately.
-
Any plans for GSI using R? I saw in the Gitlab releases that there are 1.6-q, 1.6-r and even 1.6-s but the GSI is only Q.
Congrats on this great project!
Regards
What adequate alternative is there for /e/ GSI?
/e/ and other custom Rom development teams build a modified microG GmsCore (com.google.android.gms) into their ROMs.
If you want to use the current microG GmsCore v0.2.26.223616, the /e/ GmsCore v0.2.24.214816 or v0.2.25.223616 can be manually replaced by the user. With a TWRP recovery and its FileManager this isrelatively uncomplicated to do.
At least since WEEK 36, 2022 is communicated every week:
S and R version of GSI yet to be planned. Awaiting developer availability
I’m also eagerly waiting for these GSI versions, because the /e/OS GSI ‘R’ and ‘S’ versions will allow many more devices to run the wonderful /e/OS GSI.
Install a vanilla custom ROM and install everything manually.
I did not have any luck doing this with any ROM for this device: any time I try to modify /system it results in a bootloop that can be fixed only by reflashing everything.
Yes, R or S /e/ GSI will be great!
Greetings!