I have HTC HERO smartphone, i have tried many different roms and format my sd card multiple times but every rom has 2 big issues i cant live with.
1) sometimes the screen will randomly flicker while im interacting with the phone, i have tried putting it at lowest and highest brightness and even something with overclock widget but its not doing the trick
2) sometimes i press the screen unlock button, and it does nothing, then i press it twice more and it will show the lock screen.
Is there something i am doing super wrong or is this stuff the roms normally do?
i have tried these roms: villianrom, froydvillian, cyanogen 6.1 RC, RCmix, elelinux 2.2 and fusionrom.
Related
OK, so I successfully installed the ROM. It works fine and all until I actually use openscript on the terminal. For example, I wanted to change CPU frequency. I changed it, quit the terminal, and checked the frequency in system information. It was successful. But After about a minute my screen suddenly locked and here is the current situation. The locking screen works fine (I had the pattern lock), I can even open emergency calls. But when I unlock it, the only thing I see is the notification bar (which works btw, clock, wifi , all the icons are there, I can slide it down and up and so on). Everything else is just black. The buttons work - I can quit the notification tab buy clicking back or home or something like that. But I dont see my home screen, menu, buttons - nothing. I can lock it again, and it works fine again in the lock screen but afterwards same black screen again. Reboot does not work.
So I reinstalled the rom. Immediately after installing changed the frequency and waited for a bit. Everything was fine. I installed all the crap I usually have and kept using the phone. But the next day, I got annoyed by the music player and decided to change it again via the openscript. Same thing happened. And this is where I am stuck right now (actually this is already the third time I have this problem in 3 days and it's my third reinstall of the rom, but the first one also happened after using openscript to change frequency.)
So is there a way to fix this without reinstalling the rom again, cause I've customized the **** out of it and I don't wanna do it again. If no, how can I prevent this in the future?
P.S. If this helps, when rebooting, I hear the sound before the android splash screen which is sometimes skipped and sometimes shown for an unusually short time.
P.P.S. Also, I have the apps2sd flashed.
Any help would be appreciated.
Thanks.
Got same problem
Hi,
Even I got same problem when I tried to change boot animation. Just blank screen.
But i realised it is due to, launcher app is not initiated. So tried a trick which worked indeed
Trick is when u are in a blank screen, click "HOME" button which will pop u up the list of launchers u have. Click One of them though they r not visible
Voilaa!!! Your screen is back
Regards,
Murali
I've been experiencing for some time now some random freezes when trying to face-unlock the phone. When pushing the power button to wake the phone, it displays the unlock screen but the box in the screen where your face (or whatever the front camera catches) blacks out, while the rest of the screen is normal (I can see the clock, the notification bar and the emergency call), also the leds for back and menu light up. And the phone justs stays like that, all the leds lighted up and the screen on. The home button doesn't work and the power button only works if I hold it down (it powers down / restarts the phone).
This has happened to my phone from some time ago, its purely random and it always happens when I try to unlock the phone. I haven't had any issues while using the phone nor strange bootloops or sudden reboots. I'm currently on stock XXEMB5 with Speedmod Kernel k2-13 and some apps removed, mainly yahoo widgets and some Samsung apps (I think I just removed all the hubs: game hub, social hub, etc...).
I red the bad eMMs symptoms, but it doesn't seem to be the same. If I had to guess, I would say its something with the camera, but right now I don't know for sure... Anyone has any idea where could be the problem?
Favourite culprit would be a non-standard kernel, wipe the phone and return to fully stock to test.
Your collection of mods and custom changes to rom are probably unique, if it doesn't freeze when stock then add changes one at a time until it happens again.
It intermittently crashes, and has become a lot more frequent over the last few days.
However when it crashes, the lights of the touchkeys at the bottom still light up with I touch the screen. If there's some kind of animation on the screen, it will keep moving (eg downloading animation). However it doesn't respond to anything I do and I have to restart.
I was running CyanogenMod 10.1, changed to SuperNexus 2.0 to try and resolve issue but it hasn't.
Any ideas?
Thanks, Charlie.
Flash Stock Rom and do Full Wipe Then Try Again
In two different AOKP roms (AOCP, PACman), I have a problem where if I'm on a call and forcefully turn the screen off by pressing the power button (as opposed to by the prox sensor or by timeout), the phone reboots. Interesting, if there's audio on the call, it will continue to play as the shutdown animation is playing.
I have the accessibility setting to end calls with the power button turned OFF. I can't think of any other settings which would affect this.
I tried searching on this symptom, but didn't find anyone with this issue. I clean installed both ROMs, but AOKP seems to be a common denominator. Anyone have advice for me?
Does it ever reboot at other times after you've pressed the power button, or is it only while in a call? I recently had a problem where the phone would reboot after I turned it on. I was on CM and went to SHOStock and it still did the same! I figured, hell, after two different ROMs and it still acting the same, maybe it was hardware. Ended up taking the phone apart and there was some gunk around the inside part of the power button keeping it held in too far and triggering the reboot after a few seconds. After removing the button and carefully cleaning it (it's very small), I now no longer have a reboot problem on either CM or SHOStock.
sbrown23 said:
Does it ever reboot at other times after you've pressed the power button, or is it only while in a call? I recently had a problem where the phone would reboot after I turned it on. I was on CM and went to SHOStock and it still did the same! I figured, hell, after two different ROMs and it still acting the same, maybe it was hardware. Ended up taking the phone apart and there was some gunk around the inside part of the power button keeping it held in too far and triggering the reboot after a few seconds. After removing the button and carefully cleaning it (it's very small), I now no longer have a reboot problem on either CM or SHOStock.
Click to expand...
Click to collapse
I've only had it happen so far when turning the screen back on during a call. If I don't force the screen off in the first place, the phone will happily turn the screen on and off due to prox sensor. It will also time out and let me turn it back on without the power button with no issue. Because of this, I don't believe it's a mechanical issue. I didn't have this problem until trying AOKP ROMs, the timing is too coincidental.
Based on what I'm seeing with the boot animation, it isn't a full reboot (I don't see the SGS II logo, for example). I didn't even know that rebooting only the OS was possible.
I assume there are logs I can check to help figure out what's going on, but I don't know where to find them.
I found a string of posts in the Carbon thread: http://forum.xda-developers.com/showthread.php?p=46998058&highlight=just+carbon+reboots#post47133798. Same symptom, but different trigger. I tried, I can rotate the camera just fine. I'm currently running the 10/31 nightly of PACman, guess I'll update past 11/2 later today and see what happens.
11/6 was a bust (lots of FCs after a clean install), so now I'm trying 11/10, 11/4, or 11/5.
Initial results with 11/10 show that the problem is fixed; gonna restore my old ROM, go through the TiBu dance, and see what happens when I finish setting up 11/10 completely. Maybe it's something I'm doing.
OK, 11/10 fixed my primary issue. Further, I used to have pretty nasty screen-on lag that I couldn't fix even after messing with the CPU and I/O profiles. Hurray!
Based on my experience this may affect other AOKP based ROMs (like Carbon or AOCP), but it might have been present in pure CM (CyanogenMod) - hard to tell. Hope this helps someone else.
****, it's back. Must be something I'm doing. The quest continues...
Hello, I have an i605 and have been using CM12 since it has been released and really like it as a daily driver. I have tried many different ROM's all using CM12 as a base and all, without question have had this same issue.
At least once a day (time of day varies) I will pick up my phone and turn on the screen (which button I use makes no difference) and it will be black, I see that the backlight is on but the screen is black. The home button does nothing, swiping left or right does nothing, the status bar shows up just fine, I can swipe down and see notifications and access the quick launch but if I try to access anything, it just returns me to a black screen. The only way I can get out of it is to reboot.
I am currently running the June 16 nightly with the kernel that is bundled with it. I did try a difference kernel before (I cannot think of the name right now) but the problem remained.
I have tried googling this issue to no avail and I haven't seen anything here on the forums.
Any help would be greatly appreciated.
Can you access to the recovery mod ?