Camera FC on many ROMS - Nexus 5X Q&A, Help & Troubleshooting

I installed 3 custom roms previously and all of them worked perfectly. These are the ROMS I installed:
Cosmic OS (build-2017/01/10, vendor-nmf26f, opengapps nano 2016/12/11)
SASOP-N (build-2017/01/09, vendor n4f26i, dynamic gapps full 2017/01/07)
Pure Nexus (build-2017/01/13, vendor n4f26i, dynamic gapps full 2017/01/07)
All these roms got the same bug. Camera works fine if I restart the phone when it is crashed. Please let me know if someone know the reason.

jkvithanage said:
I installed 3 custom roms previously and all of them worked perfectly. These are the ROMS I installed:
Cosmic OS (build-2017/01/10, vendor-nmf26f, opengapps nano 2016/12/11)
SASOP-N (build-2017/01/09, vendor n4f26i, dynamic gapps full 2017/01/07)
Pure Nexus (build-2017/01/13, vendor n4f26i, dynamic gapps full 2017/01/07)
All these roms got the same bug. Camera works fine if I restart the phone when it is crashed. Please let me know if someone know the reason.
Click to expand...
Click to collapse
Copy important user data to a computer. Then completely wipe your entire device by install the latest 7.1.1 factory image via fastboot. Now, test your camera.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Copy important user data to a computer. Then completely wipe your entire device by install the latest 7.1.1 factory image via fastboot. Now, test your camera.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thank you for the suggestion. Can I use Substratum theme engine on stock ROMs? I install custom ROMs to get full substratum compatibility on my device.

jkvithanage said:
Thank you for the suggestion. Can I use Substratum theme engine on stock ROMs? I install custom ROMs to get full substratum compatibility on my device.
Click to expand...
Click to collapse
I have no idea, however I don't think so.
Sent from my Nexus 5X using Tapatalk

Related

Newbie owner/questions

