Related
When installing some of the apps like IFTTT,adapticons and greenify(the most imp. app for this phone ) the phone starts rebooting and stuck on the boot image the only solution i could find is either formatting phone or deleting app data from file manager with the help of TWRP.The phone starts rebooting when the app just finished downloading from play store and starts installing.And i try to install the same apps from external source it happens again but the difference is only that this time a message prompt arrives and says play store stopped working.It happens in all the ROMS. I have tried to clear the whole internal storage(excluding recovery,obviously ) but the issue doesn't get fixed...
What can i do to solve this problem?
did you manage to solve it?
prabhavjain.08 said:
When installing some of the apps like IFTTT,adapticons and greenify(the most imp. app for this phone ) the phone starts rebooting and stuck on the boot image the only solution i could find is either formatting phone or deleting app data from file manager with the help of TWRP.The phone starts rebooting when the app just finished downloading from play store and starts installing.And i try to install the same apps from external source it happens again but the difference is only that this time a message prompt arrives and says play store stopped working.It happens in all the ROMS. I have tried to clear the whole internal storage(excluding recovery,obviously ) but the issue doesn't get fixed...
What can i do to solve this problem?
Click to expand...
Click to collapse
Did you manage to solve it somehow? I'm facing the same issues, I dont know what else to try!
ggonmar said:
Did you manage to solve it somehow? I'm facing the same issues, I dont know what else to try!
Click to expand...
Click to collapse
No i wasnt able to fix it.
and if u fix it then let me know how.!!
The solution
The only Marshmallow Rom without this issue is AOSP rom, but If you still wanna use other 6.0 Rom you will have to use older version of apps which are causing bootloops.
Also Nougat Rom's don't have this problem but I don't find them stable enough for daily use.
prabhavjain.08 said:
When installing some of the apps like IFTTT,adapticons and greenify(the most imp. app for this phone ) the phone starts rebooting and stuck on the boot image the only solution i could find is either formatting phone or deleting app data from file manager with the help of TWRP.The phone starts rebooting when the app just finished downloading from play store and starts installing.And i try to install the same apps from external source it happens again but the difference is only that this time a message prompt arrives and says play store stopped working.It happens in all the ROMS. I have tried to clear the whole internal storage(excluding recovery,obviously ) but the issue doesn't get fixed...
What can i do to solve this problem?
Click to expand...
Click to collapse
Try the VIPER OS ITS ANDROID VERSION IS 7.1/2 look in dev area of this device and remove every thing system + both caches + boot and also flash GAPPS pico version sometimes GOOGLE APP causes this problem (experienced):crying:
Lollipop ROM
nanomine said:
The only Marshmallow Rom without this issue is AOSP rom, but If you still wanna use other 6.0 Rom you will have to use older version of apps which are causing bootloops.
Also Nougat Rom's don't have this problem but I don't find them stable enough for daily use.
Click to expand...
Click to collapse
Does Lollipop ROM have this issue too?
whic h gapps version are you usinG?? I think pico is better version to this phone
I found the solution!! Posting it...
prabhavjain.08 said:
When installing some of the apps like IFTTT,adapticons and greenify(the most imp. app for this phone ) the phone starts rebooting and stuck on the boot image the only solution i could find is either formatting phone or deleting app data from file manager with the help of TWRP.The phone starts rebooting when the app just finished downloading from play store and starts installing.And i try to install the same apps from external source it happens again but the difference is only that this time a message prompt arrives and says play store stopped working.It happens in all the ROMS. I have tried to clear the whole internal storage(excluding recovery,obviously ) but the issue doesn't get fixed...
What can i do to solve this problem?
Click to expand...
Click to collapse
This happens for the "Android System Webview" apk. To solve this issue, here's a step by step guide:
1. Download Android System Webview by Google. (Not from play store. Must be downloaded as an APK)
2. Delete Current Webview with a root browser. (Es file explorer recommended. Located in system/apps/webview.)
3. Reboot device.
4. Now Install the new webview you downloaded.
Problem solved.
Tested and working successfully. Android 5.0.2 , 5.1, 6.0 All ROM with this issue is.... fixed with this method. Tested on all ROMs.
Enjoy.
---------- Post added at 03:22 PM ---------- Previous post was at 03:12 PM ----------
The webview implements a code into the system to properly show the app package to system UI. But the default Android System Webview which comes with the system is kinda bugged. It conflicts with some apps package. This conflict mess up the system... crashing the UI, then the whole system itself. So the device reboots and/or gets stuck in bootloop. Removing the preinstalled webview will solve the issue. I have posted the step by step guide above.
While updating/installing apps from the google playstore, the phone will crash and bootloop, and requires a full reinstall to get it working normally. I've attached 2 logcat files for both roms which give the same problem - Mokee5.1, CM13 on a clean installation with pico gapps and manually selecting several apps to install. One other custom rom also gave the same problem so I didn't bother trying any other custom roms. Reverting back to stock MIUIv8 gave no issues.
CM13 used to be mostly problem free until a few months ago I think when the update/install issue started happening. The playstore auto update is normally kept disabled on my phone so I'm unaware about when the problem really started happening.
Edit-
It doesn't seem to be happening anymore from a short test after flashing my CM13 backup but I've moved on to LO14.1
It may have something to do with some other complaints that people are having. It looks like some issue with Cynogenmod since Sept/Oct 2017 which needs some patching.
https://forum.xda-developers.com/general/help/bootloop-updating-apps-telegram-t3700773
Update to/ Installation of newest version breaks system
https://github.com/signalapp/Signal-Android/issues/7171
Several apps causes a phone reboot or boot loop
https://gitlab.com/fdroid/fdroiddata/issues/979
Can confirm the issue with CM13 on my Galaxy S3. Unfortunately, I do not know a solution. Just stick to older app versions.
Hi.
I've got a strange problem trying to keep my Oneplus 3T up-to-date:
Everytime I flash a lineage OS nightly build (no matter if using the auto updater or the recovery) my smartphone tries to boot normally (displaying the lineage animation), but after a minute, the recovery is started.
To fix this, I have to remove or reinstall the Google Apps (OpenGApps), which normally results in all apps to have rights removed (no location services, no storage access, no phone access, ...)
Can somebody tell me if this is a normal behaviour? Or do I do something wrong? Is there a way to avoid this?
Best regards,
_X_
XploD.GER said:
Hi.
I've got a strange problem trying to keep my Oneplus 3T up-to-date:
Everytime I flash a lineage OS nightly build (no matter if using the auto updater or the recovery) my smartphone tries to boot normally (displaying the lineage animation), but after a minute, the recovery is started.
To fix this, I have to remove or reinstall the Google Apps (OpenGApps), which normally results in all apps to have rights removed (no location services, no storage access, no phone access, ...)
Can somebody tell me if this is a normal behaviour? Or do I do something wrong? Is there a way to avoid this?
Best regards,
_X_
Click to expand...
Click to collapse
This is not normal. Maybe you should try to get a new version from open GApps.
kurtn said:
This is not normal. Maybe you should try to get a new version from open GApps.
Click to expand...
Click to collapse
OK, thanks for your help. So for the next update, I will install the newest version of GApps. I tried 2 versions (31.01 and 08.02), but both did show this behaviour... I hope this'll be fixed soon...
Code:
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/COLOR]
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended Lineage recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
More detailed instructions at:
Install LineageOS on crackling
Official Download link:
LineageOS Downloads
115ek's test builds (for testers only)
Downloads
Recommended Google Apps package:
Open GApps (pico only)
Changelog:
Changes for crackling
Bug reports:
How to submit a bug report
Donate to support development:
Donate via PayPal to LineageOS
reserved
reserved2
The "old" Lineage 17.1 thread got lost during some xda server maintenance. It's not really clear to me what happened.
It couldn't be brought back for several weeks now, so I decided to create a new thread.
I'd also like to inform you that I'll provide some test builds here. Before merging bigger changes I'd like to ensure the builds are okay (not just for me).
It would be nice if some of you could test a bit. Only caveat: You won't be able to switch between test builds/official builds easily as different signature keys are used and a factory reset is needed (alternatively flashing a migration file could save you from resetting the device (more info)). However, these test builds are thought for interested persons only
You'll find the first test build here.
Changes:
switch to userspace lmkd (more info here)
It would be interesting if you experience any differences in memory management (how many apps can be opened in background, how fast is app switching, when are apps closed...).
And of course if the system is usable at all.
Recovery
Can the lineage-recovery.img do nandroid backups now that twrp can't?
petexd said:
Can the lineage-recovery.img do nandroid backups now that twrp can't?
Click to expand...
Click to collapse
Lineage recovery can't do backups. TWRP can.
But standard users installing gapps could also do a backup via google servers. I guess that's the most "easiest" thing.
115ek said:
Lineage recovery can't do backups. TWRP can.
But standard users installing gapps could also do a backup via google servers. I guess that's the most "easiest" thing.
Click to expand...
Click to collapse
I've just tried to restore a recent backup for the first time with android 10 (lineage 17.1) and although it appears to backup the restore did not work. I tried it twice. Then I remember reading that twrp were having problems being totally compatible with the new partitioning of android 10 so there have been no updates since may 2019. I'm assuming that's the issue with the latest backups (and I don't use gapps).
petexd said:
I've just tried to restore a recent backup for the first time with android 10 (lineage 17.1) and although it appears to backup the restore did not work. I tried it twice. Then I remember reading that twrp were having problems being totally compatible with the new partitioning of android 10 so there have been no updates since may 2019. I'm assuming that's the issue with the latest backups (and I don't use gapps).
Click to expand...
Click to collapse
What's happening when you're restoring? Are you running into a bootloop?
Then probably this could help.
Please keep in mind TWRP isn't able to decrypt an encrypted /data partition. As long as we don't fix it, you won't have any chance to backup an encrypted device.
If you're not encrypted it shouldn't be a problem, though.
Edit:
You can find the build with the according changes here.
Please report back if it works for you. Keep in mind you can't dirty flash this over an official build.
Edit 2:
I checked the issue on my own and it worked. The change got already merged so it'll be included in the next official build as well. As builds are weekly temporary you could download it next saturday.
115ek said:
What's happening when you're restoring? Are you running into a bootloop?
Then probably this could help.
Please keep in mind TWRP isn't able to decrypt an encrypted /data partition. As long as we don't fix it, you won't have any chance to backup an encrypted device.
If you're not encrypted it shouldn't be a problem, though.
Edit:
You can find the build with the according changes here.
Please report back if it works for you. Keep in mind you can't dirty flash this over an official build.
Edit 2:
I checked the issue on my own and it worked. The change got already merged so it'll be included in the next official build as well. As builds are weekly temporary you could download it next saturday.
Click to expand...
Click to collapse
Thanks for the info. That's exactly what's happening but I have no idea how to apply that patch. I don't really want to install an unoffical rom: that's how I discovered twrp wasn't working properly, testing one of my builds then hoping to go back to your offical from restore.
Any way I'm happy to wait for your next issue.
Thanks for doing a great job.
I've just installed the Lineage OS 17.1 official on my Swift. Although this 17.1 thread mentions OpenGapps pico only (which was the case under LOS 16), even the pico package produces an insufficient space error on my Swift. (This is after a completely clean - wipe system and data and all caches - installation).
Have Gapps just gotten too big for these small devices? Or is there some trick to get it to work?
thanks.
libove said:
I've just installed the Lineage OS 17.1 official on my Swift. Although this 17.1 thread mentions OpenGapps pico only (which was the case under LOS 16), even the pico package produces an insufficient space error on my Swift. (This is after a completely clean - wipe system and data and all caches - installation).
Have Gapps just gotten too big for these small devices? Or is there some trick to get it to work?
thanks.
Click to expand...
Click to collapse
Last time I tried it worked. But you're right - the available space on /system is very rare. I already made some "hacks" to free up some space. You could try to overcome this by installing an older pico gapps package from here which is smaller. It'll update itself if you connect to a wifi network anyway.
Another thing you could try is using FlameGapps. The final thing would be resizing the /system partition.
Is anyone else experiencing this issue? I can't reproduce it on my device.
And can someone give feedback for the latest testbuilds featuring userspace lmkd? I'd really appreciate it.
Certification Status on 17.1
Hi,
I am currently on LineageOS 16 and Play Store reports my device as "certified", which allows me to run Netflix, banking apps, etc.
Will this also be the case when updating to 17.1 with Pico Gapps wihtout tweaking / installing anything else?
Thanks!
Must sideload, not enough space to push and install from local, I feel silly...
Aargh. Grrr. (Angry at myself. I was being stupid).
The reason why even the pico package "didn't fit" is that I'd pushed it to the device and was trying to install it locally, which (of course, in retrospect, despite there being plenty of other space on other partitions) used up some of the precious free space on /system .. for a thing that needed space to install on /system.
I deleted the local copy of the .ZIP file and sideloaded it, and it fit.
Aargh. Grrr.
Aside from my own self-stupidity, I did notice one thing that might be of interest to someone: The FlameGapps package installer refused to continue, stating that the package was built for Android 10 but this device is running (blank).
Anyway, many thanks!
-Jay
115ek said:
Last time I tried it worked. But you're right - the available space on /system is very rare. I already made some "hacks" to free up some space. You could try to overcome this by installing an older pico gapps package from here which is smaller. It'll update itself if you connect to a wifi network anyway.
Another thing you could try is using FlameGapps. The final thing would be resizing the /system partition.
Is anyone else experiencing this issue? I can't reproduce it on my device.
And can someone give feedback for the latest testbuilds featuring userspace lmkd? I'd really appreciate it.
Click to expand...
Click to collapse
zappbrannigan62 said:
Hi,
I am currently on LineageOS 16 and Play Store reports my device as "certified", which allows me to run Netflix, banking apps, etc.
Will this also be the case when updating to 17.1 with Pico Gapps wihtout tweaking / installing anything else?
Thanks!
Click to expand...
Click to collapse
I don't use gapps on my own. But play certification is a mystery sometimes. However, as nobody complained until now (and I guess most users install gapps...) it should be okay. Maybe someone can verify this.
Hello there. I am currently using the latest version of LOS 17.1. There is no problem throughout the system, but when I try to use one application, the phone resets itself. While opening the application, it stays on the white screen and the phone is reset. Application;
https://play.google.com/store/apps/details?id=com.garanti.cepsubesi&hl=tr
didyou said:
Hello there. I am currently using the latest version of LOS 17.1. There is no problem throughout the system, but when I try to use one application, the phone resets itself. While opening the application, it stays on the white screen and the phone is reset. Application;
https://play.google.com/store/apps/details?id=com.garanti.cepsubesi&hl=tr
Click to expand...
Click to collapse
Have you installed Gapps or MicroG on your system ?
Cerealekillers said:
Have you installed Gapps or MicroG on your system ?
Click to expand...
Click to collapse
Yes, installed pico GAPPS.
Works
115ek said:
I don't use gapps on my own. But play certification is a mystery sometimes. However, as nobody complained until now (and I guess most users install gapps...) it should be okay. Maybe someone can verify this.
Click to expand...
Click to collapse
I flashed the latest nightly + pico gapps using TWRP and
everything is working beautifully
Playstore reports the device to be certified
So thanks a lot!
libove said:
Aargh. Grrr. (Angry at myself. I was being stupid).
The reason why even the pico package "didn't fit" is that I'd pushed it to the device and was trying to install it locally, which (of course, in retrospect, despite there being plenty of other space on other partitions) used up some of the precious free space on /system .. for a thing that needed space to install on /system.
I deleted the local copy of the .ZIP file and sideloaded it, and it fit.
Aargh. Grrr.
Aside from my own self-stupidity, I did notice one thing that might be of interest to someone: The FlameGapps package installer refused to continue, stating that the package was built for Android 10 but this device is running (blank).
Anyway, many thanks!
-Jay
Click to expand...
Click to collapse
115ek said:
I don't use gapps on my own. But play certification is a mystery sometimes. However, as nobody complained until now (and I guess most users install gapps...) it should be okay. Maybe someone can verify this.
Click to expand...
Click to collapse
Can verify that my Play Store, on 17.1, reports my ridiculously modded Swift as certified without having to do anything to achieve that.
Sorry, I know I am a real dunderhead when it comes to these things and I apologise for such a basic question. But...
I have a Swift 2 X which is working on Oreo. If I replace this with LineageOS 17 do I have to do anything "fancy" to get Google Pay to work after I've installed LineageOS?
I've installed LineageOS on my Oppo R5 which doesn't have NFC so this can't use "Tap 'n' Pay" anyway. I've installed LineageOS on mine and my Wife's Nextbit Robin and Google Pay - "Tap 'n' Pay" - worked without doing anything more than install and go.
It's just that I do really like the facility of Google Pay and wouldn't want to lose that just for the sake of system wide dark mode.
Sorry again for being so dense as to not understand.
First update since installing Lineageos on Lenovo P2.
The navigation bar along the bottom disappeared. Couldn't be swiped up - had been fixed previously.
Then found other things as well. Fingerprint sensor not working. Pixel launcher failing. Had been using Nova launcher and foolishly removed it thinking I'd reinstall to see if it restored the nav bar. But now stuck with a failing launcher and can't start anything - including Play to reinstall Nova. Just says 'Pixel Launcher keeps stopping, App info, Close App.' Cleared cache from App info as that was all I could do but no difference.
I haven't read it anywhere but are updates cumulative? Ie, can I skip one if I miss it and get all updates rolled up into the next one. I hope so because that's what I did. Jumped from something like 9th August to 30th.
Any ideas?
Current update always include codes from previous builds so you can skip nightlies in between. There are few solutions for your problem. I'm telling you two:
1. Install a third party launcher apk through system settings
2. Reboot into TWRP, wipe system only and install latest update package with nano gApps and it should work.
alirazaagha said:
Current update always include codes from previous builds so you can skip nightlies in between. There are few solutions for your problem. I'm telling you two:
1. Install a third party launcher apk through system settings
2. Reboot into TWRP, wipe system only and install latest update package with nano gApps and it should work.
Click to expand...
Click to collapse
Thanks so much for your help. In fact, while trying your first suggestion I somehow got into Google Play through APK install settings from where I was able to reinstall Nova Launcher. So now I have a partly useable phone again but still with the problems that followed the update in my OP (navigation bar gone, fingerprint sensor stopped working plus the failing launcher - those are just the things I found without looking).
It's disappointing that the update failed though, not least as staying updated was a major reason for moving to Lineage. Any ideas why this might be?
Maybe I should try the second suggestion and reinstall the update by sideloading as described here. So do I use the same file that I use to install LineageOS in the first place from here https://download.lineageos.org/kuntao? It's not stated in the document. And will this wipe the phone clean again?
Finally would I have to re-sideload a GApps package at the same time and should it be Nano GApps as suggested? Originally I installed Open GApps as suggested in the upgrade instructions.
bind00 said:
Thanks so much for your help. In fact, while trying your first suggestion I somehow got into Google Play through APK install settings from where I was able to reinstall Nova Launcher. So now I have a partly useable phone again but still with the problems that followed the update in my OP (navigation bar gone, fingerprint sensor stopped working plus the failing launcher - those are just the things I found without looking).
It's disappointing that the update failed though, not least as staying updated was a major reason for moving to Lineage. Any ideas why this might be?
Maybe I should try the second suggestion and reinstall the update by sideloading as described here. So do I use the same file that I use to install LineageOS in the first place from here https://download.lineageos.org/kuntao? It's not stated in the document. And will this wipe the phone clean again?
Finally would I have to re-sideload a GApps package at the same time and should it be Nano GApps as suggested? Originally I installed Open GApps as suggested in the upgrade instructions.
Click to expand...
Click to collapse
The Pixel launcher in Android 10 force closes if it is not chosen as "Recents provider". Therefore, navigation bar also stops working. Hence, we need Quickswitch app to choose Pixel or any other launcher such as Lawnchair for giving them the mentioned right and that works without any hiccups.
You should install the latest update after wiping system only. You don't need to wipe everything, just wipe system partition.
Nano GApps are taken from Open Gapps website. I've suggested nano GApps because it doesnt include Pixel Launcher hence, stock ROM launcher will flawlessly work. However, if you want to use Pixel Launcher then install Magisk from recovery and Quickswitch module within Magisk. Then open Quickswitch app from launcher and click Pixel Launcher. Quickswitch app will process for a few moments and will restart your phone. Now, choose Pixel launcher as default from settings if it is not used as default and Done.
alirazaagha said:
The Pixel launcher in Android 10 force closes if it is not chosen as "Recents provider". Therefore, navigation bar also stops working. Hence, we need Quickswitch app to choose Pixel or any other launcher such as Lawnchair for giving them the mentioned right and that works without any hiccups.
You should install the latest update after wiping system only. You don't need to wipe everything, just wipe system partition.
Nano GApps are taken from Open Gapps website. I've suggested nano GApps because it doesnt include Pixel Launcher hence, stock ROM launcher will flawlessly work. However, if you want to use Pixel Launcher then install Magisk from recovery and Quickswitch module within Magisk. Then open Quickswitch app from launcher and click Pixel Launcher. Quickswitch app will process for a few moments and will restart your phone. Now, choose Pixel launcher as default from settings if it is not used as default and Done.
Click to expand...
Click to collapse
Many thanks again for your detailed help. Much appreciated.
Went for standard Open GApps just because that's what I had before and had hoped to get it all back as it was. (I've no particular preference for Pixel only that was all that was available to me after updating through updater. ) I've got the update loaded now, sideloaded with adb and TWRP. Unfortunately I seem to have accidentally factory reset from TWRP (thought I was just swiping to unlock and only noticed too late. Doh.)
TBH, this has been a whole lot of hassle for an update. After hours to get this far now have to set phone up from scratch yet again. And crucially, I still don't know why updater failed. Going to be very nervous about running update in future and staying updated was the main point of moving to Lineage in the first place.
But thanks for help again.
bind00 said:
Many thanks again for your detailed help. Much appreciated.
Went for standard Open GApps just because that's what I had before and had hoped to get it all back as it was. (I've no particular preference for Pixel only that was all that was available to me after updating through updater. ) I've got the update loaded now, sideloaded with adb and TWRP. Unfortunately I seem to have accidentally factory reset from TWRP (thought I was just swiping to unlock and only noticed too late. Doh.)
TBH, this has been a whole lot of hassle for an update. After hours to get this far now have to set phone up from scratch yet again. And crucially, I still don't know why updater failed. Going to be very nervous about running update in future and staying updated was the main point of moving to Lineage in the first place.
But thanks for help again.
Click to expand...
Click to collapse
No problem bro. Next time, when you update, follow these things:
1. Keep ROM, Magisk and GApps in a single folder.
2. When updating ROM, just install the ROM and restart.
alirazaagha said:
No problem bro. Next time, when you update, follow these things:
1. Keep ROM, Magisk and GApps in a single folder.
2. When updating ROM, just install the ROM and restart.
Click to expand...
Click to collapse
Thanks again. That's good information. So you recommend not using the Updater but adb sideloading instead?
OK, and I just read this at stackexchange "You normally don't need to re-flash GApps as most GApps installers will install an addon.d script which restores GApps automatically after flashing a new ROM that supports addon.d (LineageOS does so)." So if GApps is in the same folder it finds it automatically I guess.
I'd better clue myself up on Magisk now and a decent backup system.
cheers
bind00 said:
Thanks again. That's good information. So you recommend not using the Updater but adb sideloading instead?
OK, and I just read this at stackexchange "You normally don't need to re-flash GApps as most GApps installers will install an addon.d script which restores GApps automatically after flashing a new ROM that supports addon.d (LineageOS does so)." So if GApps is in the same folder it finds it automatically I guess.
I'd better clue myself up on Magisk now and a decent backup system.
cheers
Click to expand...
Click to collapse
Built in update works as required but if it messes with system partition then you better download update and install it through recovery.
GApps can be restored after update but the point is that you don't need it. System update only replaces the older system files with new ones without touching gApps files. Whereas, Magisk is automatically installed after update if it's in the same folder.