This thread is to discuss the notorious screen problem with our Mi A2 February Pie release. As I was digging around XDA and 4PDA it has become clear that there are at least two types of LCD vendor:
1) TIANMA
2) JDI
I suppose you to note the vendor in your comment and confirm wherever the screen flickers or not.
Mine is from TIANMA and it suffers from flickering with the new update.
There definitely can be much more vendors, we all know Xiaomi's policies, they just put whatever parts they can buy in their phones.
So I've made a small poll for all of us so our dissatisfaction could be made clear to our dearest Xiaomi developers.
Cheers!
How to check your display vendor?
sas.mar said:
This thread is to discuss the notorious screen problem with our Mi A2 February Pie release. As I was digging around XDA and 4PDA it has become clear that there are at least two types of LCD vendor:
1) TIANMA
2) JDI
I suppose you to note the vendor in your comment and confirm wherever the screen flickers or not.
Mine is from TIANMA and it suffers from flickering with the new update.
There definitely can be much more vendors, we all know Xiaomi's policies, they just put whatever parts they can buy in their phones.
So I've made a small poll for all of us so our dissatisfaction could be made clear to our dearest Xiaomi developers.
Cheers!
Click to expand...
Click to collapse
I think it's just a software issue.
You can fix the colour levels and flickering by simply flashing Hex kernel on stock February update. Mine's perfect now.
@[email protected]
Hi, the thing is, some users in Russian forums report they don't face any issues. I think it's better to discuss at least something here and make some noise... =)
I guess that intense kernel tweaking made by Xiaomi doesn't affect some part of devices. That doesn't excuse them at all though =)
I made this latest update 2 days after I purchased the A2 and didn't noticed any problem at all
My guess is that is a bug with the color profile since I'm not able to turn on the sRGB option in settings.
wadhah1000 said:
How to check your display vendor?
Click to expand...
Click to collapse
Dial *#*#64663#*#* Software Version, TP Version
My screen is flickering too...I cannot understand wtf Xiaomi is doing, seriously.
Tainma
I just noticed about the screen flickering and its really annoying. Why are these things even happening... Once I upgraded to Pie with each "update" there is something wrong with the phone, be it minor or more serious issues like contacts messing up all the time. I expected clean and seamless experience when i bought this phone, but that's not what I got.
Tianma. Already voted. This is so annoying with darker/gray colored backgrounds. Watching youtube suuucks with this bug. But i do feel the phone to be a little snappier
Tainma
The update seems pretty borked. I tried booting into safe mode and disabling HW overlays with no result.
Me Tianma
---------- Post added at 05:51 PM ---------- Previous post was at 05:48 PM ----------
1) color flickering while swiping on youtube.
2) colour gradient of gboard changed.
3) swipe left right causes difference in color
jcunltd said:
Me Tianma
---------- Post added at 05:51 PM ---------- Previous post was at 05:48 PM ----------
1) color flickering while swiping on youtube.
2) colour gradient of gboard changed.
3) swipe left right causes difference in color
Click to expand...
Click to collapse
Exactly. Same here.
Images and videos flickering in Chrome as well.
My LCD's from tianma. Now, for those of you who wish to fix this flickering problem, install Hex kernel. You'll lose OTA, but just flash the stock February boot images if you want to receive the march security update.
Download official TWRP - https://dl.twrp.me/jasmine_sprout/twrp-3.2.3-0-jasmine_sprout.img.html
Download Hex kernel - https://t.me/hexreleases/116
1) Reboot your phone to fastboot mode using volume down + power button.
2) Connect your phone to your pc. (I am assuming you have adb and the drivers installed and know just the basics of flashing)
3) Open cmd.
4) Type - fastboot devices
5) If it lists any device then you're ready to go.
6) Rename the TWRP that you download earlier to TWRP.img
7) Run the command - fastboot boot TWRP.img
8) Your phone will restart and boot into TWRP.
9) Once TWRP is loaded, Go to advanced settings in TWRP and turn on ADB sideload.
10) Rename the Hex kernel file you downloaded to HEX.zip
10) Open CMD on your PC and type the command -
adb sideload Hex.zip
11) Reboot to system from TWRP.
Done.
I have the JDI screen. I haven't noticed any issues.
[email protected] said:
My LCD's from tianma. Now, for those of you who wish to fix this flickering problem, install Hex kernel. You'll lose OTA, but just flash the stock February boot images if you want to receive the march security update.
Download official TWRP - https://dl.twrp.me/jasmine_sprout/twrp-3.2.3-0-jasmine_sprout.img.html
Download Hex kernel - https://t.me/hexreleases/116
1) Reboot your phone to fastboot mode using volume down + power button.
2) Connect your phone to your pc. (I am assuming you have adb and the drivers installed and know just the basics of flashing)
3) Open cmd.
4) Type - fastboot devices
5) If it lists any device then you're ready to go.
6) Rename the TWRP that you download earlier to TWRP.img
7) Run the command - fastboot boot TWRP.img
8) Your phone will restart and boot into TWRP.
9) Once TWRP is loaded, Go to advanced settings in TWRP and turn on ADB sideload.
10) Rename the Hex kernel file you downloaded to HEX.zip
10) Open CMD on your PC and type the command -
adb sideload Hex.zip
11) Reboot to system from TWRP.
Done.
Click to expand...
Click to collapse
How about magisk? How to have root?
Sent from my Mi A2 using XDA Labs
I have the JDI panel. I have the grayish issue but i haven't encountered the flickering.
I also encountered poor camera quality.
jcunltd said:
Me Tianma
---------- Post added at 05:51 PM ---------- Previous post was at 05:48 PM ----------
1) color flickering while swiping on youtube.
2) colour gradient of gboard changed.
3) swipe left right causes difference in color[/QUOTE
Same problem, i don't know what to do
Click to expand...
Click to collapse
Let's wait for the next update with the solution
Hello, I'm suffering from the same problem. I even recorded a video reporting it (Since I'm a new user, I can not post the direct link from the video. But just put in the YouTube search):
Screen flickering on Xiaomi Mi A2 after February Pie release
{
"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"
}
Related
https://forums.geforce.com/default/...android-5-1-lollipop-ndash-available-7-23-15/
Finally the OTA has been released
Anyone use the 5.1 xposed on this yet? Waiting to see if it works before I update.
Sent from my bacon
Is the update even out yet? It's not showing up when I click check for updates..
zach jeremay said:
Is the update even out yet? It's not showing up when I click check for updates..
Click to expand...
Click to collapse
Yeah, I downloaded it and tried to install it. I forgot I had installed a custom recovery, so it failed. I reinstalled the factory recovery and now I'm waiting for the update again.
Does anyone have the img file for lollipop? I don't know why my updates not showing up.
Ok, seems the old CWM from KitKat is working. Also SU 2.46 does.
Sadly no Miracast anymore.
A few games apart from the mentioned ones in the link above won't work too: ARC Redux (more to come)
Did anyone catch the OTA. I have the factory Image for 103 but wont flash due to the "insufficient memory" for the system.img and the userdata.img I had similar problems with the tablet and only updated via the OTA. My system isn't showing as an update available.
diigibio said:
Did anyone catch the OTA. I have the factory Image for 103 but wont flash due to the "insufficient memory" for the system.img and the userdata.img I had similar problems with the tablet and only updated via the OTA. My system isn't showing as an update available.
Click to expand...
Click to collapse
You can try flashing the factory Image from update 103.
It's available now too...
https://developer.nvidia.com/gameworksdownload
Just make an account (it's free) and set the filter to "SHIELD".
Here you go.
astuermer said:
You can try flashing the factory Image from update 103.
It's available now too...
https://developer.nvidia.com/gameworksdownload
Just make an account (it's free) and set the filter to "SHIELD".
Here you go.
Click to expand...
Click to collapse
Thanks but already tried.
Sent from my A0001 using Tapatalk
Hi !
It seems my CWM is nit "compatible" with OTA 103, i get all sort of errors in CWM when trying to execute OTA update.
Do you have any hint where to download a compatiple CWM or stock recovery ?
(Or any smarter solution for that problem of course).
Greetings,
Ender
{
"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"
}
Can anybody confirm this issues?
1. Volume way too loud
2. Volume often varies, step 1 isn't always the same level.
3. Shield Hub can't be activated with button
Couldn't install with TWRP. Got some weird error after flashing and it wouldn't boot up at all. Had to go back and restore a backup.
Sent from my bacon
Hmm, i "solved" my Problem by flashing 5.1 with Linux instead of OTA...
Greetings,
Ender
Problems I can confirm are, cant install or update anything from the play store because of "insufficient space" when I clearly have 2GBs and a 64GB micro SD card, its alot slower and Apex Launcher is now utterly terrible with the new update.
After trying to install it won't boot up. Then I tried to fastboot but I'm getting an error saying target reported max download size of 643825664 bytes error: cannot load 'recovery.img' : No error .
Any ideas
I disabled "Google" so the Shield button does not activate it but still the Game Mapper is not showing up. Thats horrible, dis anyone manage to get back the Game Mapper ?
Ender
enderffx said:
I disabled "Google" so the Shield button does not activate it but still the Game Mapper is not showing up. Thats horrible, does anyone manage to get back the Game Mapper ?
Ender
Click to expand...
Click to collapse
To enable it open the app / game then hold down the start button until it pops up, If it didn't work then read down...
for me it's working perfectly i think because i flashed it using a computer (or maybe a factory reset should do the trick) if you're going to do it make sure you do a backup in the external sdcard because everything in the internal sdcard will be deleted I'm not responsible for any lost file or any damage, I'm not trying to scare you but I will help you if I can
By the way I disabled "google" and still the gamepad mapper is working fine so "google" has nothing to do with.
How did you guys use a computer to flash it? Sis they release the img? I would like to flash it with my computer because I still haven't received the ota.
---------- Post added at 12:14 AM ---------- Previous post was at 12:10 AM ----------
Did they release the img? How did u flash it with a computer, please help me because I didn't receive the ota and ima fan of lollipop.
All of these have been brought up on the Nvidia forums, so yes, they can be confirmed. I would like to add, that the volume changes dynamically depending on the sound being played In some games and emulators, I noticed that the sound would get quieter and louder without touching anything. I had Virtua Racing for 32x running in Retroarch and the volume dropped and raised in the same places during the demo mode every time, like it was done on purpose.
Is it just me, or does it seem like Nvidia is trying to de-Nvidia the Portable?
astuermer said:
Can anybody confirm this issues?
1. Volume way too loud
2. Volume often varies, step 1 isn't always the same level.
3. Shield Hub can't be activated with button
Click to expand...
Click to collapse
LeTV 1S/X500 (Full Review & Flash Tutorial) Fingerprint ID, Helio X10 MTK6795T 2.2GHz
In-Depth Video Review
• Camera sample: https://www.mediafire.com/folder/syseaa1kdeml5/LeTV_1S_(X500)_Camera_Samples
• Geekbench 3 battery test http://browser.primatelabs.com/battery3/162631
• Fast charge is confirmed working, and it charges: 30% in 30 minutes or 100% in 100 minutes (1 hour and 40 minutes).
• AnTuTu score (max): 53.200
• For the original LeTV X500 ROM and guide for TWRP, ROOT and GAPPS search on needrom for "LeTV X500"
LeTV X500/1S - Original ROM from LeTV - 5.5.008S
- Android 5.0.2
- Build: 5.5.008S
- Only English & Chinese language
- Not rooted & no gapps (but follow my guide further down to get both!)
If you have the LeTV X500/1S with an unoriginal ROM (from one of the shops who install a modified ROM with multilanguage) but want the original ROM from LeTV follow these steps:
1. Enable USB debugging on the phone.
2. Download the file from here called "S1_x500-CN-OP-DBXCNOP5500811172S-5.5.008S.zip". Rename it to "update.zip" and copy the file to the root of the phone.
3. Shutdown the phone.
4. Hold volume up and the power button together, as soon you see the LeTV bootlogo, let both go again, and it should boot into the stock recovery.
5. Now check Clear Data so both Update system and Clear data are checked - and then press the Start button
6. Now it will start flashing, now just wait for 10 minutes, and it should boot up and you have a clean new original LeTV system - done!
Now let's install TWRP so we can get ROOT and also install the GAPPS:
1. Enable USB debugging on the phone.
2. Be sure to have installed ADB drivers, you can install http://pdanet.co/a/ for that (this is important to have a working ADB or it will not work!)
3. Download TWRP_ROOT.rar from in here. Unpack the rar file on the PC to C:TWRP_ROOT
4. Connect phone with the PC, copy the "X500-ROOT.zip" file (found in TWRP_ROOT.rar) into the root of the phone and also copy the ui.zip to the phone and place it in Phone storage/TWRP/theme/ui.zip (this will make the TWRP recovery english when you enter it, else it will be displayed in all chinese)
Copy also "open_gapps-arm64-5.0-nano-20151114.zip" to the root of the phone and "UPDATE-SuperSU-v2.46.zip"
5. Still connected, run the recover.bat on the PC inside the TWRP_ROOT directory
(If there comes a popup on the phones screen just set allow always USB debugging on the phone)
- A commandpromt screen also appears on the PC
- Press Enter there will be a black screen on the phone with a tiny text on bottom left saying fastboot.
- Press on the screen 2 and then press Enter
- On the phone there will be a black screen with tiny texts in the middle.
- Press Enter again and the phone will reboot in TWRP recovery mode that should be displayed in english
6. If you want to ROOT the phone (you can also skip this if you want) then choose in TWRP the Install button and flash the file in root (sdcard) called "UPDATE-SuperSU-v2.46.zip" reboot and the phone will be rooted.
7. If you want to flash Gapps/Play Store then choose in TWRP the Install button and flash the file in root (sdcard) called "open_gapps-arm64-5.0-nano-20151114.zip" and reboot
8. Done!
If you want to remove TWRP recovery, and flash the stock recovery:
Then go into the C:TWRP_ROOT folder and there you find recovery.img and TWRPrecovery.img - where the recovery.img is the original one. Just swap these 2 files, and run the recover.bat again from step 5. And it will flash the original back on the phone! /Guide by s7yler
If you want the X500 ROM with multilanguage and an app drawer then download the:
"Letv_X500_multilanguage_rom(but_nTA).rar" but the bad thing is that this ROM doesnt support any OTA, and it may also be missing some few features, like the IR blaster and QR scanner app is not included. So I recommend to use the official LeTV ROM instead.
LeTV 1S/X500 (Hands-on & Unboxing)
LeTV 1S/X500 vs. X600 (Quick Comparison) Helio X10 MTK6795:
Specifications:
- 5.5 inch screen, 1920x1080 pixel IPS FullHD
- Gorilla Glass 3
- Fingerprint scanner / Tap to wake & unlock in 1 go!
- Long press "home" to lock screen
- Helio X10 Turbo MTK6795T 2.2GHz Octa Core
- 3 GB RAM + 32 GB ROM
- 13MP main camera + 5MP front camera
- Single LED flash
- Android 5.0.2 OS
- Notification LED (2 colours, maybe more?)
- Capacitive touch buttons with backlight
- Multilanguage (from the shop preinstalled)
- Network 2G, 3G & 4G LTE
- Dual SIM dual standby
- 3000mAh battery (is real and with fast charging)
- USB OTG On-The-Go
- GSM 850/900/1800/1900MHz
- WCDMA 850/900/1900/2100MHz
- TD-SCDMA 1880-1920/2010-2025MHz
- FDD-LTE B1/B3/B7, TDD-LTE B38/B39/B40/B41
{
"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"
}
Good review.
i have some question.
is it Root without problem on 5.5.008S? and OTA still work after Root?
Thanks
I'm planning to buy this phone, is there any weakness i should know before?
Thanks for the review
Thank you very much for your great review of this phone
I hope more content will be posted about it soon ^^
I'm looking forward to see some tutorials for making this phone even better with some custom software
Krystyna said:
I'm planning to buy this phone, is there any weakness i should know before?
Click to expand...
Click to collapse
Only that it doesn't have a Gyroscope Sensor and that the original LeTV ROM has a bit of batterydrain when it is in standby mode. But I hope they soon fix this with an update.
OnimushaPooh said:
Good review.
i have some question.
is it Root without problem on 5.5.008S? and OTA still work after Root?
Thanks
Click to expand...
Click to collapse
You can find my guide on how to root it in here http://www.needrom.com/download/letv-x5001s/
If you root OTA will likely not work anymore, it is like this on almost all phones. Also you must use the original recovery again. (can be flashed back). So if you want to receive OTAs on the phone then I recommend not to root it, or at least unroot it again.
I just use mine with no root and with original recovery. I flashed TWRP to flash the Gapps only and then reflashed the original recovery again. I have no experience if OTA works with root and TWRP, but if anyone out there knows, please inform us.
s7yler said:
I have no experience if OTA works with root and TWRP, but if anyone out there knows, please inform us.
Click to expand...
Click to collapse
I have my le1S rooted with KingRoot.
Since it's already up to date with stable version 5.5.008S, I'll wait for an update and post if OTA is working or not ^^
Toutotomatic said:
I have my le1S rooted with KingRoot.
Since it's already up to date with stable version 5.5.008S, I'll wait for an update and post if OTA is working or not ^^
Click to expand...
Click to collapse
Okay let us know, I just know that on the X600 the OTA didn't work if the phone was rooted. Somehow the OTA was checking for root first, and if it was found it would turn out with an error. So I just assumed it is the same on the X500.
wandy77 said:
Hi i present you w ww.letv.re
Unofficial International LeTV Phone Support
I need your help all
Click to expand...
Click to collapse
Do you have any videos showing the custom ROMs running on the LeTV phones? and can the ROMs be used? or too buggy still?
Has anyone figured out how to unlock band 20 800mhz?
reganlives said:
Has anyone figured out how to unlock band 20 800mhz?
Click to expand...
Click to collapse
Are you sure that such thing is even possible? Because just because some one tried or succeeded on another phone, doesn't mean it is possible on all phones.
s7yler said:
Are you sure that such thing is even possible? Because just because some one tried or succeeded on another phone, doesn't mean it is possible on all phones.
Click to expand...
Click to collapse
I'm not sure if its possible or not but from what I've read I believe people with elephone devices as well as redmi have tried. Not sure of success rate but they have seen differences in networks available
---------- Post added at 11:27 PM ---------- Previous post was at 11:26 PM ----------
Would be great if someone with advanced knowledge/skills could figure it out though.
reganlives said:
I'm not sure if its possible or not but from what I've read I believe people with elephone devices as well as redmi have tried. Not sure of success rate but they have seen differences in networks available
---------- Post added at 11:27 PM ---------- Previous post was at 11:26 PM ----------
Would be great if someone with advanced knowledge/skills could figure it out though.
Click to expand...
Click to collapse
All Elephone's models already come with Band20. Xiaomi have a lot of models, and all (almost) come without Band20, maybe it was possible on the Redmi, not sure. But since no one have done it on other of Xiaomis models, I don't think it is that easy.
I'll do some research and see what I can find out.
download links
the downlad link of the TWRP_ROOT.rar? i don't see it..
lollo8000 said:
the downlad link of the TWRP_ROOT.rar? i don't see it..
Click to expand...
Click to collapse
It is on needrom - in there search for LeTV X500
http://www.needrom.com/wp-content/uploads/2015/11/TWRP_ROOT.rar
Very keen in getting this phone, so far is there any known issue from the phone?
Hey, I just followed your steps for installing the rom, and then installing TWRP and the root. The only issue I'm having is that even though I placed ui.zip in the TWRP/Theme folder it still is in chinese. Also, the supersu app is in chinese as well, and it won't change language in the settings. Do you have any ideas why this might be?
New user
Thanks a bunch S7yler, u really did a good job on the review and I c it as a device worth buying since I received disappointments from elephone, I hope there'll b no regrets this time around.
As regards rooting, any rooted android receives Ota but fails to do the update thing, I'll advise u leave ur fone uprooted and save d stress of uprooting and rooting again at every update received and I also belive there's a tendency of the gapps being wiped off at update, meaning one has to reinstall again, I hope that doesn't happen though.
Is the LeTV shortcut in the middle removable?
I was on untouched april stock, i used gcam enabling camera2api via this thread https://forum.xda-developers.com/mi-a1/how-to/tool-google-camera-root-magisk-enable-t3747585
I rooted yesterday for the first time to use titanium backup for backing up my apps (i like backing up with both twrp and tb just to on the safer side) as i was about to try a custom rom, after rooting i remeber there was a linux splash screen before the mi logo. After using the custom rom for a few hours i downloaded the fastboot april stock via this link http://bigota.d.miui.com/V.9.5.10.0.ODHMIFA/tissot_images_V.9.5.10.0.ODHMIFA_20180405.0000.00_8.0_b9e697ed56.tgz
flashed the rom via miflash, everything was normal as earlier, then i noticed some "Caping" app on my phone after installing nova launcher, this app was never present on my my previous rom, i uninstalled and ignored it. After that i installed magisk, my apps and went on to enable camera2api with that same tool that i used earlier. Now on each reboot i see a bootloader warning instead of that linux mascot which used to be on my previous stock, also there's a noticable lag (3-5 sec green screen) in opening gcam which wasn't the case earlier. This makes me think that there's something different about this fastboot rom, can anyone explain me this?
Linux mascot on stock? Really? Never seen that. You must have had some weird reseller firmware on there first.
No, no region difference ROM's.
CosmicDan said:
Linux mascot on stock? Really? Never seen that. You must have had some weird reseller firmware on there first.
No, no region difference ROM's.
Click to expand...
Click to collapse
yup, i thought everyone would be seeing the same so i didn't bothered clicking a pic of that bootup, the mascot was exactly like the pic i atached, but a LOT smaller with entirely dark background. Also i am from india and i bought it via official sale, so i doubt "weird reseller" case can be applied here.
{
"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"
}
UPDATE: i still havent found the mystery behind that linux mascot, but the gcam lag was fixed with locked bootloader. Probably magisk and unlocked bootloader was causing that. Hope it helps someone
pooniaprashant said:
UPDATE: i still havent found the mystery behind that linux mascot, but the gcam lag was fixed with locked bootloader. Probably magisk and unlocked bootloader was causing that. Hope it helps someone
Click to expand...
Click to collapse
The tux logo shows because your `splash.img` got cleared. I've attached the stock `splash.img` here, you just need to run `fastboot flash splash splash.img` in Fastboot mode.
justin97530 said:
The tux logo shows because your `splash.img` got cleared. I've attached the stock `splash.img` here, you just need to run `fastboot flash splash splash.img` in Fastboot mode.
Click to expand...
Click to collapse
finally someone with who gets to the topic, there's 3 screens that comes up when an unlocked device boots up,
1. the bootloader warning screen (which was where i got that linux mascot)
2. the actual splash screen, with that mi logo below, (this was always there, with/without linux mascot)
3. boot animation, (of no use here)
so you mean that the 1st thing, the bootloader warning splash screen got cleared, am i right? as both the mi logo (actual splash screen) and the bootanimation were the same.
IjazCI said:
Hey there the Capping app is because you flashed the userdata image while flashing through Mi Flash tool. You can just uninstall that.
After my first bootloader unlock i too had that cute linux mascot. Its gone after next fastboot unlock.
Click to expand...
Click to collapse
glad someone noticed the same :highfive:
pooniaprashant said:
finally someone with who gets to the topic, there's 3 screens that comes up when an unlocked device boots up,
1. the bootloader warning screen (which was where i got that linux mascot)
2. the actual splash screen, with that mi logo below, (this was always there, with/without linux mascot)
3. boot animation, (of no use here)
so you mean that the 1st thing, the bootloader warning splash screen got cleared, am i right? as both the mi logo (actual splash screen) and the bootanimation were the same.
Click to expand...
Click to collapse
Yup. The bootanimation (excluding the Mi logo) is loaded by Android from the boot animation file in `/system/media`.
IjazCI said:
The camera lag is introduced by root itself. As a workaround you can use Magisk module from this thread. https://forum.xda-developers.com/mi-a1/themes/module-long-camera-start-fix-mi-a1-t3745262/page2
Unlike other modules this keeps Selinux status as enforcing and it's from a respectable dev.
Click to expand...
Click to collapse
I removed magisk itself ?
justin97530 said:
Yup. The bootanimation (excluding the Mi logo) is loaded by Android from the boot animation file in `/system/media`.
Click to expand...
Click to collapse
What do you think triggered the splash screen deletion?
pooniaprashant said:
What do you think triggered the splash screen deletion?
Click to expand...
Click to collapse
I'm not sure, for me it was probably because of me accidentally flashing wrong images.
Update out:
https://source.android.com/security/bulletin/pixel/2019-12-01.html
Security updates noted.
Functional patch notes moved to:
Pixel Community forum https://support.google.com/pixelphone/community
Notable fixes:
{
"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"
}
In addition to the specific items listed above, the December update includes hundreds of various fixes and improvements across many areas including performance, stability, camera, display and face unlock.
12/3/19 Edit Note:
*Updated Google Pay fix to better describe actual fix. This is an experimental feature that may roll out in a future update.
Anyone updated to December patch that can verify Magisk still working?
Jexx11 said:
Anyone updated to December patch that can verify Magisk still working?
Click to expand...
Click to collapse
20.1 worked fine.
I noticed they added the styles and themes app in display settings. Tulsadiver's accent mod still works- https://forum.xda-developers.com/pixel-2-xl/themes/android-10-accents-mod-t3996755
Jexx11 said:
Anyone updated to December patch that can verify Magisk still working?
Click to expand...
Click to collapse
Works as it should
Nothing yet here in UK. Did we also get live caption feature?
100rabh7791 said:
Nothing yet here in UK. Did we also get live caption feature?
Click to expand...
Click to collapse
live caption working if you use this mode https://www.xda-developers.com/enable-pixel-4-live-caption-android-10/ thanks to @MishaalRahman
kmry said:
live caption working if you use this mode https://www.xda-developers.com/enable-pixel-4-live-caption-android-10/ thanks to @MishaalRahman
Click to expand...
Click to collapse
Thanks but not rooted so i can't use this. Can't root as use this phone for official purposes and for payments
Swipe down on homescreen for notification drawer was also added
hawkswind1 said:
20.1 worked fine.
I noticed they added the styles and themes app in display settings. Tulsadiver's accent mod still works- https://forum.xda-developers.com/pixel-2-xl/themes/android-10-accents-mod-t3996755
Click to expand...
Click to collapse
Can we change status bar icons ? Like the cellular bar and Wifi and battery?
telegram notifications failed to group together after december update
I can't seem to get root back. I did my usual things. It boots up, but when I flash the latest magisk it gets stuck at the G for a bit, then reboots into recovery, where I try again.
I'm fastboot booting the latest twrp and flashing the latest magisk there.
When I say it boots up, I always check that it does before flashing anything.
blacklisted.rock said:
Can we change status bar icons ? Like the cellular bar and Wifi and battery?
Click to expand...
Click to collapse
I believe it only changes the wifi icon on the status bar and the quick tile icons
Larzzzz82 said:
I can't seem to get root back. I did my usual things. It boots up, but when I flash the latest magisk it gets stuck at the G for a bit, then reboots into recovery, where I try again.
I'm fastboot booting the latest twrp and flashing the latest magisk there.
When I say it boots up, I always check that it does before flashing anything.
Click to expand...
Click to collapse
I suggest you flash magisk uninstaller first and then flash magisk 20.1.
jlokos said:
I suggest you flash magisk uninstaller first and then flash magisk 20.1.
Click to expand...
Click to collapse
That worked! Thank you sir.
Anybody doing ota update and keeping root and magisk?
bsg411 said:
Anybody doing ota update and keeping root and magisk?
Click to expand...
Click to collapse
Is this possible? I'd love to know how?
Also, did anyone else have to flash magisk uninstaller for this update as is mentioned a few posts above by someone? That's not part of my standard procedure.
One more positive I noticed from the update. There's no longer a delay between returning to the homescreen and when you can open a folder. Previously I had to wait a split second for the homescreen animation to finish before I could open a folder.
Seems like 3rd party launchers are supported too? I just used Nova launcher with gesture navigation(not sure if this is new)
Schroeder09 said:
Is this possible? I'd love to know how?
Also, did anyone else have to flash magisk uninstaller for this update as is mentioned a few posts above by someone? That's not part of my standard procedure.
Click to expand...
Click to collapse
I thought I read somewhere it could be done.
Well, last month was the first time I was able to flash OTA and keep root. The procedure was to uninstall Magisk from Magisk Manager (not completely) install the OTA (DON'T REBOOT!) then re-install Magisk from the manager (the after OTA option), then reboot. Worked great.
This month, I tried this and I'm not able to boot up. Reboots a couple of times then goes to a stock recovery screen telling me it can't boot and the options are "try again" and the dreaded "factory reset".
I've tried booting in TWRP (using fastboot) to flash the latest magisk uninstall, and then flashing the full factory image (with the -w flag removed)... not luck so far, but I'll try again a few times as in the past when I've had trouble, re-flashing actually helps.
Anyone else had similar trouble?
basily said:
Well, last month was the first time I was able to flash OTA and keep root. The procedure was to uninstall Magisk from Magisk Manager (not completely) install the OTA (DON'T REBOOT!) then re-install Magisk from the manager (the after OTA option), then reboot. Worked great.
This month, I tried this and I'm not able to boot up. Reboots a couple of times then goes to a stock recovery screen telling me it can't boot and the options are "try again" and the dreaded "factory reset".
I've tried booting in TWRP (using fastboot) to flash the latest magisk uninstall, and then flashing the full factory image (with the -w flag removed)... not luck so far, but I'll try again a few times as in the past when I've had trouble, re-flashing actually helps.
Anyone else had similar trouble?
Click to expand...
Click to collapse
Extract the boot.img from the factory image, put it on your phone and patch it via magisk manager. Then put the patched.img in your platform-tools folder, and fastboot it to both slots. It's also a good idea to disable all modules and substratum themes, and set your screen lock to swipe before you do monthly updates. It's what I do every month without issues for about the last 2 years :good:
{
"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:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
FlameGapps FULL
Magisk 23.0 (after first boot) - (Download from here)
First-time installation:
Be sure to be on the latest stock MIUI v12.1.5.0 base
Boot into TWRP or OrangeFox
Flash Rom
Reboot to recovery
Flash Gapps
Format Data
Reboot to system
Update installation:
Boot into TWRP or OrangeFox and flash rom
Reboot to recovery and flash Gapps, Magisk, etc.
Wipe cache
Reboot to system
Sources:
ROM: https://github.com/crdroidandroid
Kernel: VantomKernel
Download:
ROM: OSS Releases
Known issues:
You tell me
Visit the official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs
Thanks for the roms man
a query, the brightness is always turned up to the maximum when using the fingerprint?
fuathan said:
Thanks for the roms man
Click to expand...
Click to collapse
Welcome
Jcyeici said:
a query, the brightness is always turned up to the maximum when using the fingerprint?
Click to expand...
Click to collapse
That has not been fixed yet
Thank you very much for your great work, I will look forward to the fix of the brightness when using the footprint.
A suggestion
1- they can put the option to hide the notch drop,
2- double tap to lock screen please
i think my storage is encrypted? i cant copy things onto the phone
Thank you @AndroidHQ254. I installed the rom and it runs very smooth. FOD and face unlock works quite well.
I use NikGapps macro from 12/14/20 and it runs very well.
A part of my storage is still encripted, but no idea how to fix. Maybe someone can share his experience.
Bernd K said:
Thank you @AndroidHQ254. I installed the rom and it runs very smooth. FOD and face unlock works quite well.
I use NikGapps macro from 12/14/20 and it runs very well.
A part of my storage is still encripted, but no idea how to fix. Maybe someone can share his experience.
Click to expand...
Click to collapse
More details please on the part of your storage you mean?
hanste (SM-G901F) said:
i think my storage is encrypted? i cant copy things onto the phone
Click to expand...
Click to collapse
Did your format data and reboot reboot recovery?
Jcyeici said:
Thank you very much for your great work, I will look forward to the fix of the brightness when using the footprint.
A suggestion
1- they can put the option to hide the notch drop,
2- double tap to lock screen please
Click to expand...
Click to collapse
DT2W works on FTS screens
AndroidHQ254 said:
More details please on the part of your storage you mean?
Click to expand...
Click to collapse
See added screenshots.
1. error message if you wipe dalvik cache.
2. if you install from twrp recovery from internal storage
3. system is not encrypted only internal storage (sdcard)
My system run very well every think works and I followed your Flashing Instructions .
Maybe it make sense to use the no-vertiy-opt-encrypt script if you install the rom first time?
Works great! Only some issues / wishes:
Sometimes the screen wont wake (if i get a phone call, or unlock with FOD, the screen can sometimes stay all black with no other possibilty than to reboot trough the power menu.
No Home controls on power menu
SELinux is set to permissive. Im using SELinuxModeChanger to automatically set it to enforced every boot so i can use Google Pay.
FOD icon stays on top of first pin lock input on boot.
To flash and root i had to use different recoveries. PBRP for the rom, then TWRP for Magisk.
Other than what is mentioned above, everything seems to work great!
Duplicate
Very interested in this rom. Used a nexus 6p for 2 or 3 years and the last rom I used for it was crdroid rom. It was excellent for that device, but the device showed its age and I had to replace it. I quite like this device and I'm willing to depart from the stock rom. But I'm going to wait for a while until all the bugs are fixed as I use it for work too, so I need it to be stable as possible.
I used that rom the last 4 weeks without any problem. FOD and face unlock works quite well. Any update planned to CrDroid 7.2?
@AndroidHQ254 What is the status of this rom, have there been any updates? Unfortunately, there is no official support for this phone on crdriod site. I'm not sure where to track any progress if there is one.
Bernd K said:
See added screenshots.
1. error message if you wipe dalvik cache.
2. if you install from twrp recovery from internal storage
3. system is not encrypted only internal storage (sdcard)
My system run very well every think works and I followed your Flashing Instructions .
Maybe it make sense to use the no-vertiy-opt-encrypt script if you install the rom first time?
Click to expand...
Click to collapse
I have not had issues with decryption personally
vetle666 said:
Works great! Only some issues / wishes:
Sometimes the screen wont wake (if i get a phone call, or unlock with FOD, the screen can sometimes stay all black with no other possibilty than to reboot trough the power menu.
No Home controls on power menu
SELinux is set to permissive. Im using SELinuxModeChanger to automatically set it to enforced every boot so i can use Google Pay.
FOD icon stays on top of first pin lock input on boot.
To flash and root i had to use different recoveries. PBRP for the rom, then TWRP for Magisk.
Other than what is mentioned above, everything seems to work great!
Click to expand...
Click to collapse
About missing features - That is a rom side thing
Selinux - For now we are permissive
About FOD - I have not encountered that. Plus I do not think you keep rebooting your phone
Include logs for bugs
sage of six paths said:
@AndroidHQ254 What is the status of this rom, have there been any updates? Unfortunately, there is no official support for this phone on crdriod site. I'm not sure where to track any progress if there is one.
Click to expand...
Click to collapse
I work alone so the rom will be updated in due time