[Stock After SBF .340] Broken Torch/Camera/Camcorder - Droid X General

Ok, so I'm the same guy who had the torch/camera/camcorder problems a couple weeks ago on CM7.
I thought (for some reason) that a new nightly would fix my problems...so I've patiently waited and finally nightly 96 came out. Didn't fix it.
Unfortunately, I just SBF'ed and then checked my camera...which now doesn't work on stock either.
The thing that makes me think it ISN'T hardware related is that my torch doesn't work either.
Also, the camera application doesn't even attempt to take a picture (as it does on CM7) it simply blackscreens...and if I press the camera button (either physical or on-screen) it either locks up or does nothing but act like it took a picture. Nothing shows up in the gallery either.
Again, my torch/camera/camcorder worked FINE before. And I'm pretty careful with my phone...I haven't dropped it or anything like that.
HOWEVER, The camcorder seems to record sound...and a pitch black screen.
Odd.
So...
As a potential fix, I flashed the maderstcok340.zip after formatting system and wiping cache.
Still no camera/torch.
SBF'ed AGAIN...still no camera/torch.
Possible fixes from my prior thread that were never fully executed:
Init.mapphone_umts.rc <---is this file able to be swapped from phone to phone?
Or is it safe to post the file here for ya'll to verify that everything is how it should be?
Duplicate .lib files were also mentioned.
Where should I be looking for those?
I just downloaded "alogcat" from the market since my symptoms don't match up with the usual problems we have...
Here's what it spit out:
http://pastebin.com/SGLsneFv
In case it's needed...
I started alogcat.
Pressed the Hard Camera Button.
Tried to take a picture.
(Had to back out of camera app in order to switch to camcorder)
Toggled Light to *on*
Recorded a couple of seconds with the camcorder.
Edit:
After me and razorloves_DX from rootzwiki went on a spamming session of toubleshooting...we've decided this is definitely a hardware problem.
Feel free to ignore this thread, as I'll have to send my phone in to fix it =/

Related

I think my Dream is toasted... OR My experience with the "blue light"

