How to fix/change the camera horizon on custom rom AOSP? - General Questions and Answers

hi,
i have unbranded tablet 7".
i succeed to flash AOSP rom on it. everything work good ,Except the camera when i go up its go down, left its go right
i tried to change the build.prop paramters but nope..
any idea?
thanks

Related

how to make my camera+video work on cm9

hey friends,I have a Samsung Galaxy Ace GT-S5830 rooted running on ICS(4.0.4) CM9 RC1.My phone's camera is working only if I i turn my phone in 270 degree angle. Plus the camera which is pre-installed gives very poor quality pictures and I cannot change its settings and cannot turn on-off the flash,even I installed ics camera to try to fix this but it shows a error 'cannot connect to camera' everytime and force-closes.I even cannot take any videos.I read the forums on XDA that can help to fix camera,but none of them worked.I installed an patch update for camera from maclaw's website,but instead it got hanged on the samsung logo.I tried to flash nandroid backup but it showed error after 60% installation...so i flashed CM9 again. I want my camera back but for that I have to go back to stock rom.I'm not used to odin so i feel very awkward,and which is the only way to go back to stock.....Please tell me solution to this problem....should I go back to stock or is there any Patch available....please if you know help me...
Head to the galaxy ace subforum and post in the cm9 gerenal thread, i think cm9 already has a working cam.
Install the latest build, maybe wayland's.
I'm not going to stock again,instead I'M thinking of flashing 'Beats With Smooth Sense' ,is it a good ROM? what are the defects of this ROM?If someone know about it please tell me.....!!!
Lol this is general Q/A ask here http://forum.xda-developers.com/forumdisplay.php?f=1623
Hey, I got my stock ROM with the Extension ' .zip' from the site 'http://acetips.wordpress.com/roms-wiki/ . Do I need to flash through ODIN or I can flash through CWM?

[Q] Strange slider behaviour

Hi all,
I am using team OES 4.2 Nighties ROM with KAT Kernel and I have installed the KAT audio ap.
My issue is that I only have one digital slider available under the top right menu (when i slide down the top right section of the screen).
Sometimes it is the brightness slider, and sometimes it switches to the Volume slider.
I cannot find any setting that would allow me to choose what is available in this section.
I would like to find there the Volume and brightness sliders, on top of each other.
Can anyone help me fix that?
Thank you in advance.
D
Deazo said:
Hi all,
I am using team OES 4.2 Nighties ROM with KAT Kernel and I have installed the KAT audio ap.
My issue is that I only have one digital slider available under the top right menu (when i slide down the top right section of the screen).
Sometimes it is the brightness slider, and sometimes it switches to the Volume slider.
I cannot find any setting that would allow me to choose what is available in this section.
I would like to find there the Volume and brightness sliders, on top of each other.
Can anyone help me fix that?
Thank you in advance.
D
Click to expand...
Click to collapse
Revert back to your nAndroid backup and or start fresh.... could just be a bad flash or a confused mod lol make sure you wipe dalvik caches before starting from scratch
sent from
TF-101 A.R.H.D Harmony Kernel w/KingBeatz
Samsung Galaxy S3
AOKP 4.2.2 Kt747 kernel w/KingBeatz
Thank you for the response.
The solution you propose is rather drastic...
I have finally found a rom/kernel combination that works, my tablet works pretty well and this is the only issue I am having really.
What is a "bad flash"?
When installing I have wiped everything twice, and even wiped cache and datsik after install.
Is there not a way to get into system files and replace what is broken?
Just a shot in the dark, I am no android expert...
Thanks again
Deazo said:
Thank you for the response.
The solution you propose is rather drastic...
I have finally found a rom/kernel combination that works, my tablet works pretty well and this is the only issue I am having really.
What is a "bad flash"?
When installing I have wiped everything twice, and even wiped cache and datsik after install.
Is there not a way to get into system files and replace what is broken?
Just a shot in the dark, I am no android expert...
Thanks again
Click to expand...
Click to collapse
Replacing system files through device never recommend unless you know what your doing that's just method for bricking
By bad flash means when the mod/kernel etc when being downloaded isn't complete or is missing small sections that causing a portion not to work ..
AOKP 4.2.2 by Task650
Ktoonz Kernel w/KingBeatz
TF101 A.R.H.D ICS w/KingBeatz

