I wanted to ask someone with expertise regarding my d2tmo.. I am experienced with flashing roms and anything with rooting and trying roms. I wanted to ask you about a camera issue I am having. The problem is when my camera is using flash to snap pics and also sometimes when making videos without flash my system crashes and forces reboot. Before seemed like was only in aosp roms and i was thinking it could be just that cm10 bug with the cameras, but then I noticed it was happening in Tw roms and so i odin flashed stock firmware and the problem still persists. I asked someone before and they told me it for sure was a software issue and not hardware, but since I was on stock seems like could be hardware. Have you heard if this happening before? could you offer me some kind of insight for this? I am sending the phone back to tmo and getting a warranty replacement for another issue ( and yeah i triangle awayed lol) , but i was wondering if this would happen still with the new phone if i decided to flash some custom roms.. Is there a chance that samsung could of improved components or did anything different since I bought my s3 last october? I am sorry for the long story, but I really can't find help anywhere else and I really use my camera alot for work.
thanks in advance.
- J.RAD
Related
I have the EVO Rooted (the real way) and ever since installing cy's senseless RC I've been having issues with the screen registering a tap on the top left corner about 1/4th the way down the screen so I'm constantly closing the calander or whatever else I have in that area, this is including programs, phone calls etc. I was literally fighting with my phone the other day. Now I've reinstalled a 2.1 rom and it didn't do it and I've installed multiple 2.2 roms and it still does it. I thought it might be the fps uncapping hack most people include so I figured once the stock rom from sprint came out and was rooted for us it would fix my problem. Wrong... Now I'm stuck between a rock and a sprint store as I can't make it happen constantly but it happens maybe 5 times throughout the day and I have to just wipe my fingers over the area of the screen and its usually fine. I want to install the Stock rom, essentially un-rooting my phone but then if that fixes the problem I cant take it back and exchange it at sprint. Or I cant make it happen for them and then I'm stuck again with a phone that I can't root. Any ideas guys, is this happening to anyone else? I've researched online and haven't seen anyone else with a similar problem.
first off, whats the "real way" for rooting?
if unrooting fixes your problem whats the problem? is there some reason you MUST have a rooted phone? are you doing anything that you otherwise couldnt do with a rooted phone?
many people are experiencing phantom screen presses (myself included), also many people arent.
if its a rom issue, then check in the dev secion for the rom and see if anyone else is having this problem. sounds like a screen problem.
nenn said:
first off, whats the "real way" for rooting?
if unrooting fixes your problem whats the problem? is there some reason you MUST have a rooted phone? are you doing anything that you otherwise couldnt do with a rooted phone?
many people are experiencing phantom screen presses (myself included), also many people arent.
if its a rom issue, then check in the dev secion for the rom and see if anyone else is having this problem. sounds like a screen problem.
Click to expand...
Click to collapse
The real way for rooting not the unrevoked method.
Every rom after a certain kernel version does it to my phone but I couldn't begin to guess which one with all of these different version floating about. I can flash back to EVOlutionX and it doesn't do it, not that I've seen yet. If unrooting my phone fixed the problem then as I said I obviously would not be able enjoy a rooted phone. I'm not even going to begin listing the benefits of a custom rom or creating my own which I've done in the past. I was going to post in all the particular rom threads but I figured instead of posting multiple repeated threads since it happens in ALL of them, then I would do the forums a favor and post in the general Q&A section as I did. So who else is having phantom screen presses as myself and nenn are, and have you done anything to correct the problem?
Update: I found a forum post on another site of a person who took the OTA update 1.47 completely stock and its doing the same thing. I think I'm going to wait until its happening and catch it on video and then flash back to stock and take the evo in for warranty replacement. Hopefully they will accept this as reason for replacement.
Ok So I'm having some issues with my SGSII
I am rooted and I'm running Juggernaut v3.7
When I try and use my camera app I get a warning: camera failed message
It started off happening after my phone had been on for a while (I would get the error message and then reboot and the camera would work fine for a short amount of time, before the error message returned) now I am getting this error message constantly and the only way to get the camera working again is If I reboot into CWM and wipe data,cache,dalvik & reboot or go through the wipe process and re-flash the Juggernaut v3.7 rom. But still even doing so only enables the camera once and then I'm back to my original issues. I've searched the site and other resources available before making this post. Most of the information I have come across with users having similar problems refer to the I9000 and not the SGH-T989.
So my questions are (of course):
Has anyone had these issues?
Has anyone that has had these issues (if any) found a solution?
And does anyone know If this is hardware or firmware related? - (Or can someone point me to the right procedure of figuring out if it is a hardware or firmware issue?)
Hope to hear from someone soon thanks XDA
Sounds like hardware, or could be kernel, you could try a different kernel ..
Best way would be to Odin back to Stock, and see if it still does it, if it does it on pure stock , you know it is a hardware issue ...
tcboo said:
Sounds like hardware, or could be kernel, you could try a different kernel ..
Best way would be to Odin back to Stock, and see if it still does it, if it does it on pure stock , you know it is a hardware issue ...
Click to expand...
Click to collapse
Thank you for the reply, I have found a solution to the problem (so far at least no issues) I removed the sd card, re-inserted the sd card and did an sd card format and the problem has gone away. Well at least for the last 12 or so hours anyways. Hope this helps anyone with the same problem.
I was just about to say, check your SD card. Same damn thing happened to me a few weeks ago. All it takes is one corrupted image on the card to completely bork the camera.
kabuk1 said:
I was just about to say, check your SD card. Same damn thing happened to me a few weeks ago. All it takes is one corrupted image on the card to completely bork the camera.
Click to expand...
Click to collapse
Yeah, I was just messing around with it and figured out that the sd card format may have been corrupt, or it could have been a bad file messing with the camera process in android. T-mobile actually sent me a new one that should be delivered today, I'm going to have to send it back now that I have it figured out. lolol
**BTW** I'm using your throttle fix lolol thanks
No problem, glad to help
Hey...not so fast...LOL!
Totally hate to revive such and old thread, but I am currently experiencing the exact same issue using Juggernaut 5.0, and the VKL1 radio, with faux10m kernel. I have in fact remove all external sd cards, and still the camera app keeps giving me Camera Failed. I'm wondering if I install a differnt camera app from Google Play, if this will be a solution? Any tips/advice is quite welcome. I'll be back and let you know if installing another camera app works! Thanks in advance.
I had the same message as the OP pop up when I had my vibrant. I ended up having to buy a replacement camera.
Sent from my SGH-T989 using xda premium
This happened to me after throwing my phone at my bed, it bouncing off, and hitting the wall. When activating my camera, I got the message.
Called T-Mobile, told them the problem, and got a refurb. Now my phone has all sorts of problems!
When activating the camera on stock rom, rooter stock rom or custom rom the camera will lock up the phone, screen will turn off and a battery pull must be done to get the phone rebooted. Doesn't seem to matter the rom. Still the same effect.
Back story:
So my sister in law came to visit with her nice new shiny sgsII (t989). She got it from her friend who happens to be a tmobile salesmen in Seattle. She was told that the camera didn't work cause he downloaded something. But took it anyways (since he is her friend and she got it for free).
I thought I'd take a crack at it. Tried a factory reset. Same issue. Found that it was stock 2.3.5 and NOT rooted. Thought maybe a new camera app would fix it thinking the app would hook into the os/hardware and not the default camera.apk.... Same deal.
Last step I tried before coming here was to install a custom 2.3.6 ROM. It got to the standard camera screen but with nothing coming from the camera (black screen) and locked up before needing a battery pull.
I've come to the conclusion that her friend either tried to flash a different cameras firmware on the t989 or dropped it in the toilet OR BOTH!
What do you guys think the issue is?
Why would he want to flash different camera firmware?
I'm stumped. She is here on vacation and that phone is her camera.
da_dragon2k3 said:
When activating the camera on stock rom, rooter stock rom or custom rom the camera will lock up the phone, screen will turn off and a battery pull must be done to get the phone rebooted. Doesn't seem to matter the rom. Still the same effect.
Back story:
So my sister in law came to visit with her nice new shiny sgsII (t989). She got it from her friend who happens to be a tmobile salesmen in Seattle. She was told that the camera didn't work cause he downloaded something. But took it anyways (since he is her friend and she got it for free).
I thought I'd take a crack at it. Tried a factory reset. Same issue. Found that it was stock 2.3.5 and NOT rooted. Thought maybe a new camera app would fix it thinking the app would hook into the os/hardware and not the default camera.apk.... Same deal.
Last step I tried before coming here was to install a custom 2.3.6 ROM. It got to the standard camera screen but with nothing coming from the camera (black screen) and locked up before needing a battery pull.
I've come to the conclusion that her friend either tried to flash a different cameras firmware on the t989 or dropped it in the toilet OR BOTH!
What do you guys think the issue is?
Why would he want to flash different camera firmware?
I'm stumped. She is here on vacation and that phone is her camera.
Click to expand...
Click to collapse
how does one flash a camera firmware?
So this happens on every camera app?
Don't know how one would flash the camera firmware. It was an educated guess. From the info I was told "he downloaded something and now the camera doesn't work" is the only thing I could conclude from that.
On the Samsung Vibrant people would use alternative modified camera.apk or use custom kernels to get the front facing camera working but never seen of anyone changing firmware before.
I have tried technically 4 different apps. one from the stock rom, 2 from the market. PUdding camera and the other I don't recall off the top of my head. They both did the same thing. Which brings me to believe it is either the driver (which could be fixed by a different kernel) or the hardware. Come to think of it, it wasn't rooted when she got it. So I doubt he flashed anything. Unless he odin'd something....
Just got done talking the the previous owner. Turns out all he did was installed some official Google apps from the market place when this happened. Doesnt seem like he did anything wrong. He told me of two other issues that started at the same time as this one. Video playback will reboot the phone and web video reboot as well.
Got a workaround for the video playback: installed mx player and set it to render A/V in software mode. Not the best solution, but it works.
Online videos crash. IE any site with heavy flash. Updating flash didnt solve it nor an uninstall/reboot/reinstall.
That's where I'm at. 1 step forward 2 steps back...
Hate to do this, but..
Bump
I've been getting these glitches/artifacts/tearing on any 4.4+ rom on my T-mobile S3.
It's like the status bar will glitch down to the bottom of the screen.
I'm currently on a 4.3 stock rom (ENC2), It's been rooted with the samsung toolkit and has knox disabled (at least according to the app).
I've tried most current d2lte roms, PA, spirit, ACIP...ect.) and they all have it.
I know for a fact I'm missing something. I just can't remember what it is for the life of me. I know it has something to do with the bootloader/binary. I seem to remember when 4.4.1 came out there was something with the bootloader we had to do and no matter what I search nothing is coming up with the correct solution.
I'm hoping someone could tell me what i'm missing because it seems painfully obvious and I'm missing it, . I really don't enjoy using TW.
We don't ever mess with the bootloader or other parts of the base firmware, so maybe you're thinking of a different device?
When did it start? What was the last thing you did (flash)? Tbh, to me it sounds like a hardware problem. Maybe a connector got loosened, or some moisture/water damage, or even heat damage could cause what you are describing. Especially if its happening on every ROM.
Flash the stock NC2 firmware via Odin and factory reset. If it still happens after that its almost certainly hardware related.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Does it also happen with touchwiz?
So. I ran the knox removal thing from the samsung toolkit and now I don't see them on the latest CM nightly.
I have to test a few other roms but I don't know, it's somehow fixed, thank you for the responses.
Glad to hear it. Be careful with the toolkit though. It is not supported and has bricked devices.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
After giving it a few days the issue came back.
I've tested this on a stock nc2 touchwiz as well as your (doc) latest likewise release with no issues with the screen or anything.
For the non touchwiz I tried aicp latest 4.4.4, the latest cm11, the latest aospa weekly and a 4.3 AOKP release (milestone2).
The glitch issue wasnt in the cm release for a day or so then showed up, all others showed up instantly.
I also emergency recovered via kies. Then rerooted. I'm also using the latest twrp
Here is a logcat of the ROM I'm currently on, the 4.3 AOKP. I wish I had more of an understanding of logcats so i knew if I posted the right section.
http://pastebin.com/UyZFHriB
I was curious so I booted up a nandroid of aicp and then restored a backup of the boot from likewise. Results were minimal glitching but no connectivity at all. APNs didn't load and WiFi is broken. I'll post a video shortly of the screen.
The only thing that jumps out on that logcat is where you have this kind repeated several times in a row:
09-18 13:35:38.752 W/ActivityManager( *761): Permission denied: checkComponentPermission() owningUid=10060
But I honestly don't know what its referring to. But I will say that since it appears to be happening on every rom, even stock, it sounds more like a hardware issue. Display problems usually are to begin with, but almost any problem that persists across multiple ROMs and wipes can usually be blamed on a hardware malfunction.
Watch a disassembly video on youtube, then open it up and reseat all connectors. (Don't mess with the antenna. Its fragile and not related to the issue at hand.)
Sent from my SAMSUNG-SGH-T999 using Tapatalk
DocHoliday77 said:
But I will say that since it appears to be happening on every rom, even stock, it sounds more like a hardware issue.
Click to expand...
Click to collapse
That's the odd thing, On both 4.3 and 4.4.2 versions of touchwiz I don't get the glitching. Only on AOSP based roms. I could just go stick with a touchwiz based rom and be done with it but my personal preference is not using touchwiz. I'm just confused as to what is actually causing this.
I'm guessing it has to have something to do with the bootloader and baseband.
I think i did forget to mention this is a "refurbished" warranty replacement, i regret that I don't recall which specific version it had as stock, I'd guess it has to be enc2?
Here is a poor quality video to show whats happening, on the home screen you see the glitching where the status bar glitches down to the bottom. I tried to get it to do what it sometimes does in both the MLB app as well as the reddit app but it decided not to be as noticeable this time.
http://youtu.be/ZsZL1Okio-A (sorry about the added music )
Just a side question, I couldn't seem to find a definitive answer, but was it ok to downgrade within the 4.3 bootloaders? I thought I remember reading that as long as you don't go from 4.3 to 4.1.2 it was fine.
Soryy I misunderstood before about it happening on stock. Have you tried any different kernels? I'd suspect that before bootloader. But since it's a refurb, there's just no telling for sure.
Once on 4.3 you cannot downgrade your firmware at all. You can flash older roms, but that's it.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Does anyone know of a vibration logger? I've been getting random vibrations for about the past two weeks on my GS4, and I want to know what is causing them. On a GPE rom, and have been on the same one since January. The issue just started, and I have not had it before. No settings have been changed recently. Just want to know which app or process is causing it so I can deal with it, since it (may) also be causing battery drain, although that could just be me being paranoid.
A logcat would probably be sufficient if you could find someone willing to take a look at it for you. I would suggest posting in the Better Battery Stats thread or the Insanely Better Battery Life thread about your issue. Those posters are extremely helpful and can help pin down your issue if you ask nicely.
I had a similar issue recently. Do you use chenxialong's dualboot by any chance?
Hey Guy, did you ever find a solution? I want the exact same thing.
It was probably the rom causing it, and most likely resolved by re-flashin rom or switching to a more stable rom.
Pp.
PanchoPlanet said:
It was probably the rom causing it, and most likely resolved by re-flashin rom or switching to a more stable rom.
Pp.
Click to expand...
Click to collapse
Noted, thanks, but mine is stock. (it'll probably be stock till the end of time. S4 zoom)
I guess there are no apps for this. Shame :/
If you're experiencing random vibrations you may have an issue with your firmware or a rogue app.
Eliminate some apps and see if issue corrects itself or flash stock firmware.
I also run stock /rooted /no bloat and everything works the way it's supposed to.
Pp.