Develop Bugs

What has happened to my camera

I went to open my camera app on MIUI the other day and it forced closed. I thought it was a fluke so I wiped my camera app through titanium backup and launched it again. It still forced closed. I wiped my caches but that didnt work.
I have tried different kernels and roms and they all force close. Anything else I should try?
Sent from my PC36100 using XDA App

michaelvibe said:
I went to open my camera app on MIUI the other day and it forced closed. I thought it was a fluke so I wiped my camera app through titanium backup and launched it again. It still forced closed. I wiped my caches but that didnt work.
I have tried different kernels and roms and they all force close. Anything else I should try?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
So... it force closes no matter what? Every ROM you try? After full wipes?

Mine did that on MIUI too, then when I would open it I'd get an error that said "cannot connect to camera". Other camera apps worked fine. Wiping data for the camera from "manage applications" solved the issue for me. If it's across multiple roms and wipes then it probably isn't rom or app related. Have you tried third party camera apps?
Sent from my PC36100 using Tapatalk

Yes I have tried a couple apps and they just freeze on a black screen. I did a full wipe coming from my last rom and the problem is still there. Guess it is time to give the credit card company a call.
Sent from my PC36100 using XDA App

Just after making my last post I tried it again. The camera comes on but everything is tinted purple and pink. I had this problem many months ago but it went away before I could get a sprint tech to see it haha. I posted here about it and I think people just thought I was crazy. Anyways, I'm conveniently a month out of my one year warranty without insurance. What are my options at this point?
Sent from my PC36100 using XDA App
Edit:
Here is that thread for completeness
forum.xda-developers.com/showthread.php?t=993064

I heard insurance was open to enrollment for the month, but I'm not sure of the exact dates or if my info is correct. You can look that up or call Sprint & ask. If it's open, I'm not sure if there's a time limit on when you can use it - I'd think not. The month ends soon, so I'd go ahead and call.
Without insurance, I'm not sure. You can always take it in, maybe you'll get lucky. I'm not up to date on Sprint's policy for such things, I just pay my insurance every month.
Sent from my PC36100 using Tapatalk

Jellybean Camera service unavailable

Hi everyone,
I have a pretty strange problem. I have done a ton of research and seen it is common, but no one seems to have a solution. Anyways, I am unable to open neither Talk nor the camera app.
After booting the phone up, gtalk attempts to connect to the camera service. It is unavailable, so it immediately force closes. The same happens when I attempt to launch Talk.
I'm sure everyone is thinking: why don't you post a logcat, that would help. well.. I would if I could. According to alogcat as well as ADB the directory where the logcat is stored cannot be found.
I can tell from looking at the 'event log' after pushing the 'report' button when talk FC's that it is failing to launch due to a runtime error: 'failed to get camera info". This is really bothering me as I need my camera on my phone for my job.
I have flashed a few Roms in the past, but I have recently decoded to stick with the leaked stock. I've wiped EVERYTHING 5+ times, with no change. Restoring nandroids does not fix the problem either. No matter what ROM I flash, the problem remains. If anyone has any suggestions, I would greatly appreciate it.
Sent from my Galaxy Nexus using Tapatalk 2

One thing that I know will work. Unroot relock. Then it should definitely be fixed.
Then reroot and unlock.
So camera can't open at all??? Like click the icon and then force close???
--------------------------------------------------
If I have helped you.... hit that sexy thanks button. ^_^

I had this issue before. Everytime I would try to open the camera, it would forcr close. What I did was flash back to the IMM76K factory stock image. No need to relock.
Sent from my Galaxy Nexus using xda premium

DirgeExtinction said:
I had this issue before. Everytime I would try to open the camera, it would forcr close. What I did was flash back to the IMM76K factory stock image. No need to relock.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Where did you get the image you flashed from? I have found several, but they are just the ones that patch TO IMM76K.
Sent from my Galaxy Nexus using Tapatalk 2

rm2011 said:
Where did you get the image you flashed from? I have found several, but they are just the ones that patch TO IMM76K.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Look for your Galaxy Nexus type and download:
https://developers.google.com/android/nexus/images
Sent from my Galaxy Nexus using xda premium

