I flashed lineageOS with gapps earlier today and camera keeps stopping, everything else is working fine, already cleared cache and data
You need to enable Camera API either directly via build.prop or using Magisk module (Lineage doesn't have it enabled by default)
I already got camera2api enabler module but it still crashes
Cheniz said:
I flashed lineageOS with gapps earlier today and camera keeps stopping, everything else is working fine, already cleared cache and data
Click to expand...
Click to collapse
Try nano gapps package or smaller if you haven't already.
Camera close too on aex with stock gapps
resident0915 said:
Try nano gapps package or smaller if you haven't already.
Click to expand...
Click to collapse
I flashed nano when i flashed my rom, should i try a smaller one?
Cheniz said:
I flashed nano when i flashed my rom, should i try a smaller one?
Click to expand...
Click to collapse
My was also force closing, then I flashed Full version of OpenGApps and everything is fine now.
Related
I had CM13 on my Nexus 4, which worked ok.
I updated my Nexus 4 from CM 13 to CM 14.1 ( Google 7.1 base)., an overwrite update. The phone is sane but not surprising the Google Apps including the playstore are dying. I assume I need to update the exisiting Gapps to 7.1 and further assume the OpenGapps 7.1 arm stock is the right one.
The Gapps 7.1 installer terminates for insufficient space. The Nexus 4 has a 828MB system partition with 237MB availalble. Although the log shows no existing Gapps, it finds about 180MB of items to remove but is still 481MB short of being able to do the installs.
I've tried excluding as much as I can in the Gapps flash, but I'm still about 280MB short. Is there anything I can do other than wiping the phone, repartitioning and starting CM14.1 from scratch?
OpenGApps Stock package is way too big for a successful install, use Pico one. Restore your CM13 backup (assuming you made one) and flash CM14.1 nightly and Gapps both at the same go without rebooting the device. In case you didn't made the backup, factory reset is needed before flashing.
n0b0dy666 said:
OpenGApps Stock package is way too big for a successful install, use Pico one. Restore your CM13 backup (assuming you made one) and flash CM14.1 nightly and Gapps both at the same go without rebooting the device. In case you didn't made the backup, factory reset is needed before flashing.
Click to expand...
Click to collapse
Thanks!
Actually since I didn't have a CM13 backup I just went and flashed pico on my CM14.1. It seems to have worked and solved the problem.
I also added GEL via the play store and have OK GOOGLE working too., as well as Google Calender and Youtube. I don't know what else I use that pico left out. I don't use the Google branded media and game apps.
I tried by flashing new rom, but it doesnt work. I wiped all the data except sd-card. My dialer is not working after encrypting.so I'm trying to decrypt my moto x play. But I couldn't. I use open gapps aroma package.at last I could not even install open gapps zip. It's flashing but when I reboot after flash , it would not be there
ViShNu ViZz said:
I tried by flashing new rom, but it doesnt work. I wiped all the data except sd-card. My dialer is not working after encrypting.so I'm trying to decrypt my moto x play. But I couldn't. I use open gapps aroma package.at last I could not even install open gapps zip. It's flashing but when I reboot after flash , it would not be there
Click to expand...
Click to collapse
If everything fails, flash stock rom with rsdlite
ViShNu ViZz said:
I tried by flashing new rom, but it doesnt work. I wiped all the data except sd-card. My dialer is not working after encrypting.so I'm trying to decrypt my moto x play. But I couldn't. I use open gapps aroma package.at last I could not even install open gapps zip. It's flashing but when I reboot after flash , it would not be there
Click to expand...
Click to collapse
Please mention everything in detail.
Hello everyone.
So like many I was using Magisk for root purposes on my device, more specifically v12.
It was working flawlessly until now, only thing was that Google updated their safety and safetynet would fail for a couple of weeks but I didn't mind much.
I got a notification last night that v13.1 is out and I tapped on it and tapped download and install now.
I did just that, rebooted the device and to my surprise Magisk had stopped working.
Once I entered the manager app the app would force close, i tried multiple times opening it and the result was the same.
I tried flashing the uninstaller and the un-su zip and flashed v13.1 again but the same thing happened.
I tried clearing cache and dalvik cache but it didn't help.
I even tried going back to v12 but to my surprise again v12 was force closing too!
I ended up flashing the trusted old SuperSU but I really need magisk for some modules I use.
I searched the magisk subforum but couldn't find anything that fixed it for me.
Had anyone had the same experience?
Is magisk v13.1 working for you?
How did you update? (if you were running v12)
EDIT:
Thanks to @seko85, anyone who had this issue disable all substratum themes and also do this:
1. Wipe dalvik cache, cache and system
2. Install the ROM I was using (RR)
3. Install Magisk 13.1
4. Install Gapps
5. Install kernel
6. Reboot to system
7. Install all modules I was using (deep buffer remover and viper for android by ahrion)
Clear Data from Settings - Apps - Magisk Manager.
mobidor said:
Clear Data from Settings - Apps - Magisk Manager.
Click to expand...
Click to collapse
I did that, enabled any permissions required as well.
Are you using v13.1?
If you're on B25, MagiskSU force closes when allowing a "new" app root, so that could be behind the crashes
Make sure that you have the latest version of magisk manager installed. Since the app got removed from the playstore you have to update manually.
Cyb3rzombi3 said:
Make sure that you have the latest version of magisk manager installed. Since the app got removed from the playstore you have to update manually.
Click to expand...
Click to collapse
I did yeah, the latest version is 5.0.4?
Yeah got 5.0.4 as well and latest magisk is running fine.
If that is not the problem then I don't know what else it could be
Which rom do you have installed?
nfsmw_gr said:
I did that, enabled any permissions required as well.
Are you using v13.1?
Click to expand...
Click to collapse
Yes, and no problem. Installed with TWRP.
nfsmw_gr said:
Hello everyone.
So like many I was using Magisk for root purposes on my device, more specifically v12.
It was working flawlessly until now, only thing was that Google updated their safety and safetynet would fail for a couple of weeks but I didn't mind much.
I got a notification last night that v13.1 is out and I tapped on it and tapped download and install now.
I did just that, rebooted the device and to my surprise Magisk had stopped working.
Once I entered the manager app the app would force close, i tried multiple times opening it and the result was the same.
I tried flashing the uninstaller and the un-su zip and flashed v13.1 again but the same thing happened.
I tried clearing cache and dalvik cache but it didn't help.
I even tried going back to v12 but to my surprise again v12 was force closing too!
I ended up flashing the trusted old SuperSU but I really need magisk for some modules I use.
I searched the magisk subforum but couldn't find anything that fixed it for me.
Had anyone had the same experience?
Is magisk v13.1 working for you?
How did you update? (if you were running v12)
Click to expand...
Click to collapse
I had the same situation. The solution was:
1. Wipe dalvik cache, cache and system
2. Install the ROM I was using (RR)
3. Install Magisk 13.1
4. Install Gapps
5. Install kernel
6. Reboot to system
7. Install all modules I was using (deep buffer remover and viper for android by ahrion)
Root is working and passed safety net. Unfortunately I couldn't manage to run Dolby Lee Pro 3 by ahrion and I suppose that also war mod is not working (post data script is not working, using Magisk v12 I saw in Magisk log that war mod was executed now with Magisk v13.1 I don't see such message).
seko85 said:
I had the same situation. The solution was:
1. Wipe dalvik cache, cache and system
2. Install the ROM I was using (RR)
3. Install Magisk 13.1
4. Install Gapps
5. Install kernel
6. Reboot to system
7. Install all modules I was using (deep buffer remover and viper for android by ahrion)
Root is working and passed safety net. Unfortunately I couldn't manage to run Dolby Lee Pro 3 by ahrion and I suppose that also war mod is not working (post data script is not working, using Magisk v12 I saw in Magisk log that war mod was executed now with Magisk v13.1 I don't see such message).
Click to expand...
Click to collapse
Alright that advice step by step was great!
Gonna try this once I get home and post back, thanks man!
Update, thanks to @seko85 and disabling any substratum theme (dunno which made it work, could be both together as well) I managed to fix the issue.
Magisk v13.1 is up and running.
Also thanks to everyone who replied.
Peace, out.
I recently flashed my ROM to Resurrection remix named RR-N-v5.8.5-20170925-a6000-Final and installed gapps named open_gapps-arm-6.0-stock-20171022 then I installed some apps from play store. SOme apps like Backdrops after installation makes my phone to restart and whet it boots up it shows "google has stopped responding " also "process system is not responding" and then is restarts again. I tried reflashing several times but nothing seems to work.
1. Wipe Art/cache system, data, internal
2. Install HEX Firmware
3. Install 5.8.5 RR
4. Install arm 7.1 pico gapps
5. wipe cache and reboot.
Rom take some time to Battery Collaboration and Performance.
so keep patience and enjoy.
rkunaal said:
1. Wipe Art/cache system, data, internal
2. Install HEX Firmware
3. Install 5.8.5 RR
4. Install arm 7.1 pico gapps
5. wipe cache and reboot.
Rom take some time to Battery Collaboration and Performance.
so keep patience and enjoy.
Click to expand...
Click to collapse
How can I install the firmware?
The link of hex firmware is in RR thread. And you flashed marshmallow gapps on a nougat rom. Flash arm 7.1 gapps.
ameyab97 said:
The link of hex firmware is in RR thread. And you flashed marshmallow gapps on a nougat rom. Flash arm 7.1 gapps.
Click to expand...
Click to collapse
Still the same problem
I think the problem is with new playstore every time I download certain apps it crashes.
raunak51299 said:
How can I install the firmware?
Click to expand...
Click to collapse
http://berbagikoleksi.blogspot.in/2015/06/solusi-lenovo-a6000-bootloop-gagal-flash.html?m=1
Sent from my Redmi Note 4 using Tapatalk
raunak51299 said:
I recently flashed my ROM to Resurrection remix named RR-N-v5.8.5-20170925-a6000-Final and installed gapps named open_gapps-arm-6.0-stock-20171022 then I installed some apps from play store. SOme apps like Backdrops after installation makes my phone to restart and whet it boots up it shows "google has stopped responding " also "process system is not responding" and then is restarts again. I tried reflashing several times but nothing seems to work.
Click to expand...
Click to collapse
First, I would like you to know that you DID NOT follow the instructions correctly. INSTRUCTIONS said, you will flash Opengapps 7.1.X ARM not 6.0 Marshmallow. Links were already given but still you did not follow.
Download the correct gapps package - ARM > 7.1 > Pico.
Code:
http://opengapps.org
Dirty flash it but if there's still an issue, you can clean install your RR 5.8.5 Final again and flash the gapps 7.1.
Good luck!
Download :
https://download.mokeedev.com/dragon.html
Installation:
1 - Boot into TWRP
2 - Wipe system, cache, dalvik and data partitions
3 - Sideload MK100.0-dragon-201912190517-NIGHTLY.zip
4 - Install Opengapps
5 - install Magisk.zip (Optional)
6 - Reboot into system
Thanks. Been meaning to try this.
Problem with getting magisk to install as "system-as-root"
I've tried the unmount/mount system partition
(Update) Also tried manually install of magisk/root/boot.img
And hints?
jamesthedisciple said:
Thanks. Been meaning to try this.
Problem with getting magisk to install as "system-as-root"
I've tried the unmount/mount system partition
(Update) Also tried manually install of magisk/root/boot.img
And hints?
Click to expand...
Click to collapse
Which version of TWRP are you using?
jamesthedisciple said:
Thanks. Been meaning to try this.
Problem with getting magisk to install as "system-as-root"
I've tried the unmount/mount system partition
(Update) Also tried manually install of magisk/root/boot.img
And hints?
Click to expand...
Click to collapse
Same problem here latest builds will not stay rooted using twrp-3.3.1-0
Also if you flash this Rom you should be aware it forces encryption, so not easy to move to another rom afterwards.
Twrp 3.3.1-0.
Root doesn't hold for Lineage 17 or asop10r9 either.
Not worried about encryption for the moment, tend to format data anyway until i can find a longtem "10".
When I have time I'll dive a little deeper. I have a twrp 3.3.1-2 to try out!
Root holds just fine on both below roms
[ROM][OFFICIAL][LineageOS][dragon] - [Lineage/17.0] -> 20191220
[ROM][UNOFFICIAL][PixelExperience][Ten/10.0][dragon] -> 2019/12/12]
I'm running PixelExperience and its solid everything's working good
Markeee said:
Root holds just fine on both below roms
[ROM][OFFICIAL][LineageOS][dragon] - [Lineage/17.0] -> 20191220
[ROM][UNOFFICIAL][PixelExperience][Ten/10.0][dragon] -> 2019/12/12]
I'm running PixelExperience and its solid everything's working good
Click to expand...
Click to collapse
That's good. Was that in twrp, unmount system, mount system, install magisk?
jamesthedisciple said:
That's good. Was that in twrp, unmount system, mount system, install magisk?
Click to expand...
Click to collapse
I didn't even bother with any of the unmount or mount options just formatted but I'm pretty sure just normal wipe will work also flashed PixelExperience then flashed latest Magisk-v20.1 in Twrp 3.3.1-0 no need to install OpenGApps its included in the PixelExperience Rom
Root works normally no issues
Markeee said:
I didn't even bother with any of the unmount or mount options just formatted but I'm pretty sure just normal wipe will work also flashed PixelExperience then flashed latest Magisk-v20.1 in Twrp 3.3.1-0 no need to install OpenGApps its included in the PixelExperience Rom
Root works normally no issues
Click to expand...
Click to collapse
That makes life easier!
Was that the same for the latest Lineage 17?
I'm running a google free pixel C!
jamesthedisciple said:
That makes life easier!
Was that the same for the latest Lineage 17?
I'm running a google free pixel C!
Click to expand...
Click to collapse
I haven't tried the very latest Lineage 17 build but was running the previous build before that and they were close but not quite as stable as PixelExperience Rom
There was no problems with root but the camera wasn't working.
I think i read its fixed in the latest build
Markeee said:
I haven't tried the very latest Lineage 17 build but was running the previous build before that and they were close but not quite as stable as PixelExperience Rom
There was no problems with root but the camera wasn't working.
I think i read its fixed in the latest build
Click to expand...
Click to collapse
Thanks. I now have LO17 latest build and root has held. Looking good.
The donate function is an error
The unique code is alway change when I change my Wifi. This problem make the tablet error. I cannot contract to the manager of Mokee because he uses Weibo
I used to have mokee on my moto x 2104 and this is the reason I will not use mokee without root. Here is a good explaination and a way to get round the problem of "mokee phone home". This works in mokee 9.
https://forum.xda-developers.com/moto-x-2014/general/opinion-x2-oreo-roms-fixes-roundup-t3809622
I have installed this ROM and everything works fine so far. The ads are okay since it is a free service. I can live with it. But one little suggestion for the developer: since this ROM is updated on a nightly basis, could you let us know the changes of each update? No details are necessary, just a couple words would be enough.
Thanks for keeping the development for Pixel C.
Problem with encryption
After installation I have the tablet with data encrypted and I can't use it!
How can I solve?
I use twrp 3.3.1-0
francoscala said:
After installation I have the tablet with data encrypted and I can't use it!
How can I solve?
I use twrp 3.3.1-0
Click to expand...
Click to collapse
Me too.
I use official version twrp-3.3.1-1-dragon.img
Grigori88 said:
Me too.
I use official version twrp-3.3.1-1-dragon.img
Click to expand...
Click to collapse
Do you have a problem with TWRP and decryption?
I been running this rom for a couple of months already theirs been a nightly update every single day rom is solid
The only issues I have is on reboots sometimes the rom gets hang at Google boot screen and the rom fails Safetynet Check ctsProfile in Magisk
Anyone alive in this thread I been running this rom since Dec updating it everyday but I can't seem to get today's 3/13/2020 build to boot past the Google screen any suggestions ?