Does anybody know what's the best way to upgrade from 1.6 to 2.1 without breaking the camera? What I mean is, I just received my replacement Xperia x10a on AT&T US. When upgraded my original one, it broke camera and even when I went back to 1.6 it still wouldn't work. Is there a way to save my current ROM and restore it back without losing functionality?
Tbh mate that sounds like a hardware fault that just coincided with your update.
Just update it mate. If you needed your original fw back it is information readily available here, and it is a straight forward enough procedure.
Sent from my X10i using XDA App
Lord Takyon said:
Tbh mate that sounds like a hardware fault that just coincided with your update.
Just update it mate. If you needed your original fw back it is information readily available here, and it is a straight forward enough procedure.
Sent from my X10i using XDA App
Click to expand...
Click to collapse
I'm not sure if it is a hardware issue. There's a few threads on here that I've found that refer to other people having the same issue. The issue seems to be the transition from 1.6 standard camera to 2.1 HD. Some where during the update on that apk for the camera it causes the camera not to work. You'll get a camera not found or camera unavailable with the camera button or on screen icon. I just want to be sure it will work so I don't have to go through not having a camera or fix for it. Thanks for the reply.
JayWheelz said:
I'm not sure if it is a hardware issue. There's a few threads on here that I've found that refer to other people having the same issue. The issue seems to be the transition from 1.6 standard camera to 2.1 HD. Some where during the update on that apk for the camera it causes the camera not to work. You'll get a camera not found or camera unavailable with the camera button or on screen icon. I just want to be sure it will work so I don't have to go through not having a camera or fix for it. Thanks for the reply.
Click to expand...
Click to collapse
I did the update to 2.1. The camera works and seems to be working OK overall. If I experience any more issues like before I'll update this thread.
Update didn't harm my camera. As a matter of fact, I've upgraded, downgraded, changed from x10a to x10i and back to x10a, rebranded from 1234-4820 to 1234-4836, pretty much every possible thing, and never one problem with camera.
Go here to update:
http://forum.xda-developers.com/showthread.php?t=825201
Yesterday I flashed this rom onto my HTC Titan and everyting was working fabulous, one of the best roms I've encountered.... until I've noticed that camera doesn't have option for front facing camera....
Anybody else had similar situation?
abaksunovic said:
Yesterday I flashed this rom onto my HTC Titan and everyting was working fabulous, one of the best roms I've encountered.... until I've noticed that camera doesn't have option for front facing camera....
Anybody else had similar situation?
Click to expand...
Click to collapse
You will get more help if the same question was asked into that ROM thread as users who are on that ROM are likely to visit ROM thread frequently! Also ROM chef will be able to see if this is a bug or something else and then comment quickly!
abaksunovic said:
Yesterday I flashed this rom onto my HTC Titan and everyting was working fabulous, one of the best roms I've encountered.... until I've noticed that camera doesn't have option for front facing camera....
Anybody else had similar situation?
Click to expand...
Click to collapse
abaksunovic, I suspect that the guy (deepshining cook) earlier cooked for first gen device w/o front camera and he used the camera tweaks from kinda Mozart or other device w/o front camera
So - check your registry:
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Camera\Settings]
"FFCSupported"
if it is: "FFCSupported"=dword:0 - than it means the cook-guy just switched off front cam Change it to 1 and reboot.
no fornt camera
Thanks for the advice, will try it since I allready flashed another ROM because of this.
Anyway, I'm a long time WP7 user, I have had Trophy, in the meantime had an iPhone 4, and lost credentals for my old account, had to make a new one so I must post here and not in the rom section... to gain at least 10 posts again... sorry if it upsets anyone...
no fornt camera on deepshining titan rom
Yep, it just needed change in registry!
Front camera suport is back.
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Camera\Settings]
"FFCSupported"
"FFCSupported" Dword=1 (in this rom it was 0)
Thanks again for support.
Hello all, this is my first post in the S2 section. I bought a very cheap S2 today but it has 1 issue (hence why it was cheap). The rear camera will only focus on close objects (>30cm) OR when it is facing up. If I point my phone down to look at the floor for example, it won't focus on anything unless i'm ~30cm from the floor. If i point my phone to the sky or higher than eye level it will focus. It sometimes will focus when I point it at eyelevel but it usually wont. I have updated it to XWLSS and the still issue persists. I bought this phone because i thought that this issue was a software issue but updating it to 4.1.2 didn't fix it.
Camera firmware: SCEF02.
Phone Firmware: TBEC28.
I don't have FPS issues or pink issues, only focusing issues. I've tried other camera apps (lgCamera) but that didn't fix it either. I don't think my camera module is completely broken because it still focuses when pointed higher than eye level. If i select macro in camera settings, nothing changes so that's why I think it might be a software issue. This issue happens in both video and photo mode. The front camera works fine and everything else is fine. Is there anything that can be done hardware wise or software wise? I don't want to change my module due to laziness and lack of experience but is there anything I could do like resolder the module? Anything else I can do software wise? If it helps, I also have an i9100T (Telstra model, identical to the i9100 except for the radio).
If people don't really understand by what I mean (issue wise) i'll make a video showing the focusing range and non focusing range.
Could reinstalling the camera firmware fix it? Or installing a different version?
Sent from my GT-I9000 using xda app-developers app
alb3rtt said:
Could reinstalling the camera firmware fix it? Or installing a different version?
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
If anyone does have this problem, I fixed this specific i9100 by changing the camera module.
Sent from my GT-I9000 using xda app-developers app
Add solved to thread title pls :thumbup: good job solving this mate. :thumbup:
Hi,
Search everywhere and still stuck!
This is issue that I have bee trying to solve on the 'android-rsap' forum, but am completely stuck, so by posting here I am hoping that someone can shed some light on what is going on.
Link: forum.android-rsap.com/viewtopic.php?f=32&t=871
In short, the device is a Samsung Galaxy 2 (XEU), and the bluetooth rsap functionality works fine with 4.0.4 (I9100XWLPT) but when I upgrade to 4.1.2 (I9100XWLSW) it no longer works at all. What is most weird is that it seems to be only my handset that is affected, it does not seem to be a universal issue. :roll eyes: What could be specific to my handset that stops this functionality working as it should?
I have been going back to 4.0.4 and upgraded to 4.1.2. many times now, via OTA, Kies and Odin, same result every time, sadly. 4.0.4 works every time, 4.1.2 has never worked with rsap and my car
What could be specific to my handset that stops this functionality working as it should? I have tried root'ing the handset to do more testing and to try the rsap app from Google App Store, but that has the same issue. Could some of the radio software be wrong? or?
Picture shows Kies upgrade screen and the 4.0.4 and 4.1.2 versions I am getting.
Any hints would be appreciated.
Regards,
J.
Try another JB ROM, and stop going back to 4.0.4.
Sent from the little guy
gastonw said:
Try another JB ROM, and stop going back to 4.0.4.
Sent from the little guy
Click to expand...
Click to collapse
Ok, so with an XEU handset - what version would you recommend?
realist42 said:
Ok, so with an XEU handset - what version would you recommend?
Click to expand...
Click to collapse
Ok, So I am a beginner with hacking my Samsung phone, this is mainly as I use them as phones, and want to rely on them. Before I had encountered this issue I had not even rooted my phone before.
I would really appreciate some help with this, this is an issue what is well beyond me, as in my view, what I have done ought to have fixed it. If there was a firmware issue, my reload should have but it back to 'factory default' .
As for going back to 4.0.4, well it works, so it must be a baseline for something, it proves the radio and bluetooth stack is capable of doing the right thing.
I think I need some pointer of getting my had set back to completely stock PDA / CSC / PIT, but don't know how to do it, or where to get the parts, to date got the firmwares from SamMobile... Any help would be appreciated.
Regards,
J.
..
realist42 said:
Ok, So I am a beginner with hacking my Samsung phone, this is mainly as I use them as phones, and want to rely on them. Before I had encountered this issue I had not even rooted my phone before.
I would really appreciate some help with this, this is an issue what is well beyond me, as in my view, what I have done ought to have fixed it. If there was a firmware issue, my reload should have but it back to 'factory default' .
As for going back to 4.0.4, well it works, so it must be a baseline for something, it proves the radio and bluetooth stack is capable of doing the right thing.
I think I need some pointer of getting my had set back to completely stock PDA / CSC / PIT, but don't know how to do it, or where to get the parts, to date got the firmwares from SamMobile... Any help would be appreciated.
Regards,
J.
Click to expand...
Click to collapse
The firmware specified by Kies (the one in the picture you posted) is your region specific firmware, just search and download the firmware from sammobile and flash it if you want to go back to stock, gastonw was suggesting you to try a different version of jb like xwlss, xwlsn, xwlsw, etc... If it's common to other jb versions then probably Samsung removed proper support for it, it's not the first time they have done it, like for example they completely removed action shot feature in stock camera in jb(this is there in ics).
Edit:If this problem is specific only for your s2, you might have to try flashing different firmware.
Sent from my GT-P6200 using xda app-developers app
king_below_my_lord said:
The firmware specified by Kies (the one in the picture you posted) is your region specific firmware, just search and download the firmware from sammobile and flash it if you want to go back to stock, gastonw was suggesting you to try a different version of jb like xwlss, xwlsn, xwlsw, etc... If it's common to other jb versions then probably Samsung removed proper support for it, it's not the first time they have done it, like for example they completely removed action shot feature in stock camera in jb(this is there in ics).
Edit:If this problem is specific only for your s2, you might have to try flashing different firmware.
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
Thanks,
I have tried a completely different firmware, and it behaved just the same. The odd thing is that there are no other reports of users having issues with the rsap application on a S2 with JB, so the support is on there (the app provides the stack if it is missing), but the app does not work either so it looks like it is my handset that has issues. I just can't figure out what to do to fix it. There is one thing that could be at play here, I did have a flailed upgrade from GB to ICS (4.0.3) where vibrate stopped working. It was sent to Samsung for repair, not sure what they did but I suspect that the just flashed the phone with a new version of the same firmware. Could there be something there that still causes issues?
Thanks.
J.
realist42 said:
Thanks,
I have tried a completely different firmware, and it behaved just the same. The odd thing is that there are no other reports of users having issues with the rsap application on a S2 with JB, so the support is on there (the app provides the stack if it is missing), but the app does not work either so it looks like it is my handset that has issues. I just can't figure out what to do to fix it. There is one thing that could be at play here, I did have a flailed upgrade from GB to ICS (4.0.3) where vibrate stopped working. It was sent to Samsung for repair, not sure what they did but I suspect that the just flashed the phone with a new version of the same firmware. Could there be something there that still causes issues?
Thanks.
J.
Click to expand...
Click to collapse
Hmm try generating a logcat when you try to use that feature and post it here, let's see whether some useful report is generated , please generate it as quickly as you can after you try activating/using that feature.
Sent from my GT-P6200 using xda app-developers app
Repporte Redan
king_below_my_lord said:
Hmm try generating a logcat when you try to use that feature and post it here, let's see whether some useful report is generated , please generate it as quickly as you can after you try activating/using that feature.
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
HI,
Took a little time to get the phone back in order and then to go an do the trace.
Not knowing what I am really looking for, but it strikes me that the bluetooth stack looks to just be giving up...
Regards,
J.
Hi all,
Well, today I managers to briefly borrow another S2 handset with JB on it. This other handset has the same issues that I have, so this must be something in the packaging of the Bluetooth that Samsung did - but I am guessing here.
Any clues would be appreciated, although I think I am fighting a loosing battle here... (works with an S3, so I should go and upgrade! at least chapter now that there is the S4 - but I like the form factor of the S2 better)
Regards,
J
I can't find anything that can cause a reasonable problem in your logcat, since you tried it out with an other GT-I9100 running JB and reproduced the problem, my guess is as good as yours.
Sent from my GT-I9100 using xda app-developers app
king_below_my_lord said:
I can't find anything that can cause a reasonable problem in your logcat, since you tried it out with an other GT-I9100 running JB and reproduced the problem, my guess is as good as yours.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Well, thanks for looking anyway...
My thinking on this is now that as it works with newer cars and only the older ones that now have issues, it must be a version issue, i.e. the version of the bluetooth stack is not the one it should be. It would be interesting to know if there is a difference in the version of the bluetooth stack and the rsap daemon between the S3 (which works on JB) and the S2 (which does not). Would that tell me anything interesting?
Regards,
J.
Your issue is directly related to 4.1.2 (and newer) versions of Android having changes to what's known as a2dp, or Advanced Audio Distribution Profile. Supposedly, these failings with Bluetooth connectivity of our blessed i9100 are fixed in Android 4.2.2, but unfortunately this version has not yet been released for it (and before anyone says otherwise, I dare them to show me where I can get the ridgey didge true blue real deal Jellybean 4.2.2 for the i9100, especially when sammobiles - the number one place for Samsung firmwares - don't have it for any country on the planet)
djshotty said:
Your issue is directly related to 4.1.2 (and newer) versions of Android having changes to what's known as a2dp, or Advanced Audio Distribution Profile. Supposedly, these failings with Bluetooth connectivity of our blessed i9100 are fixed in Android 4.2.2, but unfortunately this version has not yet been released for it (and before anyone says otherwise, I dare them to show me where I can get the ridgey didge true blue real deal Jellybean 4.2.2 for the i9100, especially when sammobiles - the number one place for Samsung firmwares - don't have it for any country on the planet)
Click to expand...
Click to collapse
HI,
I was not aware of this, and are you saying this is specific to the S2, so the fact that is works with an S3 on 4.1.2 is irrelevant?
J.
well, I've been researching this since 4.1.2 came out, and it isn't an issue only experienced here in Australia. Google is a great resource, go for a surf and you'll find out more...
djshotty said:
well, I've been researching this since 4.1.2 came out, and it isn't an issue only experienced here in Australia. Google is a great resource, go for a surf and you'll find out more...
Click to expand...
Click to collapse
Well, my issues are with specifically with rsap, not really A2DP, but if it affects the whole stack, this could be an issue.
To illustrate: I have 2 cars, one older, one newer. With the newer car all is well, and it works at is should (as far as I know) The older car was working pretty much with out issues on 4.0.4, but refuses to work with 4.1.2. Both cars rely on rsap.
Not sure this helps, just wanted to illustrate the problem that I am trying to solve.
Regards,
J.
Have a look at what people are talking about in a Google discussion group, about this very issue...
Code:
http://code.google.com/p/android/issues/detail?id=41628
djshotty said:
Have a look at what people are talking about in a Google discussion group, about this very issue...
Code:
http://code.google.com/p/android/issues/detail?id=41628
Click to expand...
Click to collapse
Maybe I am overly cautious here, but in my case it works just as it should with an S3, no issues at all, for me it is the S2 with JB that has the issue. And the functionality that does not work does not go near the A2DP libraries as the phone becomes a bluetooth SIM card for the car to access (which is rsap)
There must be others out there that also have this issue?!?
realist42 said:
Maybe I am overly cautious here, but in my case it works just as it should with an S3, no issues at all, for me it is the S2 with JB that has the issue. And the functionality that does not work does not go near the A2DP libraries as the phone becomes a bluetooth SIM card for the car to access (which is rsap)
There must be others out there that also have this issue?!?
Click to expand...
Click to collapse
That's why I suggested you look at the forum I provided the link for, there are plenty with the 'Phone calls via Bluetooth into car stereo' issue, including myself...
Hey guys, i've been having some trouble lately with taking pictures on my front facing camera. I'm using the t-mobile variant of the samsung galaxy s3 (its actually from wind, but theyre the same). The last rom i had installed was cyanogenmod, and it was working fairly well, except every once in a while, when i took a picture or video from the front facing camera, the phone would crash immediately and reboot. I tested this with many different camera applications and they all had the same result. I decided that i would try a different rom to see if that was the issue, so i installed the latest version of Carbon. The problem persisted, and it even got worse. Now every time i take a photo using the front facing camera, the phone will crash and reboot instantly. I read around, and there appears to be some issues with snapchat and such, but i dont think that is my problem as this is occuring with every camera application i have. I have also checked out some other threads related to this issue, and some seem to have the same problem, with no real solution. Apparently a temporary fix seems to be clearing the application data, but even that doesn't work for me. If i could guess, i would say it has something to do with custom roms in general as i have seen no reports of a stock rom phone having this issue, or perhaps a gapps issue, but those are just some thoughts.
Some Info:
Model Number: SGH-T999
Android Version: 4.4.2
Carbon Version: CARBON-KK-NIGHTLY-20140316-0304
I'd be happy to provide any extra info needed. Thanks so much guys, it would be great for me and all the others that have this issue if there's some way to fix this problem. I'll try to be as active as i can to provide any info or test any possible solution for everyone. It seems like a big problem for a lot of people.
I'd really appreciate any and all feedback. Sorry for the bump.