rm2011 said:
Hi everyone,
I have a pretty strange problem. I have done a ton of research and seen it is common, but no one seems to have a solution. Anyways, I am unable to open neither Talk nor the camera app.
After booting the phone up, gtalk attempts to connect to the camera service. It is unavailable, so it immediately force closes. The same happens when I attempt to launch Talk.
I'm sure everyone is thinking: why don't you post a logcat, that would help. well.. I would if I could. According to alogcat as well as ADB the directory where the logcat is stored cannot be found.
I can tell from looking at the 'event log' after pushing the 'report' button when talk FC's that it is failing to launch due to a runtime error: 'failed to get camera info". This is really bothering me as I need my camera on my phone for my job.
I have flashed a few Roms in the past, but I have recently decoded to stick with the leaked stock. I've wiped EVERYTHING 5+ times, with no change. Restoring nandroids does not fix the problem either. No matter what ROM I flash, the problem remains. If anyone has any suggestions, I would greatly appreciate it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
seems to me that the roms you're using dont have the camera binary. adb logcat is unavailable? that's unheard of, since thats a part of android itself. even user variant builds have it. can't think of a good reason for logcat to be removed.

I wiped EVERYTHING via fastboot and reflashed the stock image as suggested. I managed to flash successfully, but camera was still unavailable.
Logcat is working now, and the problem is a runtime error; "unable to retrieve camera information"
Any idea how I can check to see if the binaries are the problem? This is very frustrating... and I don't see how its happening, to be honest. I'm fairly certain it is not a hardware issue because I am definitely not the only one having the issue.
Sent from my Galaxy Nexus using Tapatalk 2

The last guy who had this exact same problem also was unable to fix it. If you flashed all partitions to stock and it still doesn't work, a hw issue does come to mind.
Sent from my Galaxy Nexus using Tapatalk 2

I guess its a possibility. I think what I need is someone who is proficient with the android source code to look at the camera service and see what makes it throw that log error. It almost certainly an ""if/else 'whatever the problem is' doesn't exist or is not correct, log e 'the error I am seeing in the log cat'"
If I was proficient in navigating the source code, I would do it. But I wouldn't know where to look. I need assistance of someone that is capable of doing this.
Again, I appreciate any and all help or assistance. Thanks will be given where it is deserved!
Sent from my Galaxy Nexus using Tapatalk 2

Well, as far as my limited knowledge can tell, the camera binaries are included. I did some research and found out that the camera is called "ducati" and I navigated to /vendor/firmware and found the file attached in the screenshot. Any suggestions would be appreciated. :/
Sent from my Galaxy Nexus using Tapatalk 2

rm2011 said:
Well, as far as my limited knowledge can tell, the camera binaries are included. I did some research and found out that the camera is called "ducati" and I navigated to /vendor/firmware and found the file attached in the screenshot. Any suggestions would be appreciated. :/
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
yeah, thats the binary for the camera. try another camera app, if you have already i'd say return it, i guess.
Sent from my i9250

bk201doesntexist said:
yeah, thats the binary for the camera. try another camera app, if you have already i'd say return it, i guess.
Sent from my i9250
Click to expand...
Click to collapse
I wish I could... but since I bought it used, that's not possible. Hopefully I can find a dev that knows the source code well enough to know where to look to see what causes this error.
Sent from my Galaxy Nexus using Tapatalk 2

bk201doesntexist said:
yeah, thats the binary for the camera. try another camera app, if you have already i'd say return it, i guess.
Sent from my i9250
Click to expand...
Click to collapse
I wish I could... but since I bought it used, that's not possible. Hopefully I can find a dev that knows the source code well enough to know where to look to see what causes this error.
Sent from my Galaxy Nexus using Tapatalk 2

Update: it appears that the camera service is not starting for some reason....
Sent from my Galaxy Nexus using Tapatalk 2

Camera Fails to Load?

Hey I just bought a T-mobile Samsung Galaxy S2 and the camera Fails to Load. Any input on this?
Sent from my SGH-T989 using xda app-developers app

You could wipe data cache factory or Default camera options.

I tried wiping the app data. Let me try a factory reset. If that doesn't work then what?
Sent from my SGH-T989 using xda app-developers app

Change of Rom.

So root it, install cwm, make a nandroid backup, and flash a new rom? Where's a good guide on how to root the ics updated s2?
Sent from my SGH-T989 using xda app-developers app