Recently my phone started acting a little unusual. For instance, composed email weren't being sent out while syncing and a wipe and reflash seemed to fix it at first. This problem continued to get worse and at the same time, I started getting SD card ejected notifications seemingly without reason. Now it's to the point that my phone is completely unusable/useless. IF it boots all the way up, it will lock and then just go black. I have to remove the battery for some time to get it to turn on again. This includes loading the SPL and the Recovery interface. The ONLY way my fone will act semi-normal is if I remove the SIM card and boot it. Then eventually it will again just shut-off. I have reverted back to an older SPL with no luck (was using Haykuro's latest one until now). I have loaded multiple radio's with no luck (after reverting the SPL of course). I have tried multiple ROM builds, JF's, Cyanogens and Haykuro with no luck. This really sux. 4 month old fone and seems the radio might be fried. VERY disappointed in the quality. I hope I can get some help and warranty the phone. I am thankful I unlocked my old Blackjack and am able to use it for now. Just though I would share my tale of woe. I am not sure exactly what caused this. Maybe too much flashing? Not sure, but be aware; I feel like maybe I played too much with my phone. That last part REALLY sux cause I love my fone. I LOVE that I can play with it and install all of the great ROMs and themes. Anyway, best of luck to all you Dream owners. I hope I dont have to buy another one (cant afford it )
My fone is not bricked it just seems unstable in every way. Sad day 4 me
[UPDATE]
Before I made this post, I turned on the blue LED (holding trackball and power) and just let my phone sit there. Didn't really have a good reason to do so other than 'why not?'. Anyway, shortly after making this post, I couldn't just leave it alone so I picked up my phone again (I really do love it that much lol). While holding it and just thinking about my less and desirable situation, I noticed the back of the fone was warm like it is when you've been using it for some time. I couldn't help but think that the blue light was indicating that "something" was going on in the background so I just began pushing the buttons on the front and no specific way just randomly and all the sudden my fone rebooted. Sorry I can't say how long it was in "blue light" mode.
Now everything I had experienced and read concerning the "blue light" indicated the only way to get it out of this mode is to 1) remove the battery or 2) let the battery just die on its own. So you can imagine my surprise when the fone just rebooted. It booted up (no SIM inserted) and seem to be fine, but as I mentioned before, this had happened only to lock up and reboot itself. I just began using it as much as I could to see if it would fail again and it seemed to keep going fine so I thought "why not insert the sim again?" So...
With SIM inserted, the fone booted up fine. Again I began to put it through its paces and everything is good so far. Makes call (too late to have someone test call me), browses, downloads market, basically everything with no lockups and no reboots leaving all keys unresponsive. Damn I was happy! But not too much just yet. I'll let it keep going for sometime to make sure it's good, but I can't help but to think that putting my fone into "blue light" mode somehow "fixed" my fone fo lack of a better word. I am perplexed but pleased. Will update later after some decent testing time has gone by. I remain hopeful and regret my earlier comments regarding the fone's quality. I hope I remain regretful of this lol.
Interesting. Can you tell what EXACTLY was on the SDCARD when this happened?
lbcoder:
When this problem first happened on my phone I had folders containing my AppManager backups, ringtones, NES ROMS, camera pix and video files. It's the SD card I always have in there. I don't use apps2sd. I thought maybe there some problem with this card so I tried 2 other SDs I have with the same results; instability. I even tried a clean build with no SD card (as well as with and without SIM); all with the same results. I tried every possibly combination as a form of troubleshooting.
When I put it into blue light mode, the SD card that was installed contained DCIM (pix), appmanager, mp3s, video files, 2 different radios in .zip form (radio 1.22 and the sappire radio; neither with the name update.zip), .footprints folder, ime folder and that's about it. Did u have something in mind?
BTW, I wish I could edit the name of my thread to show there's an update...
The Blue LED has some other purpose and is simply not a "lock". That just seems silly and useless, especially since you'll find if you put it into this 'mode' it will drain your battery fairly quickly for a 'lock' mode (like 12 hours).
There's more than a 'lock' going on here...
I agree. It's doing something in the background other than just being a type of "lock". I'm don't want to claim that it fixed my phone because I have no idea what it's doing when that little blue lights is on. I am saying that it seems a little more than coincidental that my fubared fone (my feeling at the time) began to "magically" work after putting it into this mode and its subsequent reboot. I am really glad I did.
No amount of: fastboot erase "partition name", data wipes, radio/spl/rom flashing helped my fone. I was going to try and get warranty today, but now I don't need to. Back running ION and happy as h3ll! Maybe this will help someone else with a fone that refuses to function correct. Maybe it won't, but I definitely wanted to share my experience with it.
BTW, I was running Cyanogens 3.4 JF mod at the time this began. I understand some other people have had some similar issues as seen here:
http://forum.xda-developers.com/showthread.php?t=525306
These problems are very similar to what I was having, but mine seem irrecoverable even after flashing EVERYTHING. Just food for thought...
I wonder if it found one of those radios and did something with it?
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
hamshu said:
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
This is why I stay on Google Ion. It's clean, stable and fast. All these "optimized" builds seem plauged by bugs and quirks.
lbcoder said:
I wonder if it found one of those radios and did something with it?
Click to expand...
Click to collapse
Interesting thought. But it would have to have parsed the file and made a determination on its own as to whether or not it was a valid radio. Neither were named update.zip at the time. Also, I had already downgraded the radio to one of the versions that existed in file name radio_1.22.zip that was on the SD. That allowed me to downgrade the SPL without bricking because at the time I was running Haykuro's newest SPL (which I have since reflashed to my now functioning fone).
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
Actually I described pretty much the problem quoted below that is in the thread that I referenced earlier:
tearsphere said:
Can someone please help me..
I installed Cyanogen 3.4 when it got released a few days ago and it was running smoothly.. I think he is a genious. Just today my phone shut off on its own and I had to take the battery out and put it back in to get it to come back on.
Click to expand...
Click to collapse
So I guess it could be open to interpretation. I think Cyanogen does amazing work. I have great respect for him and all his efforts that have given us more functionality with our Dream fones. As I said, it's food for thought. I'm not drawing any conclusions as they would be based on conjecture.
I am intrigued by the blue light mode. I really wish we knew exactly what purpose it serves.

Blank/Non responsive screen.. bottom keys work