[Q] S3 Camera Breaks Upon Installing Custom ROM

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.

[Q] Samsung AT&T Infuse Problems

I have been trying to fix a this phone for a friend at work. When I got it was stuck in a boot loop, fix that problem by flashing stock rom. I got the rom with root and CWM recovery here: [ODIN][UCLB3] AT&T 2.3.6 Gingerbread with root and CWM recovery option - Infuse 4g using option C. The phone works but the navigation keys don't. So if you go into an app or anything you can't leave. I have been trying to flash a custom rom that has the option in it to put navigation "keys" on the screen but, in CWM when I go into the ex-sd card it says there are no flies. I have tried to download CWM from Rom Manger also with luck. I cant find TWRP for this phone and I cant flash it from Goo without the navigation keys so, my question is; is a custom out there that can be flash with Odin or a way to make the custom rom files work with Odin or a CWM recovery for this phone that works? Please help I have been messing with this problem for a while now and don't know what else to do. Thanks for any input.
Jerky1226 said:
I have been trying to fix a this phone for a friend at work. When I got it was stuck in a boot loop, fix that problem by flashing stock rom. I got the rom with root and CWM recovery here: [ODIN][UCLB3] AT&T 2.3.6 Gingerbread with root and CWM recovery option - Infuse 4g using option C. The phone works but the navigation keys don't. So if you go into an app or anything you can't leave. I have been trying to flash a custom rom that has the option in it to put navigation "keys" on the screen but, in CWM when I go into the ex-sd card it says there are no flies. I have tried to download CWM from Rom Manger also with luck. I cant find TWRP for this phone and I cant flash it from Goo without the navigation keys so, my question is; is a custom out there that can be flash with Odin or a way to make the custom rom files work with Odin or a CWM recovery for this phone that works? Please help I have been messing with this problem for a while now and don't know what else to do. Thanks for any input.
Click to expand...
Click to collapse
you may have a hardware issue with the nav buttons
the only way i can think of to test it is to use one of the "unbrick" package with a complete reparttition
after that, try the buttons with the stock rom - if your buttons dont work with stock rom after a complete factory reset, you need to open the phone and check the hardware
qkster said:
you may have a hardware issue with the nav buttons
the only way i can think of to test it is to use one of the "unbrick" package with a complete reparttition
after that, try the buttons with the stock rom - if your buttons dont work with stock rom after a complete factory reset, you need to open the phone and check the hardware
Click to expand...
Click to collapse
They still don't work... Is there not a way to flash a custom rom with odin? Like a stock android based rom where you can put the nav keys on the screen.
Jerky1226 said:
They still don't work... Is there not a way to flash a custom rom with odin? Like a stock android based rom where you can put the nav keys on the screen.
Click to expand...
Click to collapse
the only rom avail via Odin are the stock 2.3.6 or stock with root that jscott30 put together.
if your nav keys don't work on stock, i'm thinking that it may be hardware related. idk if firmware will fix it.
here are jscott30's thread:
http://forum.xda-developers.com/search.php?searchid=227247390
qkster said:
the only rom avail via Odin are the stock 2.3.6 or stock with root that jscott30 put together.
if your nav keys don't work on stock, i'm thinking that it may be hardware related. idk if firmware will fix it.
here are jscott30's thread:
http://forum.xda-developers.com/search.php?searchid=227247390
Click to expand...
Click to collapse
Right, I'm not trying to fix the nav keys with firmware. What I was trying to say was "soft keys." I was wanting a rom with soft keys but I just learned that there are apps on the market with them. LOL Wow I was trying to make this harder than it needed to be. Well I do thank you for your help though and sorry I wasnt more clear. Thank you!
I had similar problems, I would suggest getting all 3 buttons fixed, both volume and the power button, my Infuse had the power button damaged, it was like $15 the repair, they can re-use your current buttons they may be stuck.
Then after you get them fixed, get an odin or heimdall stock with root rom and flash it, then you can go up to 4.3.3 with one of the many roms out there, like Beanstalk or CM10.2 which is the one I'm currently running.

[Q] Anyone succeed with GPS with custom rom

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...

Categories

Resources