damon7620 said:
Hey I just bought a T-mobile Samsung Galaxy S2 and the camera Fails to Load. Any input on this?
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
From the way you worded this I'm assuming you didnt put any custom roms but just got the phone and set it up. Try doing a factory reset and/or if it doesnt work, would you be willing to try a custom rom and see if the camera works on it? If it doesnt work on a rom either then somethings wrong with the phone and I would suggest getting a replacement.
NOTE: Wait for a few other replies because someone else may have had a similiar problem and this is just a extreme.
Btw, make sure you keep track of your 20 day warranty for a full new replacement.

Also considering there is something Bad with the software try flashing any other rom i recommend you a soft one.

Talked to Samsung Support and they are going to replace it for free. Also offered to pay the shipping both ways! Thanks guys.

Happened to me all I did to fix it was a simple restart lol seriously
Sent from my SGH-T989 using xda app-developers app

T989 problem Screen

Hi everybody
i need help with my T989, I listed a few words on the screen:
HW: Not active
PDA: ********
PHONE: ******
CSC: ****
regards

What is that supposed to be need more info on the problem
Sent from my SGH-T989 using Tapatalk 2

richardlibeau said:
What is that supposed to be need more info on the problem
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
this problem

bmauri92 said:
this problem
Click to expand...
Click to collapse
Never seen that before that is a new one. Is it on every screen or just home screen? Does the phone function normal besides that?
Sent from my SGH-T989 using Tapatalk 2

richardlibeau said:
Never seen that before that is a new one. Is it on every screen or just home screen? Does the phone function normal besides that?
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I heard that people who update jb from Kies, that's what happens... I never saw something like that on my phone because I install custom rooms (4.2.2) when my phone was 4.0.4 like many others.
It's just a comment in case that you want to try something like that.
Sent from Samsung S2

TJSteveMX said:
I heard that people who update jb from Kies, that's what happens... I never saw something like that on my phone because I install custom rooms (4.2.2) when my phone was 4.0.4 like many others.
It's just a comment in case that you want to try something like that.
Sent from Samsung S2
Click to expand...
Click to collapse
No I won't try anything like that and I never use kies only odin if needed
Sent from my SGH-T989 using Tapatalk 2

richardlibeau said:
No I won't try anything like that and I never use kies only odin if needed
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Exactly... I don't use Kies for jellybean update... I said that he should try installing an aosp rom. I remember somebody had that issue and install a custom rom fixed (I don't speak English) sorry for my grammar and confusion.
Sent from Samsung S2

Thanks for the post OP. I can't post my picture because of the new user 10 comment rule.
Exact same problem. This text overlay appears on the wallpaper. If I open up another program like Internet or settings or memo or messaging it does NOT appear.
If my phone is shut off and I turn it on, there is a split second where the text isn't on the wallpaper, but it will pop up eventually (I assume its because the OS isn't fully loaded up at that point)
This occurred after I upgraded to 4.1.2 via Kies.

Is it still there if you change wallpaper or use another launcher?
Sent from XDA app

gc84245 said:
Is it still there if you change wallpaper or use another launcher?
Sent from XDA app
Click to expand...
Click to collapse
Affects all wallpapers, haven't tried another launcher and not really interested in it either. Is it worth trying to re-update? I would like to try the ODIN method but I gotta read up on it first.

It might be worth a shot. Here's an excellent guide
http://androidforums.com/samsung-galaxy-s2-t-mobile/628449-how-odin-any-stock-rom.html
Sent from XDA app

Thanks for the guide. I tried it. Same problem. The writing overlays my homescreen and apps drawer icons as well, but when I open up an actual app like internet or anything else it is not there.
The lock screen also does not have the text writing on it.
As mentioned before, if I turn off the phone and turn it on there is a few seconds where it isn't "loaded".
The same also happens when exiting an app such as internet or email. The wallpaper seems fine for a split second before the text is "loaded" back onto the wallpaper
Argh!!! It is slightly irratating. :crying:

That is strange. I know you said you didn't want to try another launcher, but if nothing else works it might be worth considering. I recommend Apex or Nova.
Sent from XDA app

and ingyivi
gc84245 said:
That is strange. I know you said you didn't want to try another launcher, but if nothing else works it might be worth considering. I recommend Apex or Nova.
Sent from XDA app
Click to expand...
Click to collapse
I wonder if it has anything to do with those phone number codes you can punch in on the dial pad...oh well. I might try a launcher...might