Anyone having a issue with the screen not coming back on and staying blank? I get this happening from time to time and the only way to fix it is to do a battery pull or do volume up + camera + power button to reboot. When it happens I can hit the power button to wake up the screen but it stays blank and just the keys on the bottom light up and respond to be touched but don't do anything.
Rooted with stock EB13, it did this on rooted DI18 also.
I've done a lot of reading on the Epic forums (General and Development) and I haven't heard of this issue before. What method did you use to update to EB13? If you didn't already do it, you might want to consider a full wipe/reflash of EB13 using Odin/Heimdall/Samsung installer. I'm not guaranteeing anything, but to me it sounds kinda like you have a bad upgrade/flash.
If wiping your caches and doing a full reflash doesn't fix it then it's probably a hardware issue.
DISCLAIMER: I'm nowhere near as experienced as some of these dudes on XDA. If anyone else thinks I'm wrong, please say so and explain why so that I don't give any more bad info! However, I try not to talk out of my ass, so I feel fairly confident in what I've said.
AmericanJedi001 said:
I've done a lot of reading on the Epic forums (General and Development) and I haven't heard of this issue before. What method did you use to update to EB13? If you didn't already do it, you might want to consider a full wipe/reflash of EB13 using Odin/Heimdall/Samsung installer. I'm not guaranteeing anything, but to me it sounds kinda like you have a bad upgrade/flash.
If wiping your caches and doing a full reflash doesn't fix it then it's probably a hardware issue.
DISCLAIMER: I'm nowhere near as experienced as some of these dudes on XDA. If anyone else thinks I'm wrong, please say so and explain why so that I don't give any more bad info! However, I try not to talk out of my ass, so I feel fairly confident in what I've said.
Click to expand...
Click to collapse
I used the Samsung installer.
Same thing has happened to me thrice today (since the upgrade last night, which came from ODINed DI18 usind update.zip).
And that's with no apps installed/running.
I've had this coming up couple times a week on DK28 ROMs, sometimes it's able to recover (like some sort of soft-reboot), most times I need to pull the battery.
I need to replace my Epic badly.. if the replacement behaves the same way, it will join a pile of junk WM6 phones in my basement.
No one else has had this?
Yes. It happened to me twice earlier today. Disturbing. I can't think of anything specific when it happened...once on Dolphin and once after using the camera i think. Have used those a lot since, and it hasn't happened again.
Stock, not rooted. I manually updated via placing the install.zip file on my SD card.
I can confirm this behavior.
Sent from my SPH-D700 using XDA App

[Q] Soundhound says mic locked?

Ok so this problem seems to be multi-connected now that I think about it. But here we go.
BTW I'm running Royal Ginger 1.5, I was running CM7 up to RC4 and two nightly's after RC4 before I switched. This problem was prevalent for most of those ROMS if not all. Fastboot wiped as we as fixed permissions PRIOR to asking this.
Anyhow it started off that when trying to use the Voice text in HTC_IME_MOD, I would get an error saying "There is a problem with the audio" also flashing the Genius Button zip when I opened the app it would show the blue screen for a few seconds then just close (no error, no FC, just close up right away.)
I thought these were 2 separate problems until last night. I went to use Soundhound for the first time in a while and was greeted with this, "Soundhound is unable to detect a working microphone. Another app may have locked the microphone. Please try restarting the phone." Restarting the phone does not fix this problem, thought pulling the battery for over 2 minutes does (for a very very short amount of time, and for everything the keyboard, Genius Button, and Soundhound.)
I have scoured the settings trying to find something about the microphone and I always come up with nothing so I really don't know what else to do. Also before anyone asks I've COMPLETELY cleaned everything, even tried the fast boot method. And also Royal Ginger self flashes/wipes everything as well so not only did I do it but Royal did it again right after.
And I'm not sure if this is related or not though I think it is (thought it was DSP Manager but I removed that app and still have issues) but when I plug a head phone jack into my phone then into my stereo to play music the phone STILL pays on speaker, just very very quietly. The only way to fix this problem is a reboot. The fact that this has fallowed me form CM7 to Royal Ginger and seems to happen when this mic issue happens tells me they have to be related.
Ok so this seems to be traced to the Genius button cuz without it installed SoundHound works great. That being said no one else has this issue?? I google searched the hell out of this and only found one post on googles forums from some guy complaining (more like b*tching) about it but no fix.
Soundhound says mic locked
The same problem occurs on the Altek Leo A14 running Android 2.1. http://media.xda-developers.com/images/smilies/confused.gif

Netflix 1.6.0 video issue

