Database Users

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

Busted Accelerometer

So, earlier I noticed that my screen wouldn't rotate into landscape (no, I didn't forget to check the correct box under settings )
Anyway, I just hit up LBStestmode, checked Sensor Data and saw:
Orentation:
false
false
false
Accelerometer:
false
false
false
Magnetic Field:
false
false
false
Any idea how to fix it without a full wipe (Nandroid restores do NOT work on my device for whatever reason).
Needless to say, this is a huge PITA.

I don't know if this is the same with the Vibrant, but I had something EXTREMELY similar with an HTC Evo that had been flashed to MetroPCS a while back...
The only way I could get it corrected was to do a full restore with a Sprint Based RUU , which of course re-flashes EVERYTHING back to factory.
A full wipe may not even help in your case - may need to ODIN.

Yea, restore it back to factory is your best bet. Had this problem with my G1 (had to reflash CM at the time to fix it)

Have the same problem! It started 2 days ago. Please help!
Sent from my SGH-T959 using XDA App

Well my problem is the a few games, you could always odin.
Sent from my SGH-T959 using Tapatalk

I just tried a factory reset and that got my screen rotation back. Restoring Data from my Nandroid. Hopefully that works, if not, I'll Odin back to stock. I hate having to do that, but you guys ease the pain letting me know there isn't much else I can do about it. Such a PITA!

I had to restore the vibrant bootloader and then it started working again. This happend to me when I went from Simply Honey to Bi-Winning with the I9000 bootloader. I Odin'd the vibrant bootloader back and everything was good again. Coincidence? Not sure....

Same thing happened when I was running bionix. fixed with master reset
Sent from my GT-I9000 using Tapatalk

Mine was all pieced together anyway. I've tinkered with things endlessly ever since I installed 1.3.1 (which was when it dropped) so it was probably time for a fresh start anyway. I've had a few hiccups with other things (I think either SetCPU or Voodoo Control set to load on Boot) but hopefully I'm about to have those worked out.

Top of screen and capacitive buttons unresponsive!

Hey everyone, I woke up this morning to find a surprise! My Atrix screen was unresponsive. It took me a couple reboots to figure out that the top part of the screen doesn't respond to touch. Worse yet, none of the capacitive buttons work. So if I get into an app, most of the time, there's no real way for me to get out of it, thus requiring a reboot and more careful selections.
The weird part is, it happened within a span of about 2 hours. I woke up around 5:30AM, checked some emails and texts, and woke back up around 7AM with a buggy screen. It did drop from about 18 inches off the couch last night. But everything was in working order...
Right now I'm in the process of backing up my text messages, because I might have to use a set of them to prove my case in court.
What's the first steps to try to get it back working? Or do you think its a hardware problem(maybe a cable loose)? As far as returning it under warranty goes, I'm rooted and unlocked on Kenn's GB ROM, so that's a no-go.

bigb252 said:
Hey everyone, I woke up this morning to find a surprise! My Atrix screen was unresponsive. It took me a couple reboots to figure out that the top part of the screen doesn't respond to touch. Worse yet, none of the capacitive buttons work. So if I get into an app, most of the time, there's no real way for me to get out of it, thus requiring a reboot and more careful selections.
The weird part is, it happened within a span of about 2 hours. I woke up around 5:30AM, checked some emails and texts, and woke back up around 7AM with a buggy screen. It did drop from about 18 inches off the couch last night. But everything was in working order...
Right now I'm in the process of backing up my text messages, because I might have to use a set of them to prove my case in court.
What's the first steps to try to get it back working? Or do you think its a hardware problem(maybe a cable loose)? As far as returning it under warranty goes, I'm rooted and unlocked on Kenn's GB ROM, so that's a no-go.
Click to expand...
Click to collapse
you are unlocked/rooted/custom rom = no warranty
anyways backup and maybe reflash the rom and see how that goes.

Hopefully you don't need to replace the digitizer... But if you do, there are lots of videos and it's reported to be one of the easier phones to do. Keep that in your back pocket as an alternative to a lengthy and costly court fight over a phone with no warranty!
Sent