if you wipe and start fresh it might fix that
here is my guide on recovery, root and roms
hope this helps m8's
http://forum.xda-developers.com/showthread.php?t=2249849

bmauri92 said:
Hi everybody
i need help with my T989, I listed a few words on the screen:
HW: Not active
PDA: ********
PHONE: ******
CSC: ****
regards
Click to expand...
Click to collapse
Its bcus u went into ur developer option an play around an enabled sumting jus go bk in there an disabled
Sent from my SGH-T989 using xda app-developers app

Temporary solution
bmauri92 said:
Hi everybody
i need help with my T989, I listed a few words on the screen:
HW: Not active
PDA: ********
PHONE: ******
CSC: ****
regards
Click to expand...
Click to collapse
I change a downloaded theme of the play store and disappeared, but using the native interface reappears. Not have a definitive solution?
When upgrading either my bluetooth works.
PD: Sorry for my grammar.
---------- Post added at 10:35 AM ---------- Previous post was at 10:09 AM ----------
Update my T989 to 4.1.2 but I get a black letters on the screen, but only in the same applications after entering no.
It's like when you aprece the background in windows is not genuine.
Operation does not affect me or anything just uncomfortable sight, an interim solution I found was using a different launcher.
But upon returning to the samsung native interface reappear me the happy lyrics.
Is there any solution for this?
Since reinstalling the ROM probe with ODIN like 4 times, give the corresponding wipe but still not solve.
Now the problem I found that my bluetook not turn on. These two are the only problems I found, after my T989 I works perfectly and with the same fluidity and even better than when I had the 2.3.6.

jjara-paraguay said:
Update my T989 to 4.1.2 but I get a black letters on the screen, but only in the same applications after entering no.
It's like when you aprece the background in windows is not genuine.
Operation does not affect me or anything just uncomfortable sight, an interim solution I found was using a different launcher.
But upon returning to the samsung native interface reappear me the happy lyrics.
Is there any solution for this?
Since reinstalling the ROM probe with ODIN like 4 times, give the corresponding wipe but still not solve.
.
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?t=2378224

Boot Looping

Was this a problem on the first Note tablet? As I get to installing a lot of apps, over 500 is what I have, I've found that the tablet is going through an infinite boot loop. I'm talking to a Samsung rep online now about it. I've tried taking out the sd card, putting it back it, etc. It appears that some are going through this too with the Galaxy Note 3.
http://forum.xda-developers.com/showthread.php?t=2467005

icebergisonfire said:
Was this a problem on the first Note tablet? As I get to installing a lot of apps, over 500 is what I have, I've found that the tablet is going through an infinite boot loop. I'm talking to a Samsung rep online now about it. I've tried taking out the sd card, putting it back it, etc. It appears that some are going through this too with the Galaxy Note 3.
http://forum.xda-developers.com/showthread.php?t=2467005
Click to expand...
Click to collapse
Updating my status. Through my own research, instead of trying to install all 500 at once, I've taken a more modest approach. I'm installing apps 4 at a time, letting it finish, powering down, then starting back up. It's working. I can get to my home screen without problem now. Maybe 500+ apps was too much of a strain for the file system to endure.

icebergisonfire said:
Maybe 500+ apps was too much of a strain for the file system to endure.
Click to expand...
Click to collapse
it would be pretty stupid if that's the case. it would seem a bug if anything, and serious for some. installing that 500th (or whatever the breaking point would be) at the wrong time could be disastrous.
perhaps we'll her more about it this weekend when the rest of us start getting ours. only i don't really have 500 apps that i want installed, lol.

icebergisonfire said:
Updating my status. Through my own research, instead of trying to install all 500 at once, I've taken a more modest approach. I'm installing apps 4 at a time, letting it finish, powering down, then starting back up. It's working. I can get to my home screen without problem now. Maybe 500+ apps was too much of a strain for the file system to endure.
Click to expand...
Click to collapse
+1... That is exactly what I do however i install about 10 apps at a time then reboot then do another 10, ETC...
...Sent from my Tablet...Please excuse any typo's...

500 is a big number for most people. i know some people who barely have 10 apps downloaded. i've got quite a bit but definitely not 500...

Yes I would agree with that as well, I don't know that I would have a advocate having 500 applications I think I may have 30 or 40 at the most
...Sent from my Tablet...Please excuse any typo's...

I have a ton of games. When I went to my Google Play for the first time, it was like it was raining apps. :laugh:

