There is a 1.5 cm black margin between the Android Auto (AA) content and the top of the car's display, which is only visible when I connect Xiaomi A2 lite. It didn't happen with my previous phone. Moreover, the bottom part of the AA content is not shown at all, so that this app became not usable at all.
This happens also when casting with Google photos to my home smart TV, so I don't think that AA is the problem.
Any suggestion of how to fix this issue?
i can confirm the issue. i already read about xiaomi had this problem in conjunction with the MI-UI.
with stock android one on the a2 lite it's obvious this is a general xiaomi problem.
by the way, the mi a1 didn't have the issue...
Eitaje said:
There is a 1.5 cm black margin between the Android Auto (AA) content and the top of the car's display, which is only visible when I connect Xiaomi A2 lite. It didn't happen with my previous phone. Moreover, the bottom part of the AA content is not shown at all, so that this app became not usable at all.
This happens also when casting with Google photos to my home smart TV, so I don't think that AA is the problem.
Any suggestion of how to fix this issue?
Click to expand...
Click to collapse
devlahr said:
i can confirm the issue. i already read about xiaomi had this problem in conjunction with the MI-UI.
with stock android one on the a2 lite it's obvious this is a general xiaomi problem.
by the way, the mi a1 didn't have the issue...
Click to expand...
Click to collapse
the problem seems caused by the aspect ratio (18:9)
There's on solution out there, quiet uncomfortable but's working:
- root your device with magisk
- install "SecondScreen - better screen mirroring for Android Braden Farmer" from play store
- create profile in secondscreen and activate:
Resolution: 800x480
Density: 120 dpi (hpi)
-> android car is fully working on HUR but the screen on handy is due the bad dpi very wired
may be some dev can provide a solution which only changes resolution and dpi on the HUR and keep the device screen on native resolution / dpi
hello, i can also confirm this issue.
attached is two snapshots. The first one is with My Samsung Galaxy S7, here is also good.
The secound one is the snapshot with Xiaomi Mi A2 Lite. Top and bottom have a black border.
I testet this device in a Hyundai i30 (Bj 2018) and Seat Leon (Bj 2018). Also the same problem.
1:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2:
Problem me too, Xiaomi Mi a2 lite and JVC M730BT, big black band above and below the screen
Unfortunately I've the same problem with my new A2 lite. On Redmi 4 note (stable Miui 9) works very well.
Lali_Papi said:
Unfortunately I've the same problem with my new A2 lite. On Redmi 4 note (stable Miui 9) works very well.
Click to expand...
Click to collapse
Is this a google fix or a xiaomi fix
New update now with patch 5 august. We Hope that Android Auto is ok!
Nothing nothing, test but fail screen
Nope
silviox said:
New update now with patch 5 august. We Hope that Android Auto is ok!
Nothing nothing, test but fail screen
Click to expand...
Click to collapse
unfortunately, patch 5 august didn't solve the problem. The problem persist.
Same problem.... on an audi A4, hope XIAOMI will solve it quickly.
Guys, A2L phones come with an app named something like "comments" (in Portuguese it's named "comentários", not 100% sure of its name in English) with an orange icon. This app allows you to report bugs directly to the dev team.
I already sent the navigation bar issue when using some apps (such as Spotify).
Try sending the photos you posted here so they can fix that issue sooner or later.
Also, the more people send all those issues, the more they will realize how critical the fixes are.
I can confirm this issue on a Mazda 2 ?
lbsilva said:
Guys, A2L phones come with an app named something like "comments" (in Portuguese it's named "comentários", not 100% sure of its name in English) with an orange icon. This app allows you to report bugs directly to the dev team.
I already sent the navigation bar issue when using some apps (such as Spotify).
Try sending the photos you posted here so they can fix that issue sooner or later.
Also, the more people send all those issues, the more they will realize how critical the fixes are.
Click to expand...
Click to collapse
I've done it.
OK, I execute your orders
silviox said:
OK, I execute your orders
Click to expand...
Click to collapse
Saw someone post it on Reddit /r/ Android & Xiaomi
Lali_Papi said:
I've done it.
Click to expand...
Click to collapse
Me too!
silviox said:
OK, I execute your orders
Click to expand...
Click to collapse
paddl82 said:
Me too!
Click to expand...
Click to collapse
Too late for me, I deleted the app ><
soulz said:
Too late for me, I deleted the app ><
Click to expand...
Click to collapse
Same problem here on a Hyundai Ionic and a Peugeot 308.
I've sent the query with the "Comment" App right now, I hope the multiple warnings will be of use.
solved by flashing lineage os 15.1 - treble
I found a rom which makes Android Auto working.
Upfdate: I also tried out ASOp from phh treble https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
- Android Auto is also working
- the notch is working here!
I downloaded lineage os Image for ARM64 A/B device with gapps from here: https://forum.xda-developers.com/pr...evice-development/lineage-phh-treble-t3767690
I followed instructions from section "Flash GSI without TWRP": https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
So what did i do exactly?
1. Unlock bootloader (my was already unlocked)
2. Download https://github.com/phhusson/treble_...load/lineage-v21/system-arm64-ab-gapps-su.img
3. Reboot to your device’s stock recovery using either a button combination when booting or issuing the following ADB command when booted in Android: adb reboot recovery. Once here, use the volume keys to navigate and the power button to select the factory reset option.
4. Once your device has been factory reset, reboot to your device’s bootloader using either a button combination when booting or issuing the following ADB command when booted in Android: adb reboot bootloader
5. With your device connected to your PC, open up a command prompt or terminal window in the same directory where you downloaded your GSI of choice.
Enter the following command: fastboot erase system
Enter a command in the following format: fastboot -u flash system-arm64-ab-gapps-su.img
Allow the image to flash, it could take a few minutes. Once it has completed, reboot your device either manually via power key or by entering fastboot reboot.
P.S. the rom doesn't know the notch, bust rest like camera etc. is working!
fizze17 said:
I found a rom which makes Android Auto working.
Upfdate: I also tried out ASOp from phh treble https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
- Android Auto is also working
- the notch is working here!
I downloaded lineage os Image for ARM64 A/B device with gapps from here: https://forum.xda-developers.com/pr...evice-development/lineage-phh-treble-t3767690
I followed instructions from section "Flash GSI without TWRP": https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
So what did i do exactly?
1. Unlock bootloader (my was already unlocked)
2. Download https://github.com/phhusson/treble_...load/lineage-v21/system-arm64-ab-gapps-su.img
3. Reboot to your device’s stock recovery using either a button combination when booting or issuing the following ADB command when booted in Android: adb reboot recovery. Once here, use the volume keys to navigate and the power button to select the factory reset option.
4. Once your device has been factory reset, reboot to your device’s bootloader using either a button combination when booting or issuing the following ADB command when booted in Android: adb reboot bootloader
5. With your device connected to your PC, open up a command prompt or terminal window in the same directory where you downloaded your GSI of choice.
Enter the following command: fastboot erase system
Enter a command in the following format: fastboot -u flash system-arm64-ab-gapps-su.img
Allow the image to flash, it could take a few minutes. Once it has completed, reboot your device either manually via power key or by entering fastboot reboot.
P.S. the rom doesn't know the notch, bust rest like camera etc. is working!
Click to expand...
Click to collapse
Uh was trying to avoid flashing my pure Android One . Maybe when official Iineage OS comes to A2 Lite
Related
Decided to create a new thread on the SE forums since we now have our own forum.
So phhusson made a treble GSI for Android P and I got further with it than with any of the other GSIs.
WIFI and BLUETOOTH both work with this GSI.
Here's what I did to get it working (your mileage may vary and I am not responsible for any broken/ bricked devices as a result of these instructions, ALWAYS MAKE SURE YOU TAKE A FULL TWRP BACKUP OF YOUR DEVICE BEFORE ATTEMPTING THIS):
Unlock bootloader.
Download the latest TWRP from here and flash it. Make sure you're running at least version 3.2.3.
Boot into TWRP, tap on Wipe and then tap on "Format Data" and enter yes. Once it's done, reboot into recovery.
Next flash the latest Xiaomi.EU MiUI 10 Beta rom from here. Download it, transfer it to your phone's storage and then use TWRP to install the zip.
After it has installed, tap on Wipe on the TWRP main menu and swipe to factory reset.
Next flash the treble GSI for Lineage 15.1 from here. Download it, transfer to your phone's storage and then use TWRP to install the image file by tapping on Install, then "Install Image" on the bottom right and then select the Lineage image you transferred earlier. Select the "system" partition on the next screen and install.
Now reboot your phone and wait for Lineage to boot up. Once it has booted successfully, reboot into recovery. Use TWRP to factory reset your device again.
Now follow the steps for an A-Only device on this article
*BUT BEFORE YOU REBOOT, GO INTO THE ADVANCED MENU ON TWRP AND TAP ON "INSTALL ROOT"*. Once Magisk has been installed, reboot into system and hopefully you should boot. If not, try rebooting again and it should work.
Bugs (that I know of):
Audio is really broken and sounds horrible even with headphones plugged in.
You can fix media audio only by flashing the ViPER4Android module through Magisk Manager.
This doesn't fix it for ringtone/notification or alarms though.
FIX FOR NOTCH:
https://github.com/pravsterrr/treble-overlay-xiaomi-mi8se/blob/master/dist/treble-overlay-xiaomi-mi8se.apk?raw=true
Download the APK.
Boot into TWRP.
Mount vendor partition.
Use ADB to move the APK to "/vendor/overlay/"
let me know if you find anything.
pravsterrr said:
Decided to create a new thread on the SE forums since we now have our own forum.
So phhusson made a treble GSI for Android P and I got further with it than with any of the other GSIs.
WIFI and BLUETOOTH both work with this GSI.
Here's what I did to get it working (your mileage may vary and I am not responsible for any broken/ bricked devices as a result of these instructions, ALWAYS MAKE SURE YOU TAKE A FULL TWRP BACKUP OF YOUR DEVICE BEFORE ATTEMPTING THIS):
Unlock bootloader.
Download the latest TWRP from here and flash it. Make sure you're running at least version 3.2.3.
Boot into TWRP, tap on Wipe and then tap on "Format Data" and enter yes. Once it's done, reboot into recovery.
Next flash the latest Xiaomi.EU MiUI 10 Beta rom from here. Download it, transfer it to your phone's storage and then use TWRP to install the zip.
After it has installed, tap on Wipe on the TWRP main menu and swipe to factory reset.
Next flash the treble GSI for Lineage 15.1 from here. Download it, transfer to your phone's storage and then use TWRP to install the image file by tapping on Install, then "Install Image" on the bottom right and then select the Lineage image you transferred earlier. Select the "system" partition on the next screen and install.
Now reboot your phone and wait for Lineage to boot up. Once it has booted successfully, reboot into recovery. Use TWRP to factory reset your device again.
Now follow the steps for an A-Only device on this article
*BUT BEFORE YOU REBOOT, GO INTO THE ADVANCED MENU ON TWRP AND TAP ON "INSTALL ROOT"*. Once Magisk has been installed, reboot into system and hopefully you should boot. If not, try rebooting again and it should work.
Bugs (that I know of):
Audio is really broken and sounds horrible even with headphones plugged in.
Notch still isn't really recognized by the system.
let me know if you find anything.
Hope someone finds a fix for the audio
Click to expand...
Click to collapse
Hi guy,my mi8 also have audio bugs,do you fix it?
Qian Lee said:
Hi guy,my mi8 also have audio bugs,do you fix it?
Click to expand...
Click to collapse
You can fix media audio only by flashing the ViPER4Android module through Magisk Manager.
This doesn't fix it for ringtone/notification or alarms though.
pravsterrr said:
You can fix media audio only by flashing the ViPER4Android module through Magisk Manager.
This doesn't fix it for ringtone/notification or alarms though.
Click to expand...
Click to collapse
THX,I had fixed media audio,and I knows someone use an app to change ringtone,then the ringtone sounds ok
ps:I am sorry for my poor english，hope you can understand :victory:
The phone app,contacts,etc,moat of the system apps might FC.Which annoyed me is the input app,it will FC too
linqihao2333 said:
The phone app,contacts,etc,moat of the system apps might FC.Which annoyed me is the input app,it will FC too
Click to expand...
Click to collapse
最新的pe gsi并没有这些问题。
Qian Lee said:
THX,I had fixed media audio,and I knows someone use an app to change ringtone,then the ringtone sounds ok
ps:I am sorry for my poor english，hope you can understand :victory:
Click to expand...
Click to collapse
Which app // 你用过什么应用程序
great to see mi8 SE moving development
Got the notch detection working with help from phh.
Not responsible for any damage to your device / for any broken devices as a result of these instructions.
FIX FOR NOTCH:
https://github.com/pravsterrr/treble-overlay-xiaomi-mi8se/blob/master/dist/treble-overlay-xiaomi-mi8se.apk?raw=true
Download the APK.
Boot into TWRP.
Mount vendor partition.
Use ADB to move the APK to "/vendor/overlay/"
pravsterrr said:
Got the notch detection working with help from phh.
Not responsible for any damage to your device / for any broken devices as a result of these instructions.
FIX FOR NOTCH:
Download the APK.
Boot into TWRP.
Mount vendor partition.
Use ADB to move the APK to "/vendor/overlay/"
Click to expand...
Click to collapse
It's good to see someone trying to make this rom works. Hope that audio problems will be fixed soon
Great, thank you. I will try it after its done first release with fixed sound issue.
pravsterrr said:
Got the notch detection working with help from phh.
Not responsible for any damage to your device / for any broken devices as a result of these instructions.
FIX FOR NOTCH:
https://github.com/pravsterrr/treble-overlay-xiaomi-mi8se/blob/master/dist/treble-overlay-xiaomi-mi8se.apk?raw=true
Download the APK.
Boot into TWRP.
Mount vendor partition.
Use ADB to move the APK to "/vendor/overlay/"
Click to expand...
Click to collapse
I will try this as well once I get a type c adaptor for my usb otg. Thanks for the tutorial.
The Mi 8 SE isn't my daily driver yet. Should I flash for testing or hold off?
Sorry but how to flash V4A through Magisk?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Silver Wind said:
Sorry but how to flash V4A through Magisk?
Click to expand...
Click to collapse
Download the zip via Magisk Manager and then flash using custom recovery
What's not working???
pravsterrr said:
Got the notch detection working with help from phh.
Not responsible for any damage to your device / for any broken devices as a result of these instructions.
FIX FOR NOTCH:
https://github.com/pravsterrr/treble-overlay-xiaomi-mi8se/blob/master/dist/treble-overlay-xiaomi-mi8se.apk?raw=true
Download the APK.
Boot into TWRP.
Mount vendor partition.
Use ADB to move the APK to "/vendor/overlay/"
Click to expand...
Click to collapse
Hey man, can you make a notch detection for android 8.1 vesion? Hope you can help me with it
new release is up, changelog:
https://github.com/phhusson/treble_experimentations/releases
September security patch
[Samsung Galaxy Note 9] Fix WiFi, brightness and fingerprint sensor
[Samsung Galaxy S9] Support assistant and partial "home" button on S9
Include phh su
[Xiaomi Mi 6X] Fix backlight control on
[Xiaomi ...] Fix sound on Mi 8 *, Poco,
[Xiaomi Mi Mix 2S] Delete fingerprint key event
[Treble app] [Huawei] Setting for hwcomposer overlay bypass option to workaround blur issue
[Treble app] minor fixes
Add support for status bar reduction for notches
Fix webview issue when not using gapps
[Known regression of this version] Broke ro.sf.hwrotation (needed for screen rotation on some devices)
Maybee our sound issue is fixed IT doesnt fixed
New PixelExperience release is up too...
https://github.com/EnesSastim/Downloads/releases
Any issues with mtp? Thanks
technoboi1 said:
new release is up, changelog:
https://github.com/phhusson/treble_experimentations/releases
September security patch
[Samsung Galaxy Note 9] Fix WiFi, brightness and fingerprint sensor
[Samsung Galaxy S9] Support assistant and partial "home" button on S9
Include phh su
[Xiaomi Mi 6X] Fix backlight control on
[Xiaomi ...] Fix sound on Mi 8 *, Poco,
[Xiaomi Mi Mix 2S] Delete fingerprint key event
[Treble app] [Huawei] Setting for hwcomposer overlay bypass option to workaround blur issue
[Treble app] minor fixes
Add support for status bar reduction for notches
Fix webview issue when not using gapps
[Known regression of this version] Broke ro.sf.hwrotation (needed for screen rotation on some devices)
Maybee our sound issue is fixed IT doesnt fixed
New PixelExperience release is up too...
https://github.com/EnesSastim/Downloads/releases
Click to expand...
Click to collapse
is the notch auto detected ?
Hey y'all, after 2 days of headaches with a semi bricked device from a friend i was finally able to get a GSI Rom running.
Here's what you need:
1. Unlocked Bootloader
2. Stock Recovery
https://mega.nz/file/m4Q0iJpR#wP9U5gpXwTVrSWezkaoJqDjgb0zadULTLpb8kLAZJRE
3. GSI Rom (i used Bliss and it works flawless)
https://forum.xda-developers.com/pr...ent/unofficial-blissroms-q-mod-bless-t4138687
4. A PC running Linux
So the problem is that this device comes with a super partition. That means TWRP isnt able to flash a System Image because there is not a system partition instead there is this super partition wich is new to Android 10 and is dynamic. However you need to boot to fastbootd mode to access the system partition inside the super partition.
Important!! You need Stock Recovery for this you can not boot into fastbootd via TWRP at this moment. Also you need Linux because there is only a unsigned Driver for Windows for the fastbootd mode and i dont recommend using unsigned chinese drivers.... i use Manjaro that worked out of the box.
Mi 10 Lite 5G is Treble A/B enabled so we need an A/B Rom Bliss is providing that. Follow these steps to flash the GSI.
1. Reboot to bootloader then enter: fastboot reboot fastboot (there should be the text fastbootd in yellow)
2. fastboot -w (there is maybe an error but this is ok)
2. fastboot erase system
3. fastboot flash system "GSI-ROM-name-without-quotes".img
4. fastboot reboot bootloader
5. fastboot reboot
If it bootloops your GSI is not compatible (Havoc for example) just try it till you're satisfied. This is an first step for Stock Android on our Device. i will build some Custom Roms in the next weeks.
EDIT:
Ok i got Bliss fully up and running Fingerprint and even Google Pay works! There is some things you need to do though.
Preparation:
Stock Recovery
Bliss GSI
Audio Policy Fix.xml: https://mega.nz/file/i4QWkbSD#a3U90V1kk0S01DYxjN3YH-0HsAbo_UUU_rMd7LhYLFc
Procedure:
1. Boot into fastbootd like described above and flash the GSI
2. After boot set Magisk there should be a Magisk link if you open it this Procedure should run automatically
3. In Magisk Download MagiskHide Props Config, Download it and install it reboot.
4. Run in terminal on the device (i used Termux) the command "props" (without quotes) and select option 1 then select from the list Xiaomi and then Device Mi 10 Lite 5G Europe after that go back to main menu and select option 2 select again Mi 10 Lite 5G and nothing else
5. Reboot and check Safety Net it should get a pass if not you did something wrong
6. Download a Root File explorer (i used JRummys Root Explorer)
7. Copy the Audio Policy xml to your phone and replace the file on /vendor/etc to get Headphone Jack and Headset Mics working
8. Go to Settings - phh treble settings - Qualcomm Features and Tick use alternate audio policy
9. Go back to misc Features and tick disable audio effects this gets Notification and Alarm Sounds and Ringtone working.
10. Reboot
11. Check if Bluetooth works it should if not well i honestly dont know for sure
And your Device should run perfectly fine, its crazy fast and i got a 8h Screen on Time. Well thats for me good enough for now im back to cocking Custom Roms
I was struggling with this for a very long time and couldn't flash any GSI!! Thank you so much for this guide, I will try it now and give you a feedback, but where can I find the unsigned chinese drivers for windows? and do you think I can flash android 11 GSI`s like Phh on our device??
Honestly i dont know, it should work just try it. Worse that can happen is a bootloop. I added the Stock Recovery in First Post. And here is a link to the unsingned Xiaomi Driver use at your own risk!
https://c.mi.com/oc/thread-3312019-1-0.html
works perfectly, then I tried to flashing Bliss 14.0.3 and it booted up and worked and now I`m testing ProjectStreak android 11 GSI also boots and almost everything works except for the fingerprint sensor and A LOT of lag in the System UI! think I will revert back to Bliss 12.2 for now!
Thanks again!
I cannot receive SMS with Bliss.
@Legacyleader
I see that you are from Germany. I am also from Germany. Do you have Telegram?
Hi @Benni1123 yes i have telegram, SMS Problem could be solved via APN Settings. In my Case Drillisch had no APN setup after that it was working fine.
Legacyleader2 said:
Hi @Benni1123 yes i have telegram, SMS Problem could be solved via APN Settings. In my Case Drillisch had no APN setup after that it was working fine.
Click to expand...
Click to collapse
Hi Legacyleader you save this device, thanks
i can't seem to get any GSI rom to boot, alway's end up in a bootloop. My Monet Device is unlocked with the latest V12.0.3.0.QJIEUXM Rom.
It enters fastbootd (yellow letters) but when i enter fastboot -w i get error: segmentation fault.
If i flash system after this and reboot, i always end up in a bootloop (device boots to Mi logo and instantly reboots, goes back to mi logo, instantly reboots etc..)
It feels like im missing something obviously? ;-)
@Legacyleader2 do i need to wipe anything after the system flash? if i follow your steps i always end up bootlooping. Tried Andy's Lineage17.1 GSI, Phh AOSP GSI(v222), tried bless, bliss all of them are instant bootlooping. When i flash superpartition over it, system instantly boots stock rom.
Any idea what i'm doing wrong?
@Legacyleader2 look DM please
Hello,
Mi 10 Lite (Monet) owner here! (and new on XDA)
These detailed instructions almost convinced me to make the jump and flash a GSI on my phone purchased recently. It looks like the "standard" procedure for flashing a GSI ROM with fastbootd.
I know I can fallback on the official MIUI ROM in case of problem, but before flashing, I would like to ensure there is at least one GSI which can keep my phone working as a phone, with all basic features working good.
Could you please provide a feedback about your experience?
1) Which GSI did you try?
I am about to try phhusson LineageOS's GSI first, and if it does not work, I'll try Bliss as it looks like it works like a charm
2) How is the battery life affected?
I really enjoy the battery life with MIUI, I don't want it to be cut by two
3) Does the cameras (front, back, pictures/videos modes) still work?
4) Do calls and SMS work?
5) During calls, is the call audio quality good on both sides?
I had issues with some ROM on my previous phones like echos.
6) Does the fingerprint reader work?
Additionally, what about Bluetooth, NFC, speakers, audio output from jack, applications/games performance, ...?
Maybe we could create a post to summarize our successful experiences.
Thank you for your time
does someone successfully installed xposed in GSI bliss room thanks?
Hello everyone one!
I wanted to share my experience after this amazing guide, I managed to follow the guide and flash bliss GSI then I was flashed A LOT of different android 11 GSIs and I was using the AOSP 11 GSI for a week (everything was okay except for the fingerprint & Bluetooth audio).
Then I stumbled upon a MIUI 12 Global build based on android 11 for monet and I'm using it now for the oast week and it's pretty stable.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does the vendor from this build affect flashing GSIs on this phone?
(Excuse my weak english)
Finally I have gone through GSIs.
On my working list.
1. Bless ver 224
2. Crdroid ver 224
3.Losq ver 224
4.Decendant X latest
I have not found any other gsi booting some body may add to the other GSIs booting.
I have not had any luck booting a port gsi.
Crdroid passes safety net out of the box.
For audio bug just tick alternative audio in phh settings and reboot.
Hmmm... I got HavocOS to work.
I used the vbmeta.img, dtbo.img and boot.img off of the latest Arrow rom (Arrow-v11.0-monet-OFFICIAL-20210412-VANILLA.zip), and then flashed the HavocOS GSI image to system, and it... didn't bootloop! It actually booted! Everything seems to work.
I just got it to run, so I'll have to play around a bit before I can give any definite guarantee, but so far everything seems fine. 5G is there as well.
Well, fingerprint doesn't work. Darn.
The two I've gotten to work are:
https://download.havoc-os.com/arm64-ab/Havoc-OS-v4.1-20210208-arm64-ab-Official.img.xz
https://download.havoc-os.com/arm64-ab/Havoc-OS-v4.1-20210208-arm64-ab-Official-GApps.img.xz
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features
Flashing Instructions:
Pre-installation:
Download latest recovery image (download)
Update to latest firmware
First time installation:
Backup your data to PC, OTG flash drive
Enter fastboot
Flash our recovery in both slot:
Code:
fastboot flash recovery_a <recovery_filename>.img
fastboot flash recovery_b <recovery_filename>.img
Reboot to recovery
Do factory reset
Back to recovery main page tap Apply update -> Apply from ADB
Now sideload <rom_filename>.zip using command:
Code:
adb sideload <rom_filename>.zip
If getting message Signature verification failed click Yes.
You'll see process stuck on 47%, Don't worry you'll get Success message just wait.
Now once again do a Factory reset
Reboot
Update installation:
Boot to recovery
Choose Apply update -> Apply from ADB
Now install <rom_filename>.zip via sideload:
Code:
adb sideload <rom_filename>.zip
Reboot
Update OnePlus internal firmware:
Download latest firmware pack (The link is in the Download section)
Reboot to crDroid recovery
Update instruction - LineageOS Wiki (From point 4)
Magisk installation:
Downloading the latest release of Magisk (apk file).
After "clean" (initial) installation :
After installing the firmware in Recovey mode, we reboot again in Recovery (so that the slot change is applied).
Choose Apply update -> Apply from ADB
Now install Magisk.apk via sideload:
[ CODE]adb sideload Magisk.apk[/CODE]
Reboot
After booting the system, install the Magisk program itself
After OTA update :
After installing the OTA update, we do not reboot the system, but launch the already installed Magisk.
Click "Install" (Magisk)
Choose a method - "Install to Inactive Slot (After OTA)
Tap "LET'S GO ->"
After installation - Reboot
Sources:ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sm8150
Common Device tree: https://github.com/crdroidandroid/android_device_oneplus_sm8150-common
Device tree: https://github.com/crdroidandroid/android_device_oneplus_hotdog
Vendor Common Device tree: https://github.com/crdroidandroid/proprietary_vendor_oneplus_sm8150-common
Vendor Device tree: https://github.com/crdroidandroid/proprietary_vendor_oneplus_hotdog
Download:
crDroid ROM
Recovery Image
OnePlus 7T Pro firmware
Changelog
GAPPS: Already Included
Known issues:
- WiFi display: Sound is not transmitted to some TV models. The sound comes from the phone speakers. 20220730
- OnePlus Camera: Portrait mode 20220708
- OnePlus Camera: Slow Motion Video
Visit official website @ crDroid.net
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
crDroid OnePlus 7T Pro (hotdog) Telegram group
Busy ...
Busy...
Does Google pay and Android auto work?
Google pay works fine for me
Both are working but I am getting a constant notification of Android system intelligence keeps crashing
crDroid paste - share logs, bugs, code and whatever else remains in plan text
paste.crdroid.net
eddyctweets said:
Both are working but I am getting a constant notification of Android system intelligence keeps crashing
Click to expand...
Click to collapse
What is installed besides the firmware? Magisk modules / Xposed modules?
ShevT said:
What is installed besides the firmware? Magisk modules / Xposed modules?
Click to expand...
Click to collapse
No magisk or xposed, installed as per instructions heres another log
crDroid paste - share logs, bugs, code and whatever else remains in plan text
paste.crdroid.net
eddyctweets said:
No magisk or xposed, installed as per instructions heres another log
crDroid paste - share logs, bugs, code and whatever else remains in plan text
paste.crdroid.net
Click to expand...
Click to collapse
I've just deleted the app so here's hoping it's something I don't need
After updating to 8.2. fingerprint option has disappeared . Even though it's working really find for apps and passwords, but the option to add it to the lockscreen disappeared.
mastrok said:
After updating to 8.2. fingerprint option has disappeared . Even though it's working really find for apps and passwords, but the option to add it to the lockscreen disappeared.
Click to expand...
Click to collapse
Everything is in its place
ShevT said:
Everything is in its place
Click to expand...
Click to collapse
I have both of the screenshots you shared also. But the option to choose fingerprint as an unlock method has just disappeared. Not sure why. I upgraded from the updater app cr droid provides. How did you update?
mastrok said:
I have both of the screenshots you shared also. But the option to choose fingerprint as an unlock method has just disappeared. Not sure why. I upgraded from the updater app cr droid provides. How did you update?
Click to expand...
Click to collapse
Right. There shouldn't be a print. First you need to select the unlock/encryption method. This is the method if the fingerprint doesn't work.
ShevT said:
Right. There shouldn't be a print. First you need to select the unlock/encryption method. This is the method if the fingerprint doesn't work.
Click to expand...
Click to collapse
Great, thank you for your clarification. I still face an issue after adding my fingerprint. That the fingerprint doesnt show on lockscreen. It shows only the pin unlock. So probably there something wrong in my update. I will try clean install and let you know.
mastrok said:
Great, thank you for your clarification. I still face an issue after adding my fingerprint. That the fingerprint doesnt show on lockscreen. It shows only the pin unlock. So probably there something wrong in my update. I will try clean install and let you know.
Click to expand...
Click to collapse
Have you tried holding your finger to the lock button? My finger still unlocks the phone
eddyctweets said:
Have you tried holding your finger to the lock button? My finger still unlocks the phone
Click to expand...
Click to collapse
it always asks for pin. the fingerprint itself doesnt flash white it's like it's turned off
mastrok said:
it always asks for pin. the fingerprint itself doesnt flash white it's like it's turned off
Click to expand...
Click to collapse
Aww ok mine works fine, I did clean flash as per the instructions. The only time I see a fingerprint button is if I have aod on
Hi together fingerprint works fine for me. But on apps the fingerprint is shown on the wrong positon. The reader ist higher then the logo which is shown. Is there a solution for this?
tobasium said:
Hi together fingerprint works fine for me. But on apps the fingerprint is shown on the wrong positon. The reader ist higher then the logo which is shown. Is there a solution for this?
Click to expand...
Click to collapse
Yes I know. I'll see...
tobasium said:
But on apps the fingerprint is shown on the wrong positon.
Click to expand...
Click to collapse
Fixed!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Google Pixel 2
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.[/CENTER]
Introduction:
This is the Official Lineage OS 19.1 thread for the Google Pixel 2.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
walleye
walleye - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Kernel Source: https://github.com/LineageOS/android_kernel_google_wahoo
I just tried this and it all works except the Camera. When trying to open it, I'm getting
Camera keeps stopping
- App info
- Close app
Any idea why that might be?
nschloe said:
I just tried this and it all works except the Camera. When trying to open it, I'm getting
Camera keeps stopping
- App info
- Close app
Any idea why that might be?
Click to expand...
Click to collapse
gah, in the unofficial I included _too new_ a google camera. Will be fixed in next build.
nschloe said:
I just tried this and it all works except the Camera. When trying to open it, I'm getting
Camera keeps stopping
- App info
- Close app
Any idea why that might be?
Click to expand...
Click to collapse
New build is up - fixed.
> New build is up - fixed.
Confirmed working. Thanks!
I'm using Official LineageOS 18.1, and now I'd like to install LOS19. But adb sideload los.zip no response for a long time. even use pure LOS recovery or twrp. In LOS recovery, 'Verifying update package...', In twrp, just keep rolling progress bar. Adb command interface no response. I can use Ctrl+C to cancle it.
I downloaded a software from Chrome.When I try to install it.The system rebooted.
dcshallot said:
I'm using Official LineageOS 18.1, and now I'd like to install LOS19. But adb sideload los.zip no response for a long time. even use pure LOS recovery or twrp. In LOS recovery, 'Verifying update package...', In twrp, just keep rolling progress bar. Adb command interface no response. I can use Ctrl+C to cancle it.
Click to expand...
Click to collapse
yup, it's verifying, leave it and wait for it - or try a different cable.
One stupid question:
As per the instructions here: https://wiki.lineageos.org/devices/walleye/upgrade
to upgrade from 18.1 to 19.1... Is it enough to just sideload the 19.1 zip file with adb? . Is it not a requirement to have flashed the correspondent recovery image for 19.1 beforehand (like in a normal first-time LOS installation)?
cognid said:
One stupid question:
As per the instructions here: https://wiki.lineageos.org/devices/walleye/upgrade
to upgrade from 18.1 to 19.1... Is it enough to just sideload the 19.1 zip file with adb? . Is it not a requirement to have flashed the correspondent recovery image for 19.1 beforehand (like in a normal first-time LOS installation)?
Click to expand...
Click to collapse
nope! that guide is right. Follow it and you'll have a good time.
However, I personally do reccoemnd lineage recovery, so I'd flash 19.1 recovery then start
is this build stable for daily usages?
galibalmasanick said:
is this build stable for daily usages?
Click to expand...
Click to collapse
of course
npjohnson said:
nope! that guide is right. Follow it and you'll have a good time.
However, I personally do reccoemnd lineage recovery, so I'd flash 19.1 recovery then start
Click to expand...
Click to collapse
OK, flashed 19.1 recovery, then sideloaded LOS19.1.zip as per the official guide... everything worked fine, phone rebooted in Android 12.
Testing here and there, everything seems to work fine. The camera app seems to have downgraded to just very basic features compared to the cam app in LOS 18.1. Thanks for that, I will report back if I notice some issue, but so far all good.
cognid said:
OK, flashed 19.1 recovery, then sideloaded LOS19.1.zip as per the official guide... everything worked fine, phone rebooted in Android 12.
Testing here and there, everything seems to work fine. The camera app seems to have downgraded to just very basic features compared to the cam app in LOS 18.1. Thanks for that, I will report back if I notice some issue, but so far all good.
Click to expand...
Click to collapse
Yeah, Snap is gone. Only Camera2 now.
My unofficial ship with Google Camera.
npjohnson said:
yup, it's verifying, leave it and wait for it - or try a different cable.
Click to expand...
Click to collapse
The phone was nearly become a brick because of the laptop. I thought it caused by Anti-Virus software. Then I used another pc to finish the installing. LOS 19 has some small issue in inform displaying, should be fixed in coming future.
dcshallot said:
The phone was nearly become a brick because of the laptop. I thought it caused by Anti-Virus software. Then I used another pc to finish the installing. LOS 19 has some small issue in inform displaying, should be fixed in coming future.
Click to expand...
Click to collapse
What small issue?
I can't fix it if I don't know what it is lol
npjohnson said:
What small issue?
I can't fix it if I don't know what it is lol
Click to expand...
Click to collapse
1, Settings -> Storage -> App usage size incorrect. Initial shown system used 14GB space, after some time(now), System 8.2GB, 'Open Camera' 5.56GB of User Data. The first time I found this issue was that after installing Nova Launch. I tried clear it's app data, not work, then I uninstalled it. Now, the space transfer to Open Camera. Uninstalling doesn't change the total usage ( The app is too small ).
2, Settings -> About Phone -> IP address, always 26.26.26.1 and da26:2626::1. I'm sure it's not my IP.
3, I use V2rayNG which is a VPN service. It has a quick setting Tiles. At once I reboot the phone and enabled v2rayNP from Tiles while the service was still off. Then I found registered VPN service disappeared from settings -> network -> vpn.
dcshallot said:
1, Settings -> Storage -> App usage size incorrect. Initial shown system used 14GB space, after some time(now), System 8.2GB, 'Open Camera' 5.56GB of User Data. The first time I found this issue was that after installing Nova Launch. I tried clear it's app data, not work, then I uninstalled it. Now, the space transfer to Open Camera. Uninstalling doesn't change the total usage ( The app is too small ).
2, Settings -> About Phone -> IP address, always 26.26.26.1 and da26:2626::1. I'm sure it's not my IP.
3, I use V2rayNG which is a VPN service. It has a quick setting Tiles. At once I reboot the phone and enabled v2rayNP from Tiles while the service was still off. Then I found registered VPN service disappeared from settings -> network -> vpn.
Click to expand...
Click to collapse
1. I have no idea why your apps report huge size. That's not a Lineage thing tho.
2. That's... Odd what router do you have?
3. That is definitely an app bug, VPNs work here.
1.As you see, Open Camera show a huge size. But actually, at first, the size was normal. Well, before Open Camera, it was Nova Launcher. It just need some time that the LOS make it so.
2. I'm in China, and I use a VPN service built by myself but it's not located in US. 26.26.26.1 is a US IP, right?
Should I make a clean LOS install? I'm not sure after the adb no response accident, has something went wrong? I don't want to download & backup & restore, that's horrible.
Hi,
I've just installed this ROM. Thanks for the work !
I just have a problem with the customization menu in the settings. The activity is crashing instantly.
It's the menu "Fond d'écran et style" in french (don't know the exact name in english :s).Tthe one allowing to change home and lockscreen background.
Is it working for you ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 12.1 (S), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Downloads:
- Here
Flashing instructions
- Here
Bugs:
- Backlight does not turn off on offline charging
Notes:
- SELinux is enforcing
- SafetyNet passes by default
- Custom recoveries, like TWRP and OFRP, are not supported
- Custom kernels, like Eva Kernel, are not supported
- OTA support is present
- Kernel is prebuilt from stock since Xiaomi has not released the source code for cannon-s-oss (Taken from cannong 13.0.3.0)
Required firmware:
- MIUI 13 based (Up to MIUI 13.0.3.0. MIUI 12.x is not supported)
Sources:
- LineageOS
- Device sources
Telegram group:
- Here
Happy modding!
Reserved
Thank you for awesome work!
tried this, sim card stopped working
jokemaster21 said:
tried this, sim card stopped working
Click to expand...
Click to collapse
Send logs and check the reporting issues section of the guide
Also make sure you're doing everything properly, as I describe, since I haven't seen anything similar myself or in some other tester.
LinkBoi said:
Send logs and check the reporting issues section of the guide...
Also make sure you're doing everything properly, as I describe, since I haven't seen anything similar myself or in some other tester.
Click to expand...
Click to collapse
where do I find my logs
edit nvm I'll report the problem properly according to your guide
LinkBoi said:
Send logs and check the reporting issues section of the guide...
Also make sure you're doing everything properly, as I describe, since I haven't seen anything similar myself or in some other tester.
Click to expand...
Click to collapse
here are the logs
Edit also it keeps bootlooping when I insert an sd card
jokemaster21 said:
here are the logs
Edit also it keeps bootlooping when I insert an sd card
Click to expand...
Click to collapse
See below:
LinkBoi said:
Okay. Try one thing first. Flash from recovery the package that I've attached, it will make your SELinux be permissive.
PS: Consider joining Telegram for more direct communication
Click to expand...
Click to collapse
Also I will need boot logs just to be sure. You can get them by rebooting your device and when you see the bootanimation do the following:
- adb root
- adb shell
- logcat -b all > /cache/logcat-boot.log
Wait a little while and press control+C to stop the process
Afterwards, send me the file from the /cache partition. You can reboot to recovery and use 'adb pull' to grab it in your PC like this:
- adb pull /cache/logcat-boot.log
LinkBoi said:
Also I will need boot logs just to be sure. You can get them by rebooting your device and when you see the bootanimation do the following:
- adb root
- adb shell
- logcat -b all > /cache/logcat-boot.log
Wait a little while and press control+C to stop the process
Afterwards, send me the file from the /cache partition. You can reboot to recovery and use 'adb pull' to grab it in your PC like this:
- adb pull /cache/logcat-boot.log
Click to expand...
Click to collapse
here you go,
btw since I don't have a sim card to use atm I can't use telegram
jokemaster21 said:
here you go,
btw since I don't have a sim card to use atm I can't use telegram
Click to expand...
Click to collapse
Which stock MIUI were you using before flashing LineageOS?
LinkBoi said:
Which stock MIUI were you using before flashing LineageOS?
Click to expand...
Click to collapse
13.0.3.0 I believe. I tried flashing 13.0.2.0, but it kept giving me an error that the SPL would be a downgrade and it wouldn't allow me to flash
jokemaster21 said:
13.0.3.0 I believe. I tried flashing 13.0.2.0, but it kept giving me an error that the SPL would be a downgrade and it wouldn't allow me to flash
Click to expand...
Click to collapse
You should flash 13.0.2.0 from fastboot. You need to download the full fastboot ROM for your specific model and then flash it from fastboot by running flash_all.bat or flash_all.sh (Depending on your OS)
LinkBoi said:
You should flash 13.0.2.0 from fastboot. You need to download the full fastboot ROM for your specific model and then flash it from fastboot by running flash_all.bat or flash_all.sh (Depending on your OS)
Click to expand...
Click to collapse
ok tried flashing it and it said it was successful, but when I tried booting it up it got completely bricked
jokemaster21 said:
ok tried flashing it and it said it was successful, but when I tried booting it up it got completely bricked
Click to expand...
Click to collapse
Check a couple of things:
- If your device powers up in any way, see if you can go into fastboot. If your device, on the splash screen says something like 'vbmeta verification failed, press the power button to continue', just press the power button to proceed (this would be due to AVB checks)
- If your device does not power up, then try plugging it in to your computer and see if it gets detected in any way
If it does, send a screenshot of Device Manager (Windows) or 'lsusb' (Linux)
Also, do you have the Global model or the Chinese one? I assume you got the Chinese one since 13.0.3.0 is not out for Global yet.
Either way, your issues before most likely stem from using newer firmware than the one I recommend.
PS: You should already have some technical knowledge to resolve such issues yourself if you're flashing custom ROMs and also keep in mind that 'bricked' says pretty much nothing (You must be more detailed when mentioning your phone's behaviour, like if it boots but stays on the splash screen, if it boots but stays on the boot animation etc)
LinkBoi said:
Check a couple of things:
- If your device powers up in any way, see if you can go into fastboot. If your device, on the splash screen says something like 'vbmeta verification failed, press the power button to continue', just press the power button to proceed (this would be due to AVB checks)
- If your device does not power up, then try plugging it in to your computer and see if it gets detected in any way
If it does, send a screenshot of Device Manager (Windows) or 'lsusb' (Linux)
Also, do you have the Global model or the Chinese one? I assume you got the Chinese one since 13.0.3.0 is not out for Global yet.
Either way, your issues before most likely stem from using newer firmware than the one I recommend.
PS: You should already have some technical knowledge to resolve such issues yourself if you're flashing custom ROMs and also keep in mind that 'bricked' says pretty much nothing (You must be more detailed when mentioning your phone's behaviour, like if it boots but stays on the splash screen, if it boots but stays on the boot animation etc)
Click to expand...
Click to collapse
it doesn't turn on in anyway, when I plug it into my computer it makes the windows sound that it's connected, but shows nothing on the device manager. it's a brick now
jokemaster21 said:
it doesn't turn on in anyway, when I plug it into my computer it makes the windows sound that it's connected, but shows nothing on the device manager. it's a brick now
Click to expand...
Click to collapse
You can recover anything on MTK anyways. Check mtkclient and this link for more info.
New LineageOS 19.1 Update // cannon and cannong // 27.08.22
Download:
- GitHub Releases
Changelog:
- Fixed minimum brightness issue (Thanks to @ganomin for finding out)
Bugs:
- None that I know of
Notes:
- Selinux is enforcing
- SafetyNet passes by default
- Custom recoveries, like TWRP and OFRP are not supported
- Custom kernels, like Eva Kernel, are not supported
- OTA support is present
LinkBoi said:
You can recover anything on MTK anyways. Check mtkclient and this link for more info.
Click to expand...
Click to collapse
no idea how to use this, too technical for me. maybe I could bring it into a repair shop.