Thanks guys, I already knew the risks associated with rooting and unlocking. I used an app called SMS Backup+ that allowed me to backup all my sms/mms and it also linked and sent copies to my Gmail.
I'll go ahead and try a reflash
*EDIT*
Did a quick wipe of the phone, and during setup, everything was OK! When blur came back, it was back to the same thing.

Bump...
Still lost

I would suggest backup all you apps and do a complete wipe of data. I had a similar problem when I first installed Alien. This fixed the issue.

bigb252 said:
Thanks guys, I already knew the risks associated with rooting and unlocking. I used an app called SMS Backup+ that allowed me to backup all my sms/mms and it also linked and sent copies to my Gmail.
I'll go ahead and try a reflash
*EDIT*
Did a quick wipe of the phone, and during setup, everything was OK! When blur came back, it was back to the same thing.
Click to expand...
Click to collapse
I would do a wipe and reinstall. You could also fix your permissions through rom manager or cwm.
Sent from my MB860 using XDA Premium App

I had a simillar problem: WIPE through CWM solved this problem

hi, guys i had the same problem... I remember getting it shortly after updating it to the leak version of gingerbread. Since then I have flash Alien built #3 but the problem remains...
I'm currently doing a Nandroid backup of my phone so i could try flashing to cherrypie hopefully this will solve my problem cuz I'm seriously feed up with it...
do you guy's think this will help? if so any suggestions before i flash? thanks in advance...

I had this problem brand new out of the box. I just took it to the store and they gave me a new one. One other thing i noticed was the FP sensor/button was almost like loose and i had to push it in real far for it to work. Maybe its a stuck FP button...
Sent from my MB860 using XDA App

im having the same issue, i cant make the buttons work, i have wiped everything in CWM, and using fastboot also and nothing, also tried flashing different roms but the problem persists, if anyone know how to solve will be great
thanks

I think you have one file corrupted... I'll try to remember which
Sent from my MB860 using XDA App

I think it may be touchpad.cfg. try Googling that and see if you can find a clue.
Sent from my MB860 using XDA App

Try here: http://www.kandroid.org/online-pdk/guide/keymaps_keyboard_input.html#androidKeymapKeyLayoutMapTitle
Sent from my MB860 using XDA App

thnaks for the answear, i flashed the 10 point multitouch patch to see if solved the problem but it didnt, yesterday i reproduced the error but idk how to solve ir, im gonna make a thread to show what i did

Working solution for random boot issues

So this morning I got a call from a friend who told me that his TF is running like crap after doing OTA upgrade to ICS.
We met up at school and I got to take a look at it. Yes, it was indeed running like crap and it even randomly rebooted while we were eating breakfast. He told me the random reboots were happening every 3-5 hours(that he could notice).
Here's what I did to fix it.
Removed his MicroSD card(not sure if necessary)
Shut down TF.
Hold [volume down] and [power] button together until you get into reset mode with 2 icons in the center of screen. Left icon is Wipe Data. Right icon is Cold boot. Right icon is selected by default.
Press [volume down] to highlight the LEFT ICON, which is Wipe Data.
Press [volume up] to confirm your selection
Go through the process.
Let your TF reboot.
Shut down TF again.
Hold [volume down] and [power] button together until you get into reset mode with 2 icons in the center of screen.
You need to do cold boot. It's already selected by default so just wait like 10 seconds and it will happen automatically. Press [volume up] if you don't want to wait.
Go through the process. Your TF will reboot afterwards.
Done.
It has been over 24 hours and his TF has been running smooth without any glitches or any random reboot. I told him to let me know immediately if a random reboot happens again.
This is simple to do. Worth trying unless you can't read English.
Edit: I didn't include this at first because I thought it would be common sense for everyone but it apparently isn't....
DO NOT JUST RESTORE ALL YOUR PREVIOUS APPS AND WIDGETS YOU HAD FROM HONEYCOMB. THAT DEFEATS THE ENTIRE PURPOSE OF DOING A RESET AND PREVENTING APP INCOMPATIBILITY.

thnx man for sharing . I actually tried every thing to solve this issue but no luck , I'll try your as sson as i go home .