icebergisonfire said:
I have a ton of games. When I went to my Google Play for the first time, it was like it was raining apps. :laugh:
Click to expand...
Click to collapse
Please keep in mind that some apps my not be fully compatible with android 4.3 yet.

Mine goes through the Samsung animation 5 times... I'm not sure at what point started doing that. I have around 100 apps and I feel very lazy to reset it and install a few apps at the time to see if that fixes the problem... Anyway I wonder what the apps have to do with the booting?
For reference I'm using: Nova Launcher, Swiftkey and not rooted yet.
Maybe a future update will fix this....?
Sent from my SM-P600 using XDA Premium 4 mobile app

I removed the Sd card (64Gb) and now just looped once... I'll reformat the card latter today and post back...
Sent from my SPH-D710BST using XDA Premium 4 mobile app
---------- Post added at 01:25 PM ---------- Previous post was at 12:31 PM ----------
Nope... I just formated the card and the Samsung animation still loops 4-5 times...
Sent from my SPH-D710BST using XDA Premium 4 mobile app

The question really is... Is that really a problem? Defective unit? Or an Android/Samsung software issue? Because it boots up anyway and works with no apparent problems... Is everyone else going through a similar/same issue?
Sent from my SM-P600 using XDA Premium 4 mobile app

icebergisonfire said:
Was this a problem on the first Note tablet? As I get to installing a lot of apps, over 500 is what I have, I've found that the tablet is going through an infinite boot loop. I'm talking to a Samsung rep online now about it. I've tried taking out the sd card, putting it back it, etc. It appears that some are going through this too with the Galaxy Note 3.
http://forum.xda-developers.com/showthread.php?t=2467005
Click to expand...
Click to collapse
Do a factory reset trough your recovery
Sent from my NexusHD2 using xda app-developers app

lolerpro8 said:
Do a factory reset trough your recovery
Sent from my NexusHD2 using xda app-developers app
Click to expand...
Click to collapse
DO NOT do this!! I did this on my own note 10.1 2014 after a bootlooping issue caused by corrupt files on my sd card (or so Ive theorized), and after doing so, my software showed as CUSTOM in the settings, and would not let me access the update servers. It was only after restoring the firmware via kies (a long and involved process, though less than odin, which probably would work too) that I was able to get it back to "Official". So unless you want to go through what I did, DO NOT factory reset via recovery. Id recommend doing everything else possible to fix this first.

jmwils3 said:
DO NOT do this!! I did this on my own note 10.1 2014 after a bootlooping issue caused by corrupt files on my sd card (or so Ive theorized), and after doing so, my software showed as CUSTOM in the settings, and would not let me access the update servers. It was only after restoring the firmware via kies (a long and involved process, though less than odin, which probably would work too) that I was able to get it back to "Official". So unless you want to go through what I did, DO NOT factory reset via recovery. Id recommend doing everything else possible to fix this first.
Click to expand...
Click to collapse
Dusko75 said:
The question really is... Is that really a problem? Defective unit? Or an Android/Samsung software issue? Because it boots up anyway and works with no apparent problems... Is everyone else going through a similar/same issue?
Sent from my SM-P600 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Whell then istall custom recovery and delete them manualy. This is possible only with twrp.

lolerpro8 said:
Whell then istall custom recovery and delete them manualy. This is possible only with twrp.
Click to expand...
Click to collapse
i suppose you have instructions on how to do so?

madsquabbles said:
i suppose you have instructions on how to do so?
Click to expand...
Click to collapse
Root it, install goo manager from play store, then press settings > install OpenRecoveryScript

... and root it how???

lolerpro8 said:
Root it, install goo manager from play store, then press settings > install OpenRecoveryScript
Click to expand...
Click to collapse
You do know that this tablet his only been out for 5 days and there is not root for it yet?
Sent from my SM-P600 using Tapatalk 4

ajamudc said:
You do know that this tablet his only been out for 5 days and there is not root for it yet?
Sent from my SM-P600 using Tapatalk 4
Click to expand...
Click to collapse
That means there is no twrp for it yet. And there are loads of universal rooting programs, and you can always do it over odin

lolerpro8 said:
That means there is no twrp for it yet. And there are loads of universal rooting programs, and you can always do it over odin
Click to expand...
Click to collapse
if you know how can you please share? i'd love root. even if giving knox a flip.