From time to time, my Infuse 4G for various reasons seems to stall on a black screen but this isn't about that phone in particular as others do it too.
When stuck on a black screen or frozen screen image, I can connect via adb get access that way. I can look around, su and reboot it works just fine. I wish I knew what in particular was failing in order to restart it's process and if it were the VM it wouldn't really matter since a reboot would accomplish the same thing. More information from the OS is always better, in my opinion, though.
Point of this thread: When the screen goes black, I am not sure what is actually being displayed or what is doing the displaying, be it an app (if full screen), the whole VM or neither of these. If it is the whole VM or just the black/void background to whatever simple graphics server runs for android, could it be possible to insert simple wallpaper-like error-message images to the root of both the simple non-X graphics server AND to the VM's root so that when nothing is being shown it will be seen?
I don't know for sure, but I imagine if the VM dies it gets restarted immediately. If it gets stuck is another thing...
If this were to work, it wouldn't accomplish much but let the end user of the rooted phone know a little more about what state the phone is in and what needs to be eviscerated from the malfunctioning device. To those more knowledgeable about the Android system setup itself, can this be technically done?
Your thoughts?
Thanks.
Related
Ok, so I have a rooted Vibrant on stock firmware and I've been having a problem with my screen becoming unresponsive. It originally happened on a smaller level when the phone was newer and unrooted, however the problem has gotten much worse. I've done a factory reset of the phone along with a nandroid backup of it before the problem was severe, yet it comes back just as strong.
I already went through the problems with the no wake from setcpu, even thought it was my lock screen becoming unresponsive until I disabled it with NoLock. Also, I have the Logcat live wallpaper, and usually when you tap the screen, you can see the system processing the information, however when the problem occurs there is no response on the logcat live wallpaper. The phone doesn't freeze at all though. All the soft keys still work perfect as do the volume and power buttons.
Any ideas, tips, suggestions that might help me narrow down this problem? Could it be from a bad version of busybox? Autokiller maybe? I have it set to strict(was previously on aggressive) but no change. Maybe Autostarts is causing something to freeze up. Thanks for any help. Seams like these phones have alot of wake up issues.
I would reflash back to stock with Odin and see what happens when you don't have task killer, set CPU, etc. Also, be careful with autostarts
So I removed Autostarts and rebooted, same deal. I did a factory reset and still the same. I just unrooted a few minutes ago and the problem seams to have gone away. I'm gonna leave it like this for a bit without installing any apps and see what happens. Is it possoble I have a bad root.zip file or bad version of busybox? Doesn't make sense to happen when I have root, then go away when I don't. Any reason it could cause this? I'm really close to sending the phone back, but don't want to waste my time if it's just a bad root file or user error.
Well I don't know for a fact, hopefully someone more knowledgeable can chime in. Maybe when you are unrooted, changes made by autostarts no longer have the permissions to affect anything. Personally I would use Odin (have done it twice already) and start from scratch. But then you risk accidentally screwing up the phone if something goes wrong.
I removed Autostarts and rebooted just to make sure the changes took effect though. Even did a factory reset. Those removed all apps that required root access and the problem was still so bad it took me an hour to get the screen responsive again. Once I did get into my phone I booted into recover and unrooted. Restared the phone and now the issue seams to have gone away. Touch screen is very responsive now which leads me to believe it was something that had to do with the root file i'm flashing, or possibly busybox. Very very strange.
Hopefully someone much smarter than me could give some insight as to what could potentially cause the touch screens to just stop recieving signal. It's just bizarre that the phone continues to run fine, just not the screen.
in july i flashed my phone over to energy's most current cookie rom and put the froyo build that danij3l had been working at on my hd2 and it worked beautifully aside from the battery life. i switched to hyperdroid in august or september and it was running even better than dan's build had; i was getting ~100 hours uptime out of each boot, SODs were rare, calls were fine, the phone barely froze. i was in love.
over the last 2? weeks however i've been having a huge amount of problems keeping my phone going. certain websites i access in android make my phone crash; it resets itself but will hardly ever get past the stick together splash screen without a hard reset. when i do get it to boot back into windows i immediately get the "device memory is critically low" message. i lost a TON of my shortcuts in my start menu completely randomly (can't access stuff like file explorer, i have to start a new task in task manager to get to anything) and when i go into settings ->system->memory it says the total amount of storage is 19.09mb and that i have NOTHING available.
keep in mind that's AFTER many a hard reset and device wipes; i can't get my phone to believe that it does in fact have more than that; in the "about" screen it says it has something like 451mb memory available it apparently can't access?
i've been trying to run a task29 to wipe it entirely before putting vbnrom reloaded 2 on it but everytime it gets to the part where it verifies my phone information it says it can't connect, while simultaneously my phone will pop up that stupid annoying low memory message D;<
if anyone has any light they can shed on this it would be really appreciated as i'm absolutely flabbergasted at this.
my radio is 2.12.50 btw
Last night I was reading Twitter before going to bed when I noticed that my GPS kept ticking on and off after I'd posted an update (I let my Twitter app access GPS to assign my location to tweets). Thinking that odd, I rebooted.
Talk about the reboot from hell.
Approximately 30 seconds after booting back up, the phone locked: I could tap buttons and feel haptic feedback, but no changes to the screen occurred. I eventually got the bright idea to lock it and unlock it; pressing the lock key blacked the screen, but pressing it again did not bring the screen back. Scared, I eventually pulled the battery and started up again.
It happened again. And again. In the midst of all this, I slowly learned a few things: it wasn't tied to any of the new apps I'd installed (I had enough "functional time" each boot to uninstall a couple of things), it wasn't tied to internet connectivity or GPS (I had time to turn both off), and the SGS3 has a dev option to monitor CPU usage of various apps/threads. That little HUD, which overlayed everything else, would remain updating through a lockup, and I found that a process named "df" was starting up and immediately sucking up the entire CPU and not letting go.
I eventually found that it worked the processor so hard that the phone would overheat if left alone and "soft reboot" (OS restarts, but no Verizon/Samsung loading screens), so I was able to at least stop pulling the battery!
Finally, I turned it off and let it cool down for a few hours whilst Googling: no results anywhere for a similar problem or regarding the "df" process. Turning the phone back on after its reset didn't help at all. The lockup time was so quick that I couldn't even initiate a factory reset--it would lock up in the midst of preparing to perform it!
I eventually restarted it into the bootloader (meant to go for recovery, oops) to poke around and got a really scary image: a "Custom" screen before the bootloader starts that the devs are saying means that system apps/files have been modified. Now, since I don't have root yet (no hacking/voiding warranty JUST yet), I am not ABLE to modify system apps, which means that something got tweaked all by its lonesome, and THAT isn't supposed to happen. It was probably what was causing the lock, though--some driver somewhere that's supposed to say "Processor, don't try to calculate pi to infinity" got hosed or whatever.
I eventually got into stock recovery and was able to initiate the factory reset from there without the use of the actual OS (thus avoiding the hard lock). The phone rebooted fine, let me sign into Google, and spent the rest of the night redownloading apps. It's fine now.
EXTREMELY worrisome. Possibly a hardware fault with the EMMC chips holding my OS or something--there's not a lot that can knock out system files on a non-rooted device. At least it doesn't appear common, insofar as all my Googling leads to no results at all.
Any ideas as to what the heck happened?
Hi, since updating to Jelly Bean, 2.4.whatever it is now. The latest one as of 04/05/2013, I've had this irritating message pop up every time I connect to, or, DISCONNECT from mobile data 3G network. Alerting me when I connect I could understand if not condone, but when I choose to DISCONNECT? What the hell android? Now as a user of an open source device, naturally I'd expect some sort of option to tick in the pop up saying "never affront me with this stupid and unnecessary bothersome tripe until the day I am a cold and maggot ridden corpse", sadly, no such thing. Every time. Every god-of-reader's-choice damned time.
On my previous S3, I found a work around. Flash a new ROM. Went with Cyanogen mod but lost a load of features I liked, such as calling people from contacts by simply swiping right, and a hell of a lot of other things I just couldn't be bothered to wait for the Cyanogen devs to build in. So I tried flashing back to stock, wrote the phone off. Yes, it was bricked beyond repair, no recovery options, just download mode, forever, and, without USB debugging so I couldn't force root or roms or anything else.
Dead.
I really don't want to have to go through that with my replacement. I have rooted it, which is basically safe, so I was able to kill the other annoying aspect of the S3, the loud alert which sounds just to let you know you've connected or disconnected the charger. AS THOUGH YOU HADN'T NOTICED WHEN YOU DID IT. So, rooted it, found the sound file, deleted. Done.
What I want to do now is, find the pop up... code. Or whatever it is. And delete that too. Or the code that says "display irritating pop up now", or something. It must be stopped. Please, if there is anyone who has found a way around this, which doesn't involve flashing a new ROM, I'd really appreciate it and by the extensive Google search, so will about...4 other people in the world.
TLDR:
Need help disabling the notification which pops up when I connect or disconnect mobile data.
I don't want to flash a new rom.
I am rooted, but wouldn't how to get into the code.
Maybe something which displays an active process tree on my PC while I'm using the phone, I can turn on data connectivity and see what the console displays? Then find and stab the sh*t out of the code...
Ta!
Hi all,
I've got an LG G Vista 2 that I've been trying to turn into an audiobook/podcast/mp3 player after decommissioning it from use as a cellphone about a year ago. However, whenever I boot the phone the screen remains black and a popup appears saying: "Unfortunately System UI has stopped". When tapping "ok" to close the popup the screen remains black and shortly later another popup appears, effectively preventing any interfacing with the device. Even keeping the power down menu open long enough to turn off the phone is a struggle.
It seems like the most common recommendation online is to factory reset the phone through recovery mode - I have tried that several times, each time the popup comes up even before going through the Android setup process. The same popup comes up even in safe mode. I'm at a loss of what to do: I have no way to interface with the phone, through the device still seems to work fine. I'm wondering if this issue is possibly caused by a hardware fault that is manifesting in a software issue, or if the OS install is just incredibly corrupted.
Is there any way to reinstall Android on the phone without being able to access its GUI? Being a lower-end phone from several years ago it is rather hard to find OEM ROMs online, though even if I had a ROM I wouldn't know exactly what to do. I would appreciate any recommendations on where to go from here.
Thanks.
Were you able to solve this issue?
No, unfortunately not. It doesn't seem to be a straightforward fix and I haven't gotten around to really working on it. I'm still open for sugustions if anyone has any tips.