The netflix app version 1.6.0 build 443 seems like it's having scaling issues. It'll play fine for a bit but then the lower third of the screen bugs out. I've searched the forums, but haven't found much information about it. Is anyone else experiencing this? If so, have you got a line on what might be going on?
Hello,
I have experiencing the same issue. I called netfilx and they basically washed their hands and they reffered me to ACER (I have an Acer Iconia A500 tablet).
Acer said that this is the first time they heard about this issue and they are going to investigate further but since there are not many eports of it I am not sure what's goin to happen.
My solution at this point was to remove v1.6.0 and reinstall theolder version 1.5.2
Netflix is now working fine.
I found the file n152.apk at filesonic.com
Thanks for the heads up. I'll give 1.5.2 a try. I've already tried the patched version (from before netflix was available on the market) but I was prompted to update the app and prevented from signing in.
Incidentally, though I haven't watched much since doing it, I changed the video quality in my netflix account settings to "better" and haven't had the screen issue yet (I also wiped the app data afterward).
I had already wiped many times before trying to fix the issue, and the video quality change was to limit data use.
I've noticed this as well. I've seen reports of this happening on Transformers, Xooms and the Sony Tablet S in the Market app reviews. This is probably an issue with Honeycomb tablets in general. One thing I've noticed is that if I flip the rotation lock switch or adjust the volume, the video returns to normal (just a tip so you don't have to restart the video or anything).
I have that issue too...
Yup. Me too.
It will be going along fine, a scene will change and either:
1) seems like I only see 3/4 of the picture with the rest off screen
2) bottom third de rezzes / turns into scan lines and mush
..and a pause will reset it back to normal.
I too will try a previous version...We'll see what happens!
I've been having this issue since they released the update to 1.6.0 as well.
This morning I put in a call to Netflix to address this issue and another on WP7, the lady on the phone said she would report everything to R&D, and sounded rather happy that someone was reporting issues.
Hopefully all it takes is a few keystrokes and we will all have yet another update!
wokker666 said:
I've been having this issue since they released the update to 1.6.0 as well.
This morning I put in a call to Netflix to address this issue and another on WP7, the lady on the phone said she would report everything to R&D, and sounded rather happy that someone was reporting issues.
Hopefully all it takes is a few keystrokes and we will all have yet another update!
Click to expand...
Click to collapse
That's great, wokker. I did the same a few days back; maybe we'll get a fix soon. The issue happened on my brother's stock a500 as well as on my rooted and OC'd a500, so it does seem to be something that could be addressed on their end. I haven't reverted yet (no time since school is back in), but has anyone else had luck with v1.5.2?
possible fix that worked for me.
I had the same issue, thought it might be when the screen tries to time out so I set the Screen Time out to never and it seems to have stopped the problem.

[Q] So i got TF101 Refurb from Newegg..

