[Q] screen goes black after app launch - Verizon Samsung Galaxy S III

My phone learned a new trick last week: launch an app, and the screen turns dead black after the app's splash loading screen.
It doesn't happen with every app or every time certain apps are launched, but if it is going to happen, it is always just after an app loading screen and before the app itself would be displayed. It never happens on a system or preference screen, or in an app without a splash animation.
Button back-lighting, volume control, and haptic seem to remain active and respond as normal, but the app seems to be locked into the foreground with a black screen, and can't seem to do anything to stop it but reboot the phone via power button hold.
I'm running CM 12.1 nightlies on a Verizon S3. I've been updating the CM nightlies, well, nightly since last week in hopes a fix would be included in one of them, but I'm not sure this is a ROM issue. I've also wiped Dalvik/Cache several times, with and without a ROM update. I saw black screens on some phones were caused by theme window animations, so I've disabled these in CM, but hasn't made a difference.

Just a guess on my part, but if the nightlies do not fix this you may end up needing to do a clean flash. Hopefully you do not have to go as far as formatting /system.

dawgdoc said:
Just a guess on my part, but if the nightlies do not fix this you may end up needing to do a clean flash. Hopefully you do not have to go as far as formatting /system.
Click to expand...
Click to collapse
Thanks, but wouldn't a "clean flash" require wiping `system`?
I'm wondering whether this is possibly a hardware problem too: this phone's been pretty beaten up, not sure how to determine that though.

deesto-xda said:
Thanks, but wouldn't a "clean flash" require wiping `system`?
I'm wondering whether this is possibly a hardware problem too: this phone's been pretty beaten up, not sure how to determine that though.
Click to expand...
Click to collapse
I'd wipe everything, including system and your internal SD card, then you'll know for sure if it's hardware related or not.

deesto-xda said:
Thanks, but wouldn't a "clean flash" require wiping `system`?
I'm wondering whether this is possibly a hardware problem too: this phone's been pretty beaten up, not sure how to determine that though.
Click to expand...
Click to collapse
Yeah, I was thinking internal sdcard, like @BadUsername said.

Related

Trouble with Touch screen, multi touch

