EskeRahn 4,335 Posted May 11 Share Posted May 11 (lineage-19.1-20220509-nightly-pro1-signed.zip on April 5 security patch installed smoothly using adb sideload and MindTheGapps-12.1.0-arm64-20220416_174313) 1 Quote Link to post Share on other sites
EskeRahn 4,335 Posted Monday at 06:13 AM Share Posted Monday at 06:13 AM (lineage-19.1-20220516-nightly-pro1-signed.zip on May 5 security patch installed smoothly using adb sideload and MindTheGapps-12.1.0-arm64-20220416_174313) EDIT:Warning the Android Market (AKA "play store") is gone! I tried to do the flashing again - same result. I re-installed last weeks 20220509 - requiring a factory reset, and got it back EDIT II: Re-install of today's 0516 on the freshly factory reset did not remove it again. So everything is working - loosing everything by the factory reset obviously....... Quote Link to post Share on other sites
EskeRahn 4,335 Posted Monday at 06:24 AM Share Posted Monday at 06:24 AM On 5/2/2022 at 10:32 PM, EskeRahn said: I tried the described unplug and replug a few times and WAS able to reproduce it twice. Trying to narrow it down, I can no longer provoke it. So it might also be a matter of the charge level, so it only occur under a certain level? But thanks anyway, we really need a way to make it reproducable, for anyone to be able to track it down. Just retried this at 44%. and was not able to trigger it. So we still lacks a secure way to reproduce the bug. Quote Link to post Share on other sites
Sean McCreary 222 Posted Monday at 09:32 PM Share Posted Monday at 09:32 PM 15 hours ago, EskeRahn said: (lineage-19.1-20220516-nightly-pro1-signed.zip on May 5 security patch installed smoothly using adb sideload and MindTheGapps-12.1.0-arm64-20220416_174313) EDIT:Warning the Android Market (AKA "play store") is gone! I tried to do the flashing again - same result. I re-installed last weeks 20220509 - requiring a factory reset, and got it back EDIT II: Re-install of today's 0516 on the freshly factory reset did not remove it again. So everything is working - loosing everything by the factory reset obviously....... I haven't experienced this problem, and I don't think anything we changed in the May 16th build would cause this. I talked to a MindTheGapps maintainer, and he has seen this sort of problem if the device isn't rebooted (to recovery) between sideloading LineageOS and MindTheGapps, or if there isn't enough available space on the device. Are either of these a possible cause in your case? 1 Quote Link to post Share on other sites
CornholioGSM 176 Posted yesterday at 12:40 AM Share Posted yesterday at 12:40 AM Soo i am now littlebit scared...update or dont update and wait for new update? 🙂 Quote Link to post Share on other sites
EskeRahn 4,335 Posted yesterday at 06:23 AM Share Posted yesterday at 06:23 AM 20 hours ago, Sean McCreary said: I haven't experienced this problem, and I don't think anything we changed in the May 16th build would cause this. I talked to a MindTheGapps maintainer, and he has seen this sort of problem if the device isn't rebooted (to recovery) between sideloading LineageOS and MindTheGapps, or if there isn't enough available space on the device. Are either of these a possible cause in your case? Nope, flashing was done with the same bat-file I use each time, and this includes booting. Note that other GApps where still there - so pretty weird. And the phone was practically empty, so that was not the case either. Note that I did NOT make a factory reset when going from 18 to 19, AND that switch included being forced to switch from OpenGapps to MiindTheGapps - so that could be the real cause. (I was quite surprised that the Gapps-switch worked in the first place) Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.