(Item: N82E16834230172)
.. & I'm just not sure if i should return it or if these issues are pretty much whats expected.
I have not upgraded to ICS from HC
Problems so far:
1. Re-booted twice on first day i had it. I'd been using it all day (installing/using apps etc) - I used it all day 2 days after that w/out issue.
2. Re-booted last night? Not sure exactly but there were no apps suspended in the bg from the night before (~8 hours before) - i had quite a few in the bg
3. 2 out of 3 times so far if i "shut down" *the power button will not power it back on* - i have to plug it into the wall/power for it to turn back on
They aren't the worst issues..yet? I don't know.. I'm pretty happy with HC at the moment & will probly avoid ICS upgrade for a bit.
Stick with it?
#3 is not supposed to happen.
#1 and #2, it depends on exactly which version of the Honeycomb firmwares you are running. Honeycomb 3.2.1 didn't do those for me, but the versions pre-3.2.1 had occasional incidents.
It's 3.2.1
We can assume that you know that you have to hold the button down for three seconds to power it on when it's completely off. Therefore, I would see about swapping it because #3 sounds like a major problem.
ssl123 said:
We can assume that you know that you have to hold the button down for three seconds to power it on when it's completely off. Therefore, I would see about swapping it because #3 sounds like a major problem.
Click to expand...
Click to collapse
Yeah i just shut it down again and it would not come on until plugging into the wall. Problem seems pretty consistent. Ugh i really don't want to have to go through this.
QUESTION: how can i pretty much wipe this device of the apps/personal info i've entered into it before sending it back?
QUESTION: Try ICS then if i'm gonna ship it back anyways?
To wipe the device, you run "Factory Reset Data" in the Settings.
Sure, might as well try out ICS if you're curious.
Sometimes when mine gets a random reboot/shutdown I have to hold the power button down for about 10 seconds to turn it on. Try this if you haven't already.
yeah the power button issue may be it not being totally shut off, so when you hold power you are shutting it down instead of starting it. happened to me a few times so figured it was worth a mention.
Thanks for the suggestions guys. Although it's a bit inconsistent on whether or not i have to hold it down for 3 seconds or 10+ one way or another (after a struggle) it does appear to consistently come up. Emphasis on struggle though.
Have you tried any custom roms yet? I personally seem to have a more stable tablet when using a custom rom due to the various tweaks and fixes.
Just install ICS - such a relief from Honeycomb!
No_u said:
Just install ICS - such a relief from Honeycomb!
Click to expand...
Click to collapse
This thing decided to re-boot randomly again. So i decided to upgrade to ICS (4.0.3) - nearing last ditch efforts.
Problems came up right away:
1. Browser having strange connectivity issues? I have Wifi Analyzer and watching the scrolling graph i don't see any dropping or problems with the connection itself. So i'm not sure what the situation is but sometimes it just doesn't want to load pages - I can't fully say if Dolphin has the same problems or not.
2. Screen tearing. Fairly frequently there's a diagonal tear occurring across the screen, when switching around in/out of apps.
3. The shutdown issue. This problem is at best the same, if not worse. So in hopes of shrugging off the other issues i did a "shut down" and i seriously battled with the power button and never got it to come back up w/out plugging into into the wall.
- What's interesting is how it always comes up RIGHT AWAY once it's plugged into the wall. I tried and tried and tried again with holding the power button 3-10-20-30+ seconds random intervals nothing worked. Hard to express the amount of times & different timings i tried.
So i'm gonna give it a whirl like this for a while and see.. i might end up doing a factory reset .. if problems persist after that it's going back to newegg
Edit: i just tried to play a youtube video and it stopped trying to cache 1/4th through it.. then i pulled up Aljazeea live and it's echoing/choking/stalling .. these problems didn't exist prior. Also, i noticed another streaming (scanner radio) app not doing so well earlier too... heh
bgl said:
This thing decided to re-boot randomly again. So i decided to upgrade to ICS (4.0.3) - nearing last ditch efforts.
Problems came up right away:
1. Browser having strange connectivity issues? I have Wifi Analyzer and watching the scrolling graph i don't see any dropping or problems with the connection itself. So i'm not sure what the situation is but sometimes it just doesn't want to load pages - I can't fully say if Dolphin has the same problems or not.
2. Screen tearing. Fairly frequently there's a diagonal tear occurring across the screen, when switching around in/out of apps.
3. The shutdown issue. This problem is at best the same, if not worse. So in hopes of shrugging off the other issues i did a "shut down" and i seriously battled with the power button and never got it to come back up w/out plugging into into the wall.
- What's interesting is how it always comes up RIGHT AWAY once it's plugged into the wall. I tried and tried and tried again with holding the power button 3-10-20-30+ seconds random intervals nothing worked. Hard to express the amount of times & different timings i tried.
So i'm gonna give it a whirl like this for a while and see.. i might end up doing a factory reset .. if problems persist after that it's going back to newegg
Edit: i just tried to play a youtube video and it stopped trying to cache 1/4th through it.. then i pulled up Aljazeea live and it's echoing/choking/stalling .. these problems didn't exist prior. Also, i noticed another streaming (scanner radio) app not doing so well earlier too... heh
Click to expand...
Click to collapse
Do a factory reset already and test it without installing any apps. You need to find out whether the problem is with hardware or software.
There's a good chance that it's a hardware problem since you got it refurbished. Maybe it was broken already and Asus didn't completely fix it.
Do yourself a favor. Root it and install the latest CM9 build. I was having all kinds of reboot and sleep issues with the stock ROM, mainly the ICS one but a few issues with HC as well. CM9 has been rock solid for me so far.
Headcase_Fargone said:
Do yourself a favor. Root it and install a custom rom. I was having all kinds of reboot and sleep issues with the stock ROM, mainly the ICS one but a few issues with HC as well. CM9 has been rock solid for me so far.
Click to expand...
Click to collapse
Fixed it for you
CM9 might not suit him, so instead he should try out several roms until he finds one hes satisfied with
Telling him to install a specific rom is fine, but it doesnt really help him out.
That said, since you brought up "rock solid", Team EOS build 19 has been really rock solid for me. Currently 202h uptime and counting.
Wow i didn't think things could get much worse but they did.
I decided to do a factory reset because generally things hadn't improved. Initially after the reset things were "OK" ("better" @ 1st but short lived)
Then a while later..
It appears the connectivity of the wireless has completely died. It will connect to wireless fine but is incapable of anything beyond that. No web pages, no connectivity/data transfer in any apps.
I did another factory reset, installed nothing, imported nothing, signed into nothing.. same issue.
Even though i have 2 other netbooks right here w/no issues at all, i tried resetting the AP multiple times. No diff.
Just before the wifi dying it was acting like it was before the reset, where things would randomly fail to stay connected, videos wouldn't fully cache, web pages wouldn't fully load etc. (general connectivity problems that didn't exist in HC, but have in ICS since update)
I think ICS was really the nail in the coffin for this thing.

Categories

Resources