After I clean flashed Paranoid Android cm10 there is no camera and google now does not work. I flashed gapps 7/26 and even tried the gapps hybrid Google Now but still no camera. Is there a zip or another way to install the camera?
Edit: I flashed everything over the ROM and everything seems to be there.
Try Re-downloading the rom, Gapps, and re-installing the rom with a full wipe. I got everything working on my P999 with the CM10 PA Rom (Build 3). Hope this helps.
maybe a bad flash,
Like yuvin said, Redo the whole process.
I've been having the same problem with PA CM10 (Build 12) from tonyp.
After a clean wipe, I flashed the rom and gaaps, and the camera is there and working. But for some reason, when I change the Paranoid Settings (lowered dpi from 240 (stock) to 190), my camera app mysteriously stops working ("App is not installed").
I've redone the process twice already and was wondering if anyone had any hints as to what's going on. I tried to search in the actual development forum and someone just "re-added the widgets" which seemed to fix the problem. I can't post in the actual development thread to try to ask however (due to low number of posts), so I thought I might try here.
EDIT: I also read that if Gallery is disabled/uninstalled, the Camera would be also. But my Gallery app still works just fine.
Related
TWRP, CM 10 9-19-2012 nightly, GAPPS for jelly bean.
OK , im a noob , you all hate me, i get it, but i have scoured this forum all day and i cannot find anywhere that explains why my aftermarket camera apps crash after i hit the shutter button , i know the camera is supposed to be built into the Gallery, but its not there. ive tried installing aftermarket camera apps like Camera JB + and nothing.
is this a major bug? or am i just a giganitic idiot?
Why didnt you post in the cm10 thread?
Oh thats right you dont have 10 posts yet. youre a noob who only post when he needs help but fail to scan the forums to see if he can help anyone with anything.
Dont thank/like/rep my posts or ill report you.
DROID3R said:
Why didnt you post in the cm10 thread?
Oh thats right you dont have 10 posts yet. youre a noob who only post when he needs help but fail to scan the forums to see if he can help anyone with anything.
Dont thank/like/rep my posts or ill report you.
Click to expand...
Click to collapse
Wow, are you drunk? Distrusting? or stupid? He said he's been looking thru the forums for an answer all day. When in fact the answer he is looking for is fairly obscure...
DSchmidt54 said:
TWRP, CM 10 9-19-2012 nightly, GAPPS *for jelly bean.
OK , im *a noob , you all hate me, i get it, but i have scoured this forum all day and i cannot find anywhere that explains why my aftermarket camera apps crash after i hit the shutter button , i know the camera is supposed to be built into the Gallery, but its not there. ive tried installing aftermarket camera apps like Camera JB + and nothing.
is this a major bug? or am i just a giganitic idiot?
Click to expand...
Click to collapse
@OP: Did you check the md5 hashes of your downloads. Either way, re-download your files. I have NO experience with TWRP so maybe you should try either the latest CWM Touch or regular CWM. Make sure you have the GAPPS from 7/26. Those are the tried and true gapps for CM10.
Above all, make sure the hashes check for both the CM10 Download and your GAPPS download.... more than likely thats the issue.
Also, when flashing, WIPE EVERYTHING. Do the data wipe/factory reset, cache wipe, and go into advanced and do a davlik wipe. (You can do the fix permissions under advanced if you feel like taking that 'extra step' but more than likely its not needed)
Also after you flashed CM, did you be sure to flash Gapps too? They are available as separate downloads and need to be flashed separately.
Also, if I'm not mistaken, CM9 is ICS correct? Did you be sure you flashed an ICS Gapps, or did you perhaps accidentally download JB Gapps?
DSchmidt54 said:
TWRP, CM 10 9-19-2012 nightly, GAPPS for jelly bean.
OK , im a noob , you all hate me, i get it, but i have scoured this forum all day and i cannot find anywhere that explains why my aftermarket camera apps crash after i hit the shutter button , i know the camera is supposed to be built into the Gallery, but its not there. ive tried installing aftermarket camera apps like Camera JB + and nothing.
is this a major bug? or am i just a giganitic idiot?
Click to expand...
Click to collapse
reflash the rom...
As the title states, how would one go about porting an 4.1 camera to 4.2? I really need a stable camera I can rely on and none of the current 4.2 Roms fit the bill. However, I really don't want to go back to 4.1.
Any help would be wonderful!
You mean run the touchwiz camera on a AOSP rom? Or run the AOSP 4.1 camera on a 4.2 rom? If you are talking the touchwiz camera then the answer is no. Touchwiz stuff needs touchwiz framework to work properly which obviously AOSP does not. There are a lot of camera apps in the playstore with similar functions as the touchwiz camera that you can run. I personally like Procapture.
x714x said:
You mean run the touchwiz camera on a AOSP rom? Or run the AOSP 4.1 camera on a 4.2 rom? If you are talking the touchwiz camera then the answer is no. Touchwiz stuff needs touchwiz framework to work properly which obviously AOSP does not. There are a lot of camera apps in the playstore with similar functions as the touchwiz camera that you can run. I personally like Procapture.
Click to expand...
Click to collapse
As stated, I'm talking about the AOSP 4.1 camera on 4.2. Not talking about touchwiz.
The 4.2 camera is extremely buggy at least for me. The 4.1 camera was rock solid.
Anyone? Or does anyone know what all files the camera needs to operate so I can copy one over myself?
After several tries, all I have managed to do is soft brick the phone, alot. Does anyone else want to solve this problem?
I don't think anyone else is having camera issues on 4.2, so you're probably not going to get a lot of support here. What issues are you having? Is never had one yet on 4.2, and I use the camera often, as I have an infant.
Sent from my SCH-I535 using xda app-developers app
Frequent FCs, sometimes rebooting will fix, other times I have to re-flash the rom. I too have an infant (2 wks old tomorrow) and a 2yr old. I also use the camera quite often for work. I know I am not the only one having the FC issues, I just don't know why it doesn't happen to others as well. When I flash a new rom I always Factory Reset, Wipe Cache/Dalvik, and Wipe System. Then flash, boot to system, wait a few minutes, reboot to recovery, flash gapps, then restore with titanium. The only camera that worked great (aside from TW of course) was the AOSP 4.1 Camera. All 4.2 cameras have failed.
brotherandyslb said:
Frequent FCs, sometimes rebooting will fix, other times I have to re-flash the rom. I too have an infant (2 wks old tomorrow) and a 2yr old. I also use the camera quite often for work. I know I am not the only one having the FC issues, I just don't know why it doesn't happen to others as well. When I flash a new rom I always Factory Reset, Wipe Cache/Dalvik, and Wipe System. Then flash, boot to system, wait a few minutes, reboot to recovery, flash gapps, then restore with titanium. The only camera that worked great (aside from TW of course) was the AOSP 4.1 Camera. All 4.2 cameras have failed.
Click to expand...
Click to collapse
I assume you have tried pulling the gallery app from a 4.1 rom and pushed it to /system/app/ on your phone. If not give that a try. Im not fully confident it will work but you might get lucky.
mentose457 said:
I assume you have tried pulling the gallery app from a 4.1 rom and pushed it to /system/app/ on your phone. If not give that a try. Im not fully confident it will work but you might get lucky.
Click to expand...
Click to collapse
Yes, I have tried just the APK. Doing that results in the camera becoming non functional. Then I expanded removed gmscore.apk and 2 lib files then added gallery.apk from 4.1 along with several files merged in to all folders set permissions, reboot ... soft brick. I'm not 100% sure what files the camera relies on and what files the system relies on. What I'd like to do is pinpoint down every file the camera relies on in both 4.1 and 4.2 then make the proper changes. I'm just not sure of how to do that. I've downloaded several different flashable cameras and it seems that each one has different files.
My specs: LG P500 Optimus One, rom: cm 10.1.0 RC3, i flashed soft and then gapps for 4.2.1
I flashed new build and i noticed, that notification area is not working properly
I cannot access quick toggles panel by clicking the top right icon.
Also swiping on the bottom bar causes weird bug, if i swipe half the way or stop swiping in between, the toggles are not flipping completely and are not clickable sadly .
Another thing is that first run android setup does not run at all after flashing 4.2.1 rashed's gapps. (on 24.04 nightly it works though)
And cronmod is not working, but i guess it's the 3.0 kernel thing. (is there any way to have something like cronmod with 3.0?)
If any of you can point me where to report bug and had experienced those too, please help me, thank You in advance.
I tried to search some contact form on jenkins, but with no luck :C
Jacek95 said:
My specs: LG P500 Optimus One, rom: cm 10.1.0 RC3, i flashed soft and then gapps for 4.2.1
I flashed new build and i noticed, that notification area is not working properly
I cannot access quick toggles panel by clicking the top right icon.
Also swiping on the bottom bar causes weird bug, if i swipe half the way or stop swiping in between, the toggles are not flipping completely and are not clickable sadly .
Another thing is that first run android setup does not run at all after flashing 4.2.1 rashed's gapps. (on 24.04 nightly it works though)
And cronmod is not working, but i guess it's the 3.0 kernel thing. (is there any way to have something like cronmod with 3.0?)
If any of you can point me where to report bug and had experienced those too, please help me, thank You in advance.
I tried to search some contact form on jenkins, but with no luck :C
Click to expand...
Click to collapse
i'm using the CM10.1.0 RC2 jenkins build too.
i did a clean install, and had no problems with the notification.
though the first run android setup did crash for me too..[flashed the ROM twice]
i guess you should do a clean install!!
Do a clean install. One more thing, gapps are already included in the builds.
No need to flash the gapps
Jacek95 said:
My specs: LG P500 Optimus One, rom: cm 10.1.0 RC3, i flashed soft and then gapps for 4.2.1
I flashed new build and i noticed, that notification area is not working properly
I cannot access quick toggles panel by clicking the top right icon.
Also swiping on the bottom bar causes weird bug, if i swipe half the way or stop swiping in between, the toggles are not flipping completely and are not clickable sadly .
Another thing is that first run android setup does not run at all after flashing 4.2.1 rashed's gapps. (on 24.04 nightly it works though)
And cronmod is not working, but i guess it's the 3.0 kernel thing. (is there any way to have something like cronmod with 3.0?)
If any of you can point me where to report bug and had experienced those too, please help me, thank You in advance.
I tried to search some contact form on jenkins, but with no luck :C
Click to expand...
Click to collapse
Gapps are already included in the ROM. No need to flash them again. If you flash the gapps, you may get those bugs as there isn't enough space for ROM as well as gapps.
try a clean install without flashing gapps.
rhar**** said:
Gapps are already included in the ROM. No need to flash them again. If you flash the gapps, you may get those bugs as there isn't enough space for ROM as well as gapps.
try a clean install without flashing gapps.
Click to expand...
Click to collapse
okay, will try now and report results soon
thanx for your effort
Okay, everything working fine, me flashing gapps over embedded ones in rom was the problem.
I dont know if its my phone or what but I haven't had any luck with AOSP ROMS on this phone. It seems like there's always some sort of bug that just kills it. I flashed a CM10.2 rom that felt like speed of lightning but was bugging out. I tried ecilpse and some others but all were to buggy for me. I recently tried to flash liquid cause I wanted to run something else other than touchwiz but it ruined my phone and now I cant flash custom ROMS(i have a help thread up..feel free).. Anyone else having bad luck on these AOSP ROMS
Not what you want to hear, but I'm having no issues with flashing new ROMs. I'm only using LiquidSmooth and waiting/hoping for a 'complete' 4.3 version, but again, no problems with flashing to a new ROM. I have been running LS2.9 (4.2.2) for several weeks and on Sunday flashed up to LS2.10 (4.3) but went back to 2.9 because when I mirror my phone on my AppRadio3, it doesn't auto-rotate my screen to landscape, so I have a portrait orientation of my phone on the radio display, which makes it so small as to be unusable.
I don't recall what method I used to root my phone, but I'm using TWRP 2.6.3 to perform a) a clean wipe every time (Factory Reset + System), then b) install the new ROM, and c) a final reboot back in to recovery and flash the latest gapps image. Does it take a little longer to follow this process? Sure, but it's a reliable process that means I don't have issues afterwards to mess with, so the extra time spent on the front end is worth it to me.
I've had moderate success with the AOSP ROMS. Each one seems to have it's own small bugs, but the AOSP ROMs that I've tried didn't have anything that ruined functionality. Been running Dirty Unicorn ROM for the past couple days and it is really solid. Haven't noticed any issues at all with it yet.
It's got to be your downloads or install process. Do you check MD5? If no then start. Remember just wipe data for each install. Updater-script in ROM zip wipes system for you. Cache resides in data. Do NOT restore system data using TiBu. Other than that I don't know what else to tell ya bud :/
Sent from my SCH-I535 using Tapatalk
Haven;t had any trouble with AOSP flashes, but many of the ROMs or maybe most have some bugs. All the so called AOSP ROMs are built off the same base, CM10. None of them support all the hardware and software features that Tocuhwiz supports. I find the custom TW ROMs far superior in features and as good or better in speed as well.
Make sure you are flashing a compatible Kernel when you switch between CM based ROMs and TW based
Hi all,
Did anyone able to use gps with custom rom ( I would say CM base). I research and try everything that's I could find here but not success.
Every time I do clean wipe everything including a internal storage. So that will nothing left behind.
I know that stock is work fine with gps. some said that install and replace stock but I have no idea that what file will left in our device when we delete all.
Always had the same problem when running Paranoid Android (not tried other ROMs). Had to return to stock, where GPS runs fine. Would also love to kknow how people have got it functioning.
I am trying too. I modified gps.conf files, tried some workarounds mentioned in cm11 thread like restoring GPS Status backup from stock with titanium so far with no success. Some people say that it works but it doesn't on mine whatever I do.
I run on CM and I don't have any problem. Everything works fine with gps and I didn't use any fix or something similar.
I'm on CM 11-20140627 and I have 1032 phone.
Interesting, why does it work on some while it doesn't on others? Maybe some variants are having problems...
I have xt1033 asia version.
spajdo said:
I run on CM and I don't have any problem. Everything works fine with gps and I didn't use any fix or something similar.
I'm on CM 11-20140627 and I have 1032 phone.
Click to expand...
Click to collapse
Which recovery did you use?
CWM
As I wonder is about library missing or some partition need from stock ?
I've also been using the micro gapps package, would this matter?
I had problems with Paranoid Android and GPS too... If anyone know something about that, please comment!
TMaxtor said:
I had problems with Paranoid Android and GPS too... If anyone know something about that, please comment!
Click to expand...
Click to collapse
Hey i found a solution, you have do this flash following in this order.
- flash stock 4.4.4 (depend on your current)
- flash cm
- flash gapp
I try this twice and work like a charm.
Sent from my Moto G using XDA Free mobile app
thestory101 said:
Hey i found a solution, you have do this flash following in this order.
- flash stock 4.4.4 (depend on your current)
- flash cm
- flash gapp
I try this twice and work like a charm.
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
I am having he same problem on XT1032 running Carbon ROM. GPS worked fine on stock, no signal with Carbon.
I found many answers saying to flash stock and then reflash custom ROM. I will try it, but I wonder, how does this help? Isn't the phone restoring the whole system? Do I have to keep the gps.conf from stock?
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
am05 said:
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
Click to expand...
Click to collapse
Did you wipe anything, like Dalvik, Cache and Data, or you just flashed it over?
am05 said:
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
Click to expand...
Click to collapse
Sorry people, I was so happy to have my phone back working, I forgot to write it back here.
Yes it worked indeed, all I did was flashing back the stock, going outside to have a gps lock with gmaps, then re-flashing back the Carbon. I also kept a copy of the gps.conf, but I never needed it, the GPS got a fix quickly. Working fine so far, it only takes some tens of seconds to fix, from time to time.
I can't remember if I also did all the wiping, I think I didn't, but I made so many trials in a couple days, I am not sure.
Thanks a lot guys!
am05 said:
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
Click to expand...
Click to collapse
Yes, this worked for me too on PA.
I couldn't even see a single sat (it wasn't just a lock problem). No matter with gps patch, gpx fix app, or gps.conf I used.
What I did?: Back to stock, lock GPS, flash again the custom ROM (but don't wipe /system!).
Good luck on that guys, it should work for you too.
thestory101 said:
Hi all,
Did anyone able to use gps with custom rom ( I would say CM base). I research and try everything that's I could find here but not success.
Every time I do clean wipe everything including a internal storage. So that will nothing left behind.
I know that stock is work fine with gps. some said that install and replace stock but I have no idea that what file will left in our device when we delete all.
Click to expand...
Click to collapse
GPS works fine on this unofficial CM11 rom for me. Stable daily driver rom for me, YMMV.
General advice is to:
- make sure you get a GPS lock on stock rom first
- flash CM11 (or other custom rom)
There may not be a file left on the device. it may just be that stock contains the code to initialize the GPS functionality on the SoC or chipset firmware. Whatever, it works...