I have cyanogens latest rom installed. I tried all the previous versions as well and I keep
having the same problem.
My Touch screen on my MyTouch3g keeps, for lack of a better description, going to sleep. I can still use the multi touch zoom function in the browser,but I cannot screen flick or get the icons to respond. I can hold the bottom of the screen and turn off and on and sometimes this will repair the problem. It seems to recur randomly. Is there any place to look in the log file to see what is causing this? I'm at a total loss after 6 or so roms and still no go. I tried the stripped down rom labeled TMO-OTA-US-DRC83-Rooted_update and also the expansion pack to no avail. I can't really believe this is hardware related since it's random and fixes with a power cycle most times. I'm just finding it annoying as hell, and I hope someone might be able to point me in the right direction.
I've done the bootloader flash/delete data and re-installed each time.
Latest rom from Cyanogen isCyanogen mod 4.2.4
Kernel version is 2.6.29.6-cm42 (does this matter? I include because I'm not sure)
Thanks
Mike
Maybe this will help
look for a post on how to install cyanogen rom on your MTY3 and dowlaod the rooted rom there.
secondly,
see this thread and the last post from me.
http://forum.xda-developers.com/showthread.php?t=583683
I've done multiple re-installs. The same problem keeps resurfacing within minutes.
I can use the touch screen and then it craps out. Oddly it will many times still allow pinch and zoom multi-touch in the browser. But single touch, such as in typing web addresses etc. , does not work.
Does anyone have an idea as to why this might be happening? Is there a particular file that is escaping the wipe/ reboot and reload process that is still not being replaced.
I'm curious if the Kernel has anything to do with this.
Any ideas?
Mike.
try redownloading the rom and the htc image like redownloading from the source wipe the ext erior partition as well pretty much completely restart the process except keep root lol... if that doesnt work then you need to unroot and reroot the bad boy all a learning experiance
Wipe the exterior partition? Doesn't this occur when I do a wipe/data? I have never partitioned the sd card. It has been the same since I received it. Will this affect the screen behavior?
Thanks for the input
Mike
oh well I figured you would be running apps2sd which requires a exterior partition or ext2/3/4 as some may call it... most roms require a wipe of that as some storage will transfer to there and cause problems ona seperate rom for some but if yours is a fresh sdcard then the only thing I can suggest is get a redownload of the cyan rom

Display / menus freezing and / or disappearing, system apps force closing

I've been searching this form for an hour or two now and still haven't found my issue, so here goes.
Just got an HTC Inspire 4G off of ebay and it arrived today.
The seller had mentioned that the phone was freezing / rebooting, but I figured.. that's because he's not running cm7, right?
Charged and booted up the phone and it turns out that the problem was a little worse than I first expected. I only experienced occasional freezing, and it only rebooted once, but there is a worse problem.
The phone loaded up fine, looked good, but tapping around on the home screen I got messages alerting me that system apps (htc sense, launcher, and even com.android.phone) had stopped responding or had shut down.
I hit the menu and go to settings. I scroll down the list and the entire list goes black. I hit home and it goes to a home screen, but with no launcher or icons. Basically, every few taps, the interface goes out. If you are on a menu it blacks out, if you are at home or press home after the menu blacks out you will get anywhere from pieces of icons / widgets to just a blank desktop. The live wallpaper even keeps going, but all of the interactive stuff quits. The disappearing menus didn't usually give app closed messages, they just went black. The home screen only gave app closed messages sometimes.
I thought this was a software problem, so I managed to root the phone and flash cm7. Everything booted good, but it still had the same problem of weird disappearing menus and home interfaces. I went ahead and flashed gapps and got the little intro thing about setting up my Inspire 4g that starts when you first boot your phone. I clicked through that but when it gets to connect wifi, the phone entirely freezes and I have to pull the battery.
I flashed inspiremod and nothing changed, tho that's for something else, so I'm not sure that's entirely relevant, but I was trying everything I could think of.
I'm definitely no expert on hardware, but it almost sounds like a ram problem, like it doesn't have enough to keep all of the interface going all the time and shuts it down or shuts parts of it down to work.. but I don't want to believe that. I'm really hoping that it's a software problem.
I got the phone at a good price and it came with an otterbox, so I won't be too disappointed if I can't get it fully functional, but it would still be a bummer.
Any help / advice / suggestions appreciated. Thanks, guys!
EDIT: I cleared the cache / dalvik cache before flashing / reflashing cm7, which I did once or twice
EDIT 2: Now if I leave it on the intro screen where it freezes it reboots after a minute or so. Gonna try flashing a different mod.. see if that helps.
That was a long post. But it was good, you gave a lot of info.
The cm7 zip that you downloaded, check the md5 checksum, make sureit matches whatever is in the op (first page) or wherever the md5 is, maybe where you downloaded it from. If it doesn't, download again.
Then,
from recovery,
Wipe data/factory reset.
Wipe dalvik
Format all partitions(except sd card)
Flash zip/rom.
Check if it works. If not, try using it without the sd card. If not, come back and report.
Sent from a dream.
Thanks for the reply and suggestions.
I check the md5, and it's good. I just did a factory reset and wiped cache and dalvik.. I'm unsure what you mean by format all partitions except sd card. I don't think I know how to do this with clockworkmod.
Started up without sd card and it still has the same problem. Looks great until I touch the screen, then everything disappears except the wallpaper.
Reboot in recovery and do it from there. You'll find format all partitions at the bottom... well, maybe. Cwm has an option to reboot in recovery, and I think if you press and hold the power button, select reboot and it will also ask you if you wantto boot into recovery. Cant remember if cm7 has it, it should.
After you wiped those, flash the rom. Stay in recovery and search for fix.permissions. Reboot.
Sent from a dream.
Just did that and re-flashed cm7, but the phone was still having the same problems.
I then repeated the process with a MIUI ICS rom and it seemingly worked for a little bit. I got a "Maps has stopped working" message, but I was able to slide back and forth through the home screens, and the menu came up. After I tapped though the menu a bit it started being weird again, but with MIUI the weirdness is different. It looked like the screen was divided up into 20 something smaller screens tiled across the display with messed up looking bits of screen in them.. weird..
If you are wiping correctly then I am out of ideas. I would say try a GB rom, however that is a strange issue and just might be a hardware problem. Tough, Im not sure.
Sent from a dream.
I've tried cm7, which is 2.3, and I've tried a 4.0.4 MIUI build and one other sense rom that didn't work well at all.
I'm wiping and flashing the same as I did on my LG p509, which works beautifully with cm7.
If it is hardware, hopefully it's something simple like the battery, and not bad RAM or anything serious..
Maybe if I keep at it I'll get it.
Thanks for all the suggestions!
Np. Keep us updated.
Sent from a dream.
I ordered a new battery for it, and that fixed the random reboots, which had been occurring more frequently, but the other problems were still there.
I flashed and re flashed and formatted and reinstalled a bunch, but still no luck. I then decided that I might take it by the local cell phone repair shop and see if they could fix it.
In preparation, I used aahk to flash the stock ruu with everything how it was when I got it. After booting it up, it seemed to be working ok.
I still get the occasional menu glitch, but it's so infrequent it's not an issue.
The phone still freezes up quite a bit when I'm using it, but it's nearly a useable device now!
awkwardcheesecake said:
I ordered a new battery for it, and that fixed the random reboots, which had been occurring more frequently, but the other problems were still there.
I flashed and re flashed and formatted and reinstalled a bunch, but still no luck. I then decided that I might take it by the local cell phone repair shop and see if they could fix it.
In preparation, I used aahk to flash the stock ruu with everything how it was when I got it. After booting it up, it seemed to be working ok.
I still get the occasional menu glitch, but it's so infrequent it's not an issue.
The phone still freezes up quite a bit when I'm using it, but it's nearly a useable device now!
Click to expand...
Click to collapse
Have you tried changing out the sd card? Having a bad sd card can cause all inds of odd issues
I booted it without an sd card before and couldn't tell the difference, but it had a lot more issues than just freezing then.
I haven't tried it since those other issues have stopped. I'll try that when I get home from work.

Anyone else with problems like this?

Recently put ViperXL on and took updates now its ViperXL 3.2.5, put kernel 3.4.10-ElementalX v5.0 vanilla on, flashed radio 2.41.,S-OFF.. Now the screen at times becomes unresponsive like when deleting apps,touch the app , it opens but it wont move or delete.IF I reboot, the screen behaves like it should for an unknown period then problem starts to repeat itself untill rebooting again. Another issue I noticed lately before flashing Viper is in TWRP , especially when rebooting, tapping the reboot button it wont respond for a short period,I might have to tap several times to get reboot to happen. I am wondering if I put too much on the system or might it be something internal?
leesumm said:
Recently put ViperXL on and took updates now its ViperXL 3.2.5, put kernel 3.4.10-ElementalX v5.0 vanilla on, flashed radio 2.41.,S-OFF.. Now the screen at times becomes unresponsive like when deleting apps,touch the app , it opens but it wont move or delete.IF I reboot, the screen behaves like it should for an unknown period then problem starts to repeat itself untill rebooting again. Another issue I noticed lately before flashing Viper is in TWRP , especially when rebooting, tapping the reboot button it wont respond for a short period,I might have to tap several times to get reboot to happen. I am wondering if I put too much on the system or might it be something internal?
Click to expand...
Click to collapse
delay with twrp reboot is normal. issues with custom kernels are pretty common as you are pushing your phone beyond spec and making the phone do things it wasn't really designed to do. imo the screen freezing is due to s2w but i could be wrong. i think you can turn s2w off in elemental, try turning it off and see if you still get freezing.
could be.
DvineLord said:
delay with twrp reboot is normal. issues with custom kernels are pretty common as you are pushing your phone beyond spec and making the phone do things it wasn't really designed to do. imo the screen freezing is due to s2w but i could be wrong. i think you can turn s2w off in elemental, try turning it off and see if you still get freezing.
Click to expand...
Click to collapse
This could be the trick. I tried this morning and so far today there hasn't been a hangup on apps. I tried a couple and everything as usual. But this has been a intermittent thing not knowing when or how it would happen.
Yeah I have found some of the Venom tweaks really affecting responsiveness. For example if you could figure power long press to turn on the flashlight it takes NOTABLY longer to wake the phone. I can see s2w having the same effect
Here I thought I was the only one experiencing this issue. I did a full wipe and format and flashed a bone stock (default configuration) flash of ViperXL to see if that would solve the issue. Screen issue doesn't occur as often as before bit it still happens. I found that if I block the light sensor, the screen begins to behave normally. I don't have a logcat yet but can upload if necessary.
Sent from my HTC One X using xda app-developers app
same problem again.
leesumm said:
This could be the trick. I tried this morning and so far today there hasn't been a hangup on apps. I tried a couple and everything as usual. But this has been a intermittent thing not knowing when or how it would happen.
Click to expand...
Click to collapse
I thought wrong , again, tried this morning just moving an app from home screen to second screen. It will open but unable to move it or delete it from the screen. Rebooted and seems everything is normal again.
Are you using 4x5 Rosie?
Sent from my VENOMized HoxL
area51avenger said:
Are you using 4x5 Rosie?
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
Not really sure, I can't find anything that 4x5 is enabled. S2W I disabled also, this is not a big problem just irritating some times. Things usually start working normal when I reboot system .
You could try increasing the voltage.
ken bentley said:
You could try increasing the voltage.
Click to expand...
Click to collapse
At this point I am not sure I am that smart to be messing with volotage and such on the inside of this thing.
just stopped using a custom kernel. i stopped using them cause of freezing issues.

Help needed; random black screens

For the past few days, my phone has been acting up pretty badly. On the rare occasions that it finishes booting (usually gets to the CM boot animation and stays there), it will then only work for a short time before either I press the lock button to wake the device, but the screen stays black, or occasionally the screen will go black while I'm actually using the phone. The only way I have managed to get the phone working again is pulling the battery and restarting, and hoping it will boot this time.
It seems to do the black screen thing particularly frequently when text messages are received, but it's not ONLY when they are received.
It started when I flashed the latest kernel posted in the Evervolv thread [here: http://forum.xda-developers.com/showpost.php?p=41359720&postcount=183]. My current rom is CM10 build #6. Once this started happening, I restored a nandroid backup I had made a few weeks ago. At first I only restored the "boot" partition, and when that didn't help I restored the "system" and "boot" partitions. That still didn't work, so I flashed the Garuda kernel v5. That also did no good.
Is my only option re-flashing my ROM? I'm a little reluctant because that would mean losing all my apps etc. and having to restore them. I guess I could try a full nandroid restore first.
But before I go too drastic and potentially lose data, does anyone have any other suggestions as to what may be the cause?
I also have Mounts2SD installed (from Play Store) in case that's relevant.
EDIT: Could I flash the ROM without wiping and thus keep my installed apps and data?
A logcat would help.. In the meantime, install the" app2zip" app from the play store.. It allows you to make flashable zips of installed apps.. Also, try to find "zipme" by jrummy.. That app lets you make a flashables of apps, app data, system data, Bluetooth pairing info, Wi-Fi info, n much more.. And just to have covered all the bases, try reflashing the full rom...
ғг๏๓ ҭђє ғเรђ™
I'm cautious about speaking too soon, but last night I fixed permissions in recovery and it hasn't black screened or rebooted since so I'm hopeful it may be Ok now. Thanks so much for the suggestions though, I'll be sure to look into those options in case something else goes wrong or else if this problem isn't actually fixed.
Edit: oh and I had tried to get a logcat but once it black screened it wouldn't respond to adb

[Q] 5113 Locking up and Strange Behavior

My neighbor's 5113 is having some strange issues I hope I can get some insight on. I've worked with a lot of Samsung phones and am very familiar with flashing, Odin, etc but have not worked with a tablet before.
First, it has 4.2.2 on it. I tried the stock software update function and it says it's up to date. Is that true? Is 4.2.2 the latest official for this device?
Second, It's having lock up issues (see below) so I thought I would "Clear Cache" in stock recovery. It starts going through the process and then errors out. It just flashes ERROR and then goes back to the stock recovery screen. I've never seen that before. Any ideas?
Lastly and most importantly, it locks up regularly. It will lock up with the screen on (although it seems to take longer to lock up with the screen on with some motion.) When the screen goes off it will lock up quickly, normally within 5 minutes and it even locks up when charging up. The charging animation stops and you have to hold the power button for 10 seconds to get it to come back to life. It's very strange. It even seems to freeze when it's off. It won't just start by pushing the power button for a couple of seconds, you have to hold it for 10 seconds until the charging animation pops up and then push the power button for a couple of seconds.
I haven't reset to factory specs because she has a ton of info on the thing and I'm afraid if it errors out clearing cache, what might it do if I try a factory reset?
Thoughts?
Thanks for the help.
UPDATE: I did a factory reset via stock recovery and it did delete all the data. It still will not let me clear cache though. It still locks up whenever the screen goes dark. It will lock up in just a couple of minutes.
Very frustrating.
I would try flashing the stock firmware and see if that clears up the locking problem, after a day or so I would flash CM11 with gapps and take it from there.
After running stock rooted before flashing CM11 do a nandroid b/u just in case it acts up. CM11 IS SUPER stable, have run it on my P5113 for several years starting with cm10.
CM12 is still buggy don't trust it.
Pp.
PanchoPlanet said:
I would try flashing the stock firmware and see if that clears up the locking problem,
Click to expand...
Click to collapse
Thank you very much PanchoPlanet. I factory reset and reloaded stock firmware several times but it would still lock up as soon as it went to sleep. And I still could not wipe cache. Very strange. I went so far as to not set up any accounts and make sure it didn't download any software updates to make sure it wasn't some update that was causing issues.
It would still lock up even when it was off and just supposed to be charging the battery! So I really think it's memory is trashed.
But I would be more than open to listen to any other ideas.
Thanks.
Maybe there could be other issues that you are not aware of, like the tab having been dropped or liquid damage or even voodoo, who knows.
Sometimes people don't disclose all the details.
Pp.
PanchoPlanet said:
Maybe there could be other issues that you are not aware of, like the tab having been dropped or liquid damage or even voodoo, who knows.
Sometimes people don't disclose all the details.
Pp.
Click to expand...
Click to collapse
It looks to be in perfect shape. But in any event, if something like that happened then it's toast anyway.
Yeah, especially the voodoo. Lol.
Pp.

Categories

Resources