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.
Related
Hello, first of all I'd like to apologise if this is not the correct forum to ask about this.
Essentially, I have CM12 on my i9195, it worked perfectly fine for a period of time, but for some reason I am unable to install 3rd-party (non-play store) apps.
I am running the newest (20150206) nightly, and I have unknown sources enabled.
Furthermore, I've already done my fair share of googling, and no I am not using any kind of screen filter app, and I have sufficient memory.
Whenever I attempt to install an apk, it just comes up with 'app not installed' - nothing more.
I have also attempted to install through the terminal (using pm install /storage/emulated/0/Download/app.apk), which resulted in 'Failure [INSTALL_FAILED_DEXOPT]'.
I am completely new to any sort of android related things, so I have no clue how to solve this.
I'd be grateful if someone was able to help me out here.
Cheers
What app were you trying to install.
Usually the error occurs when the package name of the app u are trying to install is same as a preinstalled system app.
I was attempting to install a modded version of Snapchat (without installing any other version of it before).
Only thing that I came up with was moving the apk to its folder in system/app/.
However, the error comes up with with any other app as well, and to say the least moving the apps each time and changing the permissions is slightly inconvenient.
MedzikPL said:
I was attempting to install a modded version of Snapchat (without installing any other version of it before).
Only thing that I came up with was moving the apk to its folder in system/app/.
However, the error comes up with with any other app as well, and to say the least moving the apps each time and changing the permissions is slightly inconvenient.
Click to expand...
Click to collapse
Try recovery and clearing cache and dalvik. Then when you boot up do nothing but make sure allow unknown sources is ticked, then go to filemanager and just install?
There could also be a problem with the modded snapchat version. Try redowning and older or newer version to see if that works.
Cheers,
Sora.
SORAnoDYStopia said:
Try recovery and clearing cache and dalvik. Then when you boot up do nothing but make sure allow unknown sources is ticked, then go to filemanager and just install?
There could also be a problem with the modded snapchat version. Try redowning and older or newer version to see if that works.
Cheers,
Sora.
Click to expand...
Click to collapse
I really hoped it wouldn't come to that, but I did to a full format, which did not help at all.
It is an issue with not only snapchat, but all of the 3rd apps I tried to install.
I guess it might just be an issue with the ART runtime or something, and for now I'll just be converting essential 3rd parties to system apps.
@MedzikPL Did you try to install those apks on other roms. To see if they are working there. That points towards cm12. Which nightly are you running. I will flash cm12 today and i will try to reproduce the problem you are facing. Also give me link to snapchat download.
Very strange. Well I'm on latest nightly and all my 3rd party apps install fine. Can't be runtime. Please post a link to the nodded Snapchat and I will give it a go.
Sora.
SORAnoDYStopia said:
Very strange. Well I'm on latest nightly and all my 3rd party apps install fine. Can't be runtime. Please post a link to the nodded Snapchat and I will give it a go.
Sora.
Click to expand...
Click to collapse
http://forum.xda-developers.com/android/apps-games/app-mod-snapmod-modified-snapchat-apk-t3006522
This is the mod, but as I said earlier I am generally unable to install non play store apps through the built-in installer.
Simultaneously, I did manage to get them to work by putting them in /system/app/ though, and they run just fine as I can tell.
After 20150208-NIGHTLY I am able to install apps, thread is for closure
MedzikPL said:
After 20150208-NIGHTLY I am able to install apps, thread is for closure
Click to expand...
Click to collapse
Glad its fixed.
Sora.
Hi i have samsung galaxy j5 oof it has android lollipop whenever i try to install any modded apk like asphalt 8 airbone or any other it start inatalling but after few second it say app not installed.i have even rooted my phone
Hey guys,
I've done some searching around on this issue, and it looks like Snapchat is not allowing me to login as my device is rooted. However, I had the factory OxygenOS ROM (rooted as well) installed before and never had this issue. Now that I have installed Sultanxda's "Unofficial CyanogenMod 13.0 with custom kernel", I can no longer get Snapchat to login. Like I said, from the searching that I've done it look like it is root related, so I went into SuperSU and did a complete unroot. This still hasn't solved the issue yet, so now I'm stuck and not sure what to do. Is there something I'm missing or is there a way to solve this without having to reflash a different ROM and loose all the time spent setting this one up?
Thanks for the help!
saleenman95 said:
Hey guys,
I've done some searching around on this issue, and it looks like Snapchat is not allowing me to login as my device is rooted. However, I had the factory OxygenOS ROM (rooted as well) installed before and never had this issue. Now that I have installed Sultanxda's "Unofficial CyanogenMod 13.0 with custom kernel", I can no longer get Snapchat to login. Like I said, from the searching that I've done it look like it is root related, so I went into SuperSU and did a complete unroot. This still hasn't solved the issue yet, so now I'm stuck and not sure what to do. Is there something I'm missing or is there a way to solve this without having to reflash a different ROM and loose all the time spent setting this one up?
Thanks for the help!
Click to expand...
Click to collapse
Hi, the searching can be useful sometimes
http://forum.xda-developers.com/search/forum/5476?query=snapchat
You need an fully unrooted rom to login into snapchat, after that you can flash supersu.
NevaX1 said:
Hi, the searching can be useful sometimes
http://forum.xda-developers.com/search/forum/5476?query=snapchat
You need an fully unrooted rom to login into snapchat, after that you can flash supersu.
Click to expand...
Click to collapse
Ah, looks like I just didn't search enough. This seems to have done the trick, thanks!
I think you just need to uninstall Xposed Framework for Snapchat to login and then after login you can install Xposed again.
This sounds weird but what worked for me was to download superkiwi via xposed installer, it's supposed to bypass root detection for banking apps in New Zealand but works with snapchat [emoji14]
I found this workaround in a thread somewhere and thought that it wouldn't hurt to try but actually works mighty fine!
Sent from my ONEPLUS A3003 using Tapatalk
Leaving this here in the hopes it helps someone else, took me a bit to find the correct steps.
Currently running the last official CM 13 build for the Droid Turbo (will be moving to LOS soon), rooted with SuperSU Pro, Xposed framework v87, on the newest TWRP.
Nothing worked, not Xposed Switch, Root Switch, nothing. In fact I had to reinstall Xposed Switch to be able to turn root back on, while Root Switch simply uninstalled the SuperSU binary, I had to reflash it. Finally I put it all together and in the following order I got Snapchat to work.
Make sure any OS root (my case CMroot) was turned off.
Download the correct version of Xposed framework Installer, Xposed Uninstaller, and the SuperSU binary (all flashable zip files) for your device to a location on your system that you can easily access from recovery. For me its my TWRP folder.
Uninstall Snapchat. Open a File Explorer and delete the entire Snapchat folder left over.
Select the uninstall "permanently unroot" option from SuperSU, but DON'T let it install the original... Whatever it is, the name escapes me. But don't let it!
Phone will reboot automatically after taking out root, boot to recovery, run Xposed Uninstaller, wipe Cache & Dalvik, reboot phone.
When the phone boots, confirm it is unrooted and Xposed Framework is uninstalled. A root checker app and opening the Xposed App worked for me here.
Install Snapchat, sign into Snapchat. It will accept your login if you did everything correctly.
*This step I did to save myself work in the future, but you can do it later. Turned on CMroot and took a TiBackup of logged in Snapchat in case I ever have to login again, I can just reload the data.*
Boot to recovery. Flash the Xposed framework and the SuperSU binary (in that order), wipe Cache and Dalvik, reboot system.
Open Snapchat to confirm its still logged in. If so grab a TiBack of it for use as needed later.
I hope this helps!
Sent from my DROID Turbo using XDA-Developers Legacy app
Hi there. Has anybody built a ROM with the following specs?
- based on stock 14.6.A.1.236 (android 5.1.1)
- pre-rooted
- all security patches added, e.g. patches for those 10 critical bugs that have just been fixed
It is not stock but aosp: https://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/rom-jaguar-amami-lp5-1-1-r37-hardened-t3396713
In Jaguar you get all the patches within 1 or 2 days. I am using it atm.
Alright, I just switched to Jaguar.
But it wasn't easy. Dual recovery with Philz & TWRP 2.8.x defended itself very persistently. Installing TWRP 3.0.2 had no effect - neither in recovery partition nor in FOTA kernel. Even the uninstall zip of dual recovery couldn't wipe TWRP 2.8.x, although the script said it had run successfully. So I kept installing images into different partitions in fastboot mode (which was the only mode that kept working all the time). In the end TWRP 3.0.2 suddenly appeared after 3 hours.
In Jaguar it was also a bit fiddling to get AFWall+ working. Optimumpro's dowload has a rather old version, which kept blocking all traffic. But after removing it and installing the current v2.9.1 it worked. Now I've installed all apps I need. Everything seems to work except for Gmail. That one always crashes on start. Its background process also steadily crashes, so every other minute I see a popup that tells me "Unfortunately, Gmail has stopped". Clearing cache and data has not solved the problem. Stopping sync had no effect either. Maybe re-installing the gapps.zip in TWRP will help...
I also had problems to install TWRP 3.0.2 persistantly. My solution was to install Philz TWRP 2.8 and inside TWRP 2.8 I flashed 3.0.2. After that only 3.0.2 TWRP was available.
OptimusPro pointed out that Internet is only working if you allow apps in AFWall.
I switched AFWall+ from white-listing to black-listing and put nothing on the list, so currently everything can access the internet. And that's also what I tried in the older version of AFWall+, but it didn't work there.
One more question: where did you find the zip (for installation in recovery) of TWRP 3.0.2? I can only find img files for installation with fastboot.
I think in optimuspro version he disabled it?
you do not need a zip. In TWRP 2.8 go to INSTALL and there should be a button "Install Image" Then you can load and flash an img file.
Oh, I didn't know that you can flash img files in some recoveries. However the only partition I can select in TWRP for installation is /boot. Well, I proceed with the installation just for the fun of it... (some minutes later)... and yes, it has really overwritten /boot. That's not where a recovery belongs.
Anyway, now I can hopefully solve my problems. I use a lot of Google applications, but I guess I took a package that overwrote some files in /system that are not compatible with the rest of optimuspro's ROM. So I just flash everything again, but this time with a smaller gapps package. Let's give "micro" a try...
edit: No, that was not the solution. Gmail is still crashing.
Which opengapps version are you using?
I use arm, 5.1, pico. And then I just download the gapps from the play store.
I do not have gmail account, so I cannot test gmail. It is strange that it is not working. I meand it is just a mail app or is it so deep diving in the system?
First I tried gapps "stock". Now I see that this package was too big, because it not only installed a bunch of apps I don't need, it also removed SlimPie launcher, the camera app, and the mail app that comes with Jaguar. I guess it also removed some more apps... probably every app that could be replaced by a Google app.
Now in the 2nd run I used gapps "micro". It looks like none of the Jaguar apps have been removed. Gmail still came with the gapps package, but now it has been installed side by side with the mail app that comes with Jaguar. The same for the launcher. And of course I had to install some apps in play store (e.g. maps), which were not included in the package.
Well, I'm not sure if I like the Jaguar ROM. Sure it has the right priorities. But aside from gmail I might have found some more problems. I installed Automate in order to automatically turn on/off wifi when coming home/leaving home. Turning wifi off (and using cellular data) works fine, but when coming home and wifi is being enabled AFWall+ blocks wifi traffic. So far I could manage to unblock wifi only by activating/deactivating airplane mode (or rebooting of course). And there might be problems with WhatsApp as well. Sometimes I don't receive messages until WhatsApp has been opened. Maybe the background process doesn't run or it is not able to receive data, even over wifi. Maybe AFWall+ is blocking traffic again... or some security defaults are blocking WhatsApp. I don't know. Threema doesn't seem to have the same problems, it works very well on Jaguar.
Whats App is working for me withour problems. And AFWall+ runs normal.
But yeah, I would say that custom roms are always trickier than stock roms. But for me Jaguar is the only rom where I can say, that I am on best security level. So I can live with the issues I have.
I realized that I need to do the gps fix which is mentioned in th main thread.
I have had a problem loading Android Auto (AA) on my LG G4. I have rooted with Steadfaster's UsU and installed his Lineage 15.1 rom, opengapps nano (Sept 30) and the phone is working great. Prior to rooting the phone AA worked fine with MM 6.0. After rooting the phone, when I open the AA app on the phone I get the error "Something went wrong. Google play services doesn't seem to be working right now". The error comes up immediately and then the app closes. I tried plugged into in the car as well (Pioneer AVIC 4200 deck), but the error stops the phone when opened.
I have been through Google's forums and there have been lots of posts about this error and no real solutions for me posted. I have also tried other "fixes" I have come across, including this one - https://forum.xda-developers.com/android/help/delete-disable-downgrade-prevent-update-t3091832/. This method involves:
1. Download and install System App Remover from the Google Play Store.
2. Put your device in Airplane Mode in order to prevent auto upgrade of GPS.
3. Open System App Remover and select "System App" from the menu.
4. Find Google Play Services in the list. It should be marked "Should keep", which is a suggestion from the publisher. Select it and press "Uninstall". Ignore completion message.
5. Using Settings/Apps, verify that Google Play Services has reverted to the factory-supplied version. It should be <7. "Force Stop", "Uninstall Updates", and "Disable" buttons should no longer be grayed out.
7. Reboot device and toggle Airplane Mode off.
I followed these steps, but unfortunately stock seems to be the version that came with opengapps which is current.
I'm out of ideas with this problem and need some help. AA is a great app for me and really handy on long trips. I would like to get it running if at all possible.
Appreciate any help you can provide.
jjcdennis said:
I have had a problem loading Android Auto (AA) on my LG G4. I have rooted with Steadfaster's UsU and installed his Lineage 15.1 rom, opengapps nano (Sept 30) and the phone is working great. Prior to rooting the phone AA worked fine with MM 6.0. After rooting the phone, when I open the AA app on the phone I get the error "Something went wrong. Google play services doesn't seem to be working right now". The error comes up immediately and then the app closes. I tried plugged into in the car as well (Pioneer AVIC 4200 deck), but the error stops the phone when opened.
I have been through Google's forums and there have been lots of posts about this error and no real solutions for me posted. I have also tried other "fixes" I have come across, including this one - https://forum.xda-developers.com/android/help/delete-disable-downgrade-prevent-update-t3091832/. This method involves:
1. Download and install System App Remover from the Google Play Store.
2. Put your device in Airplane Mode in order to prevent auto upgrade of GPS.
3. Open System App Remover and select "System App" from the menu.
4. Find Google Play Services in the list. It should be marked "Should keep", which is a suggestion from the publisher. Select it and press "Uninstall". Ignore completion message.
5. Using Settings/Apps, verify that Google Play Services has reverted to the factory-supplied version. It should be <7. "Force Stop", "Uninstall Updates", and "Disable" buttons should no longer be grayed out.
7. Reboot device and toggle Airplane Mode off.
I followed these steps, but unfortunately stock seems to be the version that came with opengapps which is current.
I'm out of ideas with this problem and need some help. AA is a great app for me and really handy on long trips. I would like to get it running if at all possible.
Appreciate any help you can provide.
Click to expand...
Click to collapse
Even when it sounds obvious but have you installed AA clean so without restoring data from a backup? Do you have tried to completely factory reset the phone? Do you have tried to format data in TWRP? Obviously you should have a backup of your internal storage when doing so .
You should also catch a logcat when starting the app
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Even when it sounds obvious but have you installed AA clean so without restoring data from a backup? Do you have tried to completely factory reset the phone? Do you have tried to format data in TWRP? Obviously you should have a backup of your internal storage when doing so .
You should also catch a logcat when starting the app
After rooting with UsU I followed sdembiske's recommendations for installing Lineage. This included a factory reset and formatting data with TWRP. I then installed Lineage 15.1 UsU and opengapps nano and then installed the apps I wanted. AA went on clean without restoring data. I will capture a logcat and post.
Thanks
Click to expand...
Click to collapse
steadfasterX said:
Even when it sounds obvious but have you installed AA clean so without restoring data from a backup? Do you have tried to completely factory reset the phone? Do you have tried to format data in TWRP? Obviously you should have a backup of your internal storage when doing so .
You should also catch a logcat when starting the app
After rooting with UsU I followed sdembiske's recommendations for installing Lineage. This included a factory reset and formatting data with TWRP. I then installed Lineage 15.1 UsU and opengapps nano and then installed the apps I wanted. AA went on clean without restoring data. It never opened without the error I titled this thread with.
My first attempt at a logcat. I searched in Notepad++ and used carservice as the keyword. Some errors were shown. I don't know how to interpret them and would appreciate your help
Thanks
Click to expand...
Click to collapse
jjcdennis said:
steadfasterX said:
Even when it sounds obvious but have you installed AA clean so without restoring data from a backup? Do you have tried to completely factory reset the phone? Do you have tried to format data in TWRP? Obviously you should have a backup of your internal storage when doing so .
You should also catch a logcat when starting the app
After rooting with UsU I followed sdembiske's recommendations for installing Lineage. This included a factory reset and formatting data with TWRP. I then installed Lineage 15.1 UsU and opengapps nano and then installed the apps I wanted. AA went on clean without restoring data. It never opened without the error I titled this thread with.
My first attempt at a logcat. I searched in Notepad++ and used carservice as the keyword. Some errors were shown. I don't know how to interpret them and would appreciate your help
Thanks
Click to expand...
Click to collapse
I just searched a bit regarding the errors of your logcat and found this:
https://productforums.google.com/forum/#!topic/nexus/-N8jJo7A8nI
maybe something there helps you out.
It seems definitively an issue with google play app/updates..
btw: I have just installed AA here without an issue, running LOS 15.1 on my h815..
.
Click to expand...
Click to collapse
steadfasterX said:
jjcdennis said:
I just searched a bit regarding the errors of your logcat and found this:
https://productforums.google.com/forum/#!topic/nexus/-N8jJo7A8nI
maybe something there helps you out.
It seems definitively an issue with google play app/updates..
btw: I have just installed AA here without an issue, running LOS 15.1 on my h815..
.
Click to expand...
Click to collapse
I have been through that forum and tried the last post just now - uninstall updates, clear cache, open AA - and I immediately get the error.
I'm thinking about doing a Titanium backup on apps and data (minus AA) then wipe, reinstall LOS 15.2, TWRP, Lineage SU, do a reboot, reinstall AA first and if it works then run Titanium restore for apps and data.
Make sense?
Click to expand...
Click to collapse
jjcdennis said:
steadfasterX said:
I have been through that forum and tried the last post just now - uninstall updates, clear cache, open AA - and I immediately get the error.
I'm thinking about doing a Titanium backup on apps and data (minus AA) then wipe, reinstall LOS 15.2, TWRP, Lineage SU, do a reboot, reinstall AA first and if it works then run Titanium restore for apps and data.
Make sense?
Click to expand...
Click to collapse
Sounds like a plan
Nevertheless I would to a titanium backup of play and AA BEFORE restoring as well..
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
steadfasterX said:
jjcdennis said:
Sounds like a plan
Nevertheless I would to a titanium backup of play and AA BEFORE restoring as well..
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Well I wiped cache, Dalvik, system and then formatted data, installed the 15.1 UsU rom, then installed Gapps, rebooted to recovery and installed the Lineage addonsu. I rebooted, went through setup and the first thing I did was open the Playstore install Android Auto and run it - immediate error again. Also the addonsu did not root the phone. And to top it all I did not disable the pin code.
Back to the drawing board.
Click to expand...
Click to collapse
steadfasterX said:
jjcdennis said:
btw: I have just installed AA here without an issue, running LOS 15.1 on my h815..
.
Click to expand...
Click to collapse
I have been beating the bushes and looking for a solution. None so far. You mention AA worked on your phone. Are you running LOS 15.1 and if no, which rom? Also re your install can you look in apps and notifications and see if the more options * is shown on the AA app. I have it, but when I select it nothing happens. My old Nexus 5 the * works and Android Auto opens no problem. LOS 7.1.2.
Thanks
Click to expand...
Click to collapse
jjcdennis said:
steadfasterX said:
I have been beating the bushes and looking for a solution. None so far. You mention AA worked on your phone. Are you running LOS 15.1 and if no, which rom? Also re your install can you look in apps and notifications and see if the more options * is shown on the AA app. I have it, but when I select it nothing happens. My old Nexus 5 the * works and Android Auto opens no problem. LOS 7.1.2.
Thanks
Click to expand...
Click to collapse
I run LOS 15.1 build 20181002 and at the time of installing that ROM version I used this opengapps version: open_gapps-arm64-8.1-nano-20180705.zip (download)
AA works here yes. I run it now for several days, daily, no issues here.
My version of AA is 3.7.584044 (attached: View attachment com.google.android.projection.gearhead-ffadc269cc39417e152ffcdd22183045.apk)
Not sure what you mean by "the more options *" but I've attached 2 screenshots of the app settings which may show what you meant.. if not show a pic of that setting.
oh you may meant the gear symbol at the top right? Here it opens fine but as that opens google stuff it makes sense that it fails on yours
.
Click to expand...
Click to collapse
Isn't mine basically the same as yours, other than H815? That gear icon will not open up the more options page. On my Nexus 5 with LOS 7.1.2 it opens a page with Settings for AA ie: Limit wifi, Connected cars, phone screen settings, etc.
If not the same maybe I should run your version of LOS.
jjcdennis said:
Isn't mine basically the same as yours, other than H815? That gear icon will not open up the more options page. On my Nexus 5 with LOS 7.1.2 it opens a page with Settings for AA ie: Limit wifi, Connected cars, phone screen settings, etc.
If not the same maybe I should run your version of LOS.
Click to expand...
Click to collapse
I've mentioned and linked the opengapps version, attached the AA version and mentioned the exact build for a reason yes.
The idea was that you try the exact same setup.
btw: which model do you have?
.-
steadfasterX said:
I've mentioned and linked the opengapps version, attached the AA version and mentioned the exact build for a reason yes.
The idea was that you try the exact same setup.
btw: which model do you have?
.-
Click to expand...
Click to collapse
H812 on the UsU Oreo build H812 build.
So I can copy what you have, other than I'm using the H812 versus the H815 LOS rom.
Thanks steadfasterX
steadfasterX, is it necessary that I format the data when I reload this rom. Takes a long time to restore everything.
jjcdennis said:
steadfasterX, is it necessary that I format the data when I reload this rom. Takes a long time to restore everything.
Click to expand...
Click to collapse
Use my latest preview version of TWRP then you can backup your data AND internal storage . you can first try without format. if you still have issues try to format it and if it doesn't fix anything you can restore by TWRP but ensure that you use build 144 or higher
Sent from my LG-H815 using XDA Labs
OK, thanks again. Will give it a go. I have your latest TWRP, 144_g4_0.
On the positive side after all kinds of failed troubleshooting my G4 has all of a sudden decided to connect with my PC. It shows as H812 in Explorer and in Device Manager as Lemobile Android Device with Android Composite ADB Device driver. A lot easier than using Cloud.
jjcdennis said:
OK, thanks again. Will give it a go. I have your latest TWRP, 144_g4_0.
On the positive side after all kinds of failed troubleshooting my G4 has all of a sudden decided to connect with my PC. It shows as H812 in Explorer and in Device Manager as Lemobile Android Device with Android Composite ADB Device driver. A lot easier than using Cloud.
Click to expand...
Click to collapse
Gave it a go, but as soon as I tapped on AA the error came up. I did format data to start from clean and used the older versions of AA and Google Play.
Update - I reinstalled all my apps via Titanium Pro (not AA) and set things up. I decided to tryy AA one more time before removing it and bingo it opened. Kinda waking on broken glass here and unsure whether or not the app will continue to function. Hooefully this fixed things.
Thanks again steadfasterX.
Requirements:
- Stock Clean Firmware: https://mirrors.lolinet.com/firmware/moto/kane/official/
- TWRP: https://forum.xda-developers.com/one-vision/how-to/twrp-3-3-1-0-root-updated-kane-troika-t4102839
- GSI ROM (arm64, A/B versions): https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
- Permissiver_V5 Flashable Zip: https://androidfilehost.com/?fid=6006931924117940902
- Google Play Services APK - Whenever you boot into a GSI the first thing you should do is install the Google Play Services APK. Installing it will clear the "System Updating..." notification and you will be able to login to your Google account.
Google Play Services for Android 9 GSI: https://www.apkmirror.com/apk/googl...-24-13-100400-316577029-android-apk-download/
Google Play Services for Android 10 GSI: https://www.apkmirror.com/apk/googl...-24-13-120400-316577029-android-apk-download/
Instructions:
- Flash Stock firmware
- Wipe system and data in TWRP
- Reboot to bootloader
- Run the following command in the command line:
Code:
fastboot flash system [yourGSI.img]
- While still in fastboot mode run:
Code:
fastboot -w
- Reboot to TWRP and flash Permissiver_V5 zip file
- Reboot to the system
Notes:
Look at the size of the downloaded GSI.img file (Not the zip file), If it's larger than 3GB you won't be able to flash it because the system partition is limited to 3GB)
Permissiver_V5 is required for some GSI to successfully boot, some of GSIs might work without it but if you don't flash it and the GSI doesn't boot that might be the main problem.
GSI ROMs might have some bugs, the most known bug at least on One Vision and maybe Action is the Bluetooth Freeze Bug that might happen when you try to play music over Bluetooth. Be prepared for anything.
Not every GSI will successfully boot. Some of them might not boot but don't worry as there are a lot of GSIs for you to try on.
Same procedure works for both One Action and One Vision
FAQ:
Do I need to flash GAPPS after I install an GSI?
No. Flashing GAPPS is an optional step, most of the GSIs might already come with GAPPS installed and all you have to do to enjoy your ROM is to install the Google Play Services apk mentioned in my post.
You must install GAPPS if the GSI you're using doesn't have the Google Play Store app and you want to install any apps from the Play Store, but even then there are alternatives to install Play Store apps even without installing any GAPPS package
After installing a GSI my phone it's stuck in a bootloop, what do I do?
The main reason for your android not booting up is that some vendors enforce SELinux which stops GSIs from booting and the fix for that is by flashing the Permissiver_V5 zip file to be able to boot into GSI.
But if you can't boot even after you flashed Permissiver_V5, you either downloaded the wrong GSI or the GSI isn't compatible with your device so you have to find another GSI to flash. Remember that not every GSI can successfully boot.
The X GSI has the Y problem! How do I fix it?
Even after your GSI finished booting there's no guarantee that everything will work as it should. The best thing you can do is to find support on google, or if the creator of the GSI has provided any contact links (Email, Telegram, etc) you can contact him and ask him if there's a fix for your problem or not.
This is something new for me, I was used to install rom and gapps, is this something similar?
simije97 said:
This is something new for me, I was used to install rom and gapps, is this something similar?
Click to expand...
Click to collapse
Flashing GAPPS is totally optional, GSIs will work even without flashing them. Most of them already have GAPPS installed, other might not work with GAPPS.
Is totally up to you if you want to flash GAPPS on a GSI, but as I said most of them don't need it, the most important thing to install after flashing a GSI is to install the Google Play Service to login into your Google account and fix any issues related to Android Setup
[Edit] I've added a small FAQ section to my post above
simije97 said:
This is something new for me, I was used to install rom and gapps, is this something similar?
Click to expand...
Click to collapse
There are 2 main reasons why you should install GAPPS:
1: The GSI you're flashing doesn't have any google apps and in that case to be able to login into a google account and install apps using Play Store you have to install a GAPPS package to have access to google play store
2: The GSI has access to PlayStore but you just want to have other apps like YouTube, Gmail installed in your system. In this case I myself, I prefer to install the Google apps that I need from play store rather than installing a GAPPS package that bloats my phone with apps I don't use.
Anyway, flashing GAPPS is totally optional and it's up to you if you want it or not.
The most important thing when installing a GSI is to look if it has any google apps, if yes then it's important to install Google Play Services apk listed in my post.
To give you a small example Google Experience comes with google apps included so you never have to install GAPPS. I'm using Google Experience and everything worked out of the box, it didn't require the Google Play Services but I guess I just got lucky.
This can't be said for when I've installed an Android 11 Pixel-based GSI, where I had to install the Google Play Services to be able to use my Google Account and finish the android setup.
After few weeks I decided to try this and it works just fine, thank you. Unfortunately ROMs are not created for that big hole on the screen. It hides time, notifications etc., otherwise it works pretty well.. Any sugestions how to repair it? Thank you again
Go to developer settings. You find notch settings.
rhaavin said:
Go to developer settings. You find notch settings.
Click to expand...
Click to collapse
I installed Descendant X, there are some options for notch, but it doesn't work for One Vision.
Put the apk attached in /system/overlay and it will correct the values for the punch hole. Don't forget to reboot after. Also I've made this a long time a go but I didn't had time to test it as I'm on Android 8 due to working on something.
Report back if it works or not thanks.
SnoopDoggyStyleDogg said:
Put the apk attached in /system/overlay and it will correct the values for the punch hole. Don't forget to reboot after. Also I've made this a long time a go but I didn't had time to test it as I'm on Android 8 due to working on something.
Report back if it works or not thanks.
Click to expand...
Click to collapse
Unfortunately, I had to install stock firmware because of my work and Google pay. I was trying to hide root but I was unsuccessful. Anyway, thank you very much for sharing this
I installed GSI ROM, I have been trying to root it for 3 hours. Can someone here tell me what to do?
[Q][RECOVERY][3.4.0-0][kane] Official TWRP & Root for Motorola One Vision
Root & TWRP 3.4.0 for Android 10. Page on the official TWRP website https://twrp.me/motorola/motorolaonevision.html Installation Instruction 1. Download twrp-3.4.0-0-kane.img and twrp-installer-3.4.0-0-kane.zip TWRP, patched vbmeta.img and...
forum.xda-developers.com
WellThisSucks1 said:
I installed GSI ROM, I have been trying to root it for 3 hours. Can someone here tell me what to do?
Click to expand...
Click to collapse
You can take the "Magisk-v20.x-phh.zip" for root
Magisk-v20.3-phh.zip | by shumway66 for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Should work
simije97 said:
Unfortunately, I had to install stock firmware because of my work and Google pay. I was trying to hide root but I was unsuccessful. Anyway, thank you very much for sharing this
Click to expand...
Click to collapse
This works
alphalog said:
This works
Click to expand...
Click to collapse
How do I make it work?
Como lo hago funcionar xd
ChriisTBv said:
How do I make it work?
Como lo hago funcionar xd
Click to expand...
Click to collapse
Copy the apk to system/vendor/overlay
and reboot
Thank you very much for continuing to support and improve this smartphone