I need some help figuring out how to get my camera working. I bought a droid incredible that was reconditioned and planned to root and customize it for my sister, so I followed the tutorial that seemed best to accomplish this. since getting root and s-off and trying several roms all the way from GB roms to tinys cm10 I've had no luck getting the camera to work. most camera apps I've tried just leave a black screen until for closing, the JB+ camera is the only one that will appear to be working but the screen is still black, it does not actually take a picture and when I try to back out then I get the force close. I'm wondering if along the way to getting root and s-off something got messed up. I've tried installing older roms with the same result, tried installing tinys rom with no gapps and different gapps even.
I'm wondering if anyone has a sure way to test what's wrong or if anyone could just point me in the direction of a good tutorial to wipe everything and start over. I've only had a week with this phone so not a lot of time to learn about it but any help would be appreciated.
Sent from my XT875 using xda premium
Your camera is probably hosed. Did the camera ever work prior to rooting? There's nothing in the rooting process that would break the camera.
You've already stated that GB and JB have the same issue.
What you can do to help point out the cause though it may do no good is grab a logcat.
Download a logcat app like catlog and open it after getting the force close and wait for it to start displaying code and stuff on the screen. Then go to menu and save the log. This will create a log in the sdcard under a folder called catlog inside a folder called saved_logs. Can you post it up here when done? I fear it will only confirm my suspicions of a bad camera.
I will do that later today and post the log. unfortunately my inexperience and eagerness got the best of me here, I got the phone charged up after taking it out of the box and tested everything I could think of besides the camera before hacking into it. this is a last resort before trying to exchange it.
Sent from my XT875 using xda premium
I copied the text to these links, I hope this is alright.
This one is from when I opened the jb camera.
http://pastebin.com/aDEHH4V1
This one is from the stock camera
http://pastebin.com/jxRNiqfw
Sent from my ADR6300 using xda app-developers app
Stock as in stock one with the ROM and then other was JB Camera+ - which has a known graphic glitch on this device but not related to your issue.
Here's the problem:
Code:
01-02 19:01:19.352 I/QualcommCameraHardware(113): Open Device node : /dev/msm_camera/control0
01-02 19:01:19.352 E/QualcommCameraHardware(113): startCamera X: /dev/msm_camera/control0 open failed: No such file or directory!
01-02 19:01:19.352 E/QualcommCameraHardware(113): createInstance: startCamera failed!
01-02 19:01:19.352 D/QualcommCameraHardware(113): ~QualcommCameraHardware E
This is for both camera apps?
You are using the included kernel and didn't change anything weird did you?
Also, can you get the output of the following in terminal?
ls /dev/msm_camera/*
Can you RUU back to stock and test? The fact that it reports that it cannot open the camera device doesn't bode well.
Yes each link was for one of the cameras the jb camera and the stock camera as titled. I was not aware of the jb camera issue but I included it because it had a different result from the stock camera or any other I've tried. If there is another to try I'll gladly try.
I didn't change anything with the kernel or anything besides installing busybox.
This is the result from the terminal line:
[email protected]:/ $ /dev/msm_camera/*
/system/bin/sh: /dev/msm_camera/*: not found
127|[email protected]:/ $
I can look up a tutorial to RUU back and test if that's the next thing you suggest.
Sent from my ADR6300 using xda app-developers app
You missed ls. It should be
Code:
ls /dev/msm_camera/*
However, it may not be worth wasting your time. If you have a file explorer you can check the same by checking for an msm_camera folder in /dev. If the msm_camera folder exists, check there for a control0 file. However, even then I'm probably wasting your time checking this so just RUU.
Here's a good site with various incredible resources:
http://pvillecomp.com/
Yeah there is no /msm_camera/ under dev.
Sent from my ADR6300 using xda app-developers app
ok, I went back to stock 2.3.4 and the camera works! I'm very relieved it's not the hardware. now to find an updated tutorial to root this thing and try again. I'll post the results here once I'm all done and I'll try to pin point what I may have done the first time that was different so hopefully there can be a lesson learned here, at least by me.
Sent from my XT875 using xda premium
homeskool said:
ok, I went back to stock 2.3.4 and the camera works! I'm very relieved it's not the hardware. now to find an updated tutorial to root this thing and try again. I'll post the results here once I'm all done and I'll try to pin point what I may have done the first time that was different so hopefully there can be a lesson learned here, at least by me.
Sent from my XT875 using xda premium
Click to expand...
Click to collapse
Yeah. I'm glad it's not hardware. I have doubts on it being your rooting process. I believe it could be how you flashed your ROM like if you flashed ROM and mods or kernels or just the ROM and if you forgot to wipe when updating to CM10. You said you didn't install any kernels so I'm wondering how it wouldn't report that /msm_camera location unless you have the wrong kernel or somehow the wrong ROM for your Incredible.
I got time to work on this last night and I finally got it working.
first thing I did was wipe everything I could with the factory reset, clear storage and PM31IMG the stock Rom. I still had s-off and unlocked so I followed this tutorial: http://androidforums.com/incredible-all-things-root/427344-how-root-2-3-4-downgrade-get-s-off.html
I didn't have to unlock or downgrade to get s-off so I basically used this to get the right drivers and files to upgrade the hboot then root. I double checked the md5 sum on all the files after downloading them again and every time I got the phone on I checked the camera to make sure it worked after each step. once I got CWM recovery installed and got root, I made a backup then installed tinys cm10 and gapps and now all is good.
the only thing I can imagine going wrong from the first time following the tutorial is that I wasn't as careful checking the files after downloading and I didn't double check the version of software after each step to make sure it took. during the process this time while double checking the software version after flashing the rom, I noticed it didn't take so I had to repeat that step.
this made me realize how important it is to check everything as you go. many thanks for all the help!
oh yeah! the other that was different this time is that I had an sd card installed and formatted to fat32. the first time I didn't have one until after everything was done. I noticed before I started last night that the external storage would not mount. once I wiped everything then I was able to mount the sd card. I'm not sure if that would have anything to do with my problem but I have noticed other threads where people had problems mounting sd cards. anyways, thanks!
Sent from my XT875 using xda premium
Related
Disclaimer: I didn't create Boot Manager and am not affiliated with the developers in anyway.
I didn't see anyone posting this yet so I figured some of you might be interested.
There's an app on the market now called Boot Manager that's 2.99 and allows you to dual boot up to 5 roms. You still have your main rom which is stored directly in your phone's memory and then up to four more that are stored and run from your sdcard. Because you're running secondary roms from your sdard those may not run as fast as your main phone rom but my preliminary testing has been pretty good.
Boot manager is simple to set up and use and requires no special skills. You don't even need to partition your sdcard.
All you have to do is put whatever roms you wish to run on your sdcard and then install them through Boot Manager. Initially setting up the roms takes maybe 15 minutes but once your done you can boot back and forth very quickly, much faster than doing nandroids.
Enjoy
Update: I'm now running 2 AOSP roms Kushdeck's 1.3b2(main rom) and SalvageMod 1.4 and a Sense rom SynergyRls1 and haven't noticed any major issues. Gps works on each rom as well as 4g. Synergy does have some lag and for this reason took some patience and a little longer to initially set up but it works decently for running off of an sdcard. On a side note I've heard claims that Synergy does have some lag issues running normally.
I plan on ordering a better sdcard with a faster class rating such as class 4 or 6 so hopefully this will decrease lag but overall I'm very impressed with Boot Manager. If nothing else this gives you a chance to test drive roms without having to go through the whole process of replacing your daily driver.
PLEASE READ: I've reached out to one of the developers of this app who's from XDA and asked for his help in answering the problems some of you are having. I wish I could help more especially since this a paid app and you guys deserve to have an app that work. Below are the links to email support through the app website as well as the one of the developers Conap who's from XDA. Maybe if they receive enough emails they will shoot over to this thread to help.
Sorry I can't help more. All I can do is verify that it's working on my Evo but don't have enough advanced skills to do a lot more.
App Support Address: [email protected]
Conap Contact (One of the Devs from XDA): http://forum.xda-developers.com/member.php?u=2468293 (I just pm'd him)
aerajan said:
Disclaimer: I didn't create Boot Manager and am not affiliated with the developers in anyway.
I didn't see anyone posting this yet so I figured some of you might be interested.
There's an app on the market now called Boot Manager that's 2.99 and allows you to dual boot up to 5 roms. You still have your main rom which is stored directly in your phone's memory and then up to four more that are stored and run from your sdcard. Because you're running secondary roms from your sdard those may not run as fast as your main phone rom but my preliminary testing has been pretty good.
Boot manager is simple to set up and use and requires no special skills. You don't even need to partition your sdcard.
All you have to do is put whatever roms you wish to run on your sdcard and then install them through Boot Manager. Initially setting up the roms takes maybe 15 minutes but once your done you can boot back and forth very quickly, much faster than doing nandroids.
Enjoy
Click to expand...
Click to collapse
Fantastic alternative to being able to update prl/data profile on aosp considering that functionality hasn't been adapted to aosp yet.
mattykinsx said:
Fantastic alternative to being able to update prl/data profile on aosp considering that functionality hasn't been adapted to aosp yet.
Click to expand...
Click to collapse
Yea that's a good point. I'm running Kushdeck's 1.3b2 gb aosp as my main rom and didn't even think of that.
https://market.android.com/details?id=com.drx2.bootmanager
Alright, this looks really great. Love the idea. Just wondering for those who have it, since there are different kernels associated with each ROM (going from CM to Synergy) would you have to go back in and wipe battery stats? Also, would vipermod carry from ROM to ROM or would you need to set it up for every ROM?
How much room on the SD card would you need to boot 5 ROMS?
edit: quite a bit of room, have over a gig on sd card and can't load synergy. Have to do some cleaning later. Wish it could import nands, that would rock.
edit 2: cleared room, installed synergy on slot 1, rebooted, hanging on evo 4g screen..... bah
Im trying this now. I have Mikg as my phone rom and installing miui as a test. Will report back when I do some testing on kernals and battery life.
I'm getting error on editing boot.img when trying to install salvage.
Edit: even though this is an app, someone move it to the dev section. Needs more attention.
Sent from my PC36100 using XDA Premium App
i need some more instructions. What are we supposed to wipe in the Rom Installer section? Also, how do you flash Gapps?
hasn't worked yet, boo... 2 battery yanks and nand restores
Edit: Got into salvagemod from synergy through the app. Didn't flash the Gapps, so it wouldn't recognize the app, so when I tried to go back to the "phone ROM", I get a "boot.img failed to flash, not rebooting" error.
yeah crazy... stuck in splash screen sooooo yay no bueno thus far...
locoboi187 said:
I'm getting error on editing boot.img when trying to install salvage.
Edit: even though this is an app, someone move it to the dev section. Needs more attention.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Try doing it again. I've had that happen. Also the developer does state that not all roms will work. I've had 1 so far not work but I know Salvage works because I'm running it as a secondary right now.
alaman68 said:
i need some more instructions. What are we supposed to wipe in the Rom Installer section? Also, how do you flash Gapps?
hasn't worked yet, boo... 2 battery yanks and nand restores
Edit: Got into salvagemod from synergy through the app. Didn't flash the Gapps, so it wouldn't recognize the app, so when I tried to go back to the "phone ROM", I get a "boot.img failed to flash, not rebooting" error.
Click to expand...
Click to collapse
Good question. That confused me first also. You only need to do wipes if you're installing a new rom over an original one in a slot. If the slot is empty you don't need to do any wipes.
I can't address the other problem since I'm not technically proficient enough with the app yet to give you suggestions. Sorry
To flash gapps just install the rom but don't reboot install gapps over the rom in the same slot.
jbrawley1 said:
yeah crazy... stuck in splash screen sooooo yay no bueno thus far...
Click to expand...
Click to collapse
Try doing it again or try another rom. My first tries didn't work either. Also as I mentioned above the developer says this doesn't work with all roms yet.
It takes a while. Since it's booting from your sdcard it's not quite as fast the first time as when you normally flash a rom. Mine stayed on splash screen for a little while to the first time I rebooted. Also try another rom just to see if that works for you.
aerajan said:
Try doing it again. I've had that happen. Also the developer does state that not all roms will work. I've had 1 so far not work but I know Salvage works because I'm running it as a secondary right now.
Good question. That confused me first also. You only need to do wipes if you're installing a new rom over an original one in a slot. If the slot is empty you don't need to do any wipes.
I can't address the other problem since I'm not technically proficient enough with the app yet to give you suggestions. Sorry
To flash gapps just install the rom but don't reboot install gapps over the rom in the same slot.
Try doing it again or try another rom. My first tries didn't work either. Also as I mentioned above the developer says this doesn't work with all roms yet.
Click to expand...
Click to collapse
Ext2 or ext4?
Sent from my PC36100 using XDA Premium App
Omfg will download and test this out ASAP and report back results!!
Sent from my PC36100
locoboi187 said:
Ext2 or ext4?
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Ext 2 because it's compatible with more roms.
aerajan said:
Ext 2 because it's compatible with more roms.
Click to expand...
Click to collapse
still no go, error building the boot
Sent from my PC36100 using XDA Premium App
Ok, well I've contacted one of the developers of this app who's also from XDA to see if he will come over here to answer some questions since I'm not able to help as much as I wish and you guys paid for this.
Also if you go back to OP I've posted links to email support or one of the devs who's from XDA. I pm'd him personally asking if he's willing to shoot over here and try to help. If you get the time send him a PM. Maybe if enough people from here contact him he will help.
aerajan said:
Ok, well I've contacted one of the developers of this app who's also from XDA to see if he will come over here to answer some questions since I'm not able to help as much as I wish and you guys paid for this.
Click to expand...
Click to collapse
Thanks
Sent from my PC36100 using XDA Premium App
It does not work on my evo. tried everything but it errors out while finishing building the rom.
Their description does say which phones it supports and EVo is not on there. They probably wont respond to any evo users (at least according to their description, since its a non supported phone).
pottyvick said:
It does not work on my evo. tried everything but it errors out while finishing building the rom.
Their description does say which phones it supports and EVo is not on there. They probably wont respond to any evo users (at least according to their description, since its a non supported phone).
Click to expand...
Click to collapse
I wonder what steps the other guy took to get it working on his evo
Sent from my PC36100 using XDA Premium App
well... ive gotten this to work with Miui as main rom, and Synergy Kingdom port 7/23 but confirmed i dont believe that synergy rls 1+God Mode ive tried tons this wont work...
pretty cool you can switch between aosp and sense pretty easily i like this lots hope in the future it becomes more stable and compatible!
I have looked everywhere before this post so my apologies if this is an incorrect posting, my ATT captivate glide camera says RECORDING FAILED nearly every time i open the camera app, i have tried clearing cache through multiple apps and through the recovery boot, and multiple camera apps like pudding camera, i've uninstalled every app i can think of that may interfere with the camera as well, i have also rooted my device hoping this would help, a reset will not help, a reflash of the rooted rom will not help either, i am open to try anything suggested as i trust the developers in this forum, i posted this as a new thread to see if anyone else has the same problem, thank you for your time and effort, it means a lot to us that are learning
Never seen that and I use the camera pretty regularly. Bum device maybe?
Never had this problem as well, I think you might have got a defective unit.
if you use your external SD card as storage, better check that one. If you use internal SD, you can check if you have a DCIM folder in it, try creating it manually if you do not see any.
i tried the dcim folder idea, now have a folder in usb storage, sd, and external sd, no luck but thank you
I found a thread with a promising solution, i deleted my camera.apk with titanium backup and got a camera mod here http://forum.xda-developers.com/showthread.php?t=1104051 , it's working now, i hope it continues to, i will post an update later if anyone else is having this problem, thanks to all involved
Still not resolved
Sent from my SAMSUNG-SGH-I927 using XDA App
I never had an issue with mine as well I would take it back to where you got it and let them see the issues perhaps they can swap it with another for you.
Can someone upload the original camera.apk and camera.odex from their device please
I can't warranty... rooted...
Sent from my SAMSUNG-SGH-I927 using XDA App
Can't you just put back the original rom.back to stock then warranty. Can't help you with the apk as I am not rooted sorry.
Sent from my SAMSUNG-SGH-I927R using XDA App
i'm waiting on a usb jig to get here to reset my binary download counter... after that i can warranty but until then i would like to solve the problem if i can, i think an app is running commands that are conflicted with the cam... i'm methodically uninstalling apps and clearing cache partition.... it seems to get cam working for a few hours... sometimes
dmw0215 said:
i'm waiting on a usb jig to get here to reset my binary download counter... after that i can warranty but until then i would like to solve the problem if i can, i think an app is running commands that are conflicted with the cam... i'm methodically uninstalling apps and clearing cache partition.... it seems to get cam working for a few hours... sometimes
Click to expand...
Click to collapse
Where did you buy the jig from? Do you know if it is compatible with the Glide? Let us know how it goes.
dmw0215 said:
Can someone upload the original camera.apk and camera.odex from their device please
I can't warranty... rooted...
Sent from my SAMSUNG-SGH-I927 using XDA App
Click to expand...
Click to collapse
Attached
Sent from my SAMSUNG-SGH-I927 using XDA App
Sweet thanks
Sent from my SAMSUNG-SGH-I927 using XDA App
vil33 said:
Where did you buy the jig from? Do you know if it is compatible with the Glide? Let us know how it goes.
Click to expand...
Click to collapse
I got the jig yesterday, tried the one for gs2, no luck, will only put phone in odin mode then says awaiting usb cable...
Need firmware
i checked my firmware using *#34971539# and it displayed null.... i need someone to upload the actual firmware please, or at least tell me what version they have.... thanks
Firmware
OK, here's where I'm at now... someone was kind enough to upload me the firmware, i install it and reboot my device and it works for about 5 minutes then fails again, i honestly think something is running in my device that is interfering with the camera.... if anyone has any ideas they would be appreciated...
I'm gonna try this again, camera still only working intermittently (about 10%).... in the service menu my cam firmware is null, a phone to cam fw write just reboots my device, i put the rs_m5ls.bin in the root of my SD card before write, not sure if i am doing this correctly, if i do a cam to phone fw dump i get a m5mo_dump.bin in the root of my SD card as well, I've formatted cache, data, system and reinstalled ICS ROM by jayjayjoker, I've flashed the stock GB firmware from samfirmware via Odin, and tried the firmware write every way i could think of each time... can anyone please explain how the firmware works with the ROM and driver, maybe i will understand it better or even detailed steps on the correct installation of firmware, I'm sure I'm missing something and the only info i can find is all spread out and not necessarily clear when i do find it, if any of you devs have any ideas please help.... thanks for your time, this is very frustrating
Hi can anybody assist me please I am trying to install the new camera all onto my Samsung glide, I have read that I use Root Explorer go to system/app and rename camera.apk and install the new file in its place.
But my problem is root explorer says that the system file is read only and cannot be renamed how do I get round this rather than using the Odin for my computer.
My issue with the camera is when in landscape it works perfect but when I switched to portraits the screen goes blank.
Many thanks.
pgunning1 said:
Hi can anybody assist me please I am trying to install the new camera all onto my Samsung glide, I have read that I use Root Explorer go to system/app and rename camera.apk and install the new file in its place.
But my problem is root explorer says that the system file is read only and cannot be renamed how do I get round this rather than using the Odin for my computer.
My issue with the camera is when in landscape it works perfect but when I switched to portraits the screen goes blank.
Many thanks.
Click to expand...
Click to collapse
I have the same problem with root explorer, let me know if you figure that out... and what exactly is "Camera All"... Thank You
I did the unbrick method to restore my download mode a few days ago and have since gone ahead and installed the latest roms/kernels(currently on latest TBSGS3 and an AGAT FI16 kernel I believe, also tried with Jellyverse ROM and stock kernel). Now when I try to run my apps with Eclipse or even doing them manually they appear to go through successfully but the app does not end up on my phone. I tried a few samples from google as well as a basic "Hello World" app and it's no good.
Eclipse will report:
[2013-01-08 13:06:06 - BasicGLSurfaceView] Uploading BasicGLSurfaceView.apk onto device '464119fa1e8c1eb'
[2013-01-08 13:06:06 - BasicGLSurfaceView] Installing BasicGLSurfaceView.apk...
[2013-01-08 13:06:11 - BasicGLSurfaceView] Success!
[2013-01-08 13:06:11 - BasicGLSurfaceView] Starting activity com.example.android.basicglsurfaceview.BasicGLSurfaceViewActivity on device 464119fa1e8c1eb
But there is no activity on my phone and no app in the launcher and no further activity in Eclipse's console.
Then when I try to manually do it with ADB I get:
c:\Android\sdk\platform-tools>adb install BasicGLSurfaceView.apk
240 KB/s (11599 bytes in 0.047s)
c:\Android\sdk\platform-tools>
I've done the uninstalling/reinstalling of kies/drivers and the offline install method and all of that. The phone is installed properly for storage mode and download mode and is seen with the "adb devices" command. The lack of errors is baffling to me. Any guesses here?
Please confirm that you're running a jb repack as a dd. The repacks aren't meant for daily use. Application issues are part of the known problems currently.
If you are running the repack, change to stock. At least rule out the kernel.
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
MoHoGalore said:
Please confirm that you're running a jb repack as a dd. The repacks aren't meant for daily use. Application issues are part of the known problems currently.
If you are running the repack, change to stock. At least rule out the kernel.
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Beat me to it. HAHA!
If you are stock, I found this in stackoverflow for a possible answer.
Make sure when you setup the emulator in the Hardware properties you add GPU emulation and set the value to yes.
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
Yes I'm using what I wrote in the original post. Without sounding snarky, your answer from stackoverflow clearly says emulator and something about graphics acceleration, and I'm on an ET4G with some sort of USB/permission/kernel issue...
I've been running non-stock everything since I got the phone about a year ago and never ran into this issue. I will try to revert to complete stock but I'm a bit hesitant to try that because two different roms and kernels(one stock) both have this same odd problem, no difference at all. I can't seem to find any similar cases online, the search terms "cant adb install no error"and every other way I've searched has brought up only problems with errors. I'll revert to complete stock and return with results.
If anyone knows a fix, or even something reasonable to try so I can use my favorite latest roms/kernels and retain development ability I will give it a try.
timhimosc said:
Yes I'm using what I wrote in the original post. Without sounding snarky, your answer from stackoverflow clearly says emulator and something about graphics acceleration, and I'm on an ET4G with some sort of USB/permission/kernel issue...
I've been running non-stock everything since I got the phone about a year ago and never ran into this issue. I will try to revert to complete stock but I'm a bit hesitant to try that because two different roms and kernels(one stock) both have this same odd problem, no difference at all. I can't seem to find any similar cases online, the search terms "cant adb install no error"and every other way I've searched has brought up only problems with errors. I'll revert to complete stock and return with results.
If anyone knows a fix, or even something reasonable to try so I can use my favorite latest roms/kernels and retain development ability I will give it a try.
Click to expand...
Click to collapse
You weren't being snarky. I didn't take it that way.
I was taking into account that you were having an install issue from console to device, which that's what I could only find it relating to.
What you've pasted didn't have any returns pointing to permissions and it seems stackoverflow is the only location with any real answers,. And what I said in post two, we know that there are application issues with the repack. That's why I suggested going back to stock to rule out the kernel.
The repack that you're using isn't that old so you have a confirmed setup that you had working prior, why not go back to that setup and confirming?
:edit: -For the Lurkers - Had someone ask me what Eclipse is. AdamOutler did this last year. It's the only reason I know what it is.
MoHoGalore said:
You weren't being snarky. I didn't take it that way.
I was taking into account that you were having an install issue from console to device, which that's what I could only find it relating to.
What you've pasted didn't have any returns pointing to permissions and it seems stackoverflow is the only location with any real answers,. And what I said in post two, we know that there are application issues with the repack. That's why I suggested going back to stock to rule out the kernel.
The repack that you're using isn't that old so you have a confirmed setup that you had working prior, why not go back to that setup and confirming?
:edit: -For the Lurkers - Had someone ask me what Eclipse is. AdamOutler did this last year. It's the only reason I know what it is.
Click to expand...
Click to collapse
Instead of doing something as atrocious as going back to stock I tried an ICS rom/kernel(Blu Kubans) and everything is working smoothly and quickly. I only have a small sample pool of 2 JB roms and 2 JB kernels but I'm going to go ahead and assume it's a JB problem until someone with OS/hardware programming knowledge tells me otherwise(I only do apps). Can anyone confirm this by trying to run an adb install command on a JB kernel/rom? Being on a huge developer site I assumed SOMEONE would have run into this same issue, but maybe they were more content than I am about going backwards in Android versions and not bringing it up.
Again, problem technically solved but only by switching device rom/kernel completely to ICS. The whole developing on JB is a big deal to me just for the sake of being on the latest version so I'd like to keep research going. Thanks.
Hi All,
I'm am absolutely stumped and have tried what feels like everything I can to resolve my issue to no avail. So, I'm hoping to find success from the wisdom of the seasoned XDA community.
I have an SGH-T999 with baseband UVDMD5. In early September, my camera stopped working. When I open the camera app, I'm greeted with the infamous "Can't connect to camera" message. The front camera works fine (via Skype), but the rear camera does not. I've tried all of the following but the camera still won't work:
1) Unrooted and re-flashed the stock root66;
2) Finding the correct "SLIM_ISP.bin" file, placing them in the /data folder, and set the permissions to 777;
3) Re-flashed the stock UVDMD5 bootloader, firmware, and modem;
4) Took the phone to a shop to have a new camera installed and they couldn't get the new hardware to work either (so, it's definitely software related);
5) Cleared the app cache and fixing permissions in recovery;
6) Restored a Nandroid from a previous state of the device when the camera was fully operational;
I don't know what else to do. PLEASE help me folks. I really want my camera back. Thank you in advance for your time and insight.
I've attached a Catlog I recorded while attempting to open the camera, if that helps at all.
just a thought , but if you have a nandroid backup could you uninstall current camera and then grab camera from nandroid and install it ?
or if have titanium backup hit the install button on camera apk (even though its already there). these methods have worked for me with browser issues.
just an idea.
good luck.
err on the side of kindness
Have you considered replacing the camera hw? It's very easy to do and the part usually costs less than $10.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
Have you considered replacing the camera hw? It's very easy to do and the part usually costs less than $10.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Hi Doc, I tried that. Sorry. Should have listed it. I took it to a shop to have a new camera installed and they couldn't get the new hardware to work either. So, it's definitely software related.
Thanks for the suggestion though. Please let me know if you have any other ideas.
mrrocketdog said:
just a thought , but if you have a nandroid backup could you uninstall current camera and then grab camera from nandroid and install it ?
or if have titanium backup hit the install button on camera apk (even though its already there). these methods have worked for me with browser issues.
just an idea.
good luck.
err on the side of kindness
Click to expand...
Click to collapse
mrrocketdog,
Would that work if the camera doesn't work even when the Nandroid is restored (despite that fact that the camera was functional when the Nandroid was created)? Thank you.
At this point I think that would be worth a shot. If it doesn't work though I'd have to say it sounds like it could be hardware related, even though you replaced the module. Might be a problem on the motherboard or something like that.
The only other thing I can think to try though is to flash a 4.1.1 rom. Then using the hidden code to write the camera firmware to the device. If the firmware got corrupted somehow, this could fix it. The problem though, is if you've updated to 4.3 firmware, it probably won't work. They patched against our ability to write the cameras firmware ourselves. If this was done in the controlling app, it may just work. However, if it was patched in the base firmware, there won't be any way I know of to do this.
I'll post the code in a min. Gotta hunt it down again...
Sent from my SAMSUNG-SGH-I747 using Tapatalk
---------- Post added at 12:16 AM ---------- Previous post was at 12:07 AM ----------
Ok here are the codes:
*#34971539#
*#7412365#
Enter in the stock dialer.
I'm pretty sure the first one is the one you need, but both are camera codes which is why I gave both.
If it works, it will open a menu called Camera Firmware Std
You can check the firmware versions first if you like. If the phone fw is older than the cam fw, and you do this, it is possible you could loose some features. But if so, I imagine flashing the device firmware again will update back to where it should be.
To write the camera firmware, just choose Phone to Cam FW Write.
Good luck!
Sent from my SAMSUNG-SGH-I747 using Tapatalk
halebopper said:
mrrocketdog,
Would that work if the camera doesn't work even when the Nandroid is restored (despite that fact that the camera was functional when the Nandroid was created)? Thank you.
Click to expand...
Click to collapse
i think that would be the point. the camera was functioal when the nand was created.
dont know exact function , but what about going into recovery and fixing permissions.
and going into settings>apps>camera and clearing cache ? wouldnt take but a minute and it already doesnt work so....
err on the side of kindness
mrrocketdog said:
i think that would be the point. the camera was functioal when the nand was created.
dont know exact function , but what about going into recovery and fixing permissions.
and going into settings>apps>camera and clearing cache ? wouldnt take but a minute and it already doesnt work so....
err on the side of kindness
Click to expand...
Click to collapse
Thank you for your response and the suggestions.
That point makes complete sense. However, what I'm saying is that I've restored s Nandroid from a state when the camera was functional. However, the camera still doesn't work despite restoring a Nandroid from a previously operational state. So, please correct me if I'm wrong, but, considering that, what good would extracting the apk from the Nandroid do if restoring the entire Nandroid doesn't make the camera work?
Regarding your second suggestion, I have tried clearing the app cache and fixing permissions, but it didn't work. I'll add this to my list of attempted fixes in my original post.
Thank you very much mrrocketdog. I sincerely appreciate your continued interest and support. I hope we can figure this out.
well dang it ! hopefully someone else will chime in with some ideas. sorry i didnt have anything new. will keep thinking.
err on the side of kindness
DocHoliday77 said:
At this point I think that would be worth a shot. If it doesn't work though I'd have to say it sounds like it could be hardware related, even though you replaced the module. Might be a problem on the motherboard or something like that.
The only other thing I can think to try though is to flash a 4.1.1 rom. Then using the hidden code to write the camera firmware to the device. If the firmware got corrupted somehow, this could fix it. The problem though, is if you've updated to 4.3 firmware, it probably won't work. They patched against our ability to write the cameras firmware ourselves. If this was done in the controlling app, it may just work. However, if it was patched in the base firmware, there won't be any way I know of to do this.
I'll post the code in a min. Gotta hunt it down again...
Sent from my SAMSUNG-SGH-I747 using Tapatalk
---------- Post added at 12:16 AM ---------- Previous post was at 12:07 AM ----------
Ok here are the codes:
*#34971539#
*#7412365#
Enter in the stock dialer.
I'm pretty sure the first one is the one you need, but both are camera codes which is why I gave both.
If it works, it will open a menu called Camera Firmware Std
You can check the firmware versions first if you like. If the phone fw is older than the cam fw, and you do this, it is possible you could loose some features. But if so, I imagine flashing the device firmware again will update back to where it should be.
To write the camera firmware, just choose Phone to Cam FW Write.
Good luck!
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Hi DocHoliday77,
Thank you very much for the reply and the suggestion. Your advice seems sound.
I'm not sure what you mean by "controlling app." I'm afraid my knowledge is too limited to tell you if I've flashed the 4.3 firmware.
Not sure if this helps, but I have intentionally not upgraded beyond the stock baseband UVDMD5 version. I understand the baseband versions following UVDMD5 are bad due to the addition of KNOX and the inability to flash back to previous baseband versions.
Currently, I have flashed Carbon rom, which states the Android version is 4.4.4. However, I don't know if the Android version number is reflective of the firmware.
Regarding flashing a 4.1.1 rom, is there a rom you suggest that would be better for this than others? Should I just grab an older version of Carbon or would it be best to use Odin to flash back to a stock root66 version of 4.1.1 ?
Btw, not sure if you saw, but I uploaded a Catlog I recorded while trying to launch the camera app. I don't know if that will reveal anything or not. I can't make two cents of Catlogs other than to identify that errors are occurring. I really hope this isn't a faulty motherboard.
Thank you again for your continued interest and support. I really appreciate your advice. It means a lot. I hope we are able to resolve this.
If you never updated beyond 4.1.2, you can fully downgrade to 4.1.1 and try that method I posted. The app is just the one that controls the cameras dialer code. You don't really need to worry about it. Don't remember which it is right now anyway...
If you like though, first just flash stock 4.1.2. The code might work there. I just can't remember if it was patched there or in 4.3. You'll know you need 4.1 1 if you open it and the firmware write choice is greyed out.
I suggest just flashing the root66 firmware rather than a rom. This way everything you need is included. If it does solve the problem you can flash back to whatever you like.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
If you never updated beyond 4.1.2, you can fully downgrade to 4.1.1 and try that method I posted. The app is just the one that controls the cameras dialer code. You don't really need to worry about it. Don't remember which it is right now anyway...
If you like though, first just flash stock 4.1.2. The code might work there. I just can't remember if it was patched there or in 4.3. You'll know you need 4.1 1 if you open it and the firmware write choice is greyed out.
I suggest just flashing the root66 firmware rather than a rom. This way everything you need is included. If it does solve the problem you can flash back to whatever you like.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Ok Doc. I flashed root66 T999 UVDLJC (Official JB Firmware - Latest JB 4.1.1 Firmware). After rebooting the phone, I entered the first code you provided - *#34971539# - into the phone dialer. This pulls up an all black screen with a gray colored placeholder/header at the top that reads, "CameraFirmware Standard." Again, other than the gray header and title, the rest of the screen is all black with no text or anything, except for the notification bar at the very top. Then, after sitting on that screen for a few seconds, it closes and the message, "Unfortunately, Factory Test has stopped," displays in a pop-up message.
I can make my assumptions about what that means, but I'd prefer your opinion. What do you think?
Thank you again for your time, insight, and assistance. I respectfully look forward to your response.
p.s. Just to clarify my experience for potential future readers, the second code you provided - *#7412365# - didn't work. It displayed, "Unable to process request" in a pop-up message.
That tells me that the system is most likely having problems communicating with the camera.
I'd open it up and make sure it's properly connected. It's very easy to do. You can find disassembly videos on YouTube if you want to see what to look for first.
If the shop couldn't get a new one to work, I'm honestly not sure what else you can try. It does sound like a hardware issue though. My best guess is its got something to do with the motherboard.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Ok let me be really specific i have flashed stock firmware through odin, i have done clean wipes, i have done every possible thing in my power but still experience horrible tablet preformance i get app stops and restarts everytime even after i have flashed on odin no one here has been able to help me they tell me to do the same thing over and over download stock firmware and flash, do a clean wipe iv'e done it all please help i know someone can i think its a file in the screenshots i enclosed that is corrupted but i have no idea which one is it. its not the system or the kernel it is something deeper please help i am begging you developers
k,
no offense, but your post is wildly disrespectful. [frowny face]
you are basically putting the proper ownership of your error off on others.
to be fair, in your ignorance you flashed a firmware without first doing some research on the topic.
a noobish mistake, it happens, i've done it.
there were plenty of threads created prior to your experience warning of new samsung releases
overwriting bootloaders and how to navigate the issue.
from my interaction with you, i think i am accurate in saying you did not do the aforementioned research.
i for one took time to describe a way to "fix" your issue. You chose not to attempt it, which is fair. It is risky.
Cool.
However, lots of the users you've interacted with on xda have a fair to expert handle on how to get things done.
they do what they can to help, they cannot be expected to compensate for another's impatience, lack of attention
to detail and/or incompetence/ineptitude.
m
What are you talking about i am not blaming a single soul for anything, i have been flashing roms and firmwares for years now. Somehow something went wrong and i am asking for help. I flashed the official firmware from sammobile for the sm t210r i booted into stock recovery and factory reset. And still i get the same results don't take pleading for direspect i am just frustrated not with anyone but with the tablet believe me it wasn't like this a month ago
kgalv419 said:
What are you talking about i am not blaming a single soul for anything, i have been flashing roms and firmwares for years now. Somehow something went wrong and i am asking for help. I flashed the official firmware from sammobile for the sm t210r i booted into stock recovery and factory reset. And still i get the same results don't take pleading for direspect i am just frustrated not with anyone but with the tablet believe me it wasn't like this a month ago
Click to expand...
Click to collapse
hmm,
okay, different approach.
http://m.youtube.com/watch?v=JmvCpR45LKA
just a refresher.
now,
screenshots of directories are next to useless.
what's needed is , at the very least a logcat.
to get that or anything else moving you need,
custom recovery installed.
root.
busybox.
adb setup properly on pc.
the ability to describe you problem in words other than my thing doesn't work.
the sense not to keep creating thread after thread concerning the same issue.
if you are that insistent on undoing what you have done, my previous suggestion to you is probably the best bet.
if you want "Professional" help then seek a repair service.
Savvy?
m
Gee thanks for the video very eye opening. Will post a logcat then i have all the things u mentioned recovery,adb etc all i require is clear steps to follow into fixing this lil issue and i will b a happy camper. N yes bro i savy don't be so serious i can see that your an intellectual an i respect that and apreciate any help u can offer
kgalv419 said:
Gee thanks for the video very eye opening. Will post a logcat then i have all the things u mentioned recovery,adb etc all i require is clear steps to follow into fixing this lil issue and i will b a happy camper. N yes bro i savy don't be so serious i can see that your an intellectual an i respect that and apreciate any help u can offer
Click to expand...
Click to collapse
k,
okay, cool. sorry for being so rough on you.
i am downloading a copy of 4.4.2 firmware though linking me to the firmware
you initially flashed would be good.
what would be better is if you still have the firmware file crack it open with 7zip and get me a list
of the files [.img, .bin] inside.
run logcat after you boot up. attach to post as text file
then run your routine to where you get your issue, fc's etc and run logcat again and post as text [2]
m
okay it looks like i am not going to be downloading the 4.4.2 firmware.
downloads break from the one source i found
and i have no interest in joining the other site. that's bull****.
so if you can get me the list of files contained in the realease that would be helpful.
OK bro I narrowed it down to it not being a ROM or firmware issue here is my log, the firmware that I flashed was from sammobile its a tar file and 7zip can't open it. Currently i am on tranchikat 1.8 the " unfortunately app stops" still persist its not really force closes its stops hope you can deduce something off the log and again thanks very much bro it doesnt matter how long it takes.
kgalv419 said:
OK bro I narrowed it down to it not being a ROM or firmware issue here is my log, the firmware that I flashed was from sammobile its a tar file and 7zip can't open it. Currently i am on tranchikat 1.8 the " unfortunately app stops" still persist its not really force closes its stops hope you can deduce something off the log and again thanks very much bro it doesnt matter how long it takes.
Click to expand...
Click to collapse
k,
dude, where's my car ? [log ?] :silly:
m
Here bro
kgalv419 said:
Here bro
Click to expand...
Click to collapse
k,
i am going to guess you are trying to run a battery/governor tweaker ?
i am going to guess when you type getenforce in terminal
your output will be enforcing.
i am guessing when you resend your logcat you will do so after
typing su
and then
logcat -d > /sdcard/logcat.txt
if my guesses as to the app and selinux are correct you;
a- need to let the app go into the dustbin of history
b- need to look for a tutorial on dumping/unpacking/customizing/repacking/reflashing your boot.img
in order to disable selinux and make it stick.
if my guesses are wrong it is because;
the log you posted is super-lame [sorry] use your terminal, not a catlog app.
you have yet to tell me what app are giving you your headache. in which event is an issue between you
and the app's developer.
lastly you should be question the developer of the rom.
m
Bro its not any specific app I'll give you an example. Say I am going to settings doing whatever all of a sudden boom "unfortunately settings have stopped". Say I am on my browser browsing a way I go to my bookmarks boom " unfortunately internet has stop". It does it randomly not evrytime but at random "unfortunately touchwiz has stopped" etc the apps will close an I can start them again and they will run normally until another random stop. I have tried all costom Roms on here and still have the issue so I know its not a ROM problem, I have flashed my stock firmware both 4.1.2 and 4.4.2 and it persist so that rules out it being those either. But I will do what u said and use terminal to get the log. So far what I can tell its not the apps nor the ROM nor the kernel that is causing the stops and random reboots.
kgalv419 said:
Bro its not any specific app I'll give you an example. Say I am going to settings doing whatever all of a sudden boom "unfortunately settings have stopped". Say I am on my browser browsing a way I go to my bookmarks boom " unfortunately internet has stop". It does it randomly not evrytime but at random "unfortunately touchwiz has stopped" etc the apps will close an I can start them again and they will run normally until another random stop. I have tried all costom Roms on here and still have the issue so I know its not a ROM problem, I have flashed my stock firmware both 4.1.2 and 4.4.2 and it persist so that rules out it being those either. But I will do what u said and use terminal to get the log. So far what I can tell its not the apps nor the ROM nor the kernel that is causing the stops and random reboots.
Click to expand...
Click to collapse
k,
okay, this ---> android.permission.INTERACT_ACROSS_USERS_FULL is the ballbuster.
it's connected to , from what i've read so far , a maybe faulty root and multiuser.
what version supersu are you using ? unroot and then reroot trying from version 1.97 maybe to 1.99.
kill multiuser and clear out any suspect accounts in settings. will post back if i find something more conclusive.
you can jump in as well by searching the error i mentioned.
android.permission.INTERACT_ACROSS_USERS_FULL
m
@kgalv419
edit after rooting set actions to auto grant permission and trust system
EDIT - disable xposed modules - xprivacy if you're running it.
QUESTION - THIS IS A JELLYBEAN ROM ? seems to be a jellybean issue...
EDIT-EDIT i found this... http://forum.xda-developers.com/gal...card-app-data-to-extsdcard-tw-t2178863/page16
read that page looking specifically at the portion concerning /system/etc/permissions/platform.xml
you may need to add/edit the line for
android.permission.INTERACT_ACROSS_USERS_FULL
with the proper uid [user identification] meaning the right number/symbol for root,shell,ewok, etc.
the entry looks something like this;
<assign-permission name="android.permission.INTERACT_ACROSS_USERS_FULL" uid="shell" />
and remember to reset the file's permissions correctly - 644
Nah it happens on both jellybean and KitKat for me I don't think its the root because when I flash the official samsung firmware through Odin it is basically unrooted and the problems persist
iI tell you when it first started. I was on jellybean then the kitkat update for the sm-t210r came out, I flashed it via Odin and from then it started
So naturally I downgraded back to jellybean but the issue it stayed, so that's basically the history of the random app stops and random reboots.
kgalv419 said:
Nah it happens on both jellybean and KitKat for me I don't think its the root because when I flash the official samsung firmware through Odin it is basically unrooted and the problems persist
iI tell you when it first started. I was on jellybean then the kitkat update for the sm-t210r came out, I flashed it via Odin and from then it started
So naturally I downgraded back to jellybean but the issue it stayed, so that's basically the history of the random app stops and random reboots.
Click to expand...
Click to collapse
In a situation like this thinking is guessing = no good.
re-read previous post. search, test, verify. Don't guess [think].
m
Yes bro trust me I'm trying
Are you able to flash CWM and root your device ?
I will advise what is next to be done....
Sent from my SM-T211 using XDA Free mobile app
Yes I already have it rooted with philz touch recovery
Wipe format every single partition that you see remove 1st your ext sd card this will empty all folders then redo tne Odin part
Sent from my SM-T211 using XDA Free mobile app
By every single partition you mean including those folders like acc, and others in the device?