This did indeed work for me as well. I tried this a couple days ago and I have yet to have any freezes or random reboots. I think that not restoring any backed up data, apps or settings is key to fixing the problem. I'm now very happy with ICS- burn in hell Honeycomb.

Shameful bump

When you switch from a version like HC. This is what you exactly should do!
I did this and never experienced random reboots.
My Transformer is running since three days and everything works fine!
Edit:
Another quick hint:
If you want to work with Google Docs, you have to disable Forced Hardware Rendering!

I see on forum the problem is google+
So I removed google+... Wait and see...
Sent from my Transformer TF101 using Tapatalk

billouetaudrey said:
I see on forum the problem is google+
So I removed google+... Wait and see...
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
.....lol, why post in this thread that you are not going to follow the advice of the Op?.......

Sorry to say but this is not working, already done this since the minute it was out and still have so now and then a hang boot
(random reboots that hangs on the boot)

Giving it a try
I am experiencing random reboots after ICS
Wiped transformer, cold booted, and installed the following.
Adobe Reader
Dog Catcher
updated G+ and GMail but have not run it.
Charging now, I will let you know.
Previously I had wiped it and reinstalled all, disabled syncing, disabled location info, adjusted wi-fi settings, and added CPU throttle control obviously none worked.

It might have helped some people, but it did not help me. Unless it was dogcatcher.
5 or so minutes after unhooking it from the charger, I tried to wake it. And it was unresponsive. Was only able to wake it by holding down the vol down and power button at the same time.
I will kill off Dogcatcher and try again but it is not looking so good.

JesterOC said:
It might have helped some people, but it did not help me. Unless it was dogcatcher.
5 or so minutes after unhooking it from the charger, I tried to wake it. And it was unresponsive. Was only able to wake it by holding down the vol down and power button at the same time.
I will kill off Dogcatcher and try again but it is not looking so good.
Click to expand...
Click to collapse
why are you installing dogcatcher? And this does work.. do it again. Don't install your apps.enusre it dos not lock up before you install anything.... If it locks up before you install any apps then call Asus. If not start installing one app at a time. Wait after each install. Ensure that its not doing it, once you are sure install Another ....rinse/repeat....

I installed dogcatcher because I needed something to listen to on the way in to work. I have uninstalled it. But I doubt that is the issue.
I have had these sorts of reboots on my Transformer until the third or fourth Honeycomb update. But eventually they fixed it. I suspected this would happen again.
Considering that dogcatcher one of the most popular podcast apps on the market I suspect that there are many people with no problems using it just fine.
But since I need a podcast listener to be able to use the device as I want to, does anyone without issues have a podcast listener that they use?

2 hours into the last experiment and it died again while sleeping.
So that about sums it up. This procedure might help with some issues Transformer's are having but not all.
Recap. Wiped, cold booted, gmail setup, G+ updated still equals failure.

I love how horndroid 'solved' this issue and then goes on the belittle people who are still having it as 'stupid', and probably their own fault. Horndroid, I appreciate your attempt to contribute, but your attitude and stabbing-in-the-dark protocol is not becoming nor helpful to anyone. Definitive statements pertaining to ONE TF101 device that you own are quite naive, there are several different models, and until you have personal access to each model version you should advertise your 'solutions' as "worked for ME", and understand if it doesn't work with others it isn't THEIR fault..this is not a blanket solution for every device's reboot problems. In fact, I am willing to bet the reboots being resolved by this method are of an entirely different genesis than the reboots that I and others are experiencing (hang-boots).

I hear what you are saying I have the reboot issue as well.
I did a reset before and after and only installed xda HD and ran it for 2 days and got 3 reboots so I did the cold boot and then it did it 2 more times that day. Earlier today I almost couldn't get out of the boot loop, so I wouldn't say its a app problem its something wrong with the firmware somewhere
Sent from my SGH-I897 using xda premium

Some aren't too lazy we just don't want to wipe data after every update. I think i have gotten 4? OTA updates and 2 of them screwed up deep sleep while docked. Guess what the first trouble shooting step was...wipe data. Guess what worked...the next OTA. I don't have time to read through all the different threads on the same subject but are people that flashed through cmw instead of ota having the same issue? My buddy went this route and has no issues.
Sent from my SAMSUNG-SGH-I997 using Tapatalk

