This is an unofficial and experimental build of lineage-16.0.
Please do feel free to try and report bugs on this thread (Logcats must be provided)
I will upload subsequent variants later on.
arm64 A-only Non-SU [no gapps] : https://drive.google.com/file/d/1A9kphkHJbRm1eL-6jh2-AuQABBvISOrz/view?usp=drivesdk
For future updates download links will be available at post 2.
You can join our telegram group for more help or discussion https://t.me/lineagegsi
This build has been tested and boots on Honor 7x.
Bugs noticed on the device:
Not full resolution
No torch
No hotspot
USB mtp mode has to be changed manually from dev settings.
Screenshots can be checked here, https://imgur.com/a/4GWQuQ4
Bugs may vary from device to device.
I am not the developer of this Gsi credit goes to @m_vaisakh
Thanks to @phhusson
Built using phhusson's build script.
Downloads:
ARM64 A-ONLY NO-GAPPS
ARM64-A-ONLY WITH GAPPS
Update 31/08/2018
ARM64 A/B NO-GAPPS (Thanks a lot to @eminem5055 , he built this)
You can also join telegram to support better with logcats:
Telegram Group
It's not booting on the Huawei Y6 (2018)
It is like every pie gsi everything works fine but no incall sound
iDecrypt said:
It's not booting on the Huawei Y6 (2018)
Click to expand...
Click to collapse
aljoscha81 said:
It is like every pie gsi everything works fine but no incall sound
Click to expand...
Click to collapse
Can you guys provide logs to check the issue?
Hey @avirk is volte with jio sim working???
Lucciferr said:
Hey @avirk is volte with jio sim working???
Click to expand...
Click to collapse
Haven't tested VoLTE yet. Should work, if it worked for you in los-15.1 treble build.
avirk said:
Can you guys provide logs to check the issue?
Click to expand...
Click to collapse
Yes i will send you a log file but i think it is a vendor issue cause every 9 gsi rom got that on my device
avirk said:
Can you guys provide logs to check the issue?
Click to expand...
Click to collapse
How should I provide logs when it's not booting.
iDecrypt said:
How should I provide logs when it's not booting.
Click to expand...
Click to collapse
By using adb... you can take logs as it's booting.
crayonicle said:
By using adb... you can take logs as it's booting.
Click to expand...
Click to collapse
It stucks in the bootloader so adb isn't working.
iDecrypt said:
It stucks in the bootloader so adb isn't working.
Click to expand...
Click to collapse
Huh, what the heck. You can try factory resetting? In stock recovery.
crayonicle said:
Huh, what the heck. You can try factory resetting? In stock recovery.
Click to expand...
Click to collapse
Already tried that, no Pie ROM is working on this phone :/
iDecrypt said:
Already tried that, no Pie ROM is working on this phone :/
Click to expand...
Click to collapse
Something must be broken on that side if you are at bootanimation then 90% chances that adb will work. Are you sure that you have treble supported twrp and already on a treble build?
bootloop on xiaomi mi6x
avirk said:
Something must be broken on that side if you are at bootanimation then 90% chances that adb will work. Are you sure that you have treble supported twrp and already on a treble build?
Click to expand...
Click to collapse
I don't have any TWRP but all Oreo GSIs are working fine, just the Pie GSIs aren't working, and i wont even get to the bootanimation.
Boots on P20-Lite but stuck on a Pixel configuration stopped working prompt loop.
mchtt said:
Boots on P20-Lite but stuck on a Pixel configuration stopped working prompt loop.
Click to expand...
Click to collapse
Delete SetupWizard in /system/priv-app via recovery and reboot. If you want a working Setup, use the vanilla variant an flash unofficial GApps by @Nezorflame.
Hi, Just flashed to my Umidigi A1 Pro - I am seemingly having the same issue with every Android 9 Pie GSI, everything flashes without issue, system starts and everything looks fine, then as soon as I open app drawer, or enter settings, the system freezes and screen becomes unresponsive, then phone reboots to lockscreen. I am new to flashing treble GSI's, but 8.1 Oreo GSI's don't seem to be affected. I have provided a logcat if this will be of any assistance.
https://drive.google.com/file/d/1vci1GXP9bGqWl1Pdnn9dMCloBYmVFIWf/view?usp=sharing
why cant i flash it ...it says size of image is larger than target device
Related
Hi all,
I've made my work on AOSP Phh-Treble as modular as possible, so that it can be reused on other ROMs.
As part of this effort, I'm releasing GSIs of LineageOS
This is a GSI, and true to the GSI spirit. It aims at supporting a maximum number of devices, but only with AOSP-available hardware features.
All credits obviously goes to LineageOS developers
v5: (2018-06-27)
Image for ARM64 A-only device with gapps
Image for ARM64 A-only device vanilla
Image for ARM64 A/B device with gapps
Image for ARM64 A/B device vanilla
Image for ARM32 A-only device with Android Go gapps
Image for ARM32 A-only device vanilla
v4: (2018-05-19)
Image for ARM64 A-only device
Image for ARM64 A/B device
Image for ARM32 A-only device
Image for ARM32 A-only devices, with Android Go gapps
V3: (2018-04-05)
Image for ARM64 A-only device
Image for ARM64 A/B device
Image for ARM32 A-only device
ChangeLog:
v4 (2018-05-19):
- Blackview A20 edition! Thanks to blackview for giving me this Android Go test device
- Fix Accents
- Update to latest AOSP Phh-Treble patches
- New Android Go variant with gapps
v3 (2018-04-05):
- Fix Galaxy S9 backlight control
- Support exfat sdcards on devices with exfat support in kernel
- Resize /system to maximum size on first boot
v2 (2018-03-26):
- Fix Galaxy S9 backlight control
How to build:
Code:
git clone https://github.com/phhusson/treble_experimentations
mkdir Lineage; cd Lineage
bash ../treble_experimentations/build-rom.sh android-8.1 lineage
Great Work!
Thanks for your work. I'll try this rom this weekend (I had problems with your other AOSP roms, I can't boot except the v9 one. I hope this version will boot).
iBen68 said:
Thanks for your work. I'll try this rom this weekend (I had problems with your other AOSP roms, I can't boot except the v9 one. I hope this version will boot).
Click to expand...
Click to collapse
I doubt it will boot.
What device is this? Could you get logs?
phhusson said:
I doubt it will boot.
What device is this? Could you get logs?
Click to expand...
Click to collapse
Huawei Mate 10 Pro BLA-L09. I will try to get logs when I try this rom.
Great work
bootloop on xperia xz1
i flashed it on stock rom and wipe userdata,cache on fastboot and also tried on twrp factory reset and cache,cache dalvik(i tried your aosp v9 v10 v11 it also doesn't work)
phhusson said:
I doubt it will boot.
What device is this? Could you get logs?
Click to expand...
Click to collapse
How can I get logs at this point?
eggimong said:
bootloop on xperia xz1
i flashed it on stock rom and wipe userdata,cache on fastboot and also tried on twrp factory reset and cache,cache dalvik(i tried your aosp v9 v10 v11 it also doesn't work)
Click to expand...
Click to collapse
Can you try this?
https://www.google.fr/amp/s/forum.x...l/how-to/treble-roms-pixel-2-xl-t3764851/amp/
What's the precise behaviour you're witnessing?
Do you get the White Android bootanimation, or only sony's logo?
Does it actually reboot when looping? You see the sony logo reappearing?
Does the device reboot to bootloader mode?
phhusson said:
I doubt it will boot.
What device is this? Could you get logs?
Click to expand...
Click to collapse
When I try
Code:
adb logcat
I got this:
Code:
PS C:\ADB> adb logcat
- waiting for device -
The adb daemon seems not to be started while the bootloop. When I go back to the AOSP v9 rom, I can see logs with the same command but it's pointless since this rom is booting well.
iBen68 said:
When I try
Code:
adb logcat
I got this:
Code:
PS C:\ADB> adb logcat
- waiting for device -
The adb daemon seems not to be started while the bootloop. When I go back to the AOSP v9 rom, I can see logs with the same command but it's pointless since this rom is booting well.
Click to expand...
Click to collapse
Does adb devices -l sees it?
phhusson said:
Can you try this?
https://www.google.fr/amp/s/forum.x...l/how-to/treble-roms-pixel-2-xl-t3764851/amp/
What's the precise behaviour you're witnessing?
Do you get the White Android bootanimation, or only sony's logo?
Does it actually reboot when looping? You see the sony logo reappearing?
Does the device reboot to bootloader mode?
Click to expand...
Click to collapse
Only sony's logo and it reappearing until I turn off the phone
eggimong said:
Only sony's logo and it reappearing until I turn off the phone
Click to expand...
Click to collapse
And did you try what's in the link I've given you?
phhusson said:
And did you try what's in the link I've given you?
Click to expand...
Click to collapse
can't flash on vbmeta partition with error
fastboot flash vbmeta vbmeta.img
FAILED <remote: Flashing is not allowed for partition>
Is it possible to build this w/ MicroG?
LiveDisplay and LED while charging do not work on Mido everything else work just fine
NadavCE said:
Is it possible to build this w/ MicroG?
Click to expand...
Click to collapse
Assume you're asking due to the news about Gapps and 'Uncertified Device' problems.
Seems like a lot more is riding on MicroG now ...
Also, pretty sad that Google have done this ... Treble was probably the best thing they've done for Android since its inception, both for custom ROM development and potentially speeding up software updates for those who don't tinker with their phones.
mudnightoil said:
Assume you're asking due to the news about Gapps and 'Uncertified Device' problems.
Seems like a lot more is riding on MicroG now ...
Also, pretty sad that Google have done this ... Treble was probably the best thing they've done for Android since its inception, both for custom ROM development and potentially speeding up software updates for those who don't tinker with their phones.
Click to expand...
Click to collapse
Well custom ROMs are whitelisted and so far I have not reported any issue with the Uncertified Device stuff on this GSI nor on RR GSI either, both by phhusson of course
patrick395x said:
Well custom ROMs are whitelisted and so far I have not reported any issue with the Uncertified Device stuff on this GSI nor on RR GSI either, both by phhusson of course
Click to expand...
Click to collapse
I don't think that is expected to remain the status quo. In fact if you read the screen / article, people running custom ROMs are expected to manually register their devices with Google ... and whether that is just a registration or additional tracking is unclear.
mudnightoil said:
I don't think that is expected to remain the status quo. In fact if you read the screen / article, people running custom ROMs are expected to manually register their devices with Google ... and whether that is just a registration or additional tracking is unclear.
Click to expand...
Click to collapse
I know, I read the article, but until we receive the Android ID registration we can keep using custom ROMs in an uncertified manner, once we are required to registrate our device we will see what happens
So we have official 9.0 update now, which means we have pie vendor installed our devices.
However, it seems non of GSI pie roms work on xz1 even though our vendor and kernel are working properly with pie firmware.
Is there anyone successfully installed 9.0 GSI rom after the official Pie update? Or is there any idea why they don't work?
Riskypedia said:
So we have official 9.0 update now, which means we have pie vendor installed our devices.
However, it seems non of GSI pie roms work on xz1 even though our vendor and kernel are working properly with pie firmware.
Is there anyone successfully installed 9.0 GSI rom after the official Pie update? Or is there any idea why they don't work?
Click to expand...
Click to collapse
everything is working fine on GSI 9.0 pie roms but if u need gcam, flash on aosp boot and vendor(because full camera2api and raw support), on stock blobs gcam doesnt work because there is no raw support on stock.
arslancn said:
everything is working fine on GSI 9.0 pie roms but if u need gcam, flash on aosp boot and vendor(because full camera2api and raw support), on stock blobs gcam doesnt work because there is no raw support on stock.
Click to expand...
Click to collapse
Thanks for your reply Can you suggest some roms that worked? Because whenever I try to boot my phone with this rom(https://forum.xda-developers.com/pr...opment-a-only-roms/ported-p-sgsi-pr2-t3845789), I get bootlooped
Riskypedia said:
Thanks for your reply Can you suggest some roms that worked? Because whenever I try to boot my phone with this rom(https://forum.xda-developers.com/pr...opment-a-only-roms/ported-p-sgsi-pr2-t3845789), I get bootlooped
Click to expand...
Click to collapse
try any updated ''GSI''(not sGSI) arm64 a only rom from here. sGSI roms have alot of bugs
arslancn said:
try any updated ''GSI''(not sGSI) arm64 a only rom from here. sGSI roms have alot of bugs
Click to expand...
Click to collapse
Thanks to your support, I've got finally found a working rom(Pixel Experienced Rom)! Maybe I think the roms I've tried are all sGSI roms that caused bootloops
Now I'm trying to use gcam now, so I've installed pie aosp vendor uploaded in sony open device project(fasboot flash oem ~~~.img). However, it seems it doesn't have problem with booting but gcam still crashes(I think it's cam2api problem). According to your previous comment, it seems I should flash aosp kernel which isn't provided by Sony. So should I manually compile the kernel to make it working?
Sorry for bothering :crying:
Riskypedia said:
Thanks to your support, I've got finally found a working rom(Pixel Experienced Rom)! Maybe I think the roms I've tried are all sGSI roms that caused bootloops
Now I'm trying to use gcam now, so I've installed pie aosp vendor uploaded in sony open device project(fasboot flash oem ~~~.img). However, it seems it doesn't have problem with booting but gcam still crashes(I think it's cam2api problem). According to your previous comment, it seems I should flash aosp kernel which isn't provided by Sony. So should I manually compile the kernel to make it working?
Sorry for bothering :crying:
Click to expand...
Click to collapse
use this guide and build needed AOSP images, flash all of them (boot.img, vendor.img, system.img and SODP OEM image too)
reboot one time, after u see setup, reboot recovery and make full wipe(system, data, cache, dalvik, internal), format data and reboot recovery
flash gsi image and gapps(if gapps not included)
reboot recovery, flash magisk and reboot.
now u have aosp rom with working gcam
arslancn said:
use this guide and build needed AOSP images, flash all of them (boot.img, vendor.img, system.img and SODP OEM image too)
reboot one time, after u see setup, reboot recovery and make full wipe(system, data, cache, dalvik, internal), format data and reboot recovery
flash gsi image and gapps(if gapps not included)
reboot recovery, flash magisk and reboot.
now u have aosp rom with working gcam
Click to expand...
Click to collapse
which version of gcam works?
arslancn said:
use this guide and build needed AOSP images, flash all of them (boot.img, vendor.img, system.img and SODP OEM image too)
reboot one time, after u see setup, reboot recovery and make full wipe(system, data, cache, dalvik, internal), format data and reboot recovery
flash gsi image and gapps(if gapps not included)
reboot recovery, flash magisk and reboot.
now u have aosp rom with working gcam
Click to expand...
Click to collapse
Thank you bro, everything works fine! I think I should pack the built images and upload in case someone needs this XD
Respect to Turkey, from Korea.
Riskypedia said:
Thank you bro, everything works fine! I think I should pack the built images and upload in case someone needs this XD
Respect to Turkey, from Korea.
Click to expand...
Click to collapse
:highfive: u can make a thread about flashing treble with full cameraapi 2 support and share your images with other XZ1 users!
Riskypedia said:
Thank you bro, everything works fine! I think I should pack the built images and upload in case someone needs this XD
Respect to Turkey, from Korea.
Click to expand...
Click to collapse
did you have same bug on XZ1?
the battery level always in 20%.
arslancn said:
:highfive: u can make a thread about flashing treble with full cameraapi 2 support and share your images with other XZ1 users!
Click to expand...
Click to collapse
Sadly, it seems it's impossible to use AOSP based system because of its stability. It's way too unstable to use, but I think I can share the built images to make progress! Again, thanks for your help
gacky1601 said:
did you have same bug on XZ1?
the battery level always in 20%.
Click to expand...
Click to collapse
I've never experienced the bug when I used that. Did that happen to your XZ1? Or is it the problem of the other Xperia devices? The biggest problem was that it's too unstable that I can barely use that. The network oftenly disconnects and randomly reboots itself.
Riskypedia said:
I've never experienced the bug when I used that. Did that happen to your XZ1? Or is it the problem of the other Xperia devices? The biggest problem was that it's too unstable that I can barely use that. The network oftenly disconnects and randomly reboots itself.
Click to expand...
Click to collapse
Yes,my device is G8342. The wifi bug and battery level bug.
my device couldn't connect to any wifi,but sharing hotspot in 2.4ghz/5ghz was fine.
Screen colors look strange.
Randomly reboot,too.
I don't know any solution.
I only knew the methods to the image step by step from Sony's source.
Maybe we should build the kernel by ourselves
The problem you mentioned about disconnecting network, does it happens on wifi or mobile data?
Sorry, just a quick question has as resurrection remix has a treble room out, has anyone tried it?
gacky1601 said:
Yes,my device is G8342. The wifi bug and battery level bug.
my device couldn't connect to any wifi,but sharing hotspot in 2.4ghz/5ghz was fine.
Screen colors look strange.
Randomly reboot,too.
I don't know any solution.
I only knew how to build the image step by step from Sony's source.
Maybe we should build the kernel by ourselves[/QUOTE
Yeah, we should... I'm just a newbie developer, and really sad that we're lack of developers who can help XZ1 users, but I believe one day users make this out together. The dispaly color is because of AOSP's default display color temperature, maybe we can fix this out by touch some configs of kernel
Click to expand...
Click to collapse
lilbrat said:
Sorry, just a quick question has as resurrection remix has a treble room out, has anyone tried it?
Click to expand...
Click to collapse
I think you can just try it with stock boot , vendor and oem.
I will works perfectly.
Don't forget to report if there is any problem or it work properly.
---------- Post added at 04:37 PM ---------- Previous post was at 04:20 PM ----------
[/QUOTE
Yeah, we should... I'm just a newbie developer, and really sad that we're lack of developers who can help XZ1 users, but I believe one day users make this out together. The dispaly color is because of AOSP's default display color temperature, maybe we can fix this out by touch some configs of kernel [/QUOTE]
Yeah. I think there are a few developers work on XZ1.
Have .
The working perfectly rom will be our target, like the thread below.
https://forum.xda-developers.com/xperia-xz1-compact/how-to/xz1c-g8441-lilac-aosp8-1-t3762581
Share your all files so that i can work with gcam to be installed properly to latest pixel experience.
:silly:
Thank you for the build, @luisgonzales1977
Waiting for A/B build.
ZainBilq said:
Thank you for the build, @luisgonzales1977
Waiting for A/B build.
Click to expand...
Click to collapse
when you finish testing :good::silly:
Will it include Mi9 in-display FP like in phhusson's AOSP?
luisgonzales1977 said:
when you finish testing :good::silly:
Click to expand...
Click to collapse
Yeah I know...just like that....
This Rom work in Lenovo k5 pro? Is a device arm64 aonly.
any AB love ?
TheUndertaker21 said:
any AB love ?
Click to expand...
Click to collapse
they are soon testing it...:good:
luisgonzales1977 said:
when you finish testing :good::silly:
Click to expand...
Click to collapse
I am a few hours on your rom and is working bugfree for me everything i need arcore also working very nice job:good:
Excellent work !
Booted successfully on Huawei p10 lite after changing selinux/mapping/26.0.cil .
Except I have faced settings FC when opening Decor room in X-Tensions and I'm not able to make logcat due to ADB unauthorized
Thanks
android q activity animation available sir?
won't be able to bootup on mate 10 lite
flamedrops said:
won't be able to bootup on mate 10 lite
Click to expand...
Click to collapse
you test?
successfully booted up on my Lenovo S5 (K520/Seoul), but on the first setting screen after boot it shown missmatch vendor notice (it recommend to flash vendor img). i still could skip it and continue by the way.
So about the missmatch vendor, will it hurt if i don't flash it? because i don't know which file of vendor img i should flash.
update : same as reported from other user several posts before, Decor room in X-Tensions FC when open
luisgonzales1977 said:
you test?
Click to expand...
Click to collapse
yes, i use to try every other rom, now im on havoc and it works.
Boots up in Blu Vivo XI. Can't seem to get magisk to work with any gsi's. Thanks for the rom.
aljoscha81 said:
I am a few hours on your rom and is working bugfree for me everything i need arcore also working very nice job:good:
Click to expand...
Click to collapse
Hi pal. Any specific steps to flash this rom on Z17? What rom as base do you have? Any nfound vendor or something else?
surfer30 said:
Hi pal. Any specific steps to flash this rom on Z17? What rom as base do you have? Any nfound vendor or something else?
Click to expand...
Click to collapse
I am on mokee as base installed as ever no further steps
Is there a chance to get an ARM32-A build? I would like to try this rom. Looks promising!
khuy21 said:
So about the missmatch vendor, will it hurt if i don't flash it? because i don't know which file of vendor img i should flash.
update : same as reported from other user several posts before, Decor room in X-Tensions FC when open
Click to expand...
Click to collapse
not need change vendor
just need set right fingerprint values in build.prop, some magisk modules may this
or search info and change it by hand
on short - fingerprint from system build.prop need to match values from vendor build.prop
Android 10 is here!
Took a while, but here's Lineage 17.1 builds, based on Android 10.
Everything should work AFAIK, but let me know if something doesn't.
If you run into problems installing Gapps, you might need an updated
TWRP build. It needed a change to support the new system-as-root
in Android 10. If the official TWRP builds doesn't have it yet, there's
links below of some builds I did.
For root, use Magisk: https://forum.xda-developers.com/apps/magisk
If you are doing backups of 17.1 with TWRP, and wants to restore one of these backups,
you need to flash this right after restoring, or otherwise the boot will hang: http://www.mediafire.com/file/a454nnpp8l7afbr/fix_rootfs_label.zip/file (Needed only for older TWRP, and not for the one linked to below)
Download:
GT-I9190: https://www.mediafire.com/file/ewdbbg757ujbc3r/lineage-17.1-20220816-UNOFFICIAL-serrano3gxx.zip/file
GT-I9192: https://www.mediafire.com/file/a0ya2fdcf0drjt1/lineage-17.1-20220817-UNOFFICIAL-serranodsdd.zip/file
GT-I9195: https://www.mediafire.com/file/3ky5...7.1-20220816-UNOFFICIAL-serranoltexx.zip/file
SPH-L520: https://www.mediafire.com/file/l0le....1-20220817-UNOFFICIAL-serranoltespr.zip/file
SCH-R890: https://www.mediafire.com/file/cqxl....1-20220817-UNOFFICIAL-serranolteusc.zip/file
Recovery (TWRP):
GT-I9190: https://www.mediafire.com/file/e42oml5716ekvk7/twrp-3.6.2_9-0-serrano3gxx.img/file
GT-I9192: https://www.mediafire.com/file/2plk5azmfxwsm5z/twrp-3.6.2_9-0-serranodsdd.img/file
GT-I9195: https://www.mediafire.com/file/wtsopyh3rmfoatf/twrp-3.6.2_9-0-serranoltexx.img/file
SPH-L520: https://www.mediafire.com/file/iw68mr671fgftnb/twrp-3.6.2_9-0-serranoltespr.img/file
SCH-R890: https://www.mediafire.com/file/417w6vp0m338fb0/twrp-3.6.2_9-0-serranolteusc.img/file
Link to all builds:
GT-I9190: http://www.mediafire.com/folder/4kjlyp6v2lfnh/lineage-17.1
GT-I9192: http://www.mediafire.com/folder/hw7l5hqe0fv1m/lineage-17.1
GT-I9195: http://www.mediafire.com/folder/3911mczazsvdt/lineage-17.1
Download Gapps: https://opengapps.org/?api=10.0&variant=pico
Sources:
https://github.com/LineageOS/android_kernel_samsung_msm8930-common
https://github.com/LineageOS/android_device_samsung_msm8930-common
https://github.com/LineageOS/android_device_samsung_serrano-common
https://github.com/LineageOS/android_device_samsung_serrano3gxx
https://github.com/LineageOS/android_device_samsung_serranodsdd
https://github.com/LineageOS/android_device_samsung_serranoltexx
https://github.com/arco/android_device_samsung_serranoltespr
https://github.com/arco/android_device_samsung_serranolteusc
Cellular not working on the 9192? Upgrade your baseband: https://forum.xda-developers.com/t/modem-odin-stopped-samsung-galaxy-s4-mini-duos-i9192.2768593/
Thanks arco <3
Thanks :good: arne everything working on I9192
Arslan140 said:
Thanks :good: arne everything working on I9192
Click to expand...
Click to collapse
Is it working for you???? because i try but failed... Recovery img dont work....he stoped and no recovery no boot rom...
khatir bahri said:
Is it working for you???? because i try but failed... Recovery img dont work....he stoped and no recovery no boot rom...
Click to expand...
Click to collapse
Both Rom and Recovery Works for me on my I9192
Maybe your download get corrupt
Root is not working though as arne said
i tried to patched boot.img for magisk but it did not work either
little things that i notice So far
1st when creating QR code or Scan QR code for wifi(Android 10 feature) Settings Got Crash
2nd conditions/Summaries that shown on the top section of the settings like turn on mobile data,your phone is on silent..etc There is no way to dismiss that on previous versions you can swype to dissmiss that
Everything seem to be working well in here
And here is some screenshots for ya
And another thing I installed the rom and the gapos with the latest official TWRP and not Arco's one
Hello,
thanks for your work.
Sadly there are some ugly and heavy bugs, escpecially regarding some hardware
related things.
Bluetooth Audio stutters and cause the whole system ui to get laggy and also
some force closes can happen. Audio streaming is not possible.
Wifi Direct is not working anymore.
Memory leaks appear.
And so on..
After some hours of intensive and frustrating testing i went back to stock rom
where i never encounter such issues.
Im using the phone at home without any simcard just for audio streaming from
my nas to my hometheatre-system.
Best regards.
Dear arco68 ! What about magisk ?
---------- Post added at 12:26 PM ---------- Previous post was at 11:54 AM ----------
It is not possible to send sms directly from the app ,you have to choose a sim to send sms in the "Network and Internet" settings"
Arslan140 said:
1st when creating QR code or Scan QR code for wifi(Android 10 feature) Settings Got Crash
Click to expand...
Click to collapse
Will be fixed in next build.
Jaroslav.100 said:
Dear arco68 ! What about magisk ?
Click to expand...
Click to collapse
Google magisk and system-as-root. It's not a straight forward thing in Android 10, due to the bootimage is not containing a real ramdisk anymore. As far as I could figure out, you have to patch the recoveryimage, and boot to recovery in order for magisk to load. When booting this patched recoveryimage, magisk will boot into the normal system unless you keep the hardware keys pressed all until recovery is loaded. It's all a bit messy, and I could not get this to work though. If anyones gonna mess with this, be sure you have backups, in case normal boot gets broken.
It is not possible to send sms directly from the app ,you have to choose a sim to send sms in the "Network and Internet" settings"
Click to expand...
Click to collapse
Dual SIM? Probably some stuff are not implemented yet for this.
Thank you arco, we will wait for your updates !
@arco68 is our devices can install the GSI roms or nah ?
Ala Ghanmi said:
@arco68 is our devices can install the GSI roms or nah ?
Click to expand...
Click to collapse
No
Ala Ghanmi said:
And another thing I installed the rom and the gapos with the latest official TWRP and not Arco's one
Click to expand...
Click to collapse
I've also got it right first time on my GT-I9195 with the official TWRP 3.3.1-0
Diresh said:
No
Click to expand...
Click to collapse
Okay get it
---------- Post added at 08:22 AM ---------- Previous post was at 08:21 AM ----------
Claudio4780 said:
I've also got it right first time on my GT-I9195 with the official TWRP 3.3.1-0
Click to expand...
Click to collapse
That's nice
Is network is working fine for both sim , because previously linage os 16 have issue
omgitsavinash said:
Is network is working fine for both sim , because previously linage os 16 have issue
Click to expand...
Click to collapse
Both Sims are working fine
I installed this ROM on my test device. It all works very well. The only problem I noticed was like @franticfreddy said, the Bluetooth audio doesn't work right.
Hi everyone, I've been trying to find a custom rom for Xiaomi Mi 12X, but none found so far. I tried to port Pixel Experience rom using the Xiaomi Mi 11X (alioth) device tree and changed accordingly, since the SOC and almost all specs are the same except Camera. Can anybody shed some light in how to correctly port the ROM for my devices without official device tree from LineageOS or Pixel Experience? Thank you.
Anybody has any suggestions?
JChanMe said:
Anybody has any suggestions?
Click to expand...
Click to collapse
Hi, right now I'm using crdroid gsi, which works pretty good. Except of fp, everything works as it should. It's smooth, has a good bb and even MGC's Gcam 8.1, last stable, works incl. portrait, nightmode and with all lenses (ok, no pixelbinning). Installing is pretty simple: use fastbootd and just fash img to system. That's it....
Voodoojonny said:
Hi, right now I'm using crdroid gsi, which works pretty good. Except of fp, everything works as it should. It's smooth, has a good bb and even MGC's Gcam 8.1, last stable, works incl. portrait, nightmode and with all lenses (ok, no pixelbinning). Installing is pretty simple: use fastbootd and just fash img to system. That's it....
Click to expand...
Click to collapse
Thank you but I don't see it on crdrood website, did you build it yourself?
JChanMe said:
Thank you but I don't see it on crdrood website, did you build it yourself?
Click to expand...
Click to collapse
It's a gsi treble rom (that works with many vendors)... Just search for project treble on xda!
Voodoojonny said:
It's a gsi treble rom (that works with many vendors)... Just search for project treble on xda!
Click to expand...
Click to collapse
Thank you. I figured it out and tried a few treble roms including pixel experience, there are a few problems including auto brightness, fingerprint and vibrator. You had the same problems?
JChanMe said:
Thank you. I figured it out and tried a few treble roms including pixel experience, there are a few problems including auto brightness, fingerprint and vibrator. You had the same problems?
Click to expand...
Click to collapse
Yes, especially the sound makes problems... When usung videocall, it's awfully distorted. I'm using stock for now. With Lawnchair and some modifications it's ok for now.
Do you know, why there's no thread for our phone here?
Just seen, you are forking some repositories... Have you been successful in building?
Voodoojonny said:
Just seen, you are forking some repositories... Have you been successful in building?
Click to expand...
Click to collapse
I successfully build the ROM without errors, just some warnings, but it didn't boot aftter flashing it.
JChanMe said:
I successfully build the ROM without errors, just some warnings, but it didn't boot aftter flashing it.
Click to expand...
Click to collapse
Did you flash with vendor or system only?
Voodoojonny said:
Did you flash with vendor or system only?
Click to expand...
Click to collapse
No, I used the same procedure as described for Alioth device, fastboot flash boot boot.img, then from recovery use adb push to update the zip ROM file.
JChanMe said:
No, I used the same procedure as described for Alioth device, fastboot flash boot boot.img, then from recovery use adb push to update the zip ROM file.
Click to expand...
Click to collapse
But how did you built the rom. Did you get out a flashing zip directly? Normally, you create different partitions as fas as I know... Would you share your rom? Btw. which one did you build?
Voodoojonny said:
But how did you built the rom. Did you get out a flashing zip directly? Normally, you create different partitions as fas as I know... Would you share your rom? Btw. which one did you build?
Click to expand...
Click to collapse
Yes, after building I got a zip and flashing it using update by adb push. I built Pixel Experience Android 11
JChanMe said:
Yes, after building I got a zip and flashing it using update by adb push. I built Pixel Experience Android 11
Click to expand...
Click to collapse
But you used the lineage device tree. And PE is aosp not lineage. Might that be the problem? Would you try to build crdroid? Or instruct me how to setup a build environment?
No, I used the PE device tree, not Lineage. I used the build instructions provided by Pixel Experience for Alioth.
JChanMe said:
Anybody has any suggestions?
Click to expand...
Click to collapse
Yesterday xiaomi released kernel for 12x on GitHub. So I think now you can build pe/los without troubles
Maxletsplay_1 said:
Yesterday xiaomi released kernel for 12x on GitHub. So I think now you can build pe/los without troubles
Click to expand...
Click to collapse
Didn't they release the kernel when the phone was released?
JChanMe said:
Didn't they release the kernel when the phone was released?
Click to expand...
Click to collapse
Technically yes, but i've checked GitHub(about month ago) and I didn't saw kernel for this phone, just an empty folder
JChanMe said:
Didn't they release the kernel when the phone was released?
Click to expand...
Click to collapse
Did you replaced vendor libs with libs from 12x and other stuff like fstab, bins, rc files..configs? Attach logs from boot if you decide to build again. My advice is to build as eng and disable encryption, put selinux to minimal mode, nuke livedisplay, import vendor modules if you build with stock prebuilt kernel. Always look for F Linker errors in log and resolve them.
I'm waiting for AOSP rom too.