Hey,
Recently broke my phone and bought a Find 7 as a replacement. Hate the OS so started searching for ROMS etc. Never flashed anything or rooted anything so everything I've done so far - I've just learned.
I basically want to get as close to android 6.0 marshmallow stock as possible. Which ROM is the best for this?
So basically, I've tried to flash CM13 (latest release) which I got directly from their website, all goes well however when the phone boots the screen is blank. Volume rockers work, capacitive buttons work and haptic feed back there but screen is blank. Not sure what the problem is.
ANY help at all is appreciated.
I have the Find 7 QHD version which I think is the 7S? (X9076)
Thanks all!
1) You have to flash CWM or Twrp recovery to your phone. I recommend TWRP 3.0.2. Download it for your OPPO Find 7.
Flash it. Can be done via ADB.
2) You need micro SD card formatted by the phone! Not necessary but recommended.
2) Then download needed ROM( I like crDroid : http://forum.xda-developers.com/showthread.php?t=3171600
but it's developer left it. So no further support planned) to SD card(on PC of course).
3) Put the card into the phone.
4) On the phone: go to recovery mode. Wipe data, system, cache.
5) Install ROM from the micro SD card.
That is all. Enjoy it.
Sent from my X9077 using Tapatalk
You can also check out resurrection remix rom. Find the official thread in xda for find 7. As for your screen being blank it maybe because you have a new lcd panel which the official cm rom does not support. Try flashing omni rom instead. Last nightly is from aug 30. It is very stable and very close to stock android.
Sent from my Find7 using Tapatalk
bailfire said:
Hey,
Recently broke my phone and bought a Find 7 as a replacement. Hate the OS so started searching for ROMS etc. Never flashed anything or rooted anything so everything I've done so far - I've just learned.
I basically want to get as close to android 6.0 marshmallow stock as possible. Which ROM is the best for this?
So basically, I've tried to flash CM13 (latest release) which I got directly from their website, all goes well however when the phone boots the screen is blank. Volume rockers work, capacitive buttons work and haptic feed back there but screen is blank. Not sure what the problem is.
ANY help at all is appreciated.
I have the Find 7 QHD version which I think is the 7S? (X9076)
Thanks all!
Click to expand...
Click to collapse
Also check this post http://forum.xda-developers.com/showthread.php?p=68662397
Looks like you can use rr rom wuth patch.
Sent from my Find7 using Tapatalk
Andrew111 said:
1) You have to flash CWM or Twrp recovery to your phone. I recommend TWRP 3.0.2. Download it for your OPPO Find 7.
Flash it. Can be done via ADB.
2) You need micro SD card formatted by the phone! Not necessary but recommended.
2) Then download needed ROM( I like crDroid : http://forum.xda-developers.com/showthread.php?t=3171600
but it's developer left it. So no further support planned) to SD card(on PC of course).
3) Put the card into the phone.
4) On the phone: go to recovery mode. Wipe data, system, cache.
5) Install ROM from the micro SD card.
That is all. Enjoy it.
Sent from my X9077 using Tapatalk
Click to expand...
Click to collapse
DroidSK said:
You can also check out resurrection remix rom. Find the official thread in xda for find 7. As for your screen being blank it maybe because you have a new lcd panel which the official cm rom does not support. Try flashing omni rom instead. Last nightly is from aug 30. It is very stable and very close to stock android.
Sent from my Find7 using Tapatalk
Click to expand...
Click to collapse
Hey guys,
Many thanks for those tips (especially for the LCD patch - I'll have to try that).
So CM seems to be the best for Find7 at the moment but doesn't support unified storage? Does this mean I'll have this silly app storage limit? Anyway around it using CM?
As for the rest which is best (close to stock, stable, no bugs) -
RR
Omni
Nameless
Thanks
Omni is close to stock and very stable. RR and possibly nameless are both cm based.
Used omni for a couple of months and now using rr for the last couple of days. I would choose rr because of all the additional features.
Both are great daily drivers. Both support lvm so you can unify your storage in coloros and then flash either rom.
Sent from my Find7 using Tapatalk
DroidSK said:
Omni is close to stock and very stable. RR and possibly nameless are both cm based.
Used omni for a couple of months and now using rr for the last couple of days. I would choose rr because of all the additional features.
Both are great daily drivers. Both support lvm so you can unify your storage in coloros and then flash either rom.
Sent from my Find7 using Tapatalk
Click to expand...
Click to collapse
Hmmm,
CM thread has loads of additional things like installing some of the default apps like camera etc and how to get rid of all the bloatware.
I'll probably try nameless first since it seems to be the most popular next to CM. Its hard choosing one since theres so many! Out of Omni and RR which do you think is faster? What features does RR have that made you switch over to it?
If you truly want a stock like experience without too many features and full stability in your software then I would recommend Omni for you.
RR and DU have a lot of extra features relating to various visual effects that can be tweaked to your liking which can make your software look pretty, if you are interested in that sort of thing.
Cm is also stock like experience with some bugs here and there, nothing too big.
Nameless is based on cm with a few extra features but personally that Rom gives me bad battery life. (can be different for you)
Exodus, Mokee and Crdroid are just better alternatives to CM regarding features.
Edit: There are Roms that provide you with the option of LVM and there are those which only support stock partition. (Lvm is a way to enhance storage capacity).
Cm and a few other Cm based Roms that do not support lvm can be used with the chinese partition instead which also increases storage. But that is a bit lengthy process and for someone new like you I would recommend you to stay with a Rom like Omni which does support LVM.
Hope all this helped somehow

problems since going back to OOS

I used sultan's version of CM13 for 2 month and last week end i flashed OOS beta 7 and now i have several problems :
- My booting animation is neither the oneplus animation nor the one i flashed (the marvel/dc one, yes i reflashed it after flashing OOS), it is the word android. how can i change that?
- I can't flash Xposed : he tells me there is no space on the system partition and then the phone bootloop : i have a runing superSU 3.0.2-22 (the phone is rooted, ever app that uses root works)
- I have a zooper widget who doesn't load at startup (i have to opent the zooper app) and i checked, i allowe it to start at the start of the phone
Any idea on what i can do? i thought that maybe the kernel of sultan didn't get witched back to the original kernel when i flashed OOS and that causes problems
Friend, I will advice you tu flash Freedom OS 1.11 which is build on top of beta 7. Why I am saying this.
1. It allows to change the boot animation at the time of installation.
2. It will allow you to de boat the Google/oneplus pre-installed apps at the time of installation. That you can even do on stock beta 7 using titanium Backup app. That will resolve the problem you got while flashing xposed.
3. On beta 7 xposed wont work it will stuck on boot logo. So go to official xposed link and download the latest build, that will work.
4. Before installing freedom os I will highly recommend your too go through few last pages on its thread.
Sent from my ONEPLUS A3003 using Tapatalk
manishsoni7689 said:
Friend, I will advice you tu flash Freedom OS 1.11 which is build on top of beta 7. Why I am saying this.
1. It allows to change the boot animation at the time of installation.
2. It will allow you to de boat the Google/oneplus pre-installed apps at the time of installation. That you can even do on stock beta 7 using titanium Backup app. That will resolve the problem you got while flashing xposed.
3. On beta 7 xposed wont work it will stuck on boot logo. So go to official xposed link and download the latest build, that will work.
4. Before installing freedom os I will highly recommend your too go through few last pages on its thread.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
how is the camera on freedomOS?
will freedomOS update there build at the same rate as the betas or is it exeptionaly on the same base?
for the xposed, i did use the last build and it didn't work. but i am not against
using a different OS if can solve my problems
bigben14 said:
how is the camera on freedomOS?
will freedomOS update there build at the same rate as the betas or is it exeptionaly on the same base?
for the xposed, i did use the last build and it didn't work. but i am not against
using a different OS if can solve my problems
Click to expand...
Click to collapse
1. Camera is the same that you have on beta 7. Actually Freedom os is deboated stock oxygen with some extra tweaks like custom kernel, audio mods etc. Every thing is customizable there.
2. And yes they provide update as soon as newer build comes from oneplus.
3. This can solve all the issues you mentioned with the same taste of beta 7.
Sent from my ONEPLUS A3003 using Tapatalk
manishsoni7689 said:
1. Camera is the same that you have on beta 7. Actually Freedom os is deboated stock oxygen with some extra tweaks like custom kernel, audio mods etc. Every thing is customizable there.
2. And yes they provide update as soon as newer build comes from oneplus.
3. This can solve all the issues you mentioned with the same taste of beta 7.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
thank you very much, i'll try it then. hope it fixes evrything

Sensors stop working with any 7.1.1. Bullhead custom ROM

So, I'm very eager to upgrade to a 7.1.1 custom ROM from 6.0.1 (currently using Dirty Unicorns 6.0.1), but I seem to have an issue with any android 7.1.1 version of a custom ROM I install where the sensors for auto rotate and auto brightness stop working. I've tried complete wipes and resets and installed crDroid, resurrection remix dirty unicorns and lineage OS. All of them have the same result. When downloading any apps that can be used to test and calibrate sensors, they all will read for that the sensor is unavailable for all hardware in the phone except for Wifi and GPS. Is this a general issue with android 7.0.1 on nexus 5x or is this just me? I've yet to find any other forums or pages with anyone experiencing this.
Any suggestions at all on this? I don't want to be stuck using Android 6 forever.
Any advice that can be offered would be greatly appreciated!
Ryan
kvothe26 said:
So, I'm very eager to upgrade to a 7.1.1 custom ROM from 6.0.1 (currently using Dirty Unicorns 6.0.1), but I seem to have an issue with any android 7.1.1 version of a custom ROM I install where the sensors for auto rotate and auto brightness stop working. I've tried complete wipes and resets and installed crDroid, resurrection remix dirty unicorns and lineage OS. All of them have the same result. When downloading any apps that can be used to test and calibrate sensors, they all will read for that the sensor is unavailable for all hardware in the phone except for Wifi and GPS. Is this a general issue with android 7.0.1 on nexus 5x or is this just me? I've yet to find any other forums or pages with anyone experiencing this.
Any suggestions at all on this? I don't want to be stuck using Android 6 forever.
Any advice that can be offered would be greatly appreciated!
Ryan
Click to expand...
Click to collapse
Make sure you read the OP of the ROM you are installing.
Clean flash everything with correct vendor image.
kvothe26 said:
So, I'm very eager to upgrade to a 7.1.1 custom ROM from 6.0.1 (currently using Dirty Unicorns 6.0.1), but I seem to have an issue with any android 7.1.1 version of a custom ROM I install where the sensors for auto rotate and auto brightness stop working. I've tried complete wipes and resets and installed crDroid, resurrection remix dirty unicorns and lineage OS. All of them have the same result. When downloading any apps that can be used to test and calibrate sensors, they all will read for that the sensor is unavailable for all hardware in the phone except for Wifi and GPS. Is this a general issue with android 7.0.1 on nexus 5x or is this just me? I've yet to find any other forums or pages with anyone experiencing this.
Any suggestions at all on this? I don't want to be stuck using Android 6 forever.
Any advice that can be offered would be greatly appreciated!
Ryan
Click to expand...
Click to collapse
I have a similar problem with every 7.1.1 custom ROM. Lift to check phone is not working (and yes, ambient display is enabled, vendor is correct). Every stock-based 7.1.2 ROM does work. Try flashing Stock+ 7.1.2 and see if your sensors work.
indian84 said:
Make sure you read the OP of the ROM you are installing.
Clean flash everything with correct vendor image.
Click to expand...
Click to collapse
I am always clean flashing. What do you mean by correct vendor image? It's always a bullhead version of the ROM. Maybe I misunderstand what you mean.
kvothe26 said:
I am always clean flashing. What do you mean by correct vendor image? It's always a bullhead version of the ROM. Maybe I misunderstand what you mean.
Click to expand...
Click to collapse
There is something called vendor image that you have to flash along with the ROM. It's generally linked to the build number.
Read the OP of the ROM you are using, it should have the correct vendor image you should use. If THE OP does not mention anything about the Vendor image, just search the thread or politely ask what vendor image to use.
Hopefully someone should link the download link for you. If not, you can easily Google it.
indian84 said:
There is something called vendor image that you have to flash along with the ROM. It's generally linked to the build number.
Read the OP of the ROM you are using, it should have the correct vendor image you should use. If THE OP does not mention anything about the Vendor image, just search the thread or politely ask what vendor image to use.
Hopefully someone should link the download link for you. If not, you can easily Google it.
Click to expand...
Click to collapse
Ohh. I was never aware of having to do something like this. I've always just downloaded the ROM and flashed it. Really appreciate this! Thanks! I'll have to give this a try.
kvothe26 said:
Ohh. I was never aware of having to do something like this. I've always just downloaded the ROM and flashed it. Really appreciate this! Thanks! I'll have to give this a try.
Click to expand...
Click to collapse
I have a strong feeling flashing correct vendor image will solve your problems.
indian84 said:
I have a strong feeling flashing correct vendor image will solve your problems.
Click to expand...
Click to collapse
You were right!
I downloaded the latest image from google and used the flash-all.bat script through fastboot, reflashed twrp, flashed crDroid 7.1.1, got a vendor image mismatch error on boot, then flashed the recommended vendor image version and now I'm booting without error and all sensors are working! I noticed Wifi detection and connection were working a but slow before, now everything is working perfectly. I was completely unaware that this needed to be done. It never came up as an issue for me when I was on Nexus 5.
I love the XDA community! Thanks a million for your help!
kvothe26 said:
You were right!
I downloaded the latest image from google and used the flash-all.bat script through fastboot, reflashed twrp, flashed crDroid 7.1.1, got a vendor image mismatch error on boot, then flashed the recommended vendor image version and now I'm booting without error and all sensors are working! I noticed Wifi detection and connection were working a but slow before, now everything is working perfectly. I was completely unaware that this needed to be done. It never came up as an issue for me when I was on Nexus 5.
I love the XDA community! Thanks a million for your help!
Click to expand...
Click to collapse
Separate Vendor partition was introduced with 5X and 6P. It was not needed on earlier devices.

Zenfone 5 ZE620KL Project Treble GSI Test

After days of deciding..
Yes!! i have risked my device warranty for the sake of fun and excitement. HAHA LOL
For those who asked if we can flash Treble GSI (Generic System Image) on our device. The answer is Yes, FOR ME AT LEAST!
No complicated steps or whatsoever.
I just followed the steps from this link and downloaded the GSI of my choice. CREDITS TO ALL THE DEVELOPERS WHO WORKED FOR THIS PROJECT.
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
TRY THIS AT YOUR OWN RISK! I will not be held accountable to whatever happens to your device. This post is just to prove that indeed our device is treble enabled.
Some important things to note:
- You have backup of your data
- You have a working ADB
- There might be functionalities that is not working at the moment (Read the changelogs of your GSI choice before downloading)
- The notch looks bad on these builds (Android P might be able to fix this when it arrives)
- Your device should be in stock ROM (no heavy modifications such as xposed , magisk etc..) ROOT Not needed
- You should put your device on factory reset before trying this.
I have attached some screenshots of my test.
LINK TO Treble-Enabled Device Dev
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
THANK ME LATER! PEACE OUT!
good job!
Yes great job hows the camera working for you
grodri19721 said:
Yes great job hows the camera working for you
Click to expand...
Click to collapse
Lineage includes a very basic camera. just photo and video no portrait mode etc..
Lineage also has no gapps, i dont have twrp to flash gapps still figuring out how to install it.
I switched to the PixelExperience rom its great and with gapps included.
illustrasszo27 said:
Lineage includes a very basic camera. just photo and video no portrait mode etc..
Lineage also has no gapps, i dont have twrp to flash gapps still figuring out how to install it.
I switched to the PixelExperience rom its great and with gapps included.
Click to expand...
Click to collapse
android p preview 2 developer?
Everything functional?, no bugs?
el canario said:
android p preview 2 developer?
Click to expand...
Click to collapse
No. Its Android 8.1
There is no gsi for Android P yet.
DocRambone said:
Everything functional?, no bugs?
Click to expand...
Click to collapse
The only bug i have notice so far in PixelExperience is sometimes mobile data does not turned on when you toggle it in the quick tiles. you have to restart your phone then it will work after that.
illustrasszo27 said:
The only bug i have notice so far in PixelExperience is sometimes mobile data does not turned on when you toggle it in the quick tiles. you have to restart your phone then it will work after that.
Click to expand...
Click to collapse
You have the Z version with 845-chipset?
DocRambone said:
You have the Z version with 845-chipset?
Click to expand...
Click to collapse
No this is the lower version. with snapdragon 636
im still waiting on android P rom XD
Is the status bar at the top still messed up on the pixel experience ROM?
hands0m3 said:
Is the status bar at the top still messed up on the pixel experience ROM?
Click to expand...
Click to collapse
Yes. same as with lineage. for me its tolerable since no information is being shown at that part of the status bar.
Do you think changing the dpi would help with that
hands0m3 said:
Do you think changing the dpi would help with that
Click to expand...
Click to collapse
I'm not sure bro. One thing i tried is changing the display size in settings. It looks better but everything looks so big. so i reverted to the default one.
Sir could you possibly upload the stock recovery.img of our device.? im stuck on TWRP and i cant flash regular OTA update from there
jrd1990 said:
Sir could you possibly upload the stock recovery.img of our device.? im stuck on TWRP and i cant flash regular OTA update from there
Click to expand...
Click to collapse
What ROM are you using right now? i think you can extract it from the image of that ROM. sorry if this not as helpful.
he is on Stock Rom and he would like one guy put the stock recovery.img here
Excellent job. Thank you. I understand the camera is basic, but how is image quality? Looking forward to Google Camera port tests. And perhaps the ZE620KL fully ported so can make use of the landscape camera. Not a huge deal, but would be nice, no?
As visible on screenshot, Asus Camera is properly visible in the launcher (because of being put to vendor by Asus), but does it run well?

LineageOS 18.1 [R] [11] (Unofficial) Mi Pad 4 Plus (clover)

LineageOS 18.1, see this link
Installation instructions :
- Download the zip(s).
- Install latest TWRP for clover
- Perform a backup of your current ROM (optional)
- Wipe dalvik/cache (upgrade from lineageos 18.1) and wipe system/data if upgrade from other rom.
- Flash ROM.
- Flash GApps (NikGApps is recommended) is a must.
- Optional: Flash latest Magisk for root.
Everything should work.
Source :
sdm660
Hello !
No SD card.
Clean installation.
NikGapps-core-arm64
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------
Thank you for the LOS R. Very good rom.
Clean install with Nikgapps omni, found download in Chrome to sd card showing "download pending" and chrome will force close.
Awesome! Thanks!
rchoi999 said:
Thank you for the LOS R. Very good rom.
Clean install with Nikgapps omni, found download in Chrome to sd card showing "download pending" and chrome will force close.
Click to expand...
Click to collapse
I didn't use sdcard...it would be help if log is available...
-----> Have New Update 2020/10/19 I didn't install it, don't know the difference
addro said:
-----> Have New Update 2020/10/19 I didn't install it, don't know the difference
Click to expand...
Click to collapse
Some update in lineageos qcom repo....
Thanks a lot for working on this. I tried the following versions, but they all bootloop (bootsplash, lockscreen visible for a few seconds, then reboots):
lineage-18.0-20201017-UNOFFICIAL-clover_rev0.zip
lineage-18.0-20201018-UNOFFICIAL-clover.zip
lineage-18.0-20201019-UNOFFICIAL-clover.zip
This is with a WiFI-only miPad 4, latest TWRP, complete wipe of everything first.
sb56637 said:
Thanks a lot for working on this. I tried the following versions, but they all bootloop (bootsplash, lockscreen visible for a few seconds, then reboots):
lineage-18.0-20201017-UNOFFICIAL-clover_rev0.zip
lineage-18.0-20201018-UNOFFICIAL-clover.zip
lineage-18.0-20201019-UNOFFICIAL-clover.zip
This is with a WiFI-only miPad 4, latest TWRP, complete wipe of everything first.
Click to expand...
Click to collapse
@sabar_op, @sb56637, @amityg
Please keep in mind that there are many reports of bootloops etc using TWRP with Android 11.
TWRP officially supports all devices running Android up to 10, except devices LAUNCHED with 10 or later (having dynamic/logical partitions). There are no versions officially supporting devices running Android 11 to date:
TWRP 3.4.0 does not yet bring support for dynamic/logical partitions, which is required to support devices that launch with Android 10. It does, however, fix support for legacy devices that upgraded to Android 10, but retain the old partition scheme.
Click to expand...
Click to collapse
https://www.xda-developers.com/twrp...s-support-legacy-devices-upgraded-android-10/
Latest TWRP 3.4.0 arrived in June 2020 w/ support for devices upgraded to Android 10 (only). There's been no further versions. See here:
https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post83725859
The solution for most using custom Android 11 based ROMs has been to KEEP STOCK Recovery and use ADB fastboot boot TWRP (NOT flash) command from PC when needing custom recovery functions to flash ROMs etc. This seems to work for most despite having no TWRP fully supporting Android 11.
Nb. To achieve root with MagiskSU, this method is probably even more critical as users are reporting bootloops with TWRP custom recovery (flashed) and Android 11 when flashing Magisk pretty much accross the board.
Nb2. Achieving root with MagiskSU can alternatively be done without custom recovery by flashing Magisk Manager patched boot.img (extracted from ROM) using ADB fastboot flash image command from PC. This may be a less fraught method.
I'm still on LOS 17.1, but the above outlines the approach I intend to take / try soon.
Hope it helps, PW
sb56637 said:
Thanks a lot for working on this. I tried the following versions, but they all bootloop (bootsplash, lockscreen visible for a few seconds, then reboots):
lineage-18.0-20201017-UNOFFICIAL-clover_rev0.zip
lineage-18.0-20201018-UNOFFICIAL-clover.zip
lineage-18.0-20201019-UNOFFICIAL-clover.zip
This is with a WiFI-only miPad 4, latest TWRP, complete wipe of everything first.
Click to expand...
Click to collapse
Can you take the log?
Never try for mipad 4 wifi only, I use mipad 4 wifi-lte, twrp 3.4.0 with previous los17.1 installed and no issue so far...
I tried your room on my mi pad 4 wifi with twrp 3.4.0 no installation problem.
Running well on mi pad 4 plus. Really good apart from no sd card. Trying to upload logs.
Running well on mi pad 4 plus. Really good apart from no sd card. Trying to upload logs.[/QUOTE]
View attachment 5123311
idcom said:
Running well on mi pad 4 plus. Really good apart from no sd card. Trying to upload logs.
Click to expand...
Click to collapse
View attachment 5123311[/QUOTE]
Can't open the attachment...send me a pm for the log link.
A quick question : is sdcard not showing in setting/storage?
Enry44 said:
I tried your room on my mi pad 4 wifi with twrp 3.4.0 no installation problem.
Click to expand...
Click to collapse
Thanks for confirmation...it means no problem with mipad 4 wifi only... :good::good::good:
sabar_op Sure, where can I find the log?
Can't open the attachment...send me a pm for the log link.
A quick question : is sdcard not showing in setting/storage?[/QUOTE]
Have PMed you. Settings-≥Storage shows Portable but corrupted. When I format nothing changes.
sb56637 said:
Thanks a lot for working on this. I tried the following versions, but they all bootloop (bootsplash, lockscreen visible for a few seconds, then reboots):
lineage-18.0-20201017-UNOFFICIAL-clover_rev0.zip
lineage-18.0-20201018-UNOFFICIAL-clover.zip
lineage-18.0-20201019-UNOFFICIAL-clover.zip
This is with a WiFI-only miPad 4, latest TWRP, complete wipe of everything first.
Click to expand...
Click to collapse
This is probably because didn't install a *Gapps package.
sabar_op said:
Can you take the log?
Never try for mipad 4 wifi only, I use mipad 4 wifi-lte, twrp 3.4.0 with previous los17.1 installed and no issue so far...
Click to expand...
Click to collapse
Alex Kane said:
This is probably because didn't install a *Gapps package.
Click to expand...
Click to collapse
Hmm, not sure, LineageOS 17.1 works fine on this tablet without Gapps.
sb56637 said:
Hmm, not sure, LineageOS 17.1 works fine on this tablet without Gapps.
Click to expand...
Click to collapse
Yeah, but apparently LOS 18.0 beta doesn't.
I tried LOS 18.0 (beta) without gapps first and it would bootloop after reaching the home-screen. Flashing gapps would solve the issue (for me) but I don't use gapps so ... I went back to LOS 17.1.
I also experienced the issue with the sdcard not being properly detected.

Categories

Resources