Related
Am having some problem with my nexus one ive notice since i wipe my phone and install froyo, i tried going back to my cyano 5.0.6 but my camera isnt working whenever i switch to recorde a video the phones automatically reboots,but when i flash the froyo rom the camera is working perfectly there but when i try going back to my cyanogen its not working, anybody know what the problem is, also today i flashed cy 5.0.7 and am having the same problem.
Hello,
I am new to this forum and am having an issue with my HTC Sensation 4g. Since I've installed Cyanogenmod 9 -Hypersensation 2.9, the Camera as well as the Torch have not been working properly. I've tried going to the Applications and Clearing the Data as well as re-installing the ROM, but to no avail. Any help with this issue would be greatly appreciated. Thank you. Also, whenever I try to access the Camera app it says "Cannot Connect to the Camera" and when I try to access the Torch app, it says "Unfortunately the Torch app has stopped working". I have also noticed that the GPS function does not work.
I have the same issue since I first installed a CM9 nightly on my Sensation XE.
Installing the CM RC1 and the CM Open Sensation did not fix this either.
I also tried the Android Revolution rom and had the same issues.
Would appreciate any suggestions that anyone has.
Did you fullwipe before installing CM9?
Because on my pyramid with cm9 RC1 the torch app and GPS both work fine and allways have.
andy01q said:
Did you fullwipe before installing CM9?
Because on my pyramid with cm9 RC1 the torch app and GPS both work fine and allways have.
Click to expand...
Click to collapse
Yeah - absolutely. If you don't do that on an initial install CM9 (or any other ROM) will very likely go into a boot loop.
donalmc said:
Yeah - absolutely. If you don't do that on an initial install CM9 (or any other ROM) will very likely go into a boot loop.
Click to expand...
Click to collapse
If it helps, I did a system format with CWM 5.8.0.9 and installed cm10. Camera and torch came back, but only for a week. No it shows the same as before and for you. I will do a system format soon when i have time.
Good luck.
If you have bulletproof solution to make the camera work, pls share with us.
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.
I have had Bean's Jelly 'Beans' ROM installed on my GS3 since I first got the phone in October. Verizon had to replace my phone this past week, and once I received the new one, I did the customary procedure of rooting it and installing a custom ROM. However, after I install a ROM, the Camera always breaks (I get the message "Camera Failed" and the camera screen is black when I open the stock camera app).
I have already researched the issue, and it seems there is a history of some S3's coming out of the box with a broken camera, but it is important to note that the camera works fine as long as I revert back to the stock (and rooted) rom. When installing the Jelly 'Beans' ROM, I have selected 4 different kernel options(Beans custom stock, imoseyon lean kernel, ktoonsez, and faux kernel), thinking that may be the issue, but each one still leaves a broken camera. I have also tried installing an aftermarket camera app, in case the S3 camera apk is somehow broken, and have flashed the Photosphere Camera. Nothing will get the camera to work (and yes, my battery is fully charged).
Not being able to install a custom ROM is a pretty big deal to me, and not having a working camera is a deal breaker. Unfortunately, I won't be able to get Verizon to replace the phone again since it all works on the stock ROM. Does anyone have any ideas? I have tried several things I have read in the forums, but nothing has worked so far. Thank you all in advance for your help!
tfc87 said:
I have had Bean's Jelly 'Beans' ROM installed on my GS3 since I first got the phone in October. Verizon had to replace my phone this past week, and once I received the new one, I did the customary procedure of rooting it and installing a custom ROM. However, after I install a ROM, the Camera always breaks (I get the message "Camera Failed" and the camera screen is black when I open the stock camera app).
I have already researched the issue, and it seems there is a history of some S3's coming out of the box with a broken camera, but it is important to note that the camera works fine as long as I revert back to the stock (and rooted) rom. When installing the Jelly 'Beans' ROM, I have selected 4 different kernel options(Beans custom stock, imoseyon lean kernel, ktoonsez, and faux kernel), thinking that may be the issue, but each one still leaves a broken camera. I have also tried installing an aftermarket camera app, in case the S3 camera apk is somehow broken, and have flashed the Photosphere Camera. Nothing will get the camera to work (and yes, my battery is fully charged).
Not being able to install a custom ROM is a pretty big deal to me, and not having a working camera is a deal breaker. Unfortunately, I won't be able to get Verizon to replace the phone again since it all works on the stock ROM. Does anyone have any ideas? I have tried several things I have read in the forums, but nothing has worked so far. Thank you all in advance for your help!
Click to expand...
Click to collapse
I'm going to go ahead and help myself out and respond to my own question. Upon even further research (yes, I know everyone says people don't look hard enough), I believe the issue relates to the Firmware version. Supposedly the newest firmware breaks the camera unless it's on the stock rom. There are modified firmwares out there that change the part that breaks the camera, but I believe I am going to downgrade the modem and all from what was pre-installed and see if it works.
tfc87 said:
I'm going to go ahead and help myself out and respond to my own question. Upon even further research (yes, I know everyone says people don't look hard enough), I believe the issue relates to the Firmware version. Supposedly the newest firmware breaks the camera unless it's on the stock rom. There are modified firmwares out there that change the part that breaks the camera, but I believe I am going to downgrade the modem and all from what was pre-installed and see if it works.
Click to expand...
Click to collapse
if its a custom Rom (Stock but maby some extras such as overclocking or somethin) they are Sometimes Broken They will try to fix it sometimes, upgrading to a higher android version it is sometimes is Quite hard to Fix everything.
Trozzul said:
if its a custom Rom (Stock but maby some extras such as overclocking or somethin) they are Sometimes Broken They will try to fix it sometimes, upgrading to a higher android version it is sometimes is Quite hard to Fix everything.
Click to expand...
Click to collapse
I downgraded the firmware to VRBMB1 and went back to that custom rom and the camera works flawlessly. I read in the firmware forum that the new firmware is doing this to a lot of people...I just happened to have one of the phones that came with it pre-installed. Problem solved and hopefully this post will help someone out...if not...it helped myself out at least.
tfc87 said:
I downgraded the firmware to VRBMB1 and went back to that custom rom and the camera works flawlessly. I read in the firmware forum that the new firmware is doing this to a lot of people...I just happened to have one of the phones that came with it pre-installed. Problem solved and hopefully this post will help someone out...if not...it helped myself out at least.
Click to expand...
Click to collapse
maby just wait till next firmware and they will fix it?
Trozzul said:
maby just wait till next firmware and they will fix it?
Click to expand...
Click to collapse
Yeah I'm sure it will be fixed. Either way, I don't recommend that newest firmware...signal seems to be the worst out of all of the ones I've tried...for me at least. Seems to be a lot of complaints out there with it anyways.
Similiar issue?
I am having a similiar issue with my US Cell GS3. I bought the donor version of mskip's Samsung Galaxy S3 Unified Toolkit and rooted my device yesterday now my camera is doing the same thing...fires up to a black screen, hangs a few seconds then says camera failed. I'm running Android 4.1.2, build R530UVXAMD4. I've read in a few places that I may have to either downgrade my kernel or flash with some sort of alternate firmware.
Any assistance provided is greatly appreciated!
Sterling8356 said:
I am having a similiar issue with my US Cell GS3. I bought the donor version of mskip's Samsung Galaxy S3 Unified Toolkit and rooted my device yesterday now my camera is doing the same thing...fires up to a black screen, hangs a few seconds then says camera failed. I'm running Android 4.1.2, build R530UVXAMD4. I've read in a few places that I may have to either downgrade my kernel or flash with some sort of alternate firmware.
Any assistance provided is greatly appreciated!
Click to expand...
Click to collapse
did you figure this out?
im having same problem
I had the same problem while flashing one of my friend's S3...i just did the whole process once again..and everything works fine
Sent from my Galaxy Note II using xda premium
tfc87 said:
I have had Bean's Jelly 'Beans' ROM installed on my GS3 since I first got the phone in October. Verizon had to replace my phone this past week, and once I received the new one, I did the customary procedure of rooting it and installing a custom ROM. However, after I install a ROM, the Camera always breaks (I get the message "Camera Failed" and the camera screen is black when I open the stock camera app).
I have already researched the issue, and it seems there is a history of some S3's coming out of the box with a broken camera, but it is important to note that the camera works fine as long as I revert back to the stock (and rooted) rom. When installing the Jelly 'Beans' ROM, I have selected 4 different kernel options(Beans custom stock, imoseyon lean kernel, ktoonsez, and faux kernel), thinking that may be the issue, but each one still leaves a broken camera. I have also tried installing an aftermarket camera app, in case the S3 camera apk is somehow broken, and have flashed the Photosphere Camera. Nothing will get the camera to work (and yes, my battery is fully charged).
Not being able to install a custom ROM is a pretty big deal to me, and not having a working camera is a deal breaker. Unfortunately, I won't be able to get Verizon to replace the phone again since it all works on the stock ROM. Does anyone have any ideas? I have tried several things I have read in the forums, but nothing has worked so far. Thank you all in advance for your help!
Click to expand...
Click to collapse
I have had the same problem when I installed a certain custom rom (can't remember the name ) on my s3. But later I found that during installation of the rom, there was an option to choose one of four kernels, and if I chose Boeffla kernel (included in the options) my camera wouldn't work. So I just reverted back to the stock kernel and walah! My camera works again.
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...