Can't read horndroid's "advice", because I have him on ignore for trolling, and have done for ages. From the tone of other posts here, it seems the "solution" is to wipe; if that's actually the case, it's total BS.
I wiped immediately before upgrading to ICS, wiped again afterwards, and have put almost no programs back on. I am and always have been on stock firmware and unrooted. I had no problems with boot loops, no problems with lockups, and only extremely rare problems with spontaneous reboots using Honeycomb. With ICS, I have had all three problems in a matter of days, and the lockups / spontaneous reboots are fairly regular (1-2 times per day.)
This is a problem with the stock rom, not a user app problem.

knoxploration said:
Can't read horndroid's "advice", because I have him on ignore for trolling, and have done for ages. From the tone of other posts here, it seems the "solution" is to wipe; if that's actually the case, it's total BS.
I wiped immediately before upgrading to ICS, wiped again afterwards, and have put almost no programs back on. I am and always have been on stock firmware and unrooted. I had no problems with boot loops, no problems with lockups, and only extremely rare problems with spontaneous reboots using Honeycomb. With ICS, I have had all three problems in a matter of days, and the lockups / spontaneous reboots are fairly regular (1-2 times per day.)
This is a problem with the stock rom, not a user app problem.
Click to expand...
Click to collapse
I reported him for verbal abuse and foul language. His attitude is not helpful, and if I were a mod he'd be gone already to think long and hard about his conduct. Anyways, taken your advice and blocked him. It is obviously an issue with the ROM, I'm beginning to think it has something to do with deep sleep, others posited that it may be media scanner, maybe combination of both? Maybe these two events are trying to happen at once and it doesn't like it.. a stab in the dark at least..

luna_c666 said:
I reported him for verbal abuse and foul language. His attitude is not helpful, and if I were a mod he'd be gone already to think long and hard about his conduct. Anyways, taken your advice and blocked him. It is obviously an issue with the ROM, I'm beginning to think it has something to do with deep sleep, others posited that it may be media scanner, maybe combination of both? Maybe these two events are trying to happen at once and it doesn't like it.. a stab in the dark at least..
Click to expand...
Click to collapse
It's hilarious how you think YOUR problem is the only problem that everyone is experiencing.
For a lot of people, it was the app incompatibility that was causing them issues.
Obviously you think your problems are caused by something different, but that doesn't mean there are different problems caused by other reasons.
While all of you are speculating, at least I've posted a solution(even though it's merely doing a data wipe and cold boot, pretty much common sense) that has been proven to work for a lot of people. I've never claimed it will work for everyone; just those having problems due to app incompatibility.

I'm pretty sure this is an issue with the update itself and all these "fixes" are going to be pointless in a little while when an actual fix is released by Asus.

Camera FC: "Warning: Camera Failed"

Anyone else receive a Camera Failed popup as soon as you open the camera app? I get this now and I cannot use the camera at all.
Here is what I have tried:
- Force Stop, Clear Data, Clear Cache, and Clear Defaults
- Clear Cache Partition in Recovery
- Factory Reset through Settings
- Factory Reset through Recovery
- Installed 3rd party camera app
None of these have worked. Anyone have any other suggestions?
Sent from my SM-G900V using Tapatalk

Oh yeah... I took out my SD card as well to make sure that wasn't causing the issue
Sent from my SM-G900V using Tapatalk

I had that happen to one of mine. Did you install, Instagram or snapchat? I contacted Samsung and they had me doo all kinds of things the Las they had me doo was preform a hard key reset which is didn't then a factory reset, so they say, they say it errors everything like brand new no trace of anything, here are steps if you want to try them, it didn't work for me,I am going retrain device fir a new one, but might work for you.
Here are the steps on how to perform Hard Key Reset on your device. 1. Power the device off (remove and re-insert the battery). 2. Press and hold the Volume Up key and the Home key, then press and hold the Power key. 3. When the device vibrates; release only the Power key. 4. When the Android system recovery menu displays; release the Volume Up and the Home key. 5. Navigate with the Volume keys to the wipe data/factory reset option and press the Power key to select. 6. Navigate with the Volume keys to Yes-delete all user data option and press the Power key to select. 7. After user data deletes, press the Power key to reboot system now.

