Develop Bugs

Got a weird issue I can't track down, need help

Phone is a Samsung s3, sgh-T999L on tmobile.
Problem I am having is if I install anything above like pico gapps, basically anything that has more than like google play services, my camera on KK 4.4.x roms force closes and locks up.
I have narrowed it down to somthing withing the gapps packages that is causing the issue with the camera, but I cannot for the life of me track down what app is doing it, if it IS an app, my assumption is that it's an app that conflicts with the camera.
What I have done thus far is a Ful wipe, data, cache, internal, dalvik, etc....everthing, and I do this kind of wipe on every flash/install of roms.
I have tried cm11 full gapps, pa full, micro, and pico gapps, and every one of them except for the pico gapps, causes issues with the camera.
I have tried this on 3 different 4.4.4 roms....carbon rom, cm11 rom, and Octos KK rom, and all three have the exact same issue.
I first tried without using gapps and camera worked, so I then proceeded to try different versions of gapps, and narrowed it down to pico gapps works, while other gaps do not.
So has anyone else run into this issue or problem? I've tried searching google but I'm not exactly sure what to search for so I tried different search strings with no resolve, so I decided to post here and see if anyone else has had this issue.
In TW roms camera works fine, no issues. In KK roms useing just the minimal gapps (pico gapps) camera also works fine, using anything above the gapps package be it PA or cm, the camera does not function. When I say not function I mean it locks up, fc's, gives an errors of "cannot connect to camera" (I've done a search on that as well and got nothing).
So if anyone has had this issue and/or maybe has a fix, please please help!!!!!!

Thread moved to proper forum
Sent from my SM-G900T using XDA Premium 4 mobile app

T311 - Cyano 12.1 and Facebook

Hello all,
i'm having some fun installing roms on my T311 tablet, but it seems to me that the most "stable" and "usable" one is the cyano 12.1.
Now, the problem. I can't get the facebook app installed (i always get and "error -504"), and i really don't know why.
Obviously i've googled for a while, but i've tried:
- clearing cache of google apps
- wiping cache from recovery
- new install of cyano+gapps
and nothing worked.
I've also tried to install a different gapps than "open gapps" i have, but i got an error flashing (clean cyano install), so i turned back to open gapps.
The strange thing is that with cyano13 (with the same open gapps..) it works. With other roms, it works. It's only cyano 12.1..
What can i try?
thanks
(last twrp installed, if you need it..)

Pattagghiu said:
Hello all,
i'm having some fun installing roms on my T311 tablet, but it seems to me that the most "stable" and "usable" one is the cyano 12.1.
Now, the problem. I can't get the facebook app installed (i always get and "error -504"), and i really don't know why.
Obviously i've googled for a while, but i've tried:
- clearing cache of google apps
- wiping cache from recovery
- new install of cyano+gapps
and nothing worked.
I've also tried to install a different gapps than "open gapps" i have, but i got an error flashing (clean cyano install), so i turned back to open gapps.
The strange thing is that with cyano13 (with the same open gapps..) it works. With other roms, it works. It's only cyano 12.1..
What can i try?
thanks
(last twrp installed, if you need it..)
Click to expand...
Click to collapse
just to add, even with tk gapps the same problem.
i think i'll have to change rom

Pattagghiu said:
just to add, even with tk gapps the same problem.
i think i'll have to change rom
Click to expand...
Click to collapse
I'm running 12.1 on my Tab 3 10.1 GT-P5210 and haven't run into any problems... Facebook loads and runs fine for me.

Axefiredroid said:
I'm running 12.1 on my Tab 3 10.1 GT-P5210 and haven't run into any problems... Facebook loads and runs fine for me.
Click to expand...
Click to collapse
hello,
may i ask what version? I mean the build you had when you installed facebook
i've tried tons of times with the last available build. (20151231)
now i've gone "back" to cyano 13, but the problem with wifi is so annoying.. (i mean this: http://forum.cyanogenmod.org/topic/120233-cm13-wifi-dropping/ )

Problem installing GAPPS with CM 12.1 - Android keyboard (AOSP) has stopped

Hey everyone. Just got my first Note 3 a few weeks back and finally getting around to customizing it, but I'm running into problems getting it to work just right.
I'm used to CyanogenMod and wanted to get it for this Note 3. Well, the only versions are nightlies, but those have worked for me well in the past, so I figured no harm in trying them out. Everything installs A-OK and runs fine until I try to flash GAPPS.
Correct me if I'm wrong here, but this is my method and everything that I've been able to gather from people in the CM IRC tell me it's correct:
Full wipe (system, cache, dalvik, data, internal), flash CM, flash GAPPS, reboot.
I'm using the latest CM 12.1 nightly, the latest GAPPS available for it (ARM, 5.1, pico), and clearing everything I possibly can before installing. Even still, I keep getting "Unfortunately, Android keyboard (AOSP) has stopped" upon boot every time. I can't clear the data for the keyboard either in the app settings, nor can I access the play store to try to update the keyboard since, well, I don't have a keyboard.
Any ideas of what I could try? I really enjoy CM, but have no experience trying anything else out though.

Tried other Gapp versions such as Banks?

audit13 said:
Tried other Gapp versions such as Banks?
Click to expand...
Click to collapse
No, I have not. Just pico and nano versions of the ARM 5.1.

I cannot find GAPPS by Banks anywhere. The only link I could come across is dead.

I ended up just getting an APK of SwiftKey so I could actually start using my phone. I guess this'll work, and SwiftKey is pretty widely praised it seems.

Clean flash resurrection remix, latest files; Gapps force closing on boot

Hi all,
Detailing my issue;
Oneplus 3, running custom Rom Resurrenction Remix, ElementalX kernel, all running well. Had previously installed roms a few times on the device without issues
Phone froze after using an app made by my company for a yearly event - must not have been compatible with my device. Restarting phone, bootloop.
Clearing cache/Dalvik - boot, data lost...
Trying to reinstall my Resurrection Remix rom. Tried all the old files I had from my last install, they all were still in my storage folder (OnePlus 3 firmware, the rom, the Gapps package, Elementalx... which worked on my past install)
Upon first boot (setting up the phone), all the google apps close one after the other constantly.
I re-try a full clean install (Cache, Dalvik, Data, System), latest Resurrenction official (5.8.3), latest firmware (Oneplus3_4.1.1Firmware+Modem), tried the suggested Gapps (BeanGapps Mini 7.1) but tried also nano, stock (always ARM64 for 7.1). Of course a new clean wipe between each test. Don't even bother with ElementalX until issue resolved...
And I am still getting my Google apps crashing upon phone setup, or in case of minimum gapps packs as soon as I finish installing them, incapable of opening...
Spent a few hours yesterday trying to get this right - what am I missing? Anything that is not deleted from my Clean wipe? What changed?For now my phone runs on a backup I still had running OOS nougat... but really want to get back to custom Rom.
Any lead? Many thanks for any help.

in twrp select mount and pick system
go back to the main screen then select advanced then file manager go to root/system/etc/setupmanager/setupmanager.apk
delete the file or rename it then reboot the phone

Installed unofficial lineage os 17.1 but camera does not work

I installed Ivan's Lineage OS rom, it works great. However, I have one main issue... the camera does not work. No matter what camera app I use, it just crashes.
I have tried using the kill camera app on F-Droid and restarted my phone multiple times to no avail.
If there are no solutions to this I might switch back to the stock rom.
Does anyone know a solution to this?