Yeah I tried the factory reset through recovery... it was a no go. So after all this I still haven't gotten the camera to work. What's really strange is after all this testing I thought I'd try another third party camera (pudding camera)... it allows me to use the front camera, but as soon as I switch to rear it goes black then fc's if I hit the shutter button.
I'm thinking I just have a bad camera. I think that i have done everything possible to eliminate the possibility of fault by software.
Luckily I'm still within 15 days to return to best buy.
Sent from my SM-G900V using Tapatalk

I had this happen to my GS5 last week after using it for about 5 days.
- I cleared app cache and data.
- Factory reset with SD card in
- Factory reset with no SD card
- Factory reset without adding my Google account in and went straight to the camera.
All no dice. I took it back to Best Buy mobile and their Samsung Experience Rep Flashed the factory binaries from an image (something similar to Odin) Factory reset. Still camera failed in the camera app and any app that uses the camera. IN fact if you try to open the camera in any other app like messaging etc. etc. it will force close that specific app and cause you to clear cache in said app.
Samsung tech said it was definitely hardware related and promptly gave me a new phone.
There is another thread here in Q&A with others experiencing the same issue. Either a bad batch or something larger is looming.
FWIW. It worked fine for a few days...
-Lil
---------- Post added at 01:53 PM ---------- Previous post was at 01:51 PM ----------
Here is the other thread:
http://forum.xda-developers.com/showthread.php?t=2724354
I am hoping this isnt a larger issue than a few bad 'apples'. Pun intended
-Lil'

I am having the same issue.. Tried all of the solutions mentioned. I had to have Verizon order me a new unit.. Wont ship until 4/24..

I am now real curious how many are experiencing this... maybe time to wake the PR beast in Droid-Life with a little tip if its more than the suspect few. Sounds to me like a larger issue.
-Lil'

Tried to return my release day S5 today because of bad camera at the Verizon, but couldn't the store told me it was the 5th one today they got in for the same reason, so it looks like we have a huge problem on our hands!I have to wait for them to get a shipment of new phones in to get a replacement, they noted my account just incase it goes over the 14 days.

I'm gonna shoot Droid Life a message a d see if we can get some coverage on this issue.
Sent from my SM-G900V using xda app-developers app

Tim got us some coverage... we shall see if Samsung has anything to say on the matter.
http://www.droid-life.com/2014/04/2...erience-camera-failed-issue-no-word-on-a-fix/
Sent from my SM-G900V using xda app-developers app

Flashlight app camera fix
I have this issue on my note 3. I temporary "fixed" it by installing a flash light app and turning it on then off. I wonder if that'll work for the gs5

Yep... same looking issue however nothing that worked on the Note 3 has worked to resolve this.

lilsalmon said:
Tim got us some coverage... we shall see if Samsung has anything to say on the matter.
http://www.droid-life.com/2014/04/2...erience-camera-failed-issue-no-word-on-a-fix/
Sent from my SM-G900V using xda app-developers app
Click to expand...
Click to collapse
Good lookin' out. I just exchanged mine at best buy. The Samsung person hanging around said they had heard of a couple of others that came in recently.
Hopefully this one doesn't have the same issue after a week.

Just curious, anyone having this issue also happen to switch to ART instead of Dalvik?

I had not switched mine.... I was still on Dalvik.

Annnd thankfully I didn't win that Ebay Auction. Will wait until July for new contract and less Headaches. Hope those affected get the phones fixed.

This would be huge IF no software solution. Hopefully it is a bad batch and not an issue with the design and impacts all devices.
I guess I can forget a 32gb Verizon version now. They will not add additional models until they figure this out.

I'm now having this issue on my sprint variant. Have tried everything I can.

Might be nice to track SKUs to see if there is a connection. Just got 2 s5s today. Camera works out of the box on the white one
Sent from my SM-N900V using Tapatalk

12 days. Replaced it with